This is an interesting overview. Re auto routing: one of the most important tradeoffs is speed at run-time vs. flexibility to bring in new data, such as "live"

This is an interesting overview. Re auto routing: one of the most important tradeoffs is speed at run-time vs. flexibility to bring in new data, such as "live" traffic speeds. Re public transit routing: RAPTOR (and its variants) is the most commonly used routing algorithm these days. Even though this paper says OpenTripPlanner uses RAPTOR, it did not in 2015. However, the more recent OpenTripPlanner 2.x version does now use RAPTOR: https://github.com/opentripplanner/OpenTripPlanner/releases/tag/v2.0.0 https://github.com/opentripplanner/OpenTripPlanner/releases/... The Transitland Routing API also uses a variant of RAPTOR to provide a hosted transit routing API across the entire United States: https://www.transit.land/documentation/routing-api/ https://www.transit.land/documentation/routing-api/