Option to separate ridehail skims by accessibility requirements #26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 tasks
7 tasks
This reverts commit 87c7356.
Post processing update
# Conflicts: # run.py # settings.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If we add the ACCESSIBLE tag to the
ridehail_path_mapin the settings.yaml filePILATES should now look for an extra index column in the ridehail skims (here named
wheelchairRequired) that is true/false for whether that skim is for a ridehail request requiring wheelchair access.Should also work fine with old skims if this line isn't added to the config.
DO NOT MERGE: Still needs to be tested