Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

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


Published on

Presented by Tammy Kobliuk, City of St. Albert
See more FME World Tour 2014 presentations at

Published in: Technology
  • Be the first to comment

  • Be the first to like this

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

  1. 1. CONNECT. TRANSFORM. AUTOMATE. Automating the Creation of 9-1-1 Compliant Street Data Tammy Kobliuk GIS Coordinator, I.T. Services
  2. 2. 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”)
  3. 3. Purpose of the Trip  Supporting our protective services  Standardize  Regionalize  Automate
  4. 4. 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
  5. 5. Where’s The Fire?
  6. 6. Assumption If it is good enough for the Fire Department, then it is good enough for Alberta Health Services (AHS) and the RCMP
  7. 7. 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.
  8. 8. 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
  9. 9. 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
  10. 10. The “It’s Not Pretty” Road to Deliverance X 3 • Identify line direction. • Assign FDM street classes. • Extract quadrant information. Extract and reclassify street name types. Combine into single dataset and export to shapefile Combine and remap St. Albert and Sturgeon Cty
  11. 11. St. Albert & Sturgeon County  Filter  Replace  Remap  Combine
  12. 12. The First Model
  13. 13. From A to B
  14. 14. 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.
  15. 15. From C to D (or is that B?)
  16. 16. What’s In A Name?  If you’re Edmonton, apparently everything including the kitchen sink. My personal favorite!
  17. 17. What’s In A Name?  Prefix(e.g. SouthTerwilligar 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)
  18. 18. The First Edmonton Model(s)
  19. 19. The Second Model(s)
  20. 20. Altogether Now!
  21. 21. List of Most Popular Stops  Tester  String Searcher  Substring Extractor  Attribute Filter  Attribute Creator  Case Changer
  22. 22. Future Sidetrips (Enhancements)  Spatial clipping to municipal boundaries  Automated ID numbering  Adding additional municipalities
  23. 23. Thank You!  Questions?  For more information:  Tammy Kobliuk:  City of St. Albert, I.T. Services