what’s your destination? - gis-t symposium · 2015-04-22 · what’s your destination? two...

What’s Your Destination?



Doug Argall, GISP, OCASr. Project Manager/Sr. Data Architect


Two factors have impeded traditional techniques for prioritizing locations for safety improvements1. Traditional techniques lacked the methodological

rigor necessary to produce reliable results.2. Data on locally‐owned roads often was not

available, making location‐based analyses incomplete.


In order to address the first issue, the FHWA sponsored development of a set of software tools to manage safety data analysis and countermeasure selection.FHWA partnered with 27 DOTs to develop AASHTOWare Safety Analyst™ as a cooperative effort to improve programming of site‐specific highway safety improvements.


Network screening approaches help highway agencies make better decisions about where to spend their safety dollars.Identifies countermeasures considering the crash patterns and related site conditions.Performs economic appraisals of the costs and safety benefits of selected countermeasures.Conduct safety evaluations of improvements after they are implemented.


To address the local roads data issue, FHWA established the Roadway Safety Data Program (RSDP) to advance State and local safety data systems and safety data analyses.


In the State of Arizona, some data related to crash, roadway characteristics and traffic operations are collected. However, this data is scattered, fragmented and under‐used. There is a need to consolidate the available data, identify the missing information and integrate local data for statewide deployment of Safety Analyst.


The ADOT Local Safety Data Integration Project builds on the results of the RSDP by developing guidance based on actual experience to help agencies improve the integration of local road data into State systems. There is a need to consolidate the available data, identify the missing information and integrate local data for statewide deployment of Safety Analyst. Our project will benefit ADOT by developing the tools and methodology to make local data part of the complete highway safety analysis.


Integrate local data resources with statewide data sets to create a comprehensive, statewide database.Define data standards for the integration processes.Conduct an analysis of data gaps and GIS needs.Develop database schemas to assist with the mapping of data to Safety Analyst.Support the analyses through pilot projects and training.


Task 1 – Kickoff MeetingTask 2 – Finalize Project Work PlanTask 3 – Data Gaps and GIS NeedsTask 4 – Data Quality and GovernanceTask 5 – Data IntegrationTask 6 – Data Analysis


On September 19th, 30 individuals representing 10 different organizations met to review project scope, milestones, and deliverables.Four local agencies were identified to participate in the pilot.


Describes the background and purpose of the project. Details the approach that will be taken to achieve the project objectives.Specify the time frames for conducting the work and delivering results. Enumerate potential risks.


Local agencies may be unable to supply data in a manner that meets the quality and time requirements necessary to complete the project within schedule and budget constraints.As a pre‐requisite to beginning Tasks 5 and 6, the team requires remote access to a database server with the required Roadway Characteristics Inventory (RCI) and Safety databases.


Final data set from the local agencies was received on March 27th, 3 months late.Received access to ADOT systems with RCI and Safety data on January 17th, 2 months late.


Swap Task 5 (Data Integration) with Task 6 (Data Analysis and Training).This allowed the team to give the local agencies more time to compile their data while developers created the tools to export data from ADOT’s data warehouse to Safety Analyst.


The goal for this task was to prepare a data gap analysis comparing ADOT’s RCI and Safety data warehouses to Safety Analyst’s data requirements.


Safety Analyst requires roadway characteristics, traffic volumes, and crash information.Most of this data aligns closely with the Model Inventory of Roadway Elements Fundamental Data Elements (MIRE FDE) established by FHWA


Segment Identifier Unique identifier for a section of roadwayRoute Number Signed route numberMajor Road Name Route or street nameLocation System Location reference methodBegin Segment Location Location reference End Segment Location Location of the end of the segmentRoute Type Category of the route segmentArea Type Characterize the area as rural or urbanSegment Length Length of the roadway segment in miles


Direction of Travel Direction of travel on unidirectional segmentsFunctional Class Functional class of the segmentMedian Type Type of medianAccess Control Degree of access controlOne/Two‐Way one‐ or two‐way roadwayOwnership Type of government ownershipThrough Lanes Number of through lanesInterchange Influence Segment within interchange


Identifier Unique intersection identifierLocation System Location reference methodLocation Location reference Route Type Category of the route segmentRoute Number Signed route numberArea Type Characterize the area as rural or urbanGeometry Junction geometric configuration


Ramp Identifier Unique identifier for the rampLocation System Location reference methodLocation Location reference Route Type Category of the route segmentArea Type Rural or urban areaRamp Type Connector or freeway entrance/exitRamp Configuration Design of the rampRamp Length Ramp length


