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
For turn movements which exit onto segments where a downstream ramp or exit appears shortly after, the centreline file may treat these ramps/exits as distinct segments that start at the intersection (see below):
In the example above, the turning movement counts reflect volumes that are turning from or onto segment 911550 (Burnhamthorpe Rd, W leg). A fraction of the volume that turns onto Burnhamthorpe will then exit onto the 427 NB (represented by segment 911542). Since this ramp is represented as commencing at the intersection itself, however, the volumes turning onto the W leg need to be split onto 911542 and 911550. Due to the nature of the counts, this can't be inferred directly from the data.
The text was updated successfully, but these errors were encountered:
Currently leaving the entrance/exit segments of these turns as NULL so no volumes are mapped to these segments, unless where it's obvious that vast majority of the volume ends up on one segment (i.e. major arterial vs. local road with minimal traffic).
For turn movements which exit onto segments where a downstream ramp or exit appears shortly after, the centreline file may treat these ramps/exits as distinct segments that start at the intersection (see below):
In the example above, the turning movement counts reflect volumes that are turning from or onto segment 911550 (Burnhamthorpe Rd, W leg). A fraction of the volume that turns onto Burnhamthorpe will then exit onto the 427 NB (represented by segment 911542). Since this ramp is represented as commencing at the intersection itself, however, the volumes turning onto the W leg need to be split onto 911542 and 911550. Due to the nature of the counts, this can't be inferred directly from the data.
The text was updated successfully, but these errors were encountered: