ESRI UC 2015

San Diego, CA

WHERE ARE MY ROADS?

Migrating Mainframe to a Linear

Referencing System Aja Davidson, TxDOT

Topics

2

Asset Inventory

Current Data Management System

Current GIS Model

Linear Referencing Methods

GRID

Data Highlights

Lessons Learned

1

2

3

4

5

6

7

What is an asset?

3

Current Data Management System

Texas Reference Marker System (TRM)

Development began in 1988 and went live in 1995

Mainframe system

Non-spatial

Uses reference markers to locate assets

Limited logic checks/domains

Only On-system roadways (state maintained)

4

Texas Reference Marker System (TRM)

Current Roadway Inventory

5

Current GIS Model

GIS

Roadway linework

Event tables – routed by DFO

– Off-system inventory data

– Control sections

– Concurrencies

– Bridges

Basemap layers

6

GIS

Current GIS Model

GIS Editing Matrix

7

On System

Digitize

Feature

Feature

Attributes

Calculate

Measures FC Linework

Departmental

Map

Control Section

Map

County

Mapbook

Statewide

Planning Map

(z0-z6)

State

Railroad

Map

RTE

Concurrent

Table

RTE CG

Table

RTE Control

Section Table

Bridge

Table

RTE

Subfiles

Table

Mileage

Tracking

Add Road x x x x x x x x x x x x x

Remove Road x x x x x x x x x x x

Modify Road x x x x x x x x x x

Realign Road x x x x x x x x x x x x

Change Name x x x x x x x x x x x

Change Route Class x x x x x x x x x x x

Grade Separated Connector x x x x x x

Off System

Digitize

Feature

Feature

Attributes

Calculate

Measures FC Linework

Departmental

Map

Control Section

Map

County

Mapbook

Statewide

Planning Map

(z0-z6)

State

Railroad

Map

RTE

Concurrent

Table

RTE CG

Table

RTE Control

Section Table

Bridge

Table

Subfiles

Table

Mileage

Tracking

Add Road x x x x x x x

Remove Road x x x x x

Modify Road x x x x x x

Realign Road x x x x x x

Change Name x x x x

Change Route Class x x x x x x x x x

City Limits

Digitize

Feature

Feature

Attributes

Calculate

Measures FC Linework

Departmental

Map

Control Section

Map

County

Mapbook

Statewide

Planning Map

(z0-z6)

State

Railroad

Map

RTE

Concurrent

Table

RTE CG

Table

RTE Control

Section Table

Bridge

Table

Subfiles

Table

Mileage

Tracking

Add City x x x x x x

Remove City x x x x x

Modify City x x x

Change Name x x x x x

Railroad Linework

Digitize

Feature

Feature

Attributes

Calculate

Measures FC Linework

Departmental

Map

Control Section

Map

County

Mapbook

Statewide

Planning Map

(z0-z6)

State

Railroad

Map

RTE

Concurrent

Table

RTE CG

Table

RTE Control

Section Table

Bridge

Table

Subfiles

Table

Mileage

Tracking

Add Rail line x x x x x

Remove Rail line x x x x

Modify Rail line x x x x

Realign Rail line x x x x

Change Name x x x x

Change Rail Class x x x x

Railroad Crossings

Digitize

Feature

Feature

Attributes

Calculate

Measures FC Linework

Departmental

Map

Control Section

Map

County

Mapbook

Statewide

Planning Map

(z0-z6)

State

Railroad

Map

RTE

Concurrent

Table

RTE CG

Table

RTE Control

Section Table

Bridge

Table

Subfiles

Table

Mileage

Tracking

Add Crossing x x

Remove Crossing x x

Modify Crossing x x

Change Name x x

Change Class x x

GIS Editing Matrix

Linear Referencing Methods

8

1

0

0

1

0

2

1

0

4

1

5

0

DFO

100

DFO

150

CSM

0 1086-01

CSM

