Hi Anton,<div>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.</div><div><br></div><div>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?</div>
<div><br></div><div>With GTFS data, we get the following information about a route:</div><div>1. Locations of stops visited(thus, straight line distance),</div><div>2. Sequence of stops visited(used for Non-scheduled routing),</div>
<div>3. Trip timetable(used for scheduled routing, optional),</div><div>4. Frequency of trips(used for Non-scheduled routing)</div><div><br></div><div>Fare attributes are also in the GTFS specification but I cut it down because of the complexity involved.</div>
<div><br></div><div>Am I missing storing any other information to find the ideal route?</div><div><br></div><div>Thanks &amp; Regards,</div><div>J Kishore kumar.</div><div><br></div><div>[1] - <a href="http://code.google.com/transit/spec/transit_feed_specification.html">http://code.google.com/transit/spec/transit_feed_specification.html</a></div>
<div>[2] - <a href="https://github.com/pgRouting/pgrouting/tree/gsoc-multimodal/tests/loaders/gtfs">https://github.com/pgRouting/pgrouting/tree/gsoc-multimodal/tests/loaders/gtfs</a></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
[3] - <a href="https://github.com/pgRouting/pgrouting/blob/gsoc-multimodal/tests/test_mmptr.py#L30">https://github.com/pgRouting/pgrouting/blob/gsoc-multimodal/tests/test_mmptr.py#L30</a></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8">