> > A key question is how to expose these operations in the GEOS C API. I > > see two options: > > 1) Model a Polygonal Coverage as an array of simple Polygons (and > > possibly > > MultiPolygons) > > 2) Provide a Polygonal Coverage datatype (which might contain internal > > topology) > > Could a coverage datatype allow performing operations on PostGIS > Topologies w/out building the polygons for each face ? There's an ISO > standard representation of topologies, maybe such representation could be > used to transfer those topologies back and forth with GEOS ? > > --strk; > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel
You read my mind. I'm fine with an additional type in PostGIS. Along the lines with what Dan Baston said, the idea of having a special coverage type that multiple operations can be applied to is very appealing to me. But not sure how much extra overhead or difficulty that would cause for other projects consuming such a new type. Maybe for some it can have a mutator to convert it to a polygon array or something, for projects that can't handle consuming additional types. _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