27 1086-02

CSM

1 CSM

24

RM = 140 +1.7

DFO = 141.7

CSM = 15.7

On-system asset

management

HPMS data

collection

Reference

Markers

Roadway linework

Off-system asset

management

Bridges

DFOs

Project Management

system

Unified

Transportation Plan

Control Section

Milepoints

Linear Referencing Methods

9

1

0

0

1

0

2

1

0

4

1

5

0

DFO

100

DFO

150

CSM

0 1086-01

CSM

27 1086-02

CSM

1

RM = 130 +1.3

DFO = 141.7

CSM = 16.2

CSM

24

-.4

+.5

Linear Referencing Discrepancy

10

Roadway Asset

coverage (red)

No Roadway Asset

coverage (white)

Route SH0158

DFO 50.63

Latitude 31.95239204

Longitude -101.93042369

Control Section 046303

Milepoint 13.892

Reference Marker 294

Offset 1.857

Solution - GRID

Reviewed multiple proposals including Roads and Highways

Chose a custom solution – GRID (Geospatial Roadway Inventory Database)

– Utilizes Latitude/Longitude for all LRS functionality

Integrates three current LRS methods in the UI

– DFO

– Control Section Milepoint

– Reference Markers

11

1

0

0

1

0

2

1

0

4

1

5

0 1086-01 1086-02

Roadway Edits and Displaying Assets

Current Workflow

12

Change geometry in GIS

Reapply measures

Edit Concurrencies event table in

GIS

Edit CG event table in GIS

Edit Control Section event table in GIS

Edit Bridge event table in GIS

Edit Subfiles event table in

GIS (off system)

Make edits in TRM

Compare TRM and GIS edits

Run GIS error checks and TRM

reconciliation

Request TRM data export

(RHINO) from IT

Wait several days for new

RHINO

Calibrate GIS linework to match TRM measures

Route RHINO to calibrated linework

Edit geometry in GIS

Reapply measures

Create GRID ETL packet

Upload packet and wait for ETL

process

Update assets in GRID using

edited geometry

Export RHINO directly from

GRID

Route RHINO to GIS linework (no

calibration needed)

Future Workflow

GRID System Architecture

13

GRID Maintenance Application Modules

14

GRID Database Model

15

GRID Workflow

Job Creation (single route)

LRS Job

Edit LRS features

Control Sections

Reference Markers

RAI Job

Edit RAI features

Linear Data

Speed Limit

Roadbed Surface

HPMS Samples

Point Data

Stream Crossings

Railroad Crossings

16

GRID User Interface

17

ETL

Interface between GIS edits and GRID

All basemap and roadway data is still managed in ArcGIS

18

Edit roadway geometry

and basemaps in

ArcMap

Run error checks

Create job packets

Upload job packets

Job packets are

processed

Tiles and materialized

views are regenerated

Managed by TxDOT Managed by GRID

Automated

Data Highlights

19

What people think it looks like

What it really looks like

Data Migration

Data Highlights

Data Migration Stats

2 GIS Analysts

116 total scripts

4000 hours

513 gallons of coffee

65 pounds of candy

340 data tables

8.2 million records migrated

8,675,309 80’s and 90’s pop culture references

20

Data Migration Stats

Lessons Learned

High-level

More involvement in Vendor day-to-day decisions and development meetings

Someone on staff reviewing Vendor scripts, code, and processes

Requirements gathering process should have included prototypes or labs

– Opportunity to revise requirements as project progresses

Delays are inevitable, but we now know how to manage some of them

Technical

Concept of working within an assigned job has limitations

More time should have been spent on the UI

Data Migration has required vast resources

21

High-level

Technical

Questions?

22

ESRI UC 2015

San Diego, CA

THANK YOU!

Aja Davidson

TPP - Data Management Team Lead

Texas Department of Transportation

(512) 486 - 5147 | Aja.Davidson@txdot.gov