You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: