# Applying Topological Information for Routing Commercial Vehicles Around Traffic Congestion
## 3 Data Collection
### Network Dataset and Traffic Data  
Data for this analysis were collected from various sources. First, street and traffic data were collected and processed to build a dynamic routable network dataset that stored road edges and junctions and their attributes for all segments of the road network. Second, historical traffic profiles were incorporated into road edges. This allowed time-dependent variables to be assigned to road edges and junctions to reflect actual traffic conditions throughout the day. Finally, truck alternative route selection criteria were defined to evaluate the network in terms of suitability for trucks. Figure 4 depicts the network dataset components.  
\begin{table}
\begin{tabular}{c c} \hline \hline
**Data Field Name** & **Description** \\ \hline Event ID & A unique identifier for each incident record \\ Event type & Type of incident (crash, disabled vehicle, debris in the road, fire vehicle, wildlife, police activity, emergency vehicles, or other) \\ Event latitude & Latitude of incident location \\ Event longitude & Longitude of incident location \\ Severity & Injury severity level ranging from 1 to 3 \\ WRS blockage description & A description of road blockage caused by the incident, including number of lanes \\  & blocked, shoulder closure, and exit/entry ramp closure \\  & Time and date on which incident was reported to FDOT or Florida Highway \\  & Patrol (FHP) \\ TMC notified & Time and date on which incident was reported to TMC \\ Verification & Time and date on which incident was confirmed and verified \\ First responder arrival DT4 & Time of the first responder arrival at the incident site \\ Roadway clearance & FDOT roadway clearance time is the duration between the first notification time and \\  & the time when travel lanes were cleared \\ Last DPV depart\_Clsd date & Additional assistance leaves the incident scene \\ First responder dispatch & Traveler information sent and Road Rangers dispatched \\ Last responder departure & Last Road Ranger/Severe Incident Response Vehicle (SIRV) leaves the incident scene \\ County & Name of county in which incident occurred \\ Short name & Name of route on which incident occurred \\ Sys\_location description & A detailed description of the incident site location \\ Notifier agency ID & The ID of the agency that was first notified of the incident \\ Notifier agency name & The name of the agency that was first notified of the incident \\ \hline \hline \end{tabular}
\end{table}
Table 1: Description of incident data fields.  
The ArcGIS Network Analyst extension ([[https://www.arcgis.com/index.html](https://www.arcgis.com/index.html)]([https://www.arcgis.com/index.html](https://www.arcgis.com/index.html)) accessed on 12 August 2024) was utilized to design, create, and build a transportation network dataset. For this study, a file geodatabase network was created. Streets and turn feature classes were created in one feature dataset and stored in this file geodatabase. Figure 5 presents the workflow used to build the network dataset.  
Figure 4: Required data for network analysis.  
Figure 5: Workflow to build network dataset.  
The geographic datasets used in this analysis were collected from the FDOT's Unified Basemap Repository (UBR) database. The UBR provides quarterly street and traffic datasets from the network provider NAVSTREET's street data by HERE Technologies. Additionally, the UBR database contains data suitable for routing applications with a complete navigable road network. Data were extracted in the format of a file geodatabase for the GIS platform. The Z-level layer was used to create roadway connectivity. The quality of the collected data was evaluated, and data were preprocessed for integration into the Network Analyst extension. The related dataset descriptions and sources are listed in Table 2.