Opened 15 years ago

Last modified 3 years ago

#2212 new defect

can't edit over 180th meridian

Reported by: rvollmert@… Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: edit 180 meridian Cc: flomigulau

Description (last modified by skyper)

JOSM currently treats the 180th meridian as the end of the world, making it difficult to edit data like . Disregarding the poles, JOSM should treat the world as a cylinder, not as a rectangle.

Note that the API doesn't currently support map calls that cross the 180th meridian, which could be a problem with seamless support.

I'd class it as a defect, but feel free to change to enhancement.


Attachments (0)

Change History (18)

comment:1 by Don-vip, 12 years ago

In [4580/josm]:

see #2212 - Allow JOSM to download data crossing the 180th meridian

comment:2 by skyper, 12 years ago

Keywords: edit 180 meridian added
Priority: minornormal
Version: latest

In my eyes this is at least a normal priority.

Have you ever tried to edit there ?

comment:3 by skyper, 11 years ago

Ticket #8157 has been marked as a duplicate of this ticket.

comment:4 by skyper, 11 years ago

Cc: flomigulau added
Description: modified (diff)

From #8157:

I want to do some mapping on the Fiji island of Taveuni, which stretches across the 180° longitude
(see )
My problems are that it is not possible to
a) load an area across 180° longitude
b) seamless move from the western to the eastern hemisphere. At 180° the world "ends" and a GPX track from the eastern to > the western hemisphere draws long lines across the earth.

I would expect that JOSM is able to seamless scroll from the eastern to the western hemisphere.
Use attached GPX file to reproduce the issue.

example gpx file​

Thanks for fixing the bug!

comment:5 by Don-vip, 11 years ago

See for the OSM API ticket.

comment:6 by stoecker, 9 years ago

Ticket #11205 has been marked as a duplicate of this ticket.

comment:7 by anonymous, 9 years ago

Any news on this topic? When will this bug be solved? It's since three years unsolved... In Fiji do also live people who want to use and edit OpenStreetMap.

comment:8 by Don-vip, 8 years ago

Ticket #12125 has been marked as a duplicate of this ticket.

comment:9 by RicoZ, 8 years ago

#12125 is similar but not duplicate, it describes 2 additional errors one of which may actually eat the OSM database if someone tries to edit the coast of Taveuni.

comment:10 by RicoZ, 8 years ago

After editing a few points of the coastline of Taveuni JOSM wants to upload 277 objects in 60 changesets - prefer not to test the result on the real OSM database.

Trying to move objects spanning the +/180 line gives an error "can not move objects outside of the world".

comment:11 by bastiK, 8 years ago

In r9419 we now have a projection that should improve editing near the 180th meridian:

  • EPSG:5041 for the northern hemisphere
  • EPSG:5042 for the southern hemisphere

(change in Settings > Map Settings > Map Projection > By Code (EPSG))

It makes it very easy to draw a way that crosses the 180th meridian. As most data consumers would have problems with this, there should be a validation test.

comment:12 by Don-vip, 8 years ago

I have strange graphical artifacts with EPSG:5041 (ways that simply appear or disappear when zooming/dragging the map). Have you noticed that?

comment:13 by bastiK, 8 years ago

In 9431/josm:

see #2212, see #12186 - improve display for polar projections

comment:14 by bastiK, 8 years ago

Artifacts should be gone now.

One thing to note is that Quadbuckets does not work properly when crossing the 180th meridian, i.e. it will query & attempt to draw all objects in [-180,180] longitude range, not just the objects in view.

comment:15 by Don-vip, 8 years ago

Thanks, it is much better now, the display seems 100% correct. Only one issue left: I cannot select the way(s) created exactly along 180th meridian (tested around Taveuni island). Also the projection unit tests must be updated now :)

comment:16 by bastiK, 8 years ago

The plan was to "just copy remaining projections", then update unit tests. Turns out it isn't as easy as anticipated. :)

comment:17 by bastiK, 6 years ago

In 12824/josm:

see #2212 - simplify DeepTileSet by making TileSetInfo part of TileSet

comment:18 by anonymous, 3 years ago

JOSM could not open data at 180 degree
See #20549

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to rvollmert@….
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.