Opened 15 years ago
#5439 new enhancement
Implement ability to hide selected object
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | hide expose object | Cc: |
Description
Proposed functionality description:
Provide a mechanism that would allow user to select an object and using a command (accessed from menu and/or using a keyboard shortcut) remove it from view. Another command would allow bringing hidden objects back to view - the revealed objects would remain selected to allow further operations.
Use case description:
I download an area from the OSM database with a bunch of existing objects (nodes, paths). I have a slippy map containing some authoritative data (for example an aerial map) that I want to use as a reference for fixing the OSM database data. I would like to take an object, adjust its position against the slippy map reference and hide that object from view. Hiding would serve 2 purposes:
- would clearly separate completed (fixed) objects from the unprocessed ones
- would prevent user from accidentally altering an already-fixed object from a nearby edited one.
notes:
I am aware that we have filtering, but filters work on an assumption of tag set differences existence. In the above-described scenario there are no tag differences between edited and raw objects, therefore filters can't be directly used.
Another alternative to functionality for hiding a selected object would be ability to move a it to a different layer. This would allow user to move completed objects to a hidden layer that would be exposed and committed into OSM DB upon task completion.