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

🧹 Chore: TAZ transit network - revise KNR connections #120

Open
3 tasks
i-am-sijia opened this issue Jul 26, 2023 · 0 comments
Open
3 tasks

🧹 Chore: TAZ transit network - revise KNR connections #120

i-am-sijia opened this issue Jul 26, 2023 · 0 comments
Labels
chore overhead: doesn't add additional functionality, change performance, or refactor code

Comments

@i-am-sijia
Copy link
Collaborator

i-am-sijia commented Jul 26, 2023

This is really a Lasso issue, but I'm creating it here for the moment.

The link 21 way of creating KNR connections is as follows:

  1. KNR nodes are created by offsetting the rail/ferry stops & the non-DTSF express bus stops
  2. KNR links are created between the KNR node and the transit stop. The yellow "k" links in the screenshot below.
  3. Drive links are created between the KNR node and the closest drive street node. The black "cDwb" links connecting the KNR nodes to the street network.

image

Proposal & Question: why do we need to create KNR nodes? why not just flag the closest street nodes as KNR nodes?

Progress:

  • Sufficiently defined
  • Approach decided
  • Implemented

Considerations

why do we need to create KNR nodes? why not just flag the closest street nodes as KNR nodes?

@i-am-sijia i-am-sijia added the chore overhead: doesn't add additional functionality, change performance, or refactor code label Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore overhead: doesn't add additional functionality, change performance, or refactor code
Projects
None yet
Development

No branches or pull requests

1 participant