Re: Suggestion: Tracker API addition to getPrediction for a route to a certain lat/long

[ctaweb]

Thanks for the suggestion. We'll take it under consideration for future feature additions to the APIs.

 

 

On Friday, July 27, 2012 10:11:01 AM UTC-5, Marlon wrote:

I'm developing a tracker app and found that it would be great to be able to get a prediction result for a route/direction to a lat/lon coordinate instead of just stop ids. That way, if I have a coord for an intersecting route, I can just supply that to the API to see when a route will arrive there.  For example:

I let a user pick their route to work...The get on #80 going east bound at Cicero. Then take the Ashland bus going South.

I'm riding the #80 Irving Park bus eastbound and I want to know how long its going to take for my bus to get to Ashland. If I know the lat/long for an Ashland/Irving Park stop, I could just supply that rather than trying to determine the #80's intersecting stopid.

The API could take the supplied coord then determine the route's closet coord to the point, then return that ETA. This could be immensely helpful and simplify a pretty handy use case.