-
Notifications
You must be signed in to change notification settings - Fork 1
[amenity-points] Support for the public transport scheme #4381
Comments
Author: marl increased priority after comparing it with other items on the Mapnik wish list |
Author: Seoman See ticket #4685, too |
Author: rohieb
As a simple mapping from the "old" schema to the [https://wiki.openstreetmap.org/wiki/Proposed_features/Public_Transport "new" schema], I would suggest the following:
To be honest, I never understood the rendering distinction between bus stations and railway stations, so in my opinion everything tagged with |
Author: Polyglot What about nodes tagged with public_transport=platform/bus=yes? It could, of course, be that I misunderstood, but that is what I would substitute for highway=bus_stop on nodes next to the way to indicate where the passengers wait. This is also the node which gets all the supplementary information like name, ref, route_ref, zone, operator, etc. It's the only node I'm adding to the route relation. public_transport=stop_position/bus=yes is where the bus stops. This is a node which is part of the highway. It should be rendered with a lower priority than public_transport=platform nodes. They are far less important and when I map them, it's only because this new scheme mentions them. |
Author: rohieb Replying to [comment:7 Polyglot]:
Okay, I have more of an analytic view on things ;-) For the end users of OSM, it's probably really better to render the platforms, not the stop positions, so they know where to go when waiting for a bus.
As a side note, please add the stop positions to the [https://wiki.openstreetmap.org/wiki/Proposed_features/Public_Transport#Route route relation] as well. Also, if you have a [https://wiki.openstreetmap.org/wiki/Proposed_features/Public_Transport#Stop_area stop_area relation] (which is mandatory in the new schema, as I understand it), all the name, ref, operator, network etc. can/should go in there as well. The stop_position nodes and the stop_area relations really simplify public transport routing on OSM data. The stop positions are needed to know the position of the platform on the way (if they do not exist, we're back to the old schema and have to interpolate from the platforms, which does not give a unique guess every time), and the stop areas aggregate several platforms to a "station", and provide the information where it is possible to switch to another bus line. |
Author: kocio Is it possible to resolve this ticket now, when we made the transition to the new CSS (as I understand [https://help.openstreetmap.org/questions/19349/rendering-of-public_transportplatform-on-mapnik this question] it should be simpler now)? |
Author: math1985 Yes, it should be easier to implement now. However, there is still a backlog of about 500 issues, so I can't guarantee how quickly it will be solved. The home of the new style is https://github.com/gravitystorm/openstreetmap-carto/. If you don't want to wait, you could submit a pull request that adds the new tagging. |
Author: Mateusz Konieczny This issue is now being discussed on Github: gravitystorm/openstreetmap-carto#311 Therefore, I will close the issue here. |
Reporter: marl
[Submitted to the original trac issue database at 8.27pm, Friday, 27th April 2012]
After more than a year, Mapnik should become aware of the new public transport scheme.
There seem to be two problems in particular:
"stop" role members placed on railway tracks
members tagged "train=yes"
The text was updated successfully, but these errors were encountered: