[Tagging] Tagging Cycle Route Relations vs. Ways
Brian M. Sperlongano
zelonewolf at gmail.com
Tue Nov 17 15:39:53 UTC 2020
The classic case for a "source" tag is for imports. It's useful to know
that something came from a TIGER import, or from some public database or
wherever. I think source=* makes sense when the data is literally coming
from some defined external place.
On Tue, Nov 17, 2020 at 10:36 AM Dave F via Tagging <
tagging at openstreetmap.org> wrote:
> On 17/11/2020 03:09, Seth Deegan wrote:
> > May I ask why not source=*?
> TBH. I'm not a fan of the tag. I don't think it adds much value. It's
> too subjective/variable, but...
> It relates to the individual contributor editing individual objects. A
> contributor can obtain data from many different sources within each
> changeset. Pushing the tag to the changeset meta data invalidates it's
> limited usefulness when added to individual objects.
> > many times I find myself wondering where past mappers got the info
> > for a route (this happened just today).
> Anecdotal guesstimate: For cycle route - on the ground via signage for
> the vast majority. I've found published data (from the authority
> authorised to amend the route) are often too inaccurate, out of date or
> lacking in detail to warrant transferring to OSM.
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging