search

opentripplanner / OpenTripPlanner

An open source multi-modal trip planner
http://www.opentripplanner.org
Other
2.18k stars 1.02k forks source link

Analyst API method that takes arbitrary list of points #863

Closed abyrd closed 3 years ago

abyrd commented 11 years ago

Users often want isochrones as an intermediate step to some other goal. It would be more accurate and make better use of OTPs capabilities to return travel times (or transfers or whatever once we have pluggable evaluators) to an arbitrary set of endpoints.

We would want the endpoint sets to persist to allow fast re-evaluation, so endpoint sets would be a generalization of tiles. This would mesh nicely with the batch analyst idea of populations, making it possible to do batch runs against an OTP server. (#866)

Ideally this API method would be an HTTP GET message with a body, but the world seems to disagree on whether that exists.

We could potentially allow POSTing data sets (which would return a data set token). This would make the server stateful from a user perspective which is not necessarily a good thing. Then again, it's more predictable than just hoping your data set gets cached.

abyrd commented 11 years ago

depends on #866

abyrd commented 9 years ago

We've already made a lot of progress in this direction, see Pointsets and Time Surfaces. In order to quickly perform multiple requests and combine them, the server needs to hold on to SPTs. Rather than sending the same routing query parameters over and over e.g. for each isochrone tile, we send them once and get a name for the resulting SPT. This reveals the inherently stateful nature of the operation to the user: retained SPTs are visible as "documents" in the web API, and the server should take care of re-generating them if and when they are evicted.

abyrd commented 3 years ago

This has been created in OTP 1.x, and exists in successor analysis project R5 as FreeformPointSets. Closing.