HSIP E911 Public Safety Answering Point (PSAP)
Metadata from the RGIS Metadata Repository
Identification Information
- Title HSIP E911 Public Safety Answering Point (PSAP)
- Date 2010-02-04
- Date Type Publication
- Cited Responsible Party
-
- Organization Name TechniGraphics, Inc.
- Role identify
- Presentation Form vector digital data
- Abstract 911 Public Safety Answering Point (PSAP) service area boundaries in New
Mexico According to the National Emergency Number Association (NENA), a Public
Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1
calls. The service area is the geographic area within which a 911 call placed using
a landline is answered at the associated PSAP. This dataset only includes primary
PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from
this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive
calls that have been transferred by a primary PSAP. Backup PSAPs provide service in
cases where another PSAP is inoperable. Most military bases have their own emergency
telephone systems. To connect to such system from within a military base it may be
necessary to dial a number other than 9 1 1. Due to the sensitive nature of military
installations, TGS did not actively research these systems. If civilian authorities
in surrounding areas volunteered information about these systems or if adding a
military PSAP was necessary to fill a hole in civilian provided data, TGS included
it in this dataset. Otherwise military installations are depicted as being covered
by one or more adjoining civilian emergency telephone systems. In some cases areas
are covered by more than one PSAP boundary. In these cases, any of the applicable
PSAPs may take a 911 call. Where a specific call is routed may depend on how busy
the applicable PSAPS are (i.e. load balancing), operational status (i.e.
redundancy), or time of date / day of week. If an area does not have 911 service,
TGS included that area in the dataset along with the address and phone number of
their dispatch center. These are areas where someone must dial a 7 or 10 digit
number to get emergency services. These records can be identified by a "Y" in the
[NON911EMNO] field. This indicates that dialing 911 inside one of these areas does
not connect one with emergency services. This dataset was constructed by gathering
information about PSAPs from state level officials. In some cases this was
geospatial information, in others it was tabular. This information was supplemented
with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was
researched to verify its tabular information. In cases where the source data was not
geospatial, each PSAP was researched to determine its service area in terms of
existing boundaries (e.g. city and county boundaries). In some cases existing
boundaries had to be modified to reflect coverage areas (e.g. "entire county north
of Country Road 30"). However, there may be cases where minor deviations from
existing boundaries are not reflected in this dataset, such as the case where a
particular PSAPs coverage area includes an entire county, and the homes and
businesses along a road which is partly in another county. Text fields in this
dataset have been set to all upper case to facilitate consistent database engine
search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have
been replaced with their closest equivalent English character to facilitate use with
database systems that may not support diacritics.
- Purpose Homeland Security Use Cases: Use cases describe how the data may be used and
help to define and clarify requirements. 1) A disaster has struck, or is predicted
for, a locality. The PSAP that may be affected must be identified and verified to be
operational. 2) In the event that the local PSAP is inoperable, adjacent PSAP
locations could be identified and utilized.
- Status Complete
- Point of Contact
-
- Individual Name Mike Thompson
- Organization Name
- Position Name Director of Geospatial Datasets
- Role Point of contact
- Voice 970-224-4996
- Facsimile 970-224-3001
- Address
-
- Delivery Point 3351 Eastbrook Drive
- City Fort Collins
- Administrative Area CO
- Postal Code 80525
- Country USA
- Electronic Mail Address mthompson@tgstech.com
- Maintenance and Update Frequency Unknown
- Descriptive Keywords Telephone Emergency reporting systems, Boundaries
- Access Constraints None
- Use Constraints None
- Language English
- Topic Category health
- Extent
-
- Geographic Bounding Box
-
- West Bound -109.050651333831
- East Bound -103.002065330281
- North Bound 37.0002933647488
- South Bound 31.3323747296804
- Temporal Extent
-
- Beginning Position 2007-09-10
- Ending Position 2008-03-31
Back to Top
Distribution Information
- Distributor
-
- Individual Name
- Organization Name Earth Data Analysis Center
- Position Name Clearinghouse Manager
- Role Point of contact
- Voice 505-277-3622 ext. 230
- Facsimile 505-277-3614
- Address
-
- Delivery Point MSC01 1110
- Delivery Point 1 University of New Mexico
- City Albuquerque
- Administrative Area NM
- Postal Code 87131-0001
- Country USA
- Electronic Mail Address clearinghouse@edac.unm.edu
- Transfer Options
-
- Online Resource ZIP
- Online Resource ESRI Shapefile (shp)
- Online Resource GML
- Online Resource KML
- Online Resource GeoJSON
- Online Resource JSON
- Online Resource Comma Separated Values (csv)
- Online Resource MS Excel format (xls)
Back to Top
Spatial Reference Information
- Spatial References
-
- Spatial Reference D_WGS_1984
-
- Online Reference EPSG:4326
- Spatial Reference WGS_1984
-
- Online Reference EPSG:4326
- Indirect Spatial Reference New Mexico (35)
- Geometric Object Type GT-polygon composed of rings
- Geometric Object Count 44
Back to Top
Data Quality Information
- Attribute Accuracy Report
-
- Report For entities that were contacted, the name, address, city, state, and five
(5) digit zip code of the Public Service Answering Point (PSAP) were verified to be
correct. Four (4) digit zip code extensions were derived from USPS (United States
Postal Service) data and were not verified. ID Check: The [ID] attribute is not
blank and each of its values is unique. Coordinate Check: Coordinates are not null
or zero and the x and y fields match the shape. Basic Address Check: Physical
addresses were verified to be non blank and to not be a "PO Box", "General
Delivery", "Highway Contract", or "Rural Route" address. Highway Address without
Type Check: Physical addresses containing the word "Highway" or "Route" were
verified to also contain a type designator such as "State", "US", or "County", if
one actually exists for the highway or route. These type designators are often
missing from addresses, leading to confusion if more than one "Highway" of the given
number exists in an area. Basic Name Check: Entity name is not blank, is not the
same as entity city, and has a minimum of 2 characters. Name does not contain
punctuation characters that can interfere with database operations, such as "
(quote) and * (asterisk). Basic Phone Check: All phone numbers (including the area
code) are ten (10) numeric digits. Alphabetic characters have been converted to the
corresponding numeric digit. City Check: Entity city is not blank and is found in
the named places file within 25 miles. County FIPS to State Compare Check: The
County represented by the tabular FIPS Code attribute is actually in the state
specified by the state attribute. Some records in this dataset have failed this
check. Because the location of the primary PSAP for the district may be located in a
different county and state than the county with the most coverage by the district,
the [fips] attribute may not always match the state specified in the [state]
attribute. County Name to State Compare Check: The County represented by the tabular
county name attribute is actually in the state specified by the state attribute.
Some records in this dataset have failed this check. Because the location of the
primary PSAP for the district may be located in a different county and state than
the county with the most coverage by the district, the [county] attribute may not
always match the state specified in the [state] attribute. Phone Number Format
Check: Phone numbers (including area code) were verified to be formatted as
nnn-nnn-nnnn. NPA_NXX Check: Area codes (sometimes called "Number Planning Areas",
or NPA's) and central office codes (sometimes known as exchanges, or NXX's) were
validated against data from the North American Number Planning Administration
(NANPA). In some cases, NPA-NXX combinations did not show up in the NANPA data but
were verified to work. Area Code Distance Check: Area code (NPA) is valid and is
within its area code Boundaries. Zip Code Check: The zip code is five (5) or nine
(9) numeric digits, is listed in the postal database, is in the same state as
indicated by the entity's [STATE] attribute, and is not a PO Box only zip code.
There are two (2) entities in this dataset that failed this check. These entities
did not meet the criteria to be processed and therefore have not been contacted by
TGS. County in Name vs. Geographic Location Check: The county name found in the name
of the entity matches geographic location. Some records in this dataset have failed
this check. Zip City Check: The entity's zip code and its city were verified to
match according to the USPS Address Information System (AIS). Zip Code Distance
Check: Checks to make sure that the entity is not too far away from its zip code
boundary. Geographic Spell Check: Words that appear in the entity name were checked
against a Standard English word list (and Spanish word list for entities in Puerto
Rico). Words not appearing in these standard word lists were then checked against
names appearing in the Geographic Names Information System (GNIS) of geographic
features that are located within 25 miles of the entity. Proper names were manually
reviewed for correct spelling.
- Quantitative Attribute Accuracy Assessment
-
- Attribute Accuracy Value
- Attribute Accuracy Explanation
- Horizontal Positional Accuracy Report
-
- Report This dataset is not topologically correct, nor will it be consistent with
any single other source.
- Quantitative Horizontal Positional Accuracy Assessment
-
- Horizontal Positional Accuracy Value
- Horizontal Positional Accuracy Explanation
- Logical Consistency Report See the "Attribute_Accuracy_Report" section. Many of the checks described in that
section check for both attribute accuracy and logical consistency. ArcMap 9.2's "Check
Geometry" was run on this dataset. There were no findings. "Check Geometry" looks for
the following problems: *Short segment: Some segments are shorter than allowed by the
system units of the spatial reference associated with the geometry. *Null geometry: The
feature has no geometry or nothing in the SHAPE field. *Incorrect ring ordering: The
polygon is topologically simple, but its rings may not be oriented correctly (outer
rings - clockwise, inner rings - counterclockwise). *Incorrect segment orientation:
Individual segments are not consistently oriented. The "to" point of segment i should be
incident on the "from" point of segment i+1. *Self intersections: The interior of each
part must not intersect itself or other parts. For a multipoint geometry, this means two
of the points in the multipoint are in the same location (same x and y coordinate).
*Unclosed rings: The last segment in a ring must have its "to" point incident on the
"from" point of the first segment. *Empty parts: The geometry has multiple parts, and
one of them is empty (has no geometry). This dataset does not pass ArcMap 9.1's "Check
Geometry"
- Completeness Report Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this
dataset. Most military bases have their own emergency telephone systems. To connect to
such system from within a military base it may be necessary to dial a number other than
9 1 1. Due to the sensitive nature of military installations, TGS did not actively
research these systems. If civilian authorities in surrounding areas volunteered
information about these systems or if adding a military PSAP was necessary to fill a
hole in civilian provided data, TGS included it in this dataset. Otherwise military
installations are depicted as being covered by one or more adjoining civilian emergency
telephone systems.
- Lineage
-
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Online
- Source Time Period of Content
-
- DateTime 2007
- Source Currentness Reference publication date
- Source Citation Abbreviation 911_Response_Districts
- Source Contribution This was used as a source of 911 Response Districts in the United
States.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media File Transfer Protocol
- Source Time Period of Content
-
- DateTime 2007-08-16
- Source Currentness Reference publication date
- Source Citation Abbreviation NM_Response_Districts
- Source Contribution This was used as a source of 911 Response Districts in New
Mexico.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media File Transfer Protocol
- Source Time Period of Content
-
- DateTime 2007-08-16
- Source Currentness Reference publication date
- Source Citation Abbreviation NM_County_Boundaries
- Source Contribution This was used as a reference to locate county boundaries of 911 Response
Districts in New Mexico.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Online
- Source Time Period of Content
-
- DateTime 2007-10-15
- Source Currentness Reference publication date
- Source Citation Abbreviation ind_res_boundaries
- Source Contribution This was used as a reference to locate Indian Reservations boundaries in
the United States.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Online
- Source Time Period of Content
-
- DateTime 2005-06-01
- Source Currentness Reference publication date
- Source Citation Abbreviation nat_park_boundaries
- Source Contribution This was used as a reference to locate National Park boundaries in the
United States.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Electronic Mail System
- Source Time Period of Content
-
- DateTime 2007-04-23
- Source Currentness Reference publication date
- Source Citation Abbreviation installation_boundaries
- Source Contribution This was used as a reference to locate Military Installation boundaries in
the United States.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Online Linkage
- Source Time Period of Content
-
- DateTime 2006
- Source Currentness Reference publication date
- Source Citation Abbreviation TIGER_County_Boundaries
- Source Contribution TIGER Boundaries were used as a reference to locate county boundaries of
the 911 Response Districts.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Online Linkage
- Source Time Period of Content
-
- DateTime 2006
- Source Currentness Reference publication date
- Source Citation Abbreviation TIGER_Place_Boundaries
- Source Contribution TIGER Boundaries were used as a reference to locate city boundaries of the
911 Response Districts in the United States.
- Source Information
-
- Source Citation
- Source Scale Denominator
- Type of Source Media Online Linkage
- Source Time Period of Content
-
- DateTime 2000
- Source Currentness Reference publication date
- Source Citation Abbreviation U.S. State Boundaries
- Source Contribution State Boundaries were used to determine seaward boundaries of the United
States.
- Process Step
-
- Process Description TGS 911 Response Districts Processing WHERE THE DATA CAME FROM: Each
state was contacted by TGS to determine an official source for PSAP locations.
GIS data was gathered from states willing to share such data. In cases where
states were unable or unwilling to share data in this format, TGS requested that
the states provide a source for identifying the PSAP locations. Original TGS
research was used to fill in missing information. HOW DATA WAS PROCESSED: METHOD
A: STATE SUPPLIED TABULAR DATA 1) If tabular data and boundaries were provided
by individual states, TGS utilized all provided PSAP boundaries and tabular
data. In most cases this data was used "as-is" without any modifications made by
TGS. Only incomplete tabular data was verified by phone contact. This is
referred to as "Method A1". 2) If only tabular data was provided by individual
states, TGS utilized a combination of several boundary resources such as: TIGER
(TIGER_Place_Boundaries and TIGER_County_Boundaries), Military Installations
(installation_boundaries), Indian Reservations (ind_res_boundaries) and National
Parks (nat_park_boundaries) to generate the extents of each PSAP. In most cases
the tabular data was used "as-is" without any modifications made by TGS. Only
incomplete tabular data was verified by phone contact. This is referred to as
"Method A2". METHOD B: TGS RESEARCHED TABULAR DATA 1) If tabular data was not
provided by individual states, TGS utilized researched data and a combination of
several boundary resources as shown Method A2. In most cases the tabular data
was verified through alternate references. Any discrepancies in tabular data
were then verified through phone contact. The extent of each PSAP boundary was
also verified through phone contact. This is referred to as "Method B1". 2) If
tabular data was not provided by individual states, but boundary extents were
provided, TGS utilized researched data and the boundaries provided by the state.
In most cases the tabular data was verified through alternate references. Any
discrepancies in tabular data were then verified through phone contact. Most
boundary data was not modified by TGS. This is referred to as "Method B2". New
Mexico - Method A1 3) In some cases areas are covered by more than one PSAP
boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where
a specific call is routed may depend on how busy the applicable PSAPS are (i.e.
load balancing), operational status (i.e. redundancy), or time of date / day of
week. 4) If an area does not have 911 service, TGS included that area in the
dataset along with the address and phone number of their dispatch center. These
are areas where someone must dial a 7 or 10 digit number to get emergency
services. These records can be identified by a "Y" in the [NON911EMNO] field.
This indicates that dialing 911 inside one of these areas does not connect one
with emergency services. 5) Seaward boundaries were determined using the U.S.
Bureau of the Census' U.S. State Boundaries file with a cluster tolerance of 50
meters. 6) Ran Check Geometry and Repair Geometry. These checks passed in ArcMap
9.2. 7) Gaps between simple geometries over a decimeter were eliminated. 8) Four
digit United States Postal Service (USPS) zip code extensions were assigned
based upon the USPS Address Information System (AIS). 9) County name and FIPS
codes were assigned through a spatial join. In instances where on PSAP covers
multiple counties, the county and fips with the largest amount of coverage is
represented. 10) All text fields were set to all upper case. 11) Leading and
trailing spaces were trimmed from all text fields.
- Source Used Citation Abbreviation 911_Response_Districts
- Source Used Citation Abbreviation NM_Response_Districts
- Source Used Citation Abbreviation NM_County_Boundaries
- Source Used Citation Abbreviation ind_res_boundaries
- Source Used Citation Abbreviation nat_park_boundaries
- Source Used Citation Abbreviation installation_boundaries
- Source Used Citation Abbreviation TIGER_County_Boundaries
- Source Used Citation Abbreviation TIGER_Place_Boundaries
- Source Used Citation Abbreviation U.S. State Boundaries
- Process Date 2008-04-09
- Process Time
- Process Contact
-
- Individual Name Nicole Hackworth
- Organization Name
- Position Name Project Manager
- Role Point of contact
- Voice 330-263-6222
- Facsimile
- Address
-
- Delivery Point 2000 Noble Drive
- City Wooster
- Administrative Area OH
- Postal Code 44691
- Country USA
- Electronic Mail Address nhackworth@tgstech.com
Back to Top
Metadata Reference Information
- File Identifier c3e6f7a7-df4a-4954-9264-5fbedcdb63e0
- Metadata Language English
- Hierarchy Level Dataset
- Date Stamp 2024-04-26
- Metadata Standard Name ISO 19115:2003
- Metadata Standard Version 1.0
- Metadata Contact
-
- Individual Name
- Organization Name Earth Data Analysis Center
- Position Name Clearinghouse Manager
- Role Point of contact
- Voice 505-277-3622 ext. 230
- Facsimile 505-277-3614
- Address
-
- Delivery Point MSC01 1110
- Delivery Point 1 University of New Mexico
- City Albuquerque
- Administrative Area NM
- Postal Code 87131-0001
- Country USA
- Electronic Mail Address clearinghouse@edac.unm.edu
Back to Top