validator rule for public_transport=platform

[Polyglot]

I'm getting messages from the validator claiming public_transport=platform can only be used on way or closed_way. This is not true. It can be used perfectly well on nodes. In that case the node represents the position of the pole. I just checked it on the wiki.

​http://wiki.openstreetmap.org/wiki/Buses

All the poles of Belgian transport companies De Lijn, TEC and MIVB/STIB are mapped on nodes. If there is a platform, it is mapped, but that doesn't replace the pole, nor does it get added to the route relations. All the extra details like name, ref, route_ref etc also remain on the node representing the pole. The platform ways and the stop_positions are optional. Nice to have, but not at all crucial. The NODES with

highway=bus_stop
public_transport=platform
bus=yes

railway=tram_stop
public_transport=platform
tram=yes

are what define the bus/tram stops over here and those get the details and those get added to the route relations.

So please correct the validator rule.

Kind regards,

Polyglot

[Klumbumbus]

I do not get this warning. Please doublecheck and attach Status Report and sample .osm file.

[Polyglot]

How embarassing. I had forgotten to set the platform role.

Jo

[Polyglot]

However the message of that validator rule is misleading. Instead of saying 'role missing' it says: object must be way or closedway.

Jo

[Klumbumbus]

Yes, because the validator thinks that an object without role is a route segment. And for route segments nodes are not allowed. So the validator schould check if a member without role has the tag public_transport=platform or not and then display "...missing role..." or "...wrong object type..."!? (same for the other roles)

[simon04]

How to reproduce (can you add an example)? When adding a public_transport=platform railway=tram_stop tram=yes node to a PTv2 route relation with an empty role, I get "Role member type node does not match accepted list of way/closedway in template Public Transport Route".

[Polyglot]

I'm not getting this warning anymore. I just tried it.