Upload
edmund-dickerson
View
220
Download
1
Embed Size (px)
Citation preview
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
GIS Data Model for NG9-1-1Marc Berryman, ENP
Richard Kelly
Michelle Manuel
Raymond Horner
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
NENA Intellectual Property Rights Disclaimer On behalf of the National Emergency Number Association, I welcome you to this meeting. It is
essential that we observe certain ground rules as we participate in this meeting. Antitrust laws
of the United States prohibit the discussion of a number of matters in a meeting such as this. It
is important that discussions at this meeting address only that information needed for
legitimate functioning of NENA.
Relative to any company or companies represented by any of us, there can be no discussion of:
prices; terms and conditions such as credit terms, markups, or profits; geographical areas in
which a company or companies seek or may seek to do business; the persons or companies
with whom a company or companies will or will not do business; production costs; or any future
marketing plans.
Any departure from these ground rules could result in severe civil and criminal penalties to you
as individuals and/or to your companies. Federal sentencing guidelines mandate jail sentences
for antitrust violations and call for criminal fines that may range into the millions of dollars.
NENA is committed to complying with federal antitrust regulations. Before participating in this
meeting, you are encouraged to familiarize yourself with NENA’s complete Intellectual Property
Rights and Antitrust policies, available at www.nena.org/ipr.
It is a condition of your participation in this committee that you accept the terms of the NENA
IPR Policy. If you do not accept these terms, please leave the meeting at this time.
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
WelcomeNENA GIS Data Model for NG9-1-1
Standard
Goals for todayHigh level overview of issuesDocument structureMajor discussions and decisions Discussion of Issues
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Workgroup HistoryWork Started Late 2011Meetings held weekly with some notable
exceptionsDocument has gone through Authoring
Review Currently addressing Issues brought up
after Authoring Review
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Membership 67 Members Over ½ of members work for 9-1-1
Authorities Incredible Depth of Knowledge of Public
Safety GIS
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Scope and PurposeThis document updates previous GIS Data Models for use in the NG9-1-1 system while remaining backwards compatible with existing E9-1-1 GIS data needs.
The new GIS Data Model is designed to support the location conveyed in the PIDF-LO but will work with ALI as one moves to NG9-1-1.
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Benefits
Establish standardized GIS data
provisioning requirements and
structure for all users
Establish guidelines for GIS data
needed to support existing E9-1-1
systems, while transitioning into NG9-
1-1 systems
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Benefits
Enable compatibility and interoperability
Facilitate GIS data provisioning to NG9-1-1
functional elements
Promote consistent data elements for software
development
Provide a framework to help migrate existing GIS
datasets to i3 Next Generation 9-1-1 systems
Streamlines data maintenance
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
3 Operational or Technical Description
3.1 Background
3.2 Metadata
3.3 Standardized Data Fields
3.4 Universally Unique IDs (UUID)
3.5 eXtensible Markup Language Tags
3.6 GIS Database Model Layers
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
3 Operational or Technical Description
3.7 Road Centerlines - Required
3.8 Emergency Services Boundaries -
Required
3.9 Authoritative Boundary - Required
3.10Road Name Alias Methodology Used
3.11Road Name Alias Table – Strongly
Recommended (SR)
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
3 Operational or Technical Description
3.12 Site / Structure Address Points – SR
3.14 Cell Sector Location - SR
3.15States or Equivalents – SR
3.16Counties or Equivalents – SR
3.17Municipal Boundary – SR
3.18Municipality Division Boundary – Recommended
3.19Neighborhood Boundary – Recommended
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
3 Operational or Technical Description
3.19Railroad Centerlines
3.20Hydrology Line
3.21Hydrology Polygon
3.22Mile Marker Location
3.23Projection
3.24Detailed Description of Field Names and
Associated Attribute Data
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Remaining Issues
Authorative Boundary
This required layer describes the polygon
boundary that defines the geographic area for
which the GIS data is authoritative
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Remaining IssuesRoad Name Alias Table
The recorded legal road name as assigned by the
local addressing authority should be the name
used in the Road Centerlines,
however
Alias road names are common and must be
considered
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Remaining Issues
Road Name Alias Table
This outlines an example of a data structure that
can be used to create a related table of alias road
names
Local 9-1-1 Authorities may already have a
methodology in place to manage alias road names
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Remaining Issues
Road Name Alias Table
Regardless of which method is used to define alias
road names, it is up to the 9-1-1 Authority to ensure
the methods they use are compatible with the NG9-
1-1 system and all other software and applications
that will use the alias methodology
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Remaining Issues
Road Name Alias Table
To ensure proper civic location validation by the LVF
and proper routing by the ECRF, a standardized
method of maintaining alias road names is required
The use of this Road Name Alias Table will facilitate
the sharing of data in a consistent manner by
various local 9-1-1 Authorities
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
RCL Unique
ID
Street Name Pre
Modifier
Street Name Pre
Directional
Street Name Pre
Type
Street Name
Street Name Post Type
Street Name Post Directiona
l
Street Name Post
Modifier
1 State Route
23
2 State Route
23
3 State Route
23
4 State Route
23
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Unique Alias ID
RCL Unique ID
Street Name Pre Modifier
Street Name Pre Direction
al
Street Name Pre Type
Street Name
Street Name Post Type
Street Name Post
Directional
Street Name Post
Modifier
1 1 United States Highway
59
2 2 United States Highway
59
3 3 United States Highway
59
4 4 United States Highway
59
5 1 Scenic Blvd
6 2 Scenic Blvd
7 3 Main St
8 4 Main St
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Cell sectors are the locations of the points which
represent the cell sectors. Cell sectors must be
within the PSAP polygon of the PSAP that the
wireless calls from a given cell sector will be
initially routed too
Cell Sector Location - SR
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Other Issues?
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Next Steps?
Next Steps?
N E N A D e v e l o p m e n t C o n f e r e n c e | O c t o b e r 2 0 1 4 | O r l a n d o , F l o r i d a
Thank You
Marc Berryman, ENP
Richard Kelly
Michelle Manuel
Raymond Horner