On Wed, Jan 20, 2010 at 11:05:40PM +, Mateusz Loskot wrote:
> strk wrote:
> > /usr/src/geos/cmake_build/include/geos/platform.h:147:3: error: #error
> > "Could not find finite or isfinite function or macro!"
> > make[2]: ***
> > [src/CMakeFiles/geos.dir/algorithm/distance/DiscreteHausdorffDi
#320: factory for std::vector
+---
Reporter: 12345678| Owner: geos-devel@lists.osgeo.org
Type: task| Status: new
Priority: major | Milestone:
#320: factory for std::vector
+---
Reporter: 12345678|Owner: geos-devel@lists.osgeo.org
Type: task| Status: new
Priority: major |Milestone:
#321: crash in geos::geom::WKTWriter
+---
Reporter: 12345678| Owner: geos-devel@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone:
JTS/GEOS does not support unioning GeometryCollections. Not sure how
PostGIS is sidestepping this problem - perhaps it just ignores it?
One issue is that just because a GeometryCollection of Polygons is valid
does not mean that the set of Polygons would form a valid MultiPolygon
(they might o
Hmm more smurf code but in PostGIS. I guess its been there for a while since
my PostGIS 1.3.6 exhibits the same behavior. I presume it must be then dumping
out the collection before feeding it to GEOS if GEOS doesn't support this
directly.
Martin -- If all the Polygons are valid though, the
