When I look at how PT is mapped according to what they consider to be v2 of
the public transport scheme, I notice a few problems.

The first is that details about the stops is sometimes mapped on the
stop_position node, sometimes on the platform, which can be a way or a node.

As far as I'm concerned a platform (way), a shelter, a bench, a waste
basket are all attributes of a stop. At some point the wiki said to map the
pole as platform, so I went ahead and did that. Each and every pole is now
mapped on a node next to the way:

highway=bus_stop (for rendering, tried to lose it, won't ever render)
public_transport=platform
bus=yes
name
ref
operator
network

Now I find that public_transport=stop_position is getting highway=bus_stop.
Where I'm mapping PT, not all stop_positions are present (yet). Adding
65000 bus stops on nodes next to the way, was enough work without trying to
make it twice as hard to accomplish.

In retrospect public_transport=platform was a misnomer. Maybe we should
have used public_transport=pole.

Anyway, the attempt to clear up the distinction between mapping stops next
to the road and as a node on the road has failed utterly, now all seems to
be done twice, which is a total waste of time.

My problem is that when I'm adding stops as nodes in Germany and put the
details on there, those nodes get cleared/removed. I can reinstate them,
but it won't stick, so it's futile to do so.

At some point I thought that starting to include the platform ways to the
background database would help, but that's not the case if the details are
mapped on the stop_position nodes.

The stop_area relations combine both directions, That's useless. I don't
know who abolished stop_area_group, But what good are these stop_area
relations if they don't help to relate an individual platform with a
stop_position?

Polyglot
_______________________________________________
Talk-transit mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-transit

Reply via email to