search

hotosm / osm-tasking-manager2

Designed and built for Humanitarian OpenStreetMap Team collaborative emergency/disaster mapping, the OSM Tasking Manager 2.0 divides an area into individual squares that can be rapidly mapped by thousands of volunteers.
http://tasks.hotosm.org
Other
425 stars 156 forks source link

Do import task boundary in JOSM. Automatically and as GPX. #498

Open althio opened 9 years ago

althio commented 9 years ago

Currently the boundary is made available by a link to a gpx file:

Download the following .gpx file and load it in JOSM

Since the situation is now handled gracefully with the .gpx file, a new layer, only visual, no interaction with data... revert to automatic loading/import is possible.

from https://github.com/hotosm/osm-tasking-manager2/pull/390#issuecomment-63242447:

You could import the gpx file in a new layer so the task boundary is automatically loaded in JOSM without the side effect describe in #251. http://127.0.0.1:8111/import?new_layer=true&url=http://tasks.hotosm.org/project/752/task/273.gpx

This could be automatic, or click on button/link. I would rather say automatic, it seems to me the best default is to have the boundary visible. So then remove the tip $('#josm_task_boundary_tip').

If someone is bothered by the visual boundary it can be hidden or deleted in JOSM.

pierzen commented 9 years ago

Both for imagery and this gpx file, developpers should try to find solutions to avoid mappers to take care of layers adding up in JOSM.

pellis2 commented 8 years ago

This would certainly help editors know where their editing box limits are. Some new editors to JOSM might not have all of JOSMs features mastered in order to add the GPX.