Re: [jts-dev] WKTReader problem after update

[Martin Davis <mtnclimb@xxxxxxxxx>]

There is a migration guide here:

https://github.com/locationtech/jts/blob/master/MIGRATION.md

But it is mostly focussed on deployment issues, rather than functionality changes.  

The version history which indicates changes and highlights any API-breaking changes: https://github.com/locationtech/jts/blob/master/doc/JTS_Version_History.md

In general migration doesn't seem to present very many issues.

For troubleshooting issues like this you should provide a stack trace at minimum. In this case an example failing case might be needed (which might just be a text file with the failing data.  A short code snippet is also useful.

On Tue, Aug 13, 2019 at 3:01 PM Tom S <tom-sourceforge@xxxxxxxxxxx> wrote:

I am attempting to update to the latest release, and it is failing.  The
issue is in a call to

new WKTReader().read(wkt);

where wkt is a very large (42k) polygon.  This worked fine in 1.13*.  So
two questions

1) Is there a 'migration guide', or an expectation that one is not needed?

2) Has anyone else had issues?

I'll see if changing this helps, but the one oddity I see in my data is
the element looks like

POLYGON((y x, y x, ... , y x))

which at first glance seems OK based on the docs.


_______________________________________________
jts-dev mailing list
jts-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/jts-dev