Sometimes though the reference is in general use even if it isn't
signposted. In this case having it on the renderers might be useful.
For example: we have a C road near us. On the ground the road looks like
a single road, but in reality it is made up of series of roads with
around 6 individual names. For simplicity therefore lots of local
publications (magazines, political flyers, local websites) just use the
C reference.
Having the reference on renderers is therfore useful.
That said I've seen a mapdust error that the reference wasn't signposted.
On 18/05/2011 11:03, Richard Fairhurst wrote:
I note an increasing number of roads tagged with ref=C<number>:
http://osm.org/go/euF7qf93-
http://osm.org/go/eu6CM0IS-
etc.
Leaving aside for now the question of sourcing, I feel a little uneasy
about these being rendered on the map. Anyone using the map as, well, a
navigational aid will think "turn left onto the C94... oh... hang on...
what C94?".
So if we are to have such arcana in the database, and experience
suggests you can't actually stop people adding arcana to OSM (I guess
that's one of our strengths ;) ), it would be helpful to have some way
of tagging "this ref is not actually signed". That way, renderers and
routers could choose not to show refs which aren't helpful for their
audience. Something like ref:signed=no would work.
Any thoughts?
cheers
Richard
_______________________________________________
Talk-GB mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk-gb
