You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Manually naming layers is time consuming and error prone especially when working with many changesets/layers simultaneously.
Please make it so that changesets that are opened in JOSM are automatiaclly given a relevant layer name like "Changeset ABCDEFG", rather than just "Data Layer X" when they are opened in a new layer.
What is the motivation / use case for this feature?
It makes managing data layers easier and more efficient.
It would create a synergy with other JOSM plugins/tools like the changeset reverter which names layers based on the changeset ID (if reverted in a new layer).
It would make it easier to verify and provide comments on changesets in external tools like OSMCha.
Data layers would be possible/easier to identify in the event of a JOSM crash and recovery of data layers, rather than importing/setting things up from schratch, or having to check the data within each layer.
It would reduce the likelihood of human error.
etc.
What is the current behaviour, (attach relevant screenshots) ?
I'm submitting a (feature request)
Brief Description
Manually naming layers is time consuming and error prone especially when working with many changesets/layers simultaneously.
Please make it so that changesets that are opened in JOSM are automatiaclly given a relevant layer name like "Changeset ABCDEFG", rather than just "Data Layer X" when they are opened in a new layer.
What is the motivation / use case for this feature?
Automation, efficiency, organisation & error reduction.
It makes managing data layers easier and more efficient.
It would create a synergy with other JOSM plugins/tools like the changeset reverter which names layers based on the changeset ID (if reverted in a new layer).
It would make it easier to verify and provide comments on changesets in external tools like OSMCha.
Data layers would be possible/easier to identify in the event of a JOSM crash and recovery of data layers, rather than importing/setting things up from schratch, or having to check the data within each layer.
It would reduce the likelihood of human error.
etc.
What is the current behaviour, (attach relevant screenshots) ?
What is the expected behaviour ?
When does this occur ?
Every time a changeset is opened in JOSM.
How do we replicate the issue ?
Please tell us about your environment:
Firefox V 132
Windows 10
JOSM 19253
Other Information / context:
This feature request was previously submitted via JOSM ticket 23994
Relevant page to help add this functionality: https://josm.openstreetmap.de/wiki/Help/RemoteControlCommands
The text was updated successfully, but these errors were encountered: