id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
20478	Naming of imagery layers / considering attribution aspects in changesets	Polarbear-j	team	"In https://josm.openstreetmap.de/wiki/Maps/Germany?sfp_email=&sfph_mail=&action=diff&version=248&old_version=247&sfp_email=&sfph_mail= @ Klumbumbus removed my more qualified name ""Brandenburg GeoBasis-DE/LGB (2020) / DOP20c"" and replaced it with ""Brandenburg DOP20c"" 

I see several issues here:
1. not mentioning the provider is misleading. Bing coverage of Brandenburg is ""Brandenburg DOP"" as well. 
2. The name tag is copied into the the layer name when the user activates a layer, and the layer name is subsequently auto-filled into the source tag. Thus the source tag gets filled with an ambiguous value, lacking attribution.
3. The license requirements from imagery providers demand a particular string to be added to the changesets, and this is in this case ""GeoBasis-DE/LGB (2020) / Name of dataset"", [where strangely the Geoportal-2020 is not the year of the imagery flight but the year when copied from the Geoportal (applies to other layers like ALKIS where it makes more sense]. My compromise here was to put the location at the beginning, to have things sorted by them. 

You might argue that there are separate fields in the xml for attribution and date, however they are only used internally in the editor and do not propagate to the changeset. 

Thus I think we need to live with a sightly longer name (applies to recent Berlin edits as well), or fundamentally change how to bring attribution into the changesets otherwise. "	defect	new	normal		Core imagery