© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1

Empowering People with Spatial Solutions

www.AppGeo.com

Andrew Buckabuck@appgeo.com617-447-2430

GIS-T 2016 – Raleigh 2016

Colorado DOTCADD-GIS Interoperability

Tools and Strategies

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 2

Interoperability

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 3

CADD – GISGIS - CADD

First design iteration used

project geodatabases

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 4

Tool Function

and Central Repository

Tools based on business functions

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 5

Project WorkflowOverview

Catalog

Identify ROW projects

Projects FilesAppGeo

ProjectID

SAP OTIS ProjectCode,Shape

Associate or create geometry

ProjectCode,Shape

Catalog available files

File Details

Assign to processing

queue

Process DGNProcess PDF

Hold PDF

Identify ProjectWise

DGNs

RegionalInquiry

No DGNs?

DGNs! Assign GCS

GCS’d DGNsFor CDOT

InterOpIngest

InterOpTool

Update catalogFile Details

Project QueueFile Status

DGN Processing

PDF Processing

DigitizePDF

Geodatabase

FeaturesFeatures

Extract,QC,

Deliver

Geodatabase

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 6

• Orange – SAP ROW Projects – potential DGNs • Blue – Pre-SAP – Before DGNs, PDF plan sets – may also exist under Orange• Red – State roads without identified projects

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 7

File Hierarchy / Georeferenceing

PCD

LSCD

ROW Model

PCD (Project Control Document) Survey of control monuments Used to create project

coordinate system Survey data collected in meters,

PCD should be in feet

LSCD (Land Survey Control Document) Boundary monuments May contain imported section lines Does not contain property lines

Right-of-way (ROW) Model Parcels ROW

Plans

Plans Contain design elements,

alignments, edge of oil, etc.

Full Plan Set

Full Plan Set Contains complete set of all Project information

• Not all plans are created equal

• Design best practices put control information into title sheet

• Project control can be used to georeference

• Much better solution is to put project coordinate system into DGN as a GCS

• Let BentleyMap translate from custom project coordinate system Sometimes ROW hidden in reference files

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 8

Project & File Catalog

List of projects with lookup and query functions

Selected project by AppGeoProjectID

Files associated with Project by AppGeoFileID

Project Processing Queue

File StatusExample shows original DGN copied and GCS’d for Interop tool ingest and return to CDOT

• Associates files with projects and geometry

• Manages the processing queues

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 9

• Microsoft Access UI

– Entering tool parameters

– Launch FME models via shell

• Ingest into SQL Server

• Extract to geodatabase

DGN

Interoperability Geospatial db

(SQL Server, DBMS geometry)

5/6/2015 2012-0228.00

Colorado DOTCADD to GIS Interoperability

Tool Description

CDOT File System

User open Microsoft Access, configures conversion settings, selects tools, inputs parameters, and click “Run Selected Tool”. FME models, stored in FMW Files, are executed via OS shell commands invoked by Visual Basic for Applications event procedures (see form_RunTool_frm.RunSelectedToolButton_Click). In some cases, FMX files execute Python scripts

ShellCommand = "C:\program files\FME\fme.exe " & Chr(34) &

"C:\git\cdot_2012-0228.interoperability\fmw\" & Me.ToolNameCombo.Column(2) & Chr(34)

FME Install Directory

FME Model directory

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 0

Link CADD Levels to Geospatial Features

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 1

Choose Tool, Enter Parameters, Run

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 2

Log Tool Use

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 3

Data is Organized by Source File

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 4

Ingest into SQL Server Spatial

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 5

Feature Level Metadata

Geometry and metadata stored separately

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 6

Review Ingested Data

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 7

Delivery Data Model

DOT Lines

Extracted CADD Objects

Digitized Features from PDFs

Project ROWGenerated polygons generated from DOT Lines

DOT ROWAggregated Project ROW polygons, by route, county

DOT ParcelsCDOT owned land in ROW, Excess, Remainder, General Ledger

Correction Points

Issue points for processing and client review

DeliveryData

Model

DOT_LinesCorrectionPoint

DOT_Parcels

DOT_ROWProject_ROW

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 8

Digitize Georeferenced Scans

Colored area indicate parcel acquisitions or “transactions”

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 1 9

Create PolygonsFrom Lines

• Create End Caps and Connectors

• Generate project ROW polygons

• Calculate “True Line” percentage

© 2 0 1 6 A p p l i e d G e o g r a p h i c s , I n c . S l i d e 2 0

Project ROWAreas

• Aggregate into

route polygons

• Break polygons

in logical places