Hello, I'm eager to find out why CircularString throws an exception instead of just logging a warning when confronted with geometries in 3D (or more). https://github.com/geotools/geotools/blob/master/modules/library/api/src/main/java/org/geotools/geometry/jts/CircularString.java#L90
In 10.2 we didn't get any exception. The geometry was just not handled and returned as null thus not rendering in images and no geometry node in GML-output from GeoServer. Now we do and we have to handle this exception everywhere. No images at all from GeoServer and exception in GML-output if one feature with 3D CircularRing is in the query. If we remove the throwing of exception we get an image and the 3D geometry is returned in its 2D form. This is far more useful to us since it renders in images and gives us something that is almost correct in GML-output. Would it be OK to just log this as a warning instead of throwing an exception? Perhaps some kind of option otherwise? Regards, Olle Markljung
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
