On 04.10.2010 11:09, Peter Miller wrote:
On 2 October 2010 05:28, Michał Borsuk <[email protected] <mailto:[email protected]>> wrote:2010/10/1 Jo <[email protected] <mailto:[email protected]>> [...] I'm pretty sure that if one gets the PT companies to share their data, it's not going to be in there with child relations. Usually (e.g. HaFas) timetables consist of a number of routes, and those are very detailed, each direction is mapped separately, and e.g. if a bus ends its day not at the terminus, then it's yet another route. This approach is easier to store in a database, but is in my opinion that one step too detailed for humans to manage in OSM. It would apparently make sense to make a collection named "line 123", and store child routes withing that collection, but as of today there is no efficient way to deal with this. Transmodel breaks public transport routes down into the following: [...] More here for brave people http://en.wikipedia.org/wiki/TransmodelPersonally I suggest that we limit the transit information in OSM to the minimum and leave the detail in GTFS. Personally I would like someone to create a bus-map application using OSM together with GTFS schedules - doing that would remove a lot of the pressure to model public transport in OSM.
I am for it too. There is simply too much information to deal with. I'd stick to the traditional model: graphical route display+route number.
Therefore I skip lines which aren't regular ones in the traditional sense, e.g. a collection of different routes under one number, school buses and other which run few times a day, collective taxis etc.
-- Best regards, mit freundlichen Grüssen, meilleurs sentiments, Pozdrowienia, Michał Borsuk
_______________________________________________ Talk-transit mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-transit
