On Sun, 12 May 2019 at 00:08, Johnparis <ok...@johnfreed.com> wrote:

>
> I go by the rule "if it ain't broke, don't fix it." What is "broken" by
> the existing setup? And in particular, what is "broken" that adding a
> "headsign=*" tag wouldn't fix?
>

The fact that, when I'm waiting for a bus at a stop which has several
services, some of them
variants of the same route number, I want to know what to look for on the
headsign.  I don't
want to know what the marketing dept calls that route, or what's on the
brochures and timetables
inside the bus, I want to know what is on the headsign.  I may be in a
hurry.  Too much of a hurry
to use the query tool to work my way through the several routes and
variants on that stretch of road
so I can find the headsign tags.  I'd like it on the map.  I'll accept a
superset, so if the headsign
says "Aberystwyth" and the timetable says "Cardigan to Aberystwyth via New
Quay" I'd be happy
enough with the latter.  Route designation as well, of course, especially
if that's on the headsign
(which it usually is).

All that is just my opinion.  Which may differ from best practises, worst
practises and any other
practises known to man.  I have a wish, not shared by everyone on the list,
that maps be useful.

Feel free to tell me what best practise says about
https://www.ceredigion.gov.uk/media/3813/t5-x50-554.pdf
If I get on at Cardigan the headsign says "T5 Aberystwyth".

-- 
Paul
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to