Integrating ARNOLD

into the Workflow

2016 GIS-T Symposium

Presented by:

Brett Juul, GIS Manager, ODOT

Marc Kratzschmar, Senior Consultant, Bentley Systems

April 8, 2016

2

Agenda

• Network Data Demands on DOTs

• What it takes to get statewide

coverage

– Standards and shared working

– DOT leadership

• Integrated Reporting Database

Demands On DOT Network Data

• Federal Mandates for common LRS

– Performance (HPMS includes Pavement and Traffic data)

– Bridge (NBI)

– Crash(FARS and others)

– Federal Aid Projects (FMIS)

– Certified Mileage

• DOT Decision Support and Analysis

• All rely on network data

– Increasing demands for coverage

– Increasing demands for spatial quality

– Validation against LRS

State Highways

City Streets/County Roads

Resource Lands Roads

Assembling the Network One County at a Time

• Collaborative effort among network data stewards

– Counties (Public Works and GIS)

– Cities

– Federal Agencies

– Public Safety Answering Points (PSAPs)

• Standards-based: Statewide Transportation

Framework Data Layer

• DOT Driven: One data source at a time

Oregon GIS Framework Data

• The effort is managed by the state GIS

coordinator

• Framework dataset exchange standards agreed-

upon for ease of exchange

• Effort involves participation by local, regional,

federal and state level agencies within Oregon.

• Fundamental geospatial data elements

• Typically statewide in extent

• Considered to be the best available data

• Intended to serve a broad range of user needs

Geoscience

Preparedness

Utilities

Climate

Bioscience

Landcover/Use

Oregon Specific

Hazards

Nationally Recognized

Geodetic Control

Aerial Imagery

Elevation

Boundaries

Hydrography

Transportation

Land Ownership

Framework Data Layers

Transportation Framework Layer: OR-Trans

• Statewide Road Centerline Layer

– Used for ARNOLD submittal

• Local data stewards provide annual updates

• ODOT integrates State, Local and Federal Road

data

• Development and maintenance funded by E-911

funding mechanism and State Planning and

Research (SPR) Funds

• Built to the Oregon Road Centerline Data

Standard

Managing the Update Process

• Four Separate Software Packages Used

– ArcGIS

– GeoMedia Pro

– SQL Server

– Feature Manipulation Engine (FME)

• Tailor the process for each data provider

• FME Workbench types

– Standardize

– Validate

– Detect Changes

– Update

Creating OR-Trans

Data FromLocal

Provider

Run Data Through FME Workbench

Preprocess Data In ArcGIS

State Hwy TransInfo TIG

Extract

Processes

Products

Typical workbench to standardize road authority’s data

Geometry change detector• Finds corresponding records with the same Local ID

• Checks to see if the geometries match

Attribute Change Detector• Finds corresponding records that have the same Local ID

• Declares match if geometry attributes also match

Creating OR-Trans

Data FromLocal

Provider

Run Data Through FME Workbench

Writes data to database

Preprocess Data In ArcGIS

GeoMedia Geometry

QA/QC

State Hwy TransInfo TIG

Extract

Processes

Products

Geometry check in GeoMedia Pro• Compares datasets to database

• Database now matches new geometries

Creating OR-Trans

Data FromLocal

Provider

Run Data Through FME Workbench

Check Functional

Class

Writes Data to database

Preprocess Data In ArcGIS

GeoMedia Geometry

QA/QC

SQL Attribute QA/QC

State Hwy TransInfo TIG

Extract

Processes

Products

SQL Server Management Studio to check attribute

information in SEG table.

Use SQL Server Management Studio to check attributes

in SEG_DESC table

Creating OR-Trans

Data FromLocal

Provider

Run Data Through FME Workbench

FME Database

Extract

Writes Data to database

Preprocess Data In ArcGIS

GeoMedia Geometry

QA/QC

QA/QCSQL Attribute

(FC)

State Hwy TransInfo TIG

Extract

Processes

OR-TransProducts

Dynamic Segmentation uses Segments to Build Routes

After Dynamic Segmentation• Final QA/QC

• If no errors, OR-Trans is ready for production use

OR-Trans Framework Layer (ARNOLD)

14_8747

33_12135

25_404

25_406

25_405

State Highway

County Roads

City Streets

Resource Lands Roads

25_0007Segment ID (Contributor -

Sequential Number)

County Line

293_9728

14_8748

293_9732

293_9731

25_402

14_963

293_9730

22_6461

22_6462

25_403

293_9729

State Highways

City Streets/County Roads

Resource Lands Roads

Creating OR-Trans

Data FromLocal

Provider

Run Data Through FME Workbench

FME Extract and Final QA/QC

Writes to Database

Preprocess Data In ArcGIS

GeoMedia Geometry

QA/QC

QA/QCSQL Attribute

(FC)State Hwy

TransInfo TIG Extract

ARNOLD

Processes OR-Trans Carto

Custom Tool

Support

OR-Trans

Products

Maintaining the Integrated Reporting

Database

Data integration and extract

Statewide

centerline data

Linear

Referencing

System

Business data

25

State Maintained

Roads

Functionally

Classified Local-

Agency Roads

Local-Agency

Roads

26

Three Linear Referencing Methods

• LRS

– Unique LRS ID, DOT

LRM used for DOT

applications

• ARNOLD Attributes

– Road Name

– Functional

Classification

– Ownership

– Facility Type

– State Code

– Year

– Source

• Summary Business Data

– Mileage

– Traffic

• Located Business Data

– Full extent HPMS

items and most

sample panels

– ODOT operational

data (e.g.

maintenance crews)

State Maintained Roads

27

• LRS

– Unique LRS ID, DOT

LRM used for DOT

applications

• ARNOLD Attributes

– Road Name

– Functional

Classification

– Ownership

– Facility Type

– State Code

– Year

– Source

• Summary Business Data

– Mileage

– Traffic

• Located Business Data

– Full extent HPMS

items and most

sample panels

State Maintained Roads

28

• LRM

– Based on FC, used

for HPMS reporting

only

• ARNOLD Attributes

– As for state

maintained Roads

• Summary Business Data

– As for state

maintained roads

• Located Business Data

– Full extent HPMS

items and some

sample panels

Functionally Classified Local-Agency RoadsFunctional Class = Collector and Above

29

• LRM

– Unique LRM ID

• ARNOLD Attributes

– As for state

maintained roads

• Summary Business Data

– As for state

maintained roads

• Located Business Data

– Growing

Local-Agency RoadsFunctional Class = Local and Rural Minor Collector

30

31

Business Data

Data integration and extracts

Business Data

Model

Annual

Update

Process

Extract

Process

Interfaces (Automated)

· Automated Time Capture

· Bridge Data System

· CHAMPS

· Crash Data System

· DFMS

· Digital Video Log (Web)

· Motor Carrier Electronic Routing (ERM)

(Vertical Clearance)

· Motor Carrier Restrictions

· RAIN (Right of Way)

· Signals

· Speed Zone

· SPMTS (Pavement Markings)

· Straightline Chart Diagrams

· Transportation Operations (TOC)

· TransViewer

Extracts (Files)

· Digital Video Log

· Pavement

· Project Delivery Work Planning

· SPIS

· TransGIS

TRANSINFO DATA FLOW (SCOPE)

Da

ta In

pu

tsIn

terf

ac

es

, E

xtr

ac

ts

& R

ep

ort

s

Da

tab

as

e

Revised 01/19/10

P = Paper

F = File

A = Automated

Construction

Plan Data

P

Field

Inventory

Sheets

P

Misc.

Boundary

Changes

P

Traffic

Count

Data

F

OTC

Actions

P

Features

Inventory

Summary

SheetsP

Maint.

Work

Force

Order InfoP

Minor

Betterment

Data

P

R/W Map

Info

P

Speed

Zone

Order

UpdatesP

Report Database In

Same Format as

Today

(HTDR1)

Other Extracts

· HPMS/Certified Mileage

· Oregon Hwy Monitoring

System

Custom

Reports

Highway Budget

Reports

Pipe

Outfalls

A

City

Limits

View/Reports (Manual)

· Aggregate Source

· Bridge Rating

· Hazardous Material

· HTCRS (Highway Traffic Condition)

· CSS (Camera Services System)

· HGIS

· PONTIS

· Sound wall Inventory

· Unstable Slope

· Water Quality Inventory

· WinVAN (Collection)

Curbed Shoulder (Miles)

Ditch (Miles)

Drainage Installation (Quantity)

Mowing Area (Acres)

Sprayable Shoulder (Miles)

Mowable Brush Shoulder (Miles)

Flashers & Beacons (Quantity)

Landscaped Area (Acres)

Fence (Miles)

Striped Lines (Miles)

Legends (Quantity)

Signs - (Quantity)

Illumination Units (Quantity)

Traffic Signals (Quantity)

Concrete Barrier (Miles)

Metal/Wood/Cable Rail (Miles)

Delineators/Mailbox Supports (Quantity)

Drawbridges (Quantity)

Pavement Markers (Quantity)

Water Quality Facility (Sq Ft)

Horizontal/Vertical Drains (Lin Ft)

Bridge Screen (Lin Ft)

Attenuators (Quantity)

Quantity = Occurrences of the feature by highway section ID

State Highway Definition (LRS, Highway Name,

Number, Begin and End)

Interstate, US and OR Route Numbers

Intersecting Road Jurisdiction

Intersecting Road Name

Engineering Stations

Classifications (Federal FC, State Highway Class.,

Scenic Byways, Etc.)

Posted Speed

Median Type

Median Width

Number Of Lanes

Lane Width

Shoulder Width

Pavement Shoulder Type

Pavement Type

Pavement Thickness

Base Type

Base Thickness

Traffic Volume

Vehicle Classification

HPMS Samples

Horizontal Curve

Vertical Grade

TransInfo

Green = In Scope

Grey = Not in Scope

TRANSINFO

DATA FLOW

(SCOPE)

(Not a complete list)

· GIS Road Network maintained at

same time as road features

· Ability to add, update, retire, and

query via both spatial and tabular

interfaces

GIS Network

· Highway Network

extracted to OR-Trans

and HwyNet monthly

Drainage Facility

Management System

(DFMS)

DFMS Tables

Stored in

TransInfo

Future Report

Database To Provide

New TransInfo Data

Other Boundaries (Parks, National Forest, Etc.)

Sign Bridges – location & type

Structures

Weigh Stations

City Limits

County Boundaries

Federal Aid Urban Boundaries

Region Boundaries

District Boundaries

Maintenance Unit Boundaries

Bicycle/Pedestrian

Guardrails

Curbs

Milepost Paddles

Signals – location of 3 color

Stormwater Facilities

http://intranet.odot.state.or.us/tdb/trandata/transinfo/

Updating TransInfo While Creating OR-Trans

Data FromLocal

Provider

Run Data Through FME Workbench

FME Extract and Final QA/QC

Writes to Database

Preprocess Data In ArcGIS

State Hwy TransInfo TIG

Extract

ARNOLD

Processes OR-Trans Carto

Custom Tool

Support

OR-Trans

Products

Integrated Enterprise Reporting Database

Integrated ARNOLD and HPMS Extract Process

Annual All Roads

Centerline Update

Business LRS Update

Annual Business

Data Update

Annual HPMS/ ARNOLD Extract

Integrated Enterprise Database

OR-Trans and GIS Products

All Roads centerline

All Roads LRS

Business data

location

Business data

Aggregated All Roads Updates

Synchronization Challenge

36

Update Centerline (Geometry,

Length)

Update LRS

(reclassify)

Update Business

Data Locations

37

Lessons Learned – You’ve Got This!

• All Roads Network Maintenance is Complicated

• Federal Reporting is Complex

• The Fewer Systems to Manage the Better

– Apply integrated enterprise approach to all

roads

Thank you.

39