|
I wonder why some wiki pages suggest to add the tag To me it would make more sense to add this tag to the platform, since renders (or styles) that don't support the new schema (such as the standard map displayed on osm.org, unfortunately) would display the platforms (which is more useful to people looking at the map, because only then it is visible which bus stop is on which side of the street) and renderers that do support the new schema could ignore that tag anyway. Furthermore, if I ignore how the nodes are actually rendered ("Don't tag for the renderer") tagging the platform as The only reason (that I could find) for putting the If someone knows a good reason why EDIT: The sections in the wiki I refer to are Tag: |
|
Just go ahead and tag the platform highway=bus_stop and additionally public_transport=platform. The wiki has a conceptual pitfall. It often sounds normative, but it isn't, simply because it can be changed all the time. A look on the taginfo makes clear that tagging highway=bus_stop by far outweights any of the more complicated tagging schemes. Moreover, there is common sense that the 2010 proposal covers the broadest possible consent. It says in particular "The proposed tags can and do coexist with the well known tags. The usage of the new tags is recommended but not mandatory.". It then explains that the node beside the street should be tagged highway=bus_stop. The misinterpretation of putting highway=bus_stop on the node did happen so often in the past that it got its own interpretation and was the main driving force to invent a new, distictly different set of tags, tagging both. If there are any wiki pages suggeesting to tag highway=bus_stop, in particular on the street, I would be happy for a hint such that they can be corrected to be in line to the 2010 proposal. Thanks for your answer. I added links to the two pages I refered to at the end of the question. I'd be glad if you could correct them so that they don't contradict the approved proposal anymore.
(27 Jul '12, 17:50)
dhf
|
|
This is an often discussed item, not helped by the various public transport proposals, and the translation from language to language and back again. The Common Usage on the page you mention above, is what you are proposing to do and what has always been most common practice in the UK (even before the bus stops were imported in several areas as nodes either side of the way). I don't think I've ever knowingly encountered a highway=platform node. And as you point out, anything which uses the new public_transport=* tagging shouldn't need to look at the highway=tags, so there is no problem with having highway=bus_stop and public_transport=platform on the same node, which combines the common current usage with the new tagging scheme. Note though that a few European cities have adopted the old highway=platform to the side of the way, highway=bus_stop in the way tagging scheme and if you are tagging in one of those areas there is a chance local mappers might retag what you add to bring it in line with what happens in that area. I'd perhaps ignore such changes if they happen, as life is too short to worry... |
|
Of course highway=bus_stop outweighs anything else, as that's the only tag that will get rendered. Chicken and egg. If I see a public_transport=stop_position with highway=bus_stop on it, I remove the highway=bus_stop/name/ref/etc tags. This is the node that's part of the way. Add bus=yes/tram=yes, as needed. Omit anything else. If there are no nodes either side of the road yet, I'll add them and double tag them with highway=bus_stop (to get them rendered, to hell with statistics) and public_transport=platform/bus=yes. name/ref/route_ref/operator/network/zone are put on these nodes. Recently I converted this to ref:operator/route_ref:operator/zone:operator, since there will be overlap of operators in any region near the borders. Polyglot |
Thank you for the links. I have corrected the misleading content of the wiki pages.