911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ......

27

Upload: others

Post on 02-Apr-2020

5 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016
Page 2: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

“911 call reveals confusion by dispatcher

while woman's car sunk into pond”

CHEROKEE COUNTY, GA

10/20/2016 2

Page 3: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 3

The Magic

Dial “911”

Speaking to PSAP

Emergency Call

Routing

Page 4: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 4

Legacy

40+ year old legacy

Uses tabular databases

MSAG

ALI

Page 5: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Potential Issues

Accuracy

Update Cycle

Cost

No Relationship to GIS

Constituent Expectation

10/20/2016 5

Issues MSAG/ALI

Page 6: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

E911/Legacy Workflow

Location Databases

Page 7: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

GIS role in NG911 Call Flow

Page 8: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Minimum Data Required to

Support ECRF/LVF in i3 NG9-

1-1 Architecture*Road Centerlines

PSAP Boundaries

Emergency Services Boundaries

Authoritative Boundaries

Source: data supplied to the SIF

should come from each jurisdiction as

defined by the extents of the

Authoritative Boundary polygon.

Footprint: each PSAP needs access

to a seamless, normalized and highly

accurate footprint of data from any

jurisdiction it shares a boundary with.

Update: new data and data errors

should be updated in the GIS within a

1-3 business day cycle.

Accuracy: Each source entity is

responsible for the accuracy (both

spatial and attribution) of each dataset.

This results in the need for

coordination amongst neighboring

jurisdictions as there are no allowable

gaps, overlaps or redundancies in any

of the datasets.

*Address Point data is not required per the NENA NG9-1-1 GIS Data Model but will likely be deemed so by the majority of end-users.

Page 9: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 9

900 no match ALI records when synchronized with GIS

Hamilton County Story

Page 10: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 10

900 no match ALI records when synchronized with GIS

Hamilton County Story

The comparison process will also reveal: Fictitious data,

Incomplete information,

Data that exist in only one database.

Errors or missing information exist in both databases:

Inconsistent naming conventions,

Inaccurate address information,

Improper ESN assignments to MSAG records,

Improper community assignments,

Improper exchange designations,

Other discrepancies.

Page 11: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Data Exchange

Santa Clara County• 15 GIS and Addressing

Authorities• 13 primary PSAPs• County primary PSAP for

all EMS

Page 12: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Data Cleanup and Readiness: Coordination or Technology issue?

Page 13: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 13

Page 14: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 14

Page 15: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

10/20/2016 15

Data Consultation

• Assess access and availability of required data sources from GIS authorities

• Examine the currency and completeness of data

Analysis

• MSAG/ALI Comparison

• QC Report Card

Maintenance

Planning

• Who are internal and external authorities of source data (who will provide edits)?

• Who will the mutual aid footprint of data provider be?

Data Analysis, Planning and Consulting

Page 16: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Components of the Analysis

• GIS Data “Stress Test”

• MSAG/ALI to GIS

Synchronization

• Address Comparison Tool

(ACE)

• Maintenance Workflows

10/20/2016 16

Page 17: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Purposeful Order

MSAG to

Centerline

• Correct anomalies

• Shrink MSAG/Centerline?1

Boundary

Files

• PSAP boundary true-up

• Emergency Services Boundaries

• Authoritative Boundary2

ALI to

GIS3

Iterative Validation

& Clean-Up

• Validations ran in priority

• Internal

• Between Jurisdictions4

10/20/2016 17

• ALI maintenance workflow

Page 18: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Centerline Validations

• Spatial

• Crosses Multiple Polygons

• Street pointing in wrong direction

• Not in polygon later

• Attribution

• Address range overlaps

• Parity Errors

Address Point Validations

• Spatial

• Structure on wrong side of the street

• Crosses multiple polygons

• Structure out of order

• Not in polygon layer

• Empty Geometry

• Attribute

• Not matching street range or street name

• Parity error

• On wrong block

• Out of order

• Duplicate point

Boundary Quality Control

• PSAP, ESZ, other polygons

• Gaps/Overlaps

• Attribute Spelling

Database Schemas

• Compare and map disparate datasets

