Hi Bjoern, Am 2017-05-11 um 12:08 schrieb Bjoern Hassler: > Basically, I'm trying to understand > https://wiki.openstreetmap.org/wiki/Relation:route#Members. There's the > concept of station vs. stop_position, in case there are many stop_positions > in a station / stop_area. Sorry for London examples, but I'm trying to get > to grips with TFL. So e.g. King's Cross is a station/stop_area, but with > multiple stop_positions (for underground, busses, main line, etc).
The wiki page Relation:route is an overview over all types of route (hiking, cycling, ferries, trains, …). In addition, the public transport part seems outdated. If you were able to read German, I would suggest you to read DE:Public_Transport which describes the current status of public transport mapping (its English counterpart is outdated, too). > In 'Members', there a node with role "stop"/"stop:n", described as follows > "A bus stop or train halt, on the route. The order of the members in the > relation should be identical to the order in the timetable. The number is > not needed to preserve the order of stops. It is only a guide to help > mappers finding missing or misplaced stops. You can use stop instead, if > you like." "stop:n" is totally outdated and was necessary at times when relations were not ordered list (AFAIK OSM API v0.5). The proposal page https://wiki.openstreetmap.org/wiki/Proposed_features/Public_Transport is AFAIK the best English documentation. Best regards Michael -- Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten ausgenommen) I prefer GPG encryption of emails. (does not apply on mailing lists)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
