[mapguide-internals] Review/Discuss: MapGuide RFC 153 (Geometry Simplification APIs)

Jackie Ng jumpinjackie at gmail.com
Fri Nov 20 02:09:01 PST 2015

In GEOS, failure to simplify is denoted by an empty geometry instance being
returned, which in WKT (since that's what is used to move between MgGeometry
<-> GEOS geometry forms) is being rendered out as 


The MapGuide WKT parser doesn't recognize the EMPTY part so NULL is returned
on empty GEOS geometries. There's existing code in MgGeosUtil that follows
similar logic (return NULL MgGeometry on "<GEOMTYPE> EMPTY" WKT text.

If a simplification operation is a "no-op", GEOS actually returns the same
geometry (same in the sense that its output WKT would be the same as its
input WKT)

So returning NULL should be an acceptable indication of simplification

- Jackie

View this message in context: http://osgeo-org.1560.x6.nabble.com/Review-Discuss-MapGuide-RFC-153-Geometry-Simplification-APIs-tp5237324p5237591.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.

More information about the mapguide-internals mailing list