Add a nag for missing source tag on changeset/upload

[olejorgenb]

Depressingly few people employ the source tag, at least in my area.

Maybe a nag, or at least having a dedicated textbox in the upload dialog, could help? If not for the purpose of forcing people to use the tag, then for helping people that do remember adding it.

When a changeset is closed there is no way back, and then you are left with tagging all elements, which is annoying, and have slightly different semantics. (ie. for changed, not new elements)

[anonymous]

Source should be tagged to the elements, not the changeset, for what I hope should be obvious reasons.

[stoecker]

Replying to anonymous:

Source should be tagged to the elements, not the changeset, for what I hope should be obvious reasons.

Your obvious reasons are not so obvious and contrary to the suggestion of OSM in general and also in contrast to the experiences of the past.

[olejorgenb]

Source should be tagged to the elements, not the changeset, for what I hope should be obvious reasons.

Obvious for which reasons? Lack of tools that infers the keys and coordinate sources from changesets (*)? A changeset having edits with different sources? From what I see there is currently no real conscious of what is best practice..

Either way.. a nag could also be issued if a percentage of the elements edited is missing a source tag or something similar so let's move the discussion of OSM 'policies' away from the JOSM tracker :)

(*) The absence of something like this is another shortcoming of JOSM regarding source management. (Maybe this is hard / requires lots of api calls?)

[anonymous]

The obvious reason being that a changeset may contain objects from different sources: a road pulled from a GPS trace, a footpath and some buildings from Bing, the names taken from OS Locator, etc. I trust nobody's going to suggest that such a small edit should be committed using three changesets, because that way lies madness.

[simon04]

I put a source to the changelog if (most of) the data originates from one source. I suggest to a textfield in commit dialog below of the description textfield. Users see the possibility to add such a tag and may or may not enter one. However, they are not forced to.