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

How can transfer times be included when calculating travel times? #181

Open
FlorianNachtigall opened this issue Jul 1, 2023 · 0 comments

Comments

@FlorianNachtigall
Copy link

Motivation: I would like to calculate realistic average travel times across the transit network to calculate meaningful closeness and betweenness centrality measures.

Issue: For realistic travel times, I need to consider the transfer times. However, with the current implementation I believe it is not possible to determine whether a transfer is needed between edges that are connected by the same node (stop_id). With other words, the information whether two adjacent edges belong to the same actual route or not is lost.

Approach: My initial idea was to increase the length (travel time) of walking edges by the average boarding_costs of adjacent nodes. However, for edges that connect the same node but in reality belong to different routes / transit lines, no walking transfer edges are added to the network and consequently transfer times are not included with my approach included.

So, how would you propose to include the transfer times when calculating travel times and centrality metrics?

Thanks, happy about any suggestion!

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