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.

Sign up for GitHub

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

Jump to bottom

Implement route-by-route transfer time restrictions #922

Closed
michaz opened this issue Dec 22, 2016 · 3 comments
Closed

Implement route-by-route transfer time restrictions #922

michaz opened this issue Dec 22, 2016 · 3 comments
Labels
good first issue If you just get started with GraphHopper these issues are suited for you public transport

Comments

@michaz
Copy link
Member

michaz commented Dec 22, 2016 •
edited

Not in the GTFS standard, but for example in the VBB dataset, as a custom field.

Can be implemented completely in pre-processing, on the GTFS side, by splitting stops.
@michaz michaz added public transport good first issue If you just get started with GraphHopper these issues are suited for you labels Dec 22, 2016
@michaz michaz mentioned this issue Dec 27, 2016
Closed
@michaz
Copy link
Member Author

michaz commented Dec 27, 2016

We may need exclusions from transfer rules anyway, for #919, so maybe the two can share functionality. (Don't implement it as GTFS-preprocessing after all.)

@michaz
Copy link
Member Author

michaz commented Mar 21, 2017

https://developers.google.com/transit/gtfs/reference/gtfs-extensions#TripToTripTransfers

michaz added a commit that referenced this issue Mar 21, 2017
@michaz
Rearrange the wiring-up of stop-timelines, in preparation for #922
9e3047f
michaz added a commit that referenced this issue Mar 21, 2017
@michaz
Can split stop timelines (and now, by default, do so by route), in pr…
a760e33 
…eparation for #922
michaz added a commit that referenced this issue Mar 30, 2017
@michaz
Route-by-route transfer restrictions 1/2: works at the target of the …
958cad4 
…transfer. #922
michaz added a commit that referenced this issue Apr 10, 2017
@michaz
Insert alight-edges in preparation for #922 #923
a83f297
michaz added a commit that referenced this issue Apr 10, 2017
@michaz
Route-specific transfer rules now also work for origin of transfer. #922
89a5315
@michaz
Copy link
Member Author

michaz commented Apr 10, 2017

OK, we have route-to-route specific transfer rules. (Possible) follow-up feature: Trip-to-trip specific, but that would require some more work. Route-to-route can be done simply, because a station can simply be divided into route-specific "platforms", which is not that expensive. But for trip-to-trip, we would really have to calculate.

@michaz michaz closed this as completed Apr 10, 2017
michaz added a commit that referenced this issue Apr 10, 2017
@michaz
Route-specific transfer rules now also work for origin of transfer. #922
730595d
michaz added a commit that referenced this issue Apr 10, 2017
@michaz
Insert alight-edges in preparation for #922 #923
547e78d
michaz added a commit that referenced this issue Apr 10, 2017
@michaz
Route-specific transfer rules now also work for origin of transfer. #922
2232b25
michaz added a commit that referenced this issue Apr 14, 2017
@michaz
Insert alight-edges in preparation for #922 #923
0156bab
michaz added a commit that referenced this issue Apr 14, 2017
@michaz
Route-specific transfer rules now also work for origin of transfer. #922
2bf983f
michaz added a commit that referenced this issue Apr 14, 2017
@michaz
Insert alight-edges in preparation for #922 #923
2fa346f
michaz added a commit that referenced this issue Apr 14, 2017
@michaz
Route-specific transfer rules now also work for origin of transfer. #922
deb589d
michaz added a commit that referenced this issue Apr 14, 2017
@michaz
Insert alight-edges in preparation for #922 #923
d067df9
michaz added a commit that referenced this issue Apr 14, 2017
@michaz
Route-specific transfer rules now also work for origin of transfer. #922
75e2624
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue If you just get started with GraphHopper these issues are suited for you public transport
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michaz