It should be feature-complete, but can otherwise be _completely_ naive, like having a list of all current issues next to the real graph and looking at it at every node.
Then start optimizing from there.
Skipping stops is now working.
Next: Delays, including missing transfers.
With that, I would call it a viable prototype already.
Hello @michaz! Are there any updates on this. We are looking to use graphhopper as our routing solution, but we would like to implement realtime-gtfs data.
Thanks!
Next: Delays, including missing transfers.
This works as of yesterday. On at least one dataset. ,-)
Awesome! Do you have any documentation on how to use a real-time GTFS feed? Would love to implement it!
@AAAstorga Wow, thank's for your interest! :-) At the moment, I can only refer you to the trimet branch, which is the test instance I am developing here.
Totally alpha (do not take the performance seriously, the thing currently polls the real-time feed from the operator _per request_!), but perhaps a starting point if you're going to set up your own instance?
This is now feature-complete, up to lots of testing and verifying that all features work in both search directions and such.
Continue in individual issues.
Wow, congrats :+1: !
This is awesome! Is there any documentation on how to use it?
Woo!
Most helpful comment
This works as of yesterday. On at least one dataset. ,-)