simonpoole
commented
1 year ago Currently the data layer is quite special (mainly for historic reasons) in that it isn't as self contained as other layers are and would require significant work to enable multiple instances (but it would be completely doable). As a tendency we have be reworking things slowly in that direction, for example we did that for the GPX layer in 17.1.
(Aside: this is actually the only way I would be able to display any OSM data in the app right now because of a strange bug where it won't fetch anything from openstreetmap.org. That is a separate issue, but I don't really know how to get good debug information for it)
Could you open a separate issue for this and add some details on how and when this happens?
I noticed that Vespucci has the ability to import and export JOSM files, basically for use as editing sessions.
But, for reasons, I would like to display a JOSM file as a layer, similar to a geojson layer.
In short I am prototyping an alternate map to overlay on OpenStreetMap [*], which will never be uploaded to OpenStreetMap itself; to prototype my map I would want to have it on the screen for reference while adding new points. And sometimes I might want to display my overlay layer while adding a point to normal OpenStreetMap in a clean editing session.
This should basically be a layer that displays like regular OSM data and maybe where tags can be viewed, but which will be treated separately of OSM servers, whether that means it isn't editable or is separately editable. (I know picking a layer to edit would get complicated if there was more than one, so "not editable" would be fine.)
(Aside: this is actually the only way I would be able to display any OSM data in the app right now because of a strange bug where it won't fetch anything from openstreetmap.org. That is a separate issue, but I don't really know how to get good debug information for it)
[*] more context:
edit: opened a new issue for the OSM object problem. #2151