Opened 10 years ago
Closed 9 years ago
#12065 closed enhancement (wontfix)
Improvements with locally deleted objects
| Reported by: | naoliv | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: | maxerickson@… |
Description (last modified by )
What sometimes I would like to have and do in JOSM, with locally deleted objetcs (ie, I have deleted something inside JOSM and not yet uploaded to OSM)
Search
Using a possible deleted parameter, like modified
Display
Toggling/enabling/clicking on some option, the deleted objects could be displayed on the map, using a different and highlighted color
Undelete
An option to select the deleted object and undelete it.
What I have to do know:
- save the .osm file
- open it in a text editor
- remove the
action='delete'from the objects - reopen it in JOSM
Sometimes it's also necessary to delete all the action='delete' objects in the file and redownload them.
Purge
Like we can already purge modified and non-modified objects, we could also purge the deleted ones (ie, just forget that I have deleted the object and simply remove it from my local data)
JOSM:
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2015-11-05 02:34:01 Last Changed Author: Don-vip Revision: 8993 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Relative URL: ^/trunk URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2015-11-05 03:05:19 +0100 (Thu, 05 Nov 2015) Last Changed Rev: 8993 Identification: JOSM/1.5 (8993 pt_BR) Linux Debian GNU/Linux testing (stretch) Memory Usage: 708 MB / 9102 MB (279 MB allocated, but free) Java version: 1.7.0_91, Oracle Corporation, OpenJDK 64-Bit Server VM Java package: openjdk-7-jre:amd64-7u91-2.6.2-1 VM arguments: [-Dawt.useSystemAAFontSettings=on] Plugins: - Create_grid_of_ways (31603) - OpeningHoursEditor (31696) - PicLayer (31694) - RoadSigns (31694) - SimplifyArea (31694) - apache-commons (31718) - buildings_tools (31694) - conflation (0.1.8) - contourmerge (1013) - download_along (31603) - editgpx (31603) - geotools (31603) - imagery_offset_db (31694) - importvec (31694) - jts (31603) - log4j (31603) - measurement (31694) - merge-overlap (31655) - opendata (31695) - pbf (31694) - pdfimport (31694) - poly (31694) - reverter (31694) - scripting (30722) - todo (29154) - turnrestrictions (31694) - undelete (31603) - utilsplugin2 (31694)
Attachments (0)
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Cc: | added |
|---|
comment:3 by , 9 years ago
| Description: | modified (diff) |
|---|
Search was implemented in [11446]
Purge seems to apply too?
comment:4 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Display and Undelete are a non-trvial tasks, as JOSM does not necessarily keep the original state. Thus a simple mechanism like described above will cause lots of problems.
For these very specific examples shown here I'd suggest purging the deleted objects (which is possible using the search option) and redownload them. I see no reason in supporting this workflow in the editor better than possible now.



Ticket #13796 has been marked as a duplicate of this ticket.