Talk:Key:source

Good Idea. Perhabs we schould also have a automaticly filled property, about how mad changes to a object. Like Wikiepdia "Version" tab. Sven Anders 13:43, 28 Jul 2006 (BST)

There is no suggested core value of GPS, is it assumed that if a node is above an uploaded GPX track that that is enough evidence of its source? Dmgroom 00:03, 5 September 2006 (BST)

I think it is assumed, but on the other hand I'd still add the appropriate source tag even in that case when creating the map. After all, some node/segment/way could be above a GPX track just because it's the same road, and yet it could come from a different source... using the appropriate tag in all cases won't hurt. LjL 18:25, 5 September 2006 (BST)

If I map a road and use many different sources, e.g. Yahoo Image, my own GPS-Trace (which I uploaded after using), GPS traces from other users and also data from http://wiki.openstreetmap.org/wiki/Import/Catalogue/Strassen_NRW . I use different sources in order to map the street most realistic, but with the source tag I can only declare one source. And some people even tag every road with source=survey. Is that good? What can I do / how can I declare more than one source? And if I use Yahoo Image for mapping, do I *need* to declare that I used them?

Thanks in advance. :)

official way to assign multiple values for a tag is to separate them with a semicolon, thus you could tag it like source=survey;yahoo or whatnot. i'd say - don't bother too much with it, just set the one that contributed the most. though personally, i only add source when i have used some 3rd party source like landsat etc. --Richlv 19:02, 1 May 2009 (UTC)

source:name

I actually don't like source:name since it does not comply to the logic used on other tags (e.g. all the lane proposals, the mtb stuff, and so on). I'd love to see a generic foo:bar:source approach, meaning that source:name would be replaced by name:source and the whole concept could be extended to virtually any tag, e.g. opening_hours:source, description:source and so on. I just find source as the last suffix more logical, since the value of the key is actually the source you describe, therefore it is just logic to place the source tag in last place. thoughts? --Marc 18:49, 29 January 2010 (UTC)

source = survey (wiki) vs. GPS (JOSM)

When I create streets etc from a GPS track, I'd like to note that - the wiki suggests using source=survey but JOSM does not offer survey but GPS. As long as JOSM supposes GPS it will be much easier to use it instead of survey. Please clarify and note in wiki (http://wiki.openstreetmap.org/wiki/DE:Map_Features#Erl.C3.A4uterungen and http://wiki.openstreetmap.org/wiki/Key:source) what to do / change JOSM proposals.

Multiple Values

If (say) a way has been traced from Yahoo! imagery (hence source=Yahoo), I go there and survey with my bike writing down information like lanes, surface, lit and so on but without a GPS track, should it be source=Yahoo; survey? --Nighto 00:21, 8 May 2010 (UTC)

See above, I asked the same question one year ago :D Seriously, I think that the source key should only be used on an element (a way for example) if the way is very different from what it was before or if you use keys and attributes, that seem "extraordinary". If I map a normal street I don't set the source key on the way, instead I write in the comment of the changeset what I did and where the information come from. And if I used 3rd party sources I add a source key the the changeset. That only works of course if I only use one source. If I said source=Yahoo;survey;landsat;blahblahblah it's not clear for which element I used which source. But if I use different sources for different things I just use different changesets. And of course I add the source key to an element (e.g. node, way...) if another mapper could wonder why I set those values. Under [1] you can find an example how I use the source key on a changeset. [1] On the other hand Openstreetmap is *free*, so *you* can decide how it should be tagged. Other people say the source key on every way makes sense and should be expanded. Just do what you think what makes sense. It's easy to look for the comments and source tags in a changeset with josm, because there is a very nice history function implemented now. :) --westfa 20:31, 17 May 2010 (UTC)

Just put the source=* on the changeset. That way it is easy to see what information came from where. Gnonthgol 22:16, 17 May 2010 (UTC)