mark padgham

Wow, yeah, a royal nightmare, but looking strong! I'm going to leave this issue and #1 for sometime in the hopefully not-too-distant futures. Functionality is plenty enough to plough on...

Algorithm now translated entirely to C++ (see #14, #59), making it over 10 times faster, and meaning all work on `gtfs_transfer_table()` is now finished and can be written up as...

Madrid has a "transfers.txt" table, as do the Warsaw data used by @stmarcin and discussed in #24. These can - and should - both be used as examples to develop...

hey that's great @stmarcin - it would be even better if you wanted to do it as a PR here. You could initially do it as a stand-alone function, and...

Closing because @stmarcin added this functionality via #25 - thanks!

Re-opening this issue to re-implement the entire frequencies-to-stop-times routine in C++. Finally found a feed which is almost entirely based on "frequencies" tables (Santiago, Chile), and the routines from #25...

https://multigtfs.readthedocs.io/en/latest/gtfs.html#frequencies-txt-frequency - that's the closest thing i can find for an appropriate reference on the exact relationship between "frequencies.txt" tables and values given in "stop_times.txt": > When trips are defined...

@rafapereirabr sorry for delayed response: No, it is not possible to run `gtfs_traveltimes` on a feed without a `transfers.txt` table. What i will do is to make sure that is...

Thanks for the input @luukvdmeer - that is in fact also what `gtfsrouter` does via the above code which generates extended transfer tables via the `gtfs_transfer_table` function. The start and...

Re-opened in response to the `r5r` issue linked to above, and in order to clearly document why `r5` and `gtfsrouter` ought not be expected to give identical results. @luukvdmeer thanks...