Re: [Talk-transit] New proposal to store public transport data

2011-01-25 Thread Richard Mann
See http://www.openstreetmap.org/browse/node/533877725 for a not untypical NaPTAN bus stop ref is on a plate on the stop (and is the numerical equivalent of the Naptan Code) local_ref is on a plate on the stop, and is used to tell adjacent stops apart My guess is that there are various coding

Re: [Talk-transit] New proposal to store public transport data

2011-01-24 Thread Oleksandr Vlasov
Michał Borsuk michal.borsuk at gmail.com writes: Continuing on How routing software works (and why OSM as-is is not ready for routing): Hello, makes perfect sense, assuming OSM is mapping, not routing project and some other layer will be needed for the routing. Just a small set of

Re: [Talk-transit] New proposal to store public transport data

2011-01-24 Thread Michał Borsuk
On 01/24/2011 03:04 PM, Oleksandr Vlasov wrote: Michał Borsukmichal.borsukat gmail.com writes: Just a small set of questions: 1. As I can see, currently stop-on-a-way is the preferred approach for mapping tram stops. Do you propose to map tram stops like bus ones, i.e. beside the way? I'd

Re: [Talk-transit] New proposal to store public transport data

2011-01-24 Thread Dominik Mahrer (Teddy)
On 01/24/2011 07:24 PM, Michał Borsuk wrote: On 01/24/2011 03:04 PM, Oleksandr Vlasov wrote: 3. bus_stop already defines `ref' tag, will proposed `stop_id' be something different? ref= on a bus stop? That's news to me (sadly). I used stop_id=, but the mess probably comes from the fact that

[Talk-transit] New proposal to store public transport data

2011-01-23 Thread Michał Borsuk
Continuing on How routing software works (and why OSM as-is is not ready for routing): Coming back to the mapping of bus lines in OSM: you can see now that what is presented to the user, as in the example before (the PDF http://tisseo.fr/sites/default/files/Tisseo_hiv16web.pdf), is a