You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a LinearRing's <coordinates> tag is malformed using additional commas instead of spaces (i.e. x,y,z,x,y,z,x,y,z,... instead of x,y,z x,y,z x,y,z ...), JAK simply returns a list with only the first point.
That behaviour is fair enough, but it would be nice if it could either parse the malformed data or throw an exception, since returning a single point is technically incorrect and makes it harder to catch data errors.
Google Earth and other apps parse that malformed data correctly, so perhaps it's not so uncommon? A subset of the file I'm working with is:
When a
LinearRing
's<coordinates>
tag is malformed using additional commas instead of spaces (i.e. x,y,z,x,y,z,x,y,z,... instead of x,y,z x,y,z x,y,z ...), JAK simply returns a list with only the first point.That behaviour is fair enough, but it would be nice if it could either parse the malformed data or throw an exception, since returning a single point is technically incorrect and makes it harder to catch data errors.
Google Earth and other apps parse that malformed data correctly, so perhaps it's not so uncommon? A subset of the file I'm working with is:
The text was updated successfully, but these errors were encountered: