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

Initial populating of Base Year and Year 2015 Fixes #1

Merged
merged 70 commits into from
Mar 14, 2022
Merged

Conversation

DavidOry
Copy link
Collaborator

@DavidOry DavidOry commented Oct 6, 2021

No description provided.

@DavidOry DavidOry marked this pull request as draft October 6, 2021 19:49
@DavidOry DavidOry marked this pull request as ready for review October 8, 2021 19:00
@DavidOry
Copy link
Collaborator Author

DavidOry commented Oct 8, 2021

@lmz, @FlaviaTsang, @i-am-sijia

I have completed a first pass at uploading and re-organizing the Project Cards. A few notes:

(1) In thinking ahead to the creation of a 2018 or 2020 or 2025 network, there are certain corrections that we'll want to make across base years. For example, the configuration of the bridge toll plazas and the coding of the managed lanes. I have put these types of changes in folders with a base_year prefix.

(2) Other fixes are specific to 2015, specifically the transit fixes that adjust the routing for 2015. Because we have improved our routing algorithm, these fixes will likely not be applicable when y'all create another base year network.

(3) The roadway fixes are a bit more ambiguous. I've organized them into a year_2015/roadway_fixes folder. It's likely that nearly all of these will be applicable in creating a 2020-ish network.

(4) A logical 2020ish network creation approach would therefore be to start with the 2015 roadway network, update any managed lanes or other known roadway changes in a new set of project cards, and then start with a new set of transit extractions. There will remain some hand-to-hand combat to get the transit fares right.

(5) @i-am-sijia: I have not changed the tags in the project cards, so we should be able to point our version_13 network build process to this repository (see this Issue).

I can walk everyone through the details of how this all works on our next bi-weekly call, though happy to address any questions via this PR in the meantime.

@lmz lmz self-assigned this Feb 28, 2022
@lmz lmz requested a review from FlaviaTsang March 9, 2022 01:59
@FlaviaTsang FlaviaTsang merged commit 0495027 into main Mar 14, 2022
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

Successfully merging this pull request may close these issues.

4 participants