FME 2014 - Automating Creation of 911 Compliant Data

CONNECT. TRANSFORM. AUTOMATE.

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


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”)


Purpose of the Trip Supporting our protective services Standardize Regionalize Automate


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


Where’s The Fire?

St. Albert


Assumption

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

Services (AHS) and the RCMP


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.


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


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


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


St. Albert & Sturgeon County

Filter Replace Remap Combine


The First Model


From A to B


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.


From C to D (or is that B?)


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!


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)


The First Edmonton Model(s)


The Second Model(s)


Altogether Now!


List of Most Popular Stops

Tester String Searcher Substring Extractor Attribute Filter Attribute Creator Case Changer


Future Sidetrips (Enhancements)

Spatial clipping to municipal boundaries Automated ID numbering Adding additional municipalities


Thank You!

Questions?

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

Documents

FME 2014 - Automating Creation of 911 Compliant Data