The Geographic Information Systems (GIS) Data Model document supports the NENA Next Generation 9-1-1 (NG9-1-1) Core Services (NGCS) of location validation and routing, both geospatial call routing or to the appropriate agency for dispatch. This model also defines the GIS data layers (layers) used in local Public Safety Answering Point (PSAP) and response agency mapping applications for handling and responding to 9-1-1 calls.
The objective of the templates in this repository is to provide a common transport format of NG9-1-1 data layers between GIS Data Providers and a NGCS Spatial Interface (SI). While the following scripts and tools may be used by GIS Data Providers as a template for the management of their own NG9-1-1 data, it is expected that each GIS Data Provider will adapt the scripts and extend the schema to meet their specific organization's needs and requirements.
There are two data structures provided as part of the NG9-1-1 GIS Data Model templates package; an open source version based on a PostgreSQL/PostGIS database and a version based on the Esri File GeoDatabase. The templates are meant to represent what NG9-1-1 GIS data should look like when it is being exchanged between two parties according to the NENA GIS Data Model Standard.
While preparing these templates, the Working Group developed two sets of scripts (Python and SQL) to help in creation of the template files. The scripts were originally intended to serve only as a method to help the Working Group develop the template files. However, the Working Group felt that the scripts could also prove useful to the GIS community, so they are included. While the scripts may prove useful, the Working Group does urge caution in using these scripts directly as it presents some potential for an entity to diverge from, and become incompatible with, the official NENA template files.
The current templates include:
Within the templates there are domains that have no entries. These domains include:
AddCode, AddCode_L and AddCode_R)DiscrpAgID) County, County_L, and County_R)ESN, ESN_L, and ESN_R)PostCode, PostCode_L, and PostCode_R)PostComm, PostComm_L and PostComm_R)ServiceURI) The GIS Data Provider is expected to populate these domains, in accordance with guidelines specified within the NG9-1-1 GIS Data Model standard, based on the needs within their jurisdiction.
For domains that have entries, but do not completely meet the GIS Data Provider's
needs, the GIS Data Provider is encouraged to find the proper channel through
which those domains can be extended. For example, in the case of the
Legacy Street Name Type (LSt_Typ[_L\_R]) , the owner of those entries is
the United States Postal Service; to extend that domain requires a change in
USPS Publication 28 Appendix C1.
In the case of the Street Name Pre/Post Types, Street Name Pre Type Separator
and Placement Method domains, those entries are maintained by NENA through the
NENA Registry System and
new entries can be requested through that system. In the case of
Country, Place Type and Service URN the GIS Data Provider
is encouraged to contact NENA to seek more direction for requesting new entries.
Lastly, there are some domains where extension is not anticipated. Those
include domains such as Location Marker Indicator (LM_Ind),
Location Marker Unit of Measurement (LM_Unit),
Legacy Street Name Pre/Post Directional, Street Name Pre/Post Directional,
One Way, Parity, Road Class, and Validation.
However, if a GIS Data Provider believes
changes are needed for these domains, the entity is encouraged to contact NENA
to seek more direction for requesting new entries.
The SiteStructureAddressPoint layer PlaceType domain specifies the values of the IANA Location Types Registry. The Location Types defined in this registry include vehicles (e.g., "aircraft", "automobile", "bus", "bicycle", etc.). Upon discussion of the working group, it was agreed that it is uncommon to address a vehicle but rather the space the vehicle occupies. Therefore, the vehicle location types were excluded from the templates as it is unusual to address a location that moves.
In future version of NENA-STA-006 it is expected that the LandmarkNameCompleteAliasTable and LandmarkNamePartTable will be removed.
The owner of this repository approves all changes to the repository.
This repository is owned by the NENA Data Structures Committee, DS-GIS Template working group.
Contact:
All notable changes to NG9-1-1 GIS Data Model Templates will be documented in this file. This project adheres to the NENA Rules for Code Repositories. For a more detailed Change Log, please visit each packages respective CHANGE_LOG.
Found a bug or want to suggest an enhancement? Check out previously logged Issues. If you don't see what you're looking for, feel free to submit a new issue.
The NENA Data Model Working Group welcomes contributions from anyone and everyone. There are many ways you can contribute to this repository.
By contributing your code, you agree to license your contribution under the terms of the Apache License 2.0.
To work in 9-1-1 is to be part of one of the most important institutions in America and across the globe. Since the first 9-1-1 call was placed in February 1968, untold millions of lives have been saved because of 9-1-1 professionals’ dedication to public safety and service. NENA: The 9-1-1 Association – comprised of its members, board, staff, volunteers, and event participants – is a community for all who are devoted to carrying this legacy forward and setting the standard for excellence in the industry. To do so, NENA strives to exemplify and embody the core values of respect, integrity, commitment, and cooperation.
Each association member, volunteer, and event attendee shall:
Individuals determined by the CEO, the Board of Directors, or its designee, to have violated the terms of this policy may, at NENA’s sole discretion, be subject to the application of measures that may include notification of the person’s agency or employer, forfeiture of event attendance, or revocation of membership. Should the NENA Board, or its designee, determine to remove an attendee from a NENA event or revoke membership, then it shall provide the affected person with an opportunity to respond to NENA’s concerns or allegations.
The above has been edited for clarity and is an abridged version of the board-approved Ethics & Code of Conduct Policy. See the full policy here.
NENA requires an explicit Intellectual Property Rights & Antitrust Policy to conduct its daily work. The objectives of this policy are to:
See the full policy here.
Copyright 2019-2023 National Emergency Number Association
Licensed under the Apache License, Version 2.0 (the "License"); you may not use these files except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. A copy of the License is available in the repository's LICENSE file.
Unless required by applicable law or agreed to in writing the tools distributed under the License are distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.