-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading shape files #5
Comments
From @DGuidi on July 20, 2016 6:56 can you post some sample data that actually show this failure? |
From @DGuidi on July 23, 2016 13:52 Thanks for sharing this :) ----- Messaggio originale ----- Sample data: |
OpenJUMP 1.13 loads this too. |
From @trailway on July 19, 2016 17:57
I recently encountered some shape files which the reader does not handle. It can be debated whether the files are correct but they do work in ArcMap! What happens is that the content length does not include M content which is present (although it's presence is benign because the value says that it is not meaningful). This makes the reader fail because it walks through shape geometry using content length, i.e. it expects the next element to begin at the location just after the location where the previous element ended. This works in ArcMap because they use the shape index. I think that using the shape index (which is a required file) is a more stable approach.
Copied from original issue: NetTopologySuite/NetTopologySuite#112
The text was updated successfully, but these errors were encountered: