idea: render local_ref instead of name for bus stops

[k-yle]

If a bus stop has local_ref, it would be more useful to render the local_ref instead of the name.

This is useful because:

• In these cases, the "platform" number (local_ref) is how people identify each bus stop
• repeating the same name many times is visual spam and not really helpful, since anywhere big enough to have local_ref usually has an amenity=bus_station which also renders the name

This is somewhat related to #4800

Google maps has recently made this change in some countries, and it's very useful.

Current Situation	Ideal Situation
 osm carto renders the name `Akoranga` several times	 google maps renders the name `Akoranga` once, and renders `A`/`B`/`C` for each stop.
	 

Ideal rendering in OSM Carto:

[imagico]

This is similar to #4662 - discussion there is largely also relevant here.

highway=bus_stop + ref=* has 637k uses highway=bus_stop + local_ref=* has 135k uses

and there does not appear to be consensus among mappers about a semantic difference between ref=* and local_ref=* on highway=bus_stop or if this belongs to highway=bus_stop at all or to public_transport=stop_position. It also appears that the vast majority of uses of the tag in many regions are trivial values like '1' (or '2' for direction separated bus stops) without those values being of practical use locally (people refer to the specific stop by direction rather than through a code) - see also previous discussion in https://github.com/gravitystorm/openstreetmap-carto/issues/4662#issuecomment-1224096190. ref:signed - which could help detecting those cases - is not used widely.

Like with #4662/#4800 it would be good to know about what mapping conventions exists in that field world wide (which are evidently varying) to see if something can be identified as broad consensus that we can support in rendering in a meaningful way.

Addition: I just saw that this requests to replace name rendering with ref rendering - that would require evidence that bus stops are widely referred to by ref rather than name (which seems unlikely).

[daganzdaanda]

For comparison, the ÖPNV (public transport) map layer shows the local_ref at the bus station you linked: https://www.openstreetmap.org/node/4687856163#map=18/-36.79713/174.76074&layers=O It also renders ref the same way.

Also, see the Verkehrskarte (traffic map) style: https://www.openstreetmap.org/#map=18/-36.79713/174.75980&layers=T This style does not render ref.

Found an example with both ref and local_ref: https://www.openstreetmap.org/node/1246670063#map=18/48.59003/7.74104&layers=O It seems the style will prefer the local_ref, and drop the ref.

In my opinion, Carto style still needs to show the name of the stop. For most stops, it would not help if there were only the short (local)ref. We could maybe get a label that has both the name and the (local)ref in a new line.

[k-yle]

[...] and there does not appear to be consensus among mappers about a semantic difference between ref=* and local_ref=* on highway=bus_stop [...]

This seems like the biggest obstacle that will prevent this idea from working effectively, I had a look on overpass and some cities have some rather strange examples...

Also, see the Verkehrskarte (traffic map) style:

Interestingly, this map style does not render local_ref=* if it contains a full word or several words. I'm not sure how they decide when it is appropriate to render local_ref=*... Is this map style open source or is there a way to ask the authors questions?

[RedAuburn]

How about rendering both: local_ref=M name=Carto Road

would be rendered with the name: Carto Road (M)

this is how OrganicMaps, OSMAnd, and many other map styles render it.