Replies: 2 comments
-
UK/tfl bus stops also have this, tagged as `naptan:AtcoCode' Eg. (see #3730 for related discussion) |
Beta Was this translation helpful? Give feedback.
-
Yes. In the OSM community discussion that i linked above, Andy Townsend advice was to use tag "website" which is easier to be processed by data consumers (OM in this case). The question is, is adding a "website" URL that, for several thousands of bus stops, only varies in the parameter (which is also the "ref" or some other tag) a good method to map that info? There is a chance that OM in the future uses that "website" tag in bus stop POIs? It would be better to map the url of the service at the bus network level and only the parameter at each stop? Or OM mao format could handle thousands of URL strings almost equal without impacting in the map size? Or the map size is not relevant at decisions of this kind? BTW, looking this issue i found another issues related with bus stops.
Below is an annotated screenshot of how this bus stops are displayed in the current version. |
Beta Was this translation helpful? Give feedback.
-
Hi. In POIs that are public transport stops, in several cities is becoming usual that the stop have a QR code that guides to a mobile site that gives you information about the next buses that are arriving.
I have found a post in OSM Community with this issue: https://community.openstreetmap.org/t/rfc-departures-url-on-e-g-highway-bus-stop-for-online-departures-boards/107673/13
E.g., in Montevideo, for a bus stop ref/id 3228, the URL showing the arriving buses is https://m.montevideo.gub.uy/comoir/parada?numero=3228 (the parameter is the ref/id of the bus stop)
Could this link be shown in the POI information so the user can follow it?
Have any preference in how it should be tagged in OSM?
BTW, in this case of Montevideo, this info is also available from the local government as an API at no cost, and it could be used to display the info in OM itself, but i think that it is much harder to implement worldwide, as not every city has the same API, and also the authorization token should be managed for each API. Or maybe a mixed solution, in which some cities OM could use the API, and in others follow the link.
Beta Was this translation helpful? Give feedback.
All reactions