Agency Identifier Unique segment id within ADOTAADT Annual Average Daily TrafficAADT Year Calendar year of associated traffic data


Identifier Unique intersection identifierAADT ‐Major Road AADT on the mainline roadAADT Year ‐Major Road Calendar year of traffic dataAADT ‐Minor Road AADT on the intersecting roadAADT Year ‐Minor Road Calendar year of traffic data


Ramp Identifier Unique ramp identifierAADT Annual Average Daily TrafficAADT Year Calendar year of associated traffic data


Accident Identifier Accident report or case numberLocation System Location reference methodLocation Location reference Route Type Category of the route segmentRoute Number Signed route numberAccident Date Year, month, and day of accidentAccident Severity Severity based on the most severe personal injury


Number of Injuries Number of injured persons, excluding fatalitiesCollision Type Type of first harmful eventNumber of Vehicles Number of vehicles involvedTravel Direction 1 Direction of first vehicle's travel before accidentTravel Direction 2 Direction of second vehicle's travel before accidentVehicle Maneuver 1 First vehicle maneuver prior to the first eventVehicle Maneuver 2 Second vehicle maneuver prior to the first event


ADOTSegment Identifier YesRoute Number YesMajor Road Name YesLocation System NoBegin Segment Location YesEnd Segment Location YesRoute Type YesArea Type YesSegment Length YesDirection of Travel YesFunctional Class YesMedian Type YesAccess Control YesOne/Two‐Way YesOwnership YesNumber of Through Lanes YesInterchange Influence No


ADOTIntersection Identifier NoLocation System NoLocation YesRoute Type YesRoute Number YesArea Type YesIntersection Geometry NoTraffic Control Type Yes


ADOTRamp Identifier YesLocation System YesLocation YesRoute Type YesArea Type YesRamp Type NoRamp Configuration NoRamp Length Yes


ADOTAgency Identifier YesAADT YesAADT Year YesIntersection Identifier YesAADT ‐ Major Road YesAADT Year ‐ Major Road YesAADT ‐ Minor Road YesAADT Year ‐ Minor Road YesRamp Identifier YesAADT YesAADT Year Yes


ADOTAccident Identifier YesLocation System YesLocation YesRoute Type NoRoute Number YesAccident Date YesAccident Severity YesNumber of Fatalities YesNumber of Injuries YesCollision Type YesNumber of Vehicles YesInitial Travel Direction 1 YesInitial Travel Direction 2 YesVehicle Maneuver 1 YesVehicle Maneuver 2 Yes


The purpose of this task is to provide assistance to the project participants to establish data standards for the data identified for this project. Data standards are an essential component for an organization to implement a reliable data integration process


Establish data governance responsibilitiesThe person(s) responsible for the data need to have the appropriate technical skillsSingle point of contact in each local agencyInstitute procedures to identify and correct defects in the dataAcquire as much metadata as possibleWork with IT services office to protect the data from unauthorized access and physical mishaps


ADOT Agency 1 Agency 2 Agency 3 Agency 4Segment Identifier Yes No No Yes NoRoute Number Yes Yes No Yes NoMajor Road Name Yes Yes No Yes YesLocation System No No No No NoBegin Segment Location Yes Yes No Yes YesEnd Segment Location Yes Yes No Yes YesRoute Type Yes No No No NoArea Type Yes No No No NoSegment Length Yes Yes No Yes YesDirection of Travel Yes No Yes No YesFunctional Class Yes No Yes Yes NoMedian Type Yes No No No NoAccess Control Yes No Yes No NoOne/Two‐Way Yes No Yes No YesOwnership Yes No Yes Yes NoNumber of Through Lanes Yes No Yes No YesInterchange Influence No No No No No


ADOT Agency 1 Agency 2 Agency 3 Agency 4Intersection Identifier No No No No YesLocation System No No No No NoLocation Yes No No No YesRoute Type Yes No No No NoRoute Number Yes No No No NoArea Type Yes No No No NoIntersection Geometry No No No No YesTraffic Control Type Yes No Yes No Yes


ADOT Agency 1 Agency 2 Agency 3 Agency 4Ramp Identifier Yes No No No NoLocation System Yes No No No NoLocation Yes No No No NoRoute Type Yes No No No NoArea Type Yes No No No NoRamp Type No No No No NoRamp Configuration No No No No NoRamp Length Yes No No No No


ADOT Agency 1 Agency 2 Agency 3 Agency 4Agency Identifier Yes No No No NoAADT Yes Yes Yes Yes NoAADT Year Yes Yes Yes Yes NoIntersection Identifier Yes No No No YesAADT ‐ Major Road Yes No No No YesAADT Year ‐ Major Road Yes No No No YesAADT ‐ Minor Road Yes No No No NoAADT Year ‐ Minor Road Yes No No No NoRamp Identifier Yes No No No NoAADT Yes No No No NoAADT Year Yes No No No No


