No subject

>
itinerary if you don't have all the information locally; you either hav=
e<br>
to make a lot of guesses or produce a ton of network traffic. Also,<br>
consider the one-to-many or many-to-many cases common in research and<br>
planning work (yes, public transport data are useful for many other<br>
things besides passenger information). An operation that would require<br>
millions of individual requests to a point-to-point journey planning<br>
APIs might only require a single search if we have the data locally.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-Andrew<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
open-transport mailing list<br>
<a href=3D"mailto:open-transport at lists.okfn.org">open-transport at lists.okfn.=
org</a><br>
<a href=3D"http://lists.okfn.org/mailman/listinfo/open-transport" target=3D=
"_blank">http://lists.okfn.org/mailman/listinfo/open-transport</a><br>
Unsubscribe: <a href=3D"http://lists.okfn.org/mailman/options/open-transpor=
t" target=3D"_blank">http://lists.okfn.org/mailman/options/open-transport</=
a><br>
</div></div></blockquote></div><br><br>
</div></div>

--089e0116026ab36f8304e1c96c43--