﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17905	Store the imagery layers names used to edit data and use them in source	naoliv	team	"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).

JOSM:
{{{
Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-07-08 01:14:04 +0200 (Mon, 08 Jul 2019)
Revision:15234
Build-Date:2019-07-07 23:17:09
URL:https://josm.openstreetmap.de/svn/trunk

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
}}}"	enhancement	new	normal		Core			upload changeset source imagery	
