No subject

itinerary if you don't have all the information locally; you either have
to make a lot of guesses or produce a ton of network traffic. Also,
consider the one-to-many or many-to-many cases common in research and
planning work (yes, public transport data are useful for many other
things besides passenger information). An operation that would require
millions of individual requests to a point-to-point journey planning
APIs might only require a single search if we have the data locally.

-Andrew