This repository was archived by the owner on Jul 24, 2021. It is now read-only.
This repository was archived by the owner on Jul 24, 2021. It is now read-only.
allow map call spanning 180th meridian #1612
Open
Description
Reporter: robx
[Submitted to the original trac issue database at 10.17pm, Thursday, 19th February 2009]
Currently, the API doesn't treat map calls for areas overlapping the 180th meridian nicely.
For a bbox with minlon=179, maxlon=-179, it should return a 2 degree slip along the 180th meridian.
It might be worth specifying -180 <= lon < 180 in general; that's what GPX does, at least: http://www.topografix.com/GPX/1/1/#type_longitudeType
I'm not sure if there's other situations where the API assumes the earth is a rectangle.
Cheers
Robert
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
openstreetmap-trac commentedon Jul 23, 2021
Author: gpspilot1
[Added to the original trac issue at 5.02am, Sunday, 16th December 2012]
This defect has been independently rediscovered by me, and confirmed by aseerel4c26 and scai (see https://help.openstreetmap.org/questions/18437/osm-shows-2-road-segments-potlatch-2-only-shows-one ). Hope I'm not out of line by bumping up the priority.
openstreetmap-trac commentedon Jul 23, 2021
Author: TomH
[Added to the original trac issue at 8.38am, Sunday, 16th December 2012]
Not really out of line, but it won't make a blind bit of difference to whether anybody feels like fixing it.
openstreetmap-trac commentedon Jul 23, 2021
Author: gpspilot1
[Added to the original trac issue at 11.10pm, Sunday, 16th December 2012]
The following bizarre error message is associated with this bug: "A server error occurred. Do you want to retry? (The server said: The node is outside this world)"
If I really did have the power to place extra-worldly nodes, that would be really cool.
openstreetmap-trac commentedon Jul 23, 2021
Author: gpspilot1
[Added to the original trac issue at 8.32pm, Monday, 17th December 2012]
This bug is drastically detrimental to roads in Siberia, as well as in Fiji. (For example, here are two un-joinable Fijian ways: http://osm.org/go/FEABUUQBB-- )
openstreetmap-trac commentedon Jul 23, 2021
Author: TomH
[Added to the original trac issue at 12.30am, Tuesday, 18th December 2012]
No this is not "critical" in any way shape or form. That would be things like "nobody can upload any data".
The API has never supported this, so adding it would basically be an enhancement, and at least one person has argued to me that it shouldn't do so and that clients should split the request - they can do so just as easily as the server can.
openstreetmap-trac commentedon Jul 23, 2021
Author: emj
[Added to the original trac issue at 8.31am, Tuesday, 18th December 2012]
It's obviously an issue, people editing borders that span the 180th resort to this:
http://www.openstreetmap.org/browse/way/46113981
openstreetmap-trac commentedon Jul 23, 2021
Author: gpspilot1
[Added to the original trac issue at 7.16am, Saturday, 22nd December 2012]
Replying to [comment:7 TomH]:
Oh dear, I really overreached.
But I find it quite annoying that I can't draw a way that spans the 180th. Are you saying that Potlatch2 could be modified to "split the request," and this would fix the problem?
openstreetmap-trac commentedon Jul 23, 2021
Author: Richard
[Added to the original trac issue at 5.05pm, Saturday, 22nd December 2012]
It certainly could be, but you'd need to find a developer who was interested in fixing the issue!
openstreetmap-trac commentedon Jul 23, 2021
Author: woodpeck
[Added to the original trac issue at 7.23pm, Saturday, 22nd December 2012]
It is not too difficult to modify the API to return data for bboxes that cross the dateline (I made a start here https://github.com/woodpeck/openstreetmap-website/tree/bbox-cross-dateline but this doesn't cover cgimap or AMF). Having clients handle this does mean that all clients have to implement it and it also means less efficient querying.
But I guess this is much more than just a "can the API handle this" question. I suspect that if you created a way that went from (179.99,0) to (-179.99,0), most clients (editors as well as renderers) would draw a 40,075 km line along the equator. And why exactly would this be wrong?
Perhaps it isn't the worst thing that creating such ways is currently very difficult ;)
openstreetmap-trac commentedon Jul 23, 2021
Author: JohnDoe23
[Added to the original trac issue at 3.29pm, Saturday, 29th March 2014]
Has someone of the developers here ever tried to edit at 180 and -180? I'm editing there right now and can tell you that it's a big mess. Every good GIS-software has no problems with handling the 180th meridian, just OSM can't handle it.
I can't understand why this problem isn't classified as critical - just try editing with JOSM in this area und you'll change your mind.
8 remaining items