Modify

Opened 5 years ago

Last modified 5 years ago

#19841 new enhancement

Allow editing outside of UTM zone

Reported by: nkamapper Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:

Description

When UTM has been chosen for map projection in JOSM, attempts to edit outside of the chosen UTM zone will produce a "Cannot edit a node outside of the world" error message. Would it be possible to allow editing at least for the closest neighbor zones?

My problem is that Norway spans UTM zones 32-35, yet some of the official WMS's for the country are only provided for the 33 zone, which is regarded by the mapping authority as the "standard" zone for the country. So editing with one of those WMS's as background layer in JOSM is not possible for more than half of the country.

Attachments (0)

Change History (7)

comment:1 by kebisi, 5 years ago

Why is it necessary to edit "more than half of the country"? Mechanical changes?

comment:2 by nkamapper, 5 years ago

No, the point is that I am unable to add even a single node outside of the UTM zone. So with the national UTM 33 imagery, I am unable to edit in for example Bergen (in the west) or in Kirkenes (in the north), despite the fact that UMT 33 provides a correct and sensible projection also in those areas.

Last edited 5 years ago by nkamapper (previous) (diff)

comment:3 by stoecker, 5 years ago

Can you please provide more details? Which EPSG code, which layers/maps? I think we need to extend the projects bounds to ±1 zone. Although it is unusual that such a server does not offer UTM for all covered zones.

A workaround(?): Does reprojecting work? You should be able to use another zone for display (e.g. our standard mercator). I'm not sure if there the same bounds apply.

comment:4 by nkamapper, 5 years ago

I actually found a different WMS now with more supported projections, so my problem for the time being has been solved. It would however be useful to be able to edit just outside of a UTM zone, especially when editing very close to the zone bound.

The EPSG codes in question: 32636, 32633, 32634, 32635 (32633 is the "standard" projection here). Reprojecting would work for predefined imagery in https://josm.openstreetmap.de/wiki/Maps (I think), but I do not know how to get reprojection for user-defined imagery in JOSM.

comment:5 by nkamapper, 5 years ago

Here is a similar problem in Sweden: The official projection used by the national Swedish mapping authority is EPSG:3006. The bounds of of that projection excludes mapping in JOSM of the north/east part of Sweden, for example most of the city of Luleå.

Example WMS: https://kso.etjanster.lantmateriet.se/karta/ortofoto/wms/v1.3?LAYERS=Ortofoto_0.5,Ortofoto_0.4,Ortofoto_0.25,Ortofoto_0.16&FORMAT=image/png&TRANSPARENT=TRUE&STYLES=default,default&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS={proj}&BBOX={bbox}&WIDTH={width}&HEIGHT={height}

in reply to:  4 ; comment:6 by stoecker, 5 years ago

Replying to nkamapper:

Reprojecting would work for predefined imagery in https://josm.openstreetmap.de/wiki/Maps (I think), but I do not know how to get reprojection for user-defined imagery in JOSM.

There are three ways I know:

  • Add the imagery to our wiki when using them for OSM is allowed
  • Create a similar file to our wiki imagery and store it somewhere else (e.g. locally). Then enter the file in JOSM as a secondary source for imagery definitions. I e.g. have such a file for imagery not allowed for OSM use which I use for other purposes.
  • Directly change the JOSM config file XML (or JOSM advanced prefs) and add the missing parameters which can't be modified in the imagery dialogs

in reply to:  6 comment:7 by nkamapper, 5 years ago

Replying to stoecker:
Thank you. I could try # 2 or # 3.

Maybe demanding for the occasional mapper in Luelå though :)
Perhaps the error message could be replaced by a warning within a wider zone?

Modify Ticket

Change Properties
Set your email in Preferences
Action
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 nkamapper.
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.