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

Travel times for corridor segments don't sum to whole corridor #100

Open
Nate-Wessel opened this issue Mar 12, 2024 · 1 comment
Open

Travel times for corridor segments don't sum to whole corridor #100

Nate-Wessel opened this issue Mar 12, 2024 · 1 comment

Comments

@Nate-Wessel
Copy link
Contributor

Example query: results.csv

If corridor is subdivided into smaller corridors, the travel times for the sub-corridors don't sum cleanly to the travel time for the whole corridor. The difference is big enough that it doesn't seem to just be rounding / floating point error.

Need to at least identify the source of this issue so it can be explained.

@Nate-Wessel
Copy link
Contributor Author

I currently suspect this has to do with the data availability threshold being based on length. Some one-hour bins may meet the criteria for a sub-segment of the corridor but not for the whole thing taken as a whole. Thus, the shorter corridors will generally incorporate observations which don't make it into a spatially longer aggregation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant