Open laurentg opened 8 years ago
This should be made optional as for some input data (many stations with many stops) the generated data can grow quite large.
Another idea is to "generate" those virtual transfers at the DAO or service layer, with query functions that automatically generate missing transfers according to those expansion rules.
(Extract from WIKI GTFS' model)
Proposal: expansion of transfers
In GTFS, a transfer that is defined for a station will apply, if not redefined, to all the station stops. A proposal to GTFS' is to expand any station transfer to sub-stops, if a transfer is not already redefined for the stops.
Goal: to provide for the API user an easy access of transfers between stops w/o having to check for transfers between stations. The check/load sequence can be rather complex (stop to stop, stop to station, station to stop, station to station...)
For example let's assume we have station A with stops A1 and A2, and station B with stops B1 and B2, and the following transfers:
The transfer expansion process would expand to the following: