railway station as node
Closed almost 6 years ago by axelr
railway=station only as node
Ok, but tags scheme public_transport not need to move to a node.
Often we have both: The way as railway. And the vehicle to transport people as public_transport.
It is not correct and right to map railway stations as ways. There are multiple definitions about the extend of a railway station. While passengers say that it is the area formed by the platforms and the building, railway staff says that it is even more (parallel freight tracks etc.).
Mapping stations as nodes is a compromise to satisfy both people mapping the passenger perspective and railway staff/fan perspective. Railway fans/staff can add a operation site relation (https://wiki.openstreetmap.org/wiki/OpenRailwayMap/Tagging#Operating_Site_.28Relation.29) and public transport mappers can add a polygon with public_transport=station or can create a stop area relation (type=public_transport, public_transport=stop_area). Data users can decided which perspective they want to follow and calculate an convex hull around the members of stop area relations (Transport Map already does some fancy stuff like that).
Каргаполье (https://www.openstreetmap.org/way/282744496) is wrong because there is building=train_station to tag station buildings and because the railway station is much larger than the building footprint.
I hereby ask you, freeExec, to revert your revert and discuss such modifications in advance. Just reverting someone else's work is not friendly and not welcomed if (happened in this case) you remove someone's correct data (you removed railway=stop from https://www.openstreetmap.org/node/286108552/history – this is not correct).
(railway mapper and co-developer of OpenRailwayMap)
Returned. But now in the railway=station no more sense than the label on mapnik
Log in to join the discussion
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by UCL, Fastly, Bytemark Hosting, and other partners.