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
I have started to do a lot of plotting of data on maps and have been reading up on this.
Any longitude value less than -180 or bigger than 180 is obviously an invalid longitude value. However, the current geoJSON specification has a problem. This problem is easiest to explain with a LineString, and then expanded to include polygons.
Let's say that you have 2 lines
Line X goes from [179, 90] to [-179, 90]
Line X goes east and do cross the International Date Time Line
Line Y goes from [179, 90] to [-179, 90]
Line Y goes west and do not cross the International Date Time Line
How do you tell these two lines apart? Please remember that direction is important. Line [[179, 90], [-179, 90] ]is not the same line as[[-179, 90], [179, 90]].
One popular solution is to break the rule, and write line X as [[179, 90], [181, 90]]. However, the recommended solution is to break the lines into a MultiLine and have it as [[[179, 90], [180, 90]], [[-180, 90], [-179, 90]]].
The same problem occur for polygons and are solved in the same way.
This software seem to be using the first approach to this problem. I don't know if that is intended behavior from @gabzim or not.
I will close this issue since it is a duplicate of #4 . I have also added #4 to the TODO list hand hope to have it solved for the next version release.
If we call this package with the below values, it's is giving some point which cannot be plotted in the google map.
In the result, there are some point like:
[-180.02911542185794, -21.856002776317947] (long lat format) which cannot be plotted in the google map.
The text was updated successfully, but these errors were encountered: