Hi Anton,
Glad to see you are back. I was working with producing GTFS data over the last week and am planning to use GTFS format[1][2] tables for holding public transit topology.
Since a lot of tables are involved(like trips, routes, stops, stop_times), we cannot use the regular syntax of passing a select query as the first argument to the core routing function. Hence, I encapsulated all the tables into a Schema and pass it as the first argument[3] Will there be any problems in this case?
With GTFS data, we get the following information about a route:
- Locations of stops visited(thus, straight line distance),
- Sequence of stops visited(used for Non-scheduled routing),
- Trip timetable(used for scheduled routing, optional),
- Frequency of trips(used for Non-scheduled routing)
Fare attributes are also in the GTFS specification but I cut it down because of the complexity involved.
Am I missing storing any other information to find the ideal route?
Thanks & Regards,
J Kishore kumar.
[1] - http://code.google.com/transit/spec/transit_feed_specification.html
[2] - https://github.com/pgRouting/pgrouting/tree/gsoc-multimodal/tests/loaders/gtfs
[3] - https://github.com/pgRouting/pgrouting/blob/gsoc-multimodal/tests/test_mmptr.py#L30