Opened 5 years ago

Last modified 5 years ago

#17905 new enhancement

Store the imagery layers names used to edit data and use them in source

Reported by: naoliv Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: upload changeset source imagery Cc:


Would it be possible for JOSM to store the name of the layers that were enabled and used for edition?

ie, if we add/modify/delete any data, then we store the top-most active layer name (which is the current visible layer).

With this we could have a more accurate source that was used for editing, regardless of whether the layer is disabled or even removed.

For example, right now we have this:

  • create e new data layer
  • add any imagery layer
  • insert some data
  • disable the imagery layer
  • ask to upload the data
  • click on obtain from current layers at the source and see how nothing is inserted

Instead using only the names of the active layers, we would use the stored names where in fact some data was edited.

Maybe there could also be an option to use the names of the active layers and/or the used layers.

This info should be included on the session files and the autosave files too, if possible (so even if JOSM/the computer crashes, we would still have a list of the used layers).


Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-07-08 01:14:04 +0200 (Mon, 08 Jul 2019)
Build-Date:2019-07-07 23:17:09

Identification: JOSM/1.5 (15234 pt_BR) Linux Debian GNU/Linux 10 (buster)
Memory Usage: 322 MB / 2048 MB (85 MB allocated, but free)
Java version: 11.0.4-ea+10-post-Debian-1, Debian, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-11-jre:amd64-11.0.4+10-1
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-22
libcommons-compress-java: libcommons-compress-java:all-1.18-2
libcommons-logging-java: libcommons-logging-java:all-1.2-2
VM arguments: [-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2, -Dawt.useSystemAAFontSettings=gasp]
Dataset consistency test: No problems found

Attachments (0)

Change History (4)

comment:1 by Don-vip, 5 years ago

Can you please give a real example where this feature would be useful?

comment:2 by naoliv, 5 years ago

In a lot of times I use 2 or 3 layers to edit some data, but some of them stay disabled for most of the time (usually I only have 1 active imagery layer).

When uploading and clicking obtain from current layers it only gets the enabled layers (thus leaving behind some layers which I did use but are just disabled).

Sometimes I realize this, other times I don't notice and the source gets incomplete.

It is similar to iD recording all the layers which were used to modify some data (in imagery_used; example

comment:3 by Don-vip, 5 years ago

OK thanks, understood now.

comment:4 by Don-vip, 5 years ago

Keywords: upload changeset source imagery added
Summary: Store the layers names used to edit data and use them in sourceStore the imagery layers names used to edit data and use them in source

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to naoliv.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.