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

Enforce flow of traffic stops #17

Open
Zebreu opened this issue Apr 7, 2022 · 0 comments
Open

Enforce flow of traffic stops #17

Zebreu opened this issue Apr 7, 2022 · 0 comments
Labels
enhancement New feature or request request solver This involves the optimization routines

Comments

@Zebreu
Copy link
Collaborator

Zebreu commented Apr 7, 2022

BACKGROUND: The routes could only collect down the right side of the street.
REQUEST: The optimization would account for road type (OSM data) and enforce right-side-of-the-road collection for Highways, but not for “lesser” street types.

Resequencing is affected, which is a post-processing trick we use so the nodes are reordered to avoid having a driver pass in front of a house without stopping on the first pass as this was a user request (only relevant when a driver goes both ways through a road segment, e.g. a dead end). We will need to keep track of which nodes land on a highway in the build_time_dist_matrix.py, tag them as “approaches=curb” in osrm requests, and not resequence these nodes in optimization.py. Resequencing is toggle-able as well in case the user does not need it. Implementation might take some time (a few days?) but is likely to succeed.

@Zebreu Zebreu added enhancement New feature or request request solver This involves the optimization routines labels Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request request solver This involves the optimization routines
Projects
None yet
Development

No branches or pull requests

1 participant