Understanding How GIS Data Impacts Legacy 9-1-1 Versus NG 9-1-1 ( - - PowerPoint PPT Presentation

Understanding How GIS Data Impacts Legacy 9-1-1 Versus NG 9-1-1

( Should I be worried?? ) Mary Harris – Director 9-1-1 South Western Oklahoma Development Agency SWODA

Mary Harris

• Currently 9-1-1 Director at SWODA
• 9-1-1 and GIS consulting for 15 years prior
• Prior to that worked for SBC (AT&T)

GIS Timeline

1962 Roger Tomlinson – Canada Land Inventory considered beginning of GIS (the term “GIS” was coined a few years later in a report by Duane Marble and Michael Darcy in 1965) 1969 ESRI founded by Jack & Laura Dangermond 1981 First ESRI User Conference 1982 ARC/INFO – first release available to the public 1986 Topologically Integrated Encoding and Referencing (TIGER) data created by US Census bureau 1991 First desktop ESRI version ARCVIEW was released 1998 ESRI published the shapefile format

9-1-1 Service Basics

1. Basic 9-1-1 (1960’s)

• Created one number to dial for any type of emergency
• Didn’t provide any location information
• Calls were relayed to responder agencies depending on the

emergency type

Local Phone Company

9-1-1 Service Basics cont’d

• 2. Enhanced 9-1-1 (1980’s in OK)
• Added location information of the caller
• Landline only – static address record queried at time of call
• Routing of 9-1-1 call depends on ESN (Emergency Service

Number)

CLEC Serving Central Office ILEC Serving Central Office

Selective Router

911 DATABASE

911 PSAP

9-1-1 Service Basics cont’d

• 3. Wireless Enhanced 9-1-1 (2000’s in OK)
• Added ability to get x,y coordinates through the addition of Mobile

Positioning Centers.

• 9-1-1 wireless call routing is based cell-sector information
• First 9-1-1 requirement for GIS data to plot location coordinates

Selective Router

911 DATABASE

911 PSAP

Mobile Switching Center Mobile Positioning Center

Map Map

9-1-1 Service Basics cont’d

In the current 9-1-1 service structure, the only requirement for GIS data is to provide a method to plot coordinate data on a map in the PSAP (Public Safety Answering Point)

• GIS Data only impacts one PSAP
• Map vendors and CAD vendors dictate the requirements
• Each agency can develop or use any GIS data that works
• Quality of GIS data does not effect the location information

presented on the screen of the call-taker nor does it effect the routing of the 9-1-1 call

NG 9-1-1 CHANGES EVERYTHING!!!

• GIS data is still used at PSAP to display caller’s location
• GIS data is used at the origination of a 9-1-1 call to determine

and validate the location of the caller (LIS and LVF)

• GIS data is used to determine which PSAP can provide

emergency services to the caller (ECRF)

• GIS data is used in creating the routing tables for the 9-1-1

call to traverse the ESInet to arrive at the correct PSAP (ECRF & ESRP)

NG9-1-1

Service Provider ESInet State or Regional ESInet ESRP

ECRF

LVF LIS State or Regional GIS Data Aggregation & Validation ESRP I3 Service Provider GIS Routing & Validation Database

I3 911 Agencies GIS Data I3 911 Agencies I3 911 Agencies

Standardized GIS Data

ECRF

ESRP

NG9-1-1 cont’d

There can be NO ambiguity in the GIS data. The map is no longer just a picture, the data behind each feature creates the tables on which location and routing decisions are made by the location functions in an ESInet.

THEREFORE 9-1-1 GIS data MUST be developed as outlined in the

STATE of OKLAHOMA GEOGRAPHIC INFORMATION NG9-1- 1 and ADDRESSING STANDARD

http://okmaps.onenet.net/documents/OK_ADDRESS_STANDARDS_ADOPTED _05-09-18.pdf http://okmaps.onenet.net/documents/OK%20Standards%20Schemas%20050320 18.pdf

NG9-1-1 cont’d

Required Layers

• 1. Street Centerlines

2. Address Points 3. ESZ Law 4. ESZ Fire 5. ESZ EMS 6. PSAP Boundaries 7. Provisioning Boundaries 8. ESN (support legacy)

Strongly Recommended

1. Incorporated Municipality Boundary 2. Unincorporated Community Bndry 3. County Boundary 4. Neighborhood Community Boundary 5. Any other Responder Boundary 6. Street Name Alias Table 7. Complete Landmark Name Table 8. Landmark Name Part Table

NG9-1-1 cont’d

• The PSAP boundary and ESB boundary layers provide

fields that identify resources in an ESInet much like an URL finds information locations on the world wide web

NG9-1-1 cont’d

• 1. Data Fields must be complete

Data Field Requirement attributes are tagged as Mandatory (M), Conditional (C), Optional (O) or Transportation (T). Transportation fields have been included for use in other public safety applications.

• Mandatory implies the data field must be populated

(i.e. The field “County” will ALWAYS have a value such as “GARVIN”) in every record

• Conditional implies that IF an attribute value exists for a given

feature, it MUST be populated. If no value exists for a given feature, the data field is left blank unless other guidance is given.

(i.e. The Street Prefix Direction “PreDir” MAY have a value such as “N” in 100 N MAIN)

NG9-1-1 cont’d

• Optional implies the data field must be present but may or may

not be populated

• Transportation denotes fields that are only essential to

Transportation and Routing functionality, the data fields must be present but may or may not be populated. (i.e. The Street Speed Limit “SpeedLimit” MAY have a value such as “25” if so then 25 will be included in the data field. Default speed limit WILL be set at “21” unless the limit is known

• Additional fields can be added as desired (However private

information should be stripped before uploading data to aggregation sites)

NG9-1-1 cont’d

Globally Unique ID for every feature

Oklahoma GIS Standard excerpt

NG9-1-1 cont’d

• Example of Standards Schema

NG9-1-1 cont’d

2. GIS data attributes must be correct

• Pre-determined data types as specified
• ALPHANUMERIC – Text Fields
• DATETIME- Date (yyyy-mm-dd hh:mm:ss)
• NUMERIC – Short or Long Integer (whole numbers)
• DECIMAL – Float or Double (decimals)
• Pre-determined field lengths
• Domain tables used to provide only valid field values

NG9-1-1 cont’d

3. GIS data must be spatially accurate

• Correct spatial location for feature referenced
• Address Points should easily indicate the correct

structure

• Centerlines should follow the roadbed
• Polygons must include, exclude or split roads as

required

NG9-1-1 cont’d

Local data may be stored in any projection desired as long as the data projection is clearly defined and is a regionally recognized projection. Prior to implementing into an active I3 environment, the data must be in the following projection:

PROJECTION of DATA

NG9-1-1 cont’d

4. GIS data must be topologically correct

• Centerlines must be snapped at line breaks and

intersections

• Centerlines must show correct direction of address flow
• Features that are coincidental must be snapped
• Polygons must not contain gaps or overlaps

X X X X

NG9-1-1 cont’d

GIS Data MUST be be able to provide a location for all possible 9-1-1 callers

9-1-1 calls that initially provide coordinate location (x,y) are no problem 9-1-1 calls that initiate with street style addressing must match the geodatabase (geo-msag) perfectly

NG9-1-1 cont’d

GIS is the foundation for NG9-1-1 So Create a plan!

NG9-1-1 cont’d

• 1. Assess your GIS data and skill sets (remember no one’s

data is ready)

• What skills are available in-house?
• Can I improve the existing data layers to meet requirements?
• Can I create any new data layers required?
• Can I create or acquire the validation tools needed to perform

quality checks on large datasets?

• Can I create or acquire the tools needed to validate MSAG

and/or TN datasets against my GIS data?

NG9-1-1 cont’d

2. Based on your assessment, is doing the work in-house realistic or do I need a 9-1-1 GIS vendor to perform the initial upgrade to NG9-1-1 standards?

• Yes – Then try to make a realistic estimate of the man-

hours required to perform the work and if any additional tools or software are need to accomplish the task.

• No - Get estimates from outside sources for the work
• Be prepared with dollar amounts and scope of work

details in order to justify your need if grant monies become available

NG9-1-1 cont’d

3. Based on your assessment, can you maintain and validate your GIS data once it has been updated to NG9-1-1 standards?

• Do you have the skilled employees?
• Do you have software and tools to develop, maintain and validate

the new GIS data long term?

• Yes – Then try to make a realistic estimate of the man-hours

required to perform the work and if any additional tools or software are need to accomplish the task.

• No - Get estimates from outside sources for the work
• Be prepared with dollar amounts and scope of work details in
• rder to justify your need if grant monies become available