• Ensure cardinality of attributes

• One-to-one mapping with master dataset

• Identify missing attributes

• Attribute type formatting

Quality Control (QC) Report Card

Page 19: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

What to Fix First?

10/20/2016 19

Page 20: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Master Street Address Guide

DI STREET LOW HIGH COMM ST O_E ESN

N 10TH ST 100 1099 WEST MONROE LA 002

N 10TH ST 2400 2699 WEST MONROE LA 002

FID PL_ADD_F PL_ADD_T PR_ADD_F PR_ADD_T PRE_DIR STREET_NAM STREET_TYP CITY_L CITY_R ESN_L ESN_R

503 401 899 400 898N 10th St West Monroe West Monroe 2 2

1498 2701 2799 2700 2798N 10th St West Monroe West Monroe 2 2

5851 1001 1099 1000 1098N 10th St West Monroe West Monroe 2 2

7585 2401 2499 2400 2498N 10th St West Monroe West Monroe 2 2

7620 2501 2599 2500 2598N 10th St West Monroe West Monroe 2 2

8021 901 999 900 998N 10th St West Monroe West Monroe 2 2

8124 2601 2699 2600 2698N 10th St West Monroe West Monroe 2 2

Typical street centerline

attribute table

Corresponding MSAG features

Page 21: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Roads in the GIS centerline file that do not exist in the

MSAG

10/20/2016 21

For example in the GIS dataset, Arnold Smith Rd has an ESN left of 88 and right of 3…In the MSAG, however, it has an ESN listing of only 3

Likely ESN 88

NOTE: coordination will be necessary between the two jurisdictions when it is time to provision a seamless centerline file to the ECRF and LVF.

Page 22: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

• DataMark Data Exchange (DX) (DX-QA)

• Translate – validate – extract

• SI and Mutual Aid Footprint Data Quality

Metrics

• DataMark Editor (DME)

• Edit functionality based upon

authoritative “users”

• Robust observation system allowing for

2-way communication of data errors

(crowd sourced or internal)

10/20/2016 22

Page 23: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

DX

Data Update

New versions of Centerline, Address Points, Boundary Files submitted via the application.

Database Translation

Schemas are verified, new data is compared to old data with only updated (adds, deletes and changes) being coalesced into the master database.

Quality Control Check

Data is again processed through the spatial and attribution quality control checks.

Reporting

Summary and detail reports are produced for each data update provided. Each feature that fails quality control metric is detailed for review or exposed for being marked as exception (and will not fail again)

Step 1 Step 2 Step 3 Step 4

Extract

A user selected footprint of the DX™ database is available for customized extraction. Data can be translated into any saved schema to meet any business driver and downloaded or published as a feed.

Step 5

Page 24: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Need for Iterative QC Assessment

Pros

Good baseline

assessment of where

data anomalies exist

Extensive “questioning” of

data

Good exposure to

MSAG/ALI validation

process

Cons

No clear path laid to what

priority errors should be

addressed

No ability to iterate

validations after updates

have been made.

10/20/2016 24

Page 25: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Address Points EditingThe Address Points layer editing session have the below controls in the Map View.1. A toolbar which has various address point editing

tools.2. Tools for collaboration like sharing, refreshing,

change history etc.3. Information related to the current editing session.4. TOC layer for showing current session changes.5. Use “Close Session” button to close the current

editing session. Make sure that the changes are saved to the server using “Save Edits” tool.

1

2 3

4

Editing of Address Point Layer

5

Page 26: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Centerline – Edit ToolbarValidate Topology option allows to validate the changes based on pre-set topology rules. The exceptions will be shown in a validation result window.

Editing of Centerline Layer (Contd..)

1

2

3

4

Page 27: 911 call reveals confusion by dispatcher...“911 call reveals confusion by dispatcher ... 10/20/2016 3 The Magic Dial “911” Speaking to PSAP Emergency Call Routing. 10/20/2016

Submit ObservationIt also has function to submit observations about all data in view.1. Right click on map area to submit observation.2. Fill in title and comments. (will auto populate

sender and location)

1

2

Steve Bein

[email protected]

DataMarkGIS.com