Skip to content

Problems and bugs around +/- 180 meridian #81

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

Open
ghost opened this issue Dec 6, 2015 · 2 comments
Open

Problems and bugs around +/- 180 meridian #81

ghost opened this issue Dec 6, 2015 · 2 comments
Assignees
Milestone

Comments

@ghost
Copy link

ghost commented Dec 6, 2015

Taveuni is pretty island split in half by the meridian and in need of more mapping which is pretty difficult with the tools tested so far.
http://www.openstreetmap.org/?lat=-16.853&lon=-179.935&zoom=11&layers=M
https://en.wikipedia.org/wiki/Taveuni

Merkaartor bugs there:

  • attempts to download data across +/- 180 meridian cause illegal OSM-api requests
  • panning from west to east across +/- 180 meridian displays coordinates > +180 which would probably cause trouble if data is edited and uploaded

See also https://wiki.openstreetmap.org/wiki/Fiji#Problems_with_the_.2B.2F-_180.C2.B0_meridian

@Krakonos
Copy link
Member

Krakonos commented Jan 4, 2016

I have fixed the invalid API in 36d72ad, and will do more testing on test api for the second point.

I think it's good for use, if you will handle the the boundary yourself. Is there something that can be done, besides checking node placement to avoid problems?

I probably won't be able to implement full seamless editation around the 180 meridian anytime soon.

@Krakonos Krakonos added this to the 0.19.0 milestone Jan 4, 2016
@Krakonos Krakonos self-assigned this Jan 4, 2016
@Krakonos Krakonos removed the Bug label Jan 7, 2016
@ghost
Copy link
Author

ghost commented Jan 10, 2016

Thanks, I am not sure when I have the chance to test the updated version but will try to compile it.

@Krakonos Krakonos modified the milestones: 0.20.0, next Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant