Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split isochrone into isochrone + isotrips functions #58

Closed
mpadge opened this issue Nov 26, 2020 · 1 comment
Closed

Split isochrone into isochrone + isotrips functions #58

mpadge opened this issue Nov 26, 2020 · 1 comment

Comments

@mpadge
Copy link
Member

mpadge commented Nov 26, 2020

Following on from discussions in #56 & #57, the current updates to the isochrone function effectively (only) return the best isotrip to each end station. There may have been several candidate trips along other routes, but the eventual selection of a single best route effectively drops these intermediate stations, leaving the midpoints objects containing only a restricted subset of all stations which were actually visited on the way to calculating the isochrone.

In effect, the current version generates some more like "isotrips", representing the single fastest trips out to each end station, and only those midpoint stations visited along the paths of these single best trips. This could be exposed in a few isotrips() function, while the isochrone function itself could return a structure similar to the current version, except which contains all midpoint stations visited along the way, along with associated statistics.

@mpadge
Copy link
Member Author

mpadge commented Mar 4, 2021

Closing now, because the whole isochrone function(s) will be deprecated anyway, to be replaced by the new gtfs_traveltimes() function.

@mpadge mpadge closed this as completed Mar 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant