using fme to automate the creation of 9‐1‐1 compliant data

23
CONNECT. TRANSFORM. AUTOMATE. Automating the Creation of 9-1-1 Compliant Street Data Tammy Kobliuk GIS Coordinator, I.T. Services

Upload: safe-software

Post on 21-Jun-2015

348 views

Category:

Technology


8 download

DESCRIPTION

Presented by Tammy Kobliuk, City of St. Albert See more FME World Tour 2014 presentations at www.safe.com/recap2014

TRANSCRIPT

Page 1: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

CONNECT. TRANSFORM. AUTOMATE.

Automating the Creation of9-1-1 Compliant Street DataTammy KobliukGIS Coordinator, I.T. Services

Page 2: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Road-Trip Agenda

Purpose of the trip Why we’re travelling Where’s the fire? What’s the problem, aren’t the roads

mapped?(otherwise known as “all roads aren’t created equal”)

Page 3: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Purpose of the Trip

Supporting our protective services Standardize Regionalize Automate

Page 4: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Background

St. Albert RCMP detachment is the primary 9-1-1 call centre

Fire Department does fire services equipment dispatching

Alberta Health Services (AHS) does the ambulance dispatching

St. Albert operates ambulances under contract to AHS

St. Albert GIS supplies data for all three systems

Page 5: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Where’s The Fire?

St. Albert

Page 6: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Assumption

If it is good enough for the Fire Department, then it is good enough for Alberta Health

Services (AHS) and the RCMP

Page 7: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Known 9-1-1 Data CAD Uses

9-1-1 (secondary) call matching. The geocoding of the Telus

ANI/ALI feed. Primary call matching =

address points. Fastest route calculation. Interactive dispatch map

display.

Page 8: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Regional Road Network(Follow the Smoke)

Inputs: St. Albert, City of Edmonton, Sturgeon County

Output Target: FDM Street Requirements

Non-matching table structures Nothing meets FDM structure needs Target update cycle: quarterly Automate as much as possible

Page 9: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Data Notes

St. Albert road data is updated whenever roads and addresses change. Significant work completed to meet FDM

requirements. City of Edmonton road data

Downloaded quarterly Static data model Most information compiled into single fields

Sturgeon County – very rough; requires TLC

Page 10: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

The “It’s Not Pretty” Road to Deliverance

X 3

• Identify line direction.• Assign FDM street classes.• Extract quadrant information.

Extract and reclassifystreet name types.

Combine into single dataset and export to

shapefile

Combine and remap St. Albert and

Sturgeon Cty

Page 11: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

St. Albert & Sturgeon County

Filter Replace Remap Combine

Page 12: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

The First Model

Page 13: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

From A to B

Page 14: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Off To The Big City (Edmonton)!

Individual input layers for each arterial, collector, and local class. Alleys ignored.

Fully concatenated street names. Street name types are not abbreviated. Two different street classifications – they don’t

match our FDM classes. Names ALL CAPITALIZED. Data table structure is static.

Page 15: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

From C to D (or is that B?)

Page 16: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

What’s In A Name?

If you’re Edmonton, apparently everything including the kitchen sink.

101A AVENUE NW

ALBERTA HOSPITAL ROAD ONE NW

BEARSPAW DRIVE EAST NW

WEST VIEW CLOSE NW

MILL WOODS ROAD SOUTH NW

NOT NAMED ROAD NW

My personal favorite!

Page 17: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

What’s In A Name?

Prefix (e.g. South Terwilligar Drive) Name Only part (e.g. Stony Plain Road) Name Type – using standard MSAG abbrev.

(e.g. Avenue = AV; Crescent = CR) Suffix (e.g. Everitt Drive North; 112 Street

NW)

Also need a Display Name for the CAD map.(e.g. Coal Mine Rd)

Page 18: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

The First Edmonton Model(s)

Page 19: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

The Second Model(s)

Page 20: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Altogether Now!

Page 21: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

List of Most Popular Stops

Tester String Searcher Substring Extractor Attribute Filter Attribute Creator Case Changer

Page 22: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Future Sidetrips (Enhancements)

Spatial clipping to municipal boundaries Automated ID numbering Adding additional municipalities

Page 23: Using FME to Automate the Creation of 9‐1‐1 Compliant Data

Thank You!

Questions?

For more information: Tammy Kobliuk: [email protected] City of St. Albert, I.T. Services