ADOT Agency 1 Agency 2 Agency 3 Agency 4Accident Identifier Yes Yes Yes Yes YesLocation System Yes No No Yes NoLocation Yes Yes Yes Yes YesRoute Type No No No No NoRoute Number Yes Yes Yes Yes YesAccident Date Yes Yes Yes Yes YesAccident Severity Yes Yes Yes No YesNumber of Fatalities Yes Yes Yes Yes YesNumber of Injuries Yes Yes Yes Yes YesCollision Type Yes Yes Yes Yes YesNumber of Vehicles Yes Yes Yes Yes YesInitial Travel Direction 1 Yes Yes Yes Yes YesInitial Travel Direction 2 Yes Yes Yes No YesVehicle Maneuver 1 Yes Yes Yes No YesVehicle Maneuver 2 Yes Yes Yes No Yes


Develop and execute a methodology to perform an ETL process to create CSV files that can be imported into Safety Analyst. Innovative procedures had to be developed in order to produce the best possible exports for analysis.A system of database views, one for each data element, was created in the ADOT data warehouse.


SELECT RouteId,ROUND(FromMeasure, 3) AS FromMeasure,ROUND(ToMeasure, 3) AS ToMeasure, CASE WHEN CarriagewayDir = 'NB' THEN 'NB'

WHEN CarriagewayDir = 'SB' THEN 'SB' WHEN CarriagewayDir = 'EB' THEN 'EB' WHEN CarriagewayDir = 'WB' THEN 'WB' WHEN CarriagewayDir IN ('UH', 'DH') THEN 'NA' ELSE 'X'

END AS travelDirectionFROM RCI_RH.dbo.LRSE_CARRIAGEWAY

WHERE (VirtualDeletion = 0) AND (RouteId IS NOT NULL) AND (FromMeasure IS NOT NULL) AND (ToMeasure IS NOT NULL) AND (FromDate IS NOT NULL) AND (ToDate IS NULL) AND (GETDATE() >= FromDate);


SELECT * FROM dbo.travelDirectionView;

RouteId FromMeasure ToMeasure travelDirection I 008 0.779 179.471 EB I 008 0 0.788 179.762 WB I 008001E 0.000 0.148 NA I 008001J 0.008 0.024 WB I 008001J 0.024 0.050 WB I 008001J 0.050 0.137 WB I 008001L1 0.006 0.020 EB I 008001R1 0.132 0.155 EB


SELECT RouteId, ROUND(FromMeasure, 3) AS FromMeasure, ROUND(ToMeasure, 3) AS ToMeasure, CASE WHEN FunctionalClass IN (1, 11) THEN 1

WHEN FunctionalClass IN (3, 12) THEN 2 WHEN FunctionalClass IN (2, 14) THEN 3 WHEN FunctionalClass IN (6, 16) THEN 4 WHEN FunctionalClass IN (7, 17) THEN 5 WHEN FunctionalClass IN (8, 18) THEN 6 WHEN FunctionalClass IN (9, 19) THEN 7

END AS roadwayClass1FROM RCI_RH.dbo.LRSE_FUNCTIONALCLASS

WHERE (VirtualDeletion = 0) AND (RouteId IS NOT NULL) AND (FromMeasure IS NOT NULL) AND (ToMeasure IS NOT NULL) AND (FromDate IS NOT NULL) AND (ToDate IS NULL) AND (GETDATE() >= FromDate);


SELECT * FROM dbo.roadwayClassView;

RouteId FromMeasure ToMeasure roadwayClass I 008 0 0.788 8.340 1 I 008 0 8.340 15.216 1 I 008 0 15.216 80.697 1 I 008 0 80.697 148.433 1 I 008 0 148.433 162.406 1 I 008 0 162.406 179.147 1 I 008001E 0.000 0.148 4 I 010263E 0 0.005 0.693 7


Develop partnerships with IT support and local agencies.Gain an understanding of each local agency’s data maturity and ability to collect and maintain data.Establish rules for data quality and governance.Develop tools that can adapt to change with changes to the data warehouse.


Stuart Thompson FHWA Office of Safety – Program ManagerBob Scopatz VHB – Project ManagerPradeep Tiwari ADOT – Project Manager


Doug Argall, GISP, [email protected]

what’s your destination? - gis-t symposium · 2015-04-22 · what’s your destination? two...

Documents