Closed aharpalaniTO closed 7 years ago
Have addressed Step 4 through creation of prj_volume.tmc_turns
. Does not account for directionality of segment at the moment. Need to still build "manual mappings" table, subsequent update script, and porting over to final volumes table.
Addressed through prj_volume.tmc_turns_corr
.
Present thinking is that this will consist of five steps:
Automated assignment of N, E, S, and W legs of intersection to specific TCL segments based on spatial distance to node and azimuth of segment relative to node (done)
Identification and "correction" of segments where the assigned direction is likely to be misaligned with that reflected in the turning movement count data (i.e. Kingston Rd.) (hopefully automated - to be looked at)
Additional segment corrections that are not picked up by the automated process in steps
1
and2
(lookup table manually created - not done yet)Translation of the results from
1
,2
, and3
into a detailed intemediate table that maps each (artery code-turning movement) combination to a (TCL from segment) and (TCL to segment) - (automated process, to be developed)Result set from
4
is updated using a seperate table consisting of manual changes that reflect "strange" intersections (i.e. Lakeshore and Lower Spadina). - (manual process, to developed)The table I envision looks something like this: