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

Encode directionality into FLOW counts #27

Open
cczhu opened this issue Dec 3, 2019 · 0 comments
Open

Encode directionality into FLOW counts #27

cczhu opened this issue Dec 3, 2019 · 0 comments
Assignees
Labels
inputdata miniproject Work self-contained enough to be treated as small projects

Comments

@cczhu
Copy link
Contributor

cczhu commented Dec 3, 2019

Currently, prj_volume.uoft_centreline_volumes_output uses a grid angle system to delineate traffic direction, where +1 roughly reflects north and eastbound and -1 roughly reflects south and westbound. This is difficult to parse back into road directions eg. on the directional centreline for routing purposes. We need to replace this system with one that allows us to easily determine which direction along a road each count represents, which would let us calculate traffic upstream and downstream from a point.

One possible solution would be to associate each count with the directional centreline. It might also make sense to be able to map counts to the system we use to calculate network distances. @radumas would have a much better sense of an ideal solution.

Regardless of the solution, it could be done by modifying the arterycode mapping process developed by @aharpalaniTO et al., documented here.

@cczhu cczhu added miniproject Work self-contained enough to be treated as small projects inputdata labels Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inputdata miniproject Work self-contained enough to be treated as small projects
Projects
None yet
Development

No branches or pull requests

2 participants