Closed mpadge closed 1 year ago
That commit adds most of the functionality. It just needs to be switched on by:
m4ra_gtfs_traveltimes()
to determine whether or not to do these extra calculations.gtfs_next_intervals()
function.And that should do it.
Note that the above commit resolves the issue of some trip intervals being negative. Those are actually not a bug, but reflect instances where exclusion of initial trips leads to routing on subsequent trips which leave earlier overall, yet involve more transfers so are not picked up in the initial scan.
Re-opening to incorporate the output of the GTFS function, which is part of the pre-calcualtion routines, into the output of the main multi-modal travel times functions.
Current ˋm4ra::m4ra_times_multi_modeˋ function returns single fastest time in specified internal. This should be extended to run just the GTFS part starting at just after the fastest service, and returning the time internal between the two as an indicator of service frequency.