Opened 6 years ago

Closed 4 years ago

#4381 closed enhancement (duplicate)

[amenity-points] Support for the public transport scheme

Reported by: marl Owned by: mapnik-team@…
Priority: major Milestone: Wishlist
Component: mapnik Version:
Keywords: Cc: SDavies, Ravu, al, Hemio, gnurk, tfischer

Description

After more than a year, Mapnik should become aware of the new public transport scheme.

There seem to be two problems in particular:

  1. railway stations seem not to show up. As it is not easy to find out what exactly to render, I propose to show at least public_transport=station in the way railway=station is displayed now. Of course, approaches may be more sophisticated, for example showing stop_areas with one of these:
  • "stop" role members placed on railway tracks
  • members tagged "train=yes"
  1. public_transport=platform is not drawn at all, leaving stations looking funny. Only highway=platform and railway=platform are displayed.

Change History (13)

comment:1 Changed 6 years ago by marl

  • Priority changed from minor to major

increased priority after comparing it with other items on the Mapnik wish list

comment:2 Changed 6 years ago by SDavies

  • Cc SDavies added

comment:3 Changed 6 years ago by Ravu al Hemio

  • Cc Ravu al Hemio added

comment:4 Changed 6 years ago by gnurk

  • Cc gnurk added

comment:5 Changed 5 years ago by Seoman

See ticket #4685, too

comment:6 Changed 5 years ago by rohieb

As it is not easy to find out what exactly to render […]

As a simple mapping from the "old" schema to the "new" schema, I would suggest the following:

  • nodes tagged with public_transport=stop_position, {tram|monorail}=yes to be rendered like railway=tram_stop or railway=halt (a little blue square on the rail with the name above it)
  • nodes tagged with public_transport=stop_position, {subway|light_rail|train}=yes to be rendered like railway=station (a bigger blue square on the rail with the name above it)
  • nodes tagged with public_transport=stop_position, {bus|trolleybus=yes to be rendered like highway=bus_stop (a little blue bus icon on the road)
  • ways tagged with public_transport=platform to be rendered like highway=platform (with no distinction between bus platforms and railways platforms)

To be honest, I never understood the rendering distinction between bus stations and railway stations, so in my opinion everything tagged with public_transport=stop_position could be rendered as a blue square on the way.

comment:7 follow-up: Changed 5 years ago by 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.
They are not totally useless though. I wrote a python script a few days ago, which works inside JOSM. Starting from a public_transport=platform this script is capable to determine the correct road that needs to be added to the route relation by searching for the nearest stop_position.

comment:8 in reply to: ↑ 7 Changed 5 years ago by rohieb

Replying to 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.

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.

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.

As a side note, please add the stop positions to the route relation as well. Also, if you have a 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.

comment:9 Changed 5 years ago by tfischer

  • Cc tfischer added

comment:10 Changed 4 years ago by math1985

  • Summary changed from Support for the public transport scheme to [amenity-points] Support for the public transport scheme

comment:11 Changed 4 years ago by kocio

Is it possible to resolve this ticket now, when we made the transition to the new CSS (as I understand this question it should be simpler now)?

comment:12 Changed 4 years ago by 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.

comment:13 Changed 4 years ago by Mateusz Konieczny

  • Resolution set to duplicate
  • Status changed from new to closed

This issue is now being discussed on Github: https://github.com/gravitystorm/openstreetmap-carto/issues/311 Therefore, I will close the issue here.

Note: See TracTickets for help on using tickets.