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?

asked 08 Jul '21, 16:20

Itserpol's gravatar image

Itserpol
71448
accept rate: 0%


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.

permanent link

answered 08 Jul '21, 18:42

zorglubu's gravatar image

zorglubu
309126
accept rate: 16%

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.

permanent link

answered 09 Jul '21, 09:39

bxl-forever's gravatar image

bxl-forever
211
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×918
×83
×61
×54
×4

question asked: 08 Jul '21, 16:20

question was seen: 588 times

last updated: 09 Jul '21, 09:39

powered by OSQA