On Fri, Aug 28, 2015 at 3:27 AM, Olle Markljung wrote:
> It's not alot but it might happen and since everything then breaks the
> impact is quite profound.
> It's an Oracle NG datastore. When making offsets Oracle Spatial might
> create arcs.
>
> Before no one noticed since images from GeoServer
One more thought: We had some kind of FORCE 2D hint that WMS could use to
ask for the data back as 2D (ignoring the 2.5 D for speed).
Perhaps if you can figure out how to get oracle to respect that (with an
SQL function) we can get the curves back from the database as 2D...). I
can find some exam
It's not alot but it might happen and since everything then breaks the
impact is quite profound.
It's an Oracle NG datastore. When making offsets Oracle Spatial might
create arcs.
Before no one noticed since images from GeoServer would be without these
and GML-responses would have no geometry node
Interesting, from my perspective this was a new feature and I did not
expect any regressions. The exception makes a bit of sense, unable to
interpolate the 3D positions.
I am curious what store you are using for your data that has lots of
circular strings. How did it work previously that the geome
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 di
