> I have been told ( on the talk-US email list ) that use of
> {{key|source}} on objects has been deprecated for years and that
> such information is only of historical interest and its use should
> be restricted to changesets.  This is not reflected in anything I
> can find on the wiki, and I've done an incomplete search of the
> subject fields on this forum to see if this has been discussed.
> Could you please clarify this for me?  Should I a) not be adding
> {{key|source}} to objects and b) should I be adding content in such
> a way that a single source tag on the changeset is valid for all
> content in that changeset (this has major implications for my
> editing behavior).

It would be very premature to call this "deprecated" - it is still
widely used and endorsed by many mappers.

I do agree with the sentiment that source is usually best placed on
the changeset, though. While mass-adding source tags is quite easy
when tracing buildings, for example, and of course even easier during
an import, updating source tags on existing objects is a lot more
cumbersome. Therefore, sources of later changes will often not be
accurately reflected by source tags on objects.

Adding sources for changesets will also more naturally represent the
source of individual modifications - for example, a lake outline may
have originally been traced from Landsat, improved using Bing imagery,
and finally an average water depth may have been added based on
government open data.

You can of course use and document multiple sources for a changeset,
using a semicolon-separated value list.

Tobias

_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging

Reply via email to