[Open-transport] Trnsprt.ch

Tue Oct 23 22:55:42 UTC 2012

On 10/24/2012 12:36 AM, Hannes Gassert wrote:
> I agree with you that when paging comes into play then things get less
> clear, no doubt about that. But how to identify unique individual
> connections and still have easy to understand URLs is not obvious yet
> to me - $from+$to+$time just is not unique.
>
> So what's OTP's solution for that?

Hi Hannes,

Currently OTP trip planning requests use query strings like:

http://ride.trimet.org/prod?maxTransfers=3&_dc=1351032237494&from=&to=&arriveBy=false&time=12%3A43%20am&ui_date=10%2F24%2F2012&mode=TRANSIT%2CWALK&optimize=QUICK&maxWalkDistance=840&date=2012-10-24&toPlace=45.498879%2C-122.636012&fromPlace=45.546987%2C-122.659358

They are not made to be particularly compact or human-readable so I 
think this is not what you are after. Pieter was referring to a 
different comment I made last weekend. Since several open source trip 
planners have appeared, I was thinking we should avoid fragmentation and 
attempt to standardize on a minimum trip planning API that all systems 
could support to promote interoperability among clients and trip planner 
engines. This would include not only URIs but the response structure.

Is anyone interested in participating in such an effort?

We are hoping to organize a European open source / open data-driven trip 
planning meetup in the first quarter of 2013, which could be a good time 
to work on such a standard.

-Andrew