Laserfiche WebLink
Jennifer Wiltgen <br />Minnesota Department of Transportation <br />June 29, 2021 <br />Page 3 <br />Streetlight Platform and Data Configurations <br />The OD analysis was completed using the StreetLight Data software platform. StreetLight is a private <br />company that compiles anonymized location records from smart phones and navigation devices in <br />connected vehicles and transforms these location records into travel patterns. It delivers unique <br />insights into how vehicles, bicycles, and pedestrians move on virtually every road and census block. <br />Two types of data were extracted from StreetLight for the OD analysis: Origin -Middle -Filter - <br />Destination (OMD) trips and Top Routes data. This data was used to identify the origins (Os) and <br />destinations (Ds) of the trips using the river crossings (Middle Filters) via different highways (Top <br />Routes). <br />The OD analysis was conducted primarily for person trips during the AM peak period (6:00 to 10:00 <br />am), the PM peak period (3:00 to 7:00 pm) and daily during weekdays (Monday —Thursday) from <br />April 1st to 30th and September 1st to October 31 st, 2019. A comparative analysis was conducted <br />later between weekdays and Memorial Day Friday afternoon to investigate how travel patterns change <br />between a weekday afternoon and a holiday weekend Friday afternoon. <br />Origin -Destination Zone Development <br />MnDOT conducted an initial OD study using zip code boundaries in the study area. Further OD <br />analysis indicated two major drawbacks when the zip code boundaries were used for the crossing OD <br />analysis: <br />• Some zip code areas covered both sides of the Mississippi River, and thus the extracted OD <br />trips withing those zip codes do no demonstrate how the trips used the river crossings (for <br />example, the zip code for the city of Elk River). <br />• Some zip code areas covered multiple cities in the immediate river crossing area and the OD <br />trips within those zip codes do not fully demonstrate how the trips would differ from city to <br />city in the immediate river crossing while this level of OD data would be the most desirable <br />for this analysis. <br />To overcome these drawbacks, a refined Traffic Analysis Zone (TAZ) structure was used. This TAZ <br />structure was developed by the Met Council for its regional travel demand model and modified to <br />establish ODs for this analysis. The Met Council TAZ structure with 3,030 TAZs was aggregated into <br />86 ODs in three subregions. Figure 0.1 in the appendix illustrates the three subregions and ODs based <br />on the Met Council TAZs. The city and county jurisdictional boundaries were used as boundaries <br />whenever possible in the OD development process to ensure that OD trips from the StreetLight data <br />could be aggregated at those jurisdiction levels. There were 31 external pass -through stations which <br />were included to capture interregional trips using the river crossings. To capture OD trips using the <br />river crossings, six pass -through gates were defined on the three crossings in both directions as Middle <br />Filter Zones. <br />Origin -Destination Data Postprocessing <br />StreetLight provides visualization results along with hundreds of thousands of OD data records in <br />CSV files. Each raw OD record includes the total volumes (averaged from the three months of data) <br />