|
I'm attempting to map a bus stop that's used by two different bus networks, each of which calls the stop by a different name. I'd like to avoid overloading the name tag with multiple values, but none of the variant tags suggested on the wiki seem appropriate. Would it be appropriate to use something like name:network1=name1 and name:network2=name2? |
|
I already met this kind of stop, I use two nodes in order to have a good routing for both networks. Let say that we could have one shelter (or one pole) with two nodes bus_stop. Hmmm, that seems...inelegant to me. But it may very well be the best way to handle routing for both networks.
(08 Jul '21, 20:16)
Itserpol
|
|
This is a frequent case in Belgium. When this happens, we use a prefix to the name tag. For instance name:De_Lijn=Elsene Triomf while selecting one of the names—typically the major operator—as the main name. The only drawback is that your app must be aware of those prefixes and parse them appropriately when presenting the information to end users. |
