Open GoogleCodeExporter opened 8 years ago
I think this kind of functionality is very valuable to riders. However, I'm
unconvinced that incorporating this information into the transit feeds is the
right way to provide it. This puts the responsibility for maintaining this
extra POI data on transit agencies.
There are already a number of ways POI information is gathered so that it can
be displayed as a part of integrated geographic information. There's not a
good technical reason I can think of that it can't be integrated into the
applications use to access transit information without adding it to the transit
feeds.
Original comment by justinca...@google.com
on 11 Mar 2011 at 8:23
The intent is not to publish POI but to make POI available for a routing
request.
Example, you request a route for a trip by transit from work to a meeting 5
miles away. You want to pick up lunch along the route that is returned, What
restaurants choices are available with in a 15 minute walk along the route.
The prefered return would be 15 minutes walk radius searches for stops along
the route for restaurants.
This data would be provided not by transit agencies but available to tranist
riders from a search on the website for a transit routing.
Another example:
you are traveling from Las Vegas Nevada to Dallas Texas and you want to see
HISTORIC points of interest along the route within a 2-5 mile area from the
returned route.
so what you get is a search for POI of historical interest within a 5 mile
buffer of the returned route.
Ideally how it woudl present:
you do a search like normal, you get a few alternatives routes
You pick one and in showing you that route you get an option to search POI
It uses your returned route as a buffer to find POI that fit
If transit, the search is from bus stops and searches are related to walking
times
if it is by walking, it is a buffer from the walking route in terms of walking
times
If it is by car, it is a buffer from the traveled route and in terms if driving
distance or driving time from the route...
Is that clearer?
Original comment by sql_ale...@rtcsnv.com
on 11 Mar 2011 at 9:42
Original issue reported on code.google.com by
sql_ale...@rtcsnv.com
on 22 Feb 2011 at 10:00