Open nlehuby opened 5 years ago
Currently the standard trips creator uses a kind of standartized time table input format, with the idea to cover all possibilities. In Managua we also have frequency/interval based data, we just converted it to the timetable format with a simple script. Your proposed direct interval approach is surely a simplification, which is interesting.
Is your proposal to remove the timetable input and to replace it with the interval
approach? Or do think on supporting both? In the latter case, how do you suggest to differentiate between the two?
converted it to the timetable format with a simple script
Just for reference, you can find it here.
I think back then we went for the standard stop_times.txt
approach as the frequencies.txt
information seemed to be not fully supported by some GTFS consumers (?). There was also the idea of integrating the script into the osm2gtfs
code.
to differentiate between the two [approaches]?
I would say, if the schedule_source
key is present and set within the configuration (as e.g. for Estelí), it would use the already available standard approach. If it is not present, osm2gtfs
could automatically use the schedule information from OSM or dump default values if there is no information on OSM either as proposed in #118.
:+1: fully agreed with @ialokim:
schedule_source
is provided, use it as it currently worksinterval
and duration
tags are set in OSM, use them Very nice idea :+1:
The ci_abidjan
creator implements this and can be used a basis to add this feature in the default implementation.
We should allow the default TripCreator to work without schedule data and then generate a GTFS with a
frequency.txt
file that only uses OSM data.Even if it won't fit all needs, it will allow to create very easily a first GTFS from OSM data that could even be usable for some simple cases (long distances buses with low frequency, ferries and shuttle bus, subways with high frequency, etc)
We can use
interval
OSM tag to get the frequency : https://wiki.openstreetmap.org/wiki/Key:intervalopening_hours
to define the stop time at the first stopsduration
key (and the GTFS interpolate stop time utility) to deduce times at each stopsThe Accra creator is a good start to implement this as it already does that. Well, almost :
opening_hours
hard codedtravel_time
tag instead ofduration
andfrequency
tag instead ofinterval
interval
tag is not supported