[Talk-transit] Public Transit Timetables Proposal

[Noémie Lehuby]

Hi, 

In Accra, we have added frequency and duration information on bus route
relations, and we were able to create a GTFS for the network using only
OSM data. So I would very much vote for a proposal to add these optional
tags on route (or even route_master) relations : the frequency tag would
be useful to create better transport map, and for very regular networks
(such as subway ones), both tags could allow to create full transport
data with computed timetables. 

But I don't think it is reasonable or even desirable to go beyond this.

Have you considered OSM2GTFS [1] ? it allows to create a GTFS by using
OSM for the geographical part, and some "simple" json files for the
schedule information. 
It seems to me that it would be easier to manage this way. 

Small question: I don't understand why ferry routes are not handled just
like any other routes ? 
They should have their route_master and their route relations for each
direction. 

nlehuby 

Le 2018-11-02 13:01, talk-transit-request at openstreetmap.org a écrit :

> Date: Thu, 1 Nov 2018 19:03:22 -0400
> From: Leif Rasmussen <354lbr at gmail.com>
> To: talk-transit at openstreetmap.org
> Subject: [Talk-transit] Public Transit Timetables Proposal
> 
> Hi everyone,
> I recently sent an RFC to the tagging list about a new public transport
> timetables proposal.  Does anyone here have any suggestions for improving
> the proposal?
> 
> The proposal has three parts:
> 
> 1) A new tag, "interval", for describing how often trains or buses run on a
> route.  Added to the route relation.
> 
> 2) A new set of tags to add to a ferry route that will provide complete
> timetable data for both directions.  This is very useful for navigation
> applications using OSM data.
> 
> 3) A new type of relation that will contain both a platform and a route
> relation as members, and have the tag "departures"="<departure times for a
> single route at a single platform>".  This new relation is easy to remove
> (in case it is outdated and wrong) and does not affect existing OSM transit
> data.  Each timetable relation is basically a separate "file" that contains
> a timetable, a route, and a stop.
> 
> Example timetable relation:
> *  https://www.osm.org/relation/8873463
> 
> Wiki page for the proposal:
> *  https://wiki.osm.org/wiki/Proposed_features/Public_transport_schedules
> 
> Thanks,
> Leif Rasmussen
 

Links:
------
[1] https://github.com/grote/osm2gtfs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-transit/attachments/20181102/302887a6/attachment.html>