Getting Intergraph and Esri to Play Nicely Using FME

Getting Intergraph and Esri to Play Nicely Using FMELou ManglassSystems Analyst II

9 APR 2013

Introducing The Kids

ESRI ArcGIS Server (Planning, Public Works)

Includes Feature-Linked Annotation Shapefiles (UGA, Assessor) File/Personal Geodatabases (various annotations)

Intergraph Proprietary .map format (.dgn v7) for each agency

Proprietary .ply format (text polygon output)

SQL/Excel (non-spatial sources) Various spatial information in non-spatial formats

Intergraph’s Needs

Creating a 911 map isn’t just dumping out a file Three customer groups require different .maps

ACCPD/UGA Dispatchers, ACCPD/UGA mobiles, Fire Modern formats hard to convert to DGN v7 Text files (.ply) defining dispatch zones/beats SQL Database

Special Address tables maintain verified addresses and location of access for parcels

Segment and Node tables manage road network and routing information

Code Tables (e.g. street) provide LUTs

A Quick Detour: DGN v7

File system Database

DGN v7 files .map file Spatial DataSQL Database

MSlink

Tabular Data

63 layer limit 32 MB limit (DGN) Retired in 1999

Spatial info in UORs MSlink relates map Funky legacy issues

Athens-Clarke County’s Map Layers

Setting The Play Date

GeoMedia Pro is cumbersome to use with I/CAD, little room for automation and no data validation

FME provides validation and conversion paths for all of our data sources Data is synthesized, checked for changes and

verified despite political barriers ESRI Annotations converted letter-by-letter to DGN Tabular sources can be converted to spatial data And vice-versa

And we can version product files

County Replicator

County Replicator (cont’d)

County Replicator (cont’d)

Anno to DGN

Anno to DGN (cont’d)

Anno to DGN (cont’d)

Special Address Updates

Polygon File Generator

Polygon File Generator (cont’d)

Map Stamp

How FME Returned Our Investment(TL;DL: Very Well)

License for GeoLabel Pro: $1,995 / $399 p.a. Time saved through automation: 2 days/roll ($480)

Data collection, validation, conversion automation 4 weeks to 4 hours! (FME gets half credit: $2,340) That’s per roll, by the way

Fewer errors: ≈60 output layers, all automated Version stamps also reduce testing confusion Customers much happier with consistent product

Target 4 map rolls a year, but now could do 5 or 6

Where Do We Go Next?

More scripting Continue to logically group sets of workspaces

Feature Addition Add custom fields, functions to dispatch workflow FME performs ETL, validation, QA, logging

FME Server Offload processing from map development station Schedule workspace groups for nightly builds Provide daily graphic-side updates for .map file

Thank You!

Questions?

For more information: Lou Manglass: [email protected]

Athens-Clarke County Police Department