HSIP E911 Public Safety Answering Point (PSAP)
Metadata from the RGIS Metadata Repository
Identification Information
- Citation
-
- Citation Information
-
- Originator TechniGraphics, Inc.
- Publication Date 2010-02-04
- Publication Time 10:06:57
- Title HSIP E911 Public Safety Answering Point (PSAP)
- Geospatial Data Presentation Form vector digital data
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/services/ogc/wms?SERVICE=wms&REQUEST=GetCapabilities&VERSION=1.1.1
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/services/ogc/wfs?SERVICE=wfs&REQUEST=GetCapabilities&VERSION=1.0.0
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.shp
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.original.zip
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.gml
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.kml
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.geojson
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.json
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.csv
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.xls
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/FGDC-STD-001-1998.xml
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/FGDC-STD-001-1998.html
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19115:2003.xml
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19115:2003.html
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19119:WMS.xml
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19119:WFS.xml
- Online Linkage https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19110.xml
- Larger Work Citation
- Description
-
- 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.
- Time Period of Content
-
- Range of Dates/Times
-
- Beginning Date 2007-09-10
- Ending Date 2008-03-31
- Currentness Reference ground condition
- Status
-
- Progress Complete
- Maintenance and Update Frequency Unknown
- Spatial Domain
-
- Bounding Coordinates
-
- West Bounding Coordinate -109.050651333831
- East Bounding Coordinate -103.002065330281
- North Bounding Coordinate 37.0002933647488
- South Bounding Coordinate 31.3323747296804
- Keywords
-
- Theme
-
- Thesaurus LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov
- Keyword Telephone Emergency reporting systems
- Keyword Boundaries
- Theme
-
- Thesaurus ISO 19115 Topic Categories
- Keyword health
- Place
-
- Thesaurus LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov
- Keyword New Mexico
- Access Constraints None
- Use Constraints None
- Point of Contact
-
- Contact Information
-
- Contact Person Primary
-
- Contact Person Mike Thompson
- Contact Organization TechniGraphics, Inc.
- Contact Organization Primary
-
- Contact Organization
- Contact Person
- Contact Position Director of Geospatial Datasets
- Contact Address
-
- Address Type Mailing and Physical Address
- Address 3351 Eastbrook Drive
- City Fort Collins
- State or Province CO
- Postal Code 80525
- Country USA
- Contact Voice Telephone 970-224-4996
- Contact Facsimile Telephone 970-224-3001
- Contact Electronic Mail Address mthompson@tgstech.com
- Hours of Service 8am - 5pm, Monday - Friday, Mountain Time
- Contact Instructions
- Security Information
-
- Security Classification System DOD
- Security Classification Unclassified
- Security Handling Description Unclassified
- Native Data Set Environment Microsoft Windows XP Professional Version 2002 Service Pack 2 >ESRI ArcMap 9.1
>ESRI ArcMap 9.2 >ESRI ArcView 3.2 Metadata written using TKME by Peter N.
Schweitzer (U.S. Geological Survey, Reston, VA 22092) version 2.9.17
http://geology.usgs.gov/tools/metadata/ Metadata tested for compliance to
FGDC-STD-001-1998 and converted to HTML using MP version 2.8.25 by Peter N. Schweitzer
(U.S. Geological Survey) http://geology.usgs.gov/tools/metadata/
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
-
- Citation Information
-
- Originator TGS research
- Publication Date 2007
- Publication Time
- Title 911 Response Districts
- Geospatial Data Presentation Form
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Source Scale Denominator
- Type of Source Media Online
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator New Mexico Department of Health
- Publication Date 2007-08-16
- Publication Time
- Title NM_PSAPS_Live
- Geospatial Data Presentation Form
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Source Scale Denominator
- Type of Source Media File Transfer Protocol
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator New Mexico Department of Health
- Publication Date 2007-08-16
- Publication Time
- Title nm_cnty_rgis_20060523
- Geospatial Data Presentation Form
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Source Scale Denominator
- Type of Source Media File Transfer Protocol
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator National Atlas of the United States
- Publication Date 2007-10-15
- Publication Time
- Title indlanp020
- Geospatial Data Presentation Form
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Online Linkage http://nationalatlas.gov/atlasftp.html
- Source Scale Denominator
- Type of Source Media Online
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator National Park Service
- Publication Date 2005-06-01
- Publication Time
- Title nps_Boundaries
- Geospatial Data Presentation Form
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Online Linkage http://nrdata.nps.gov/programs/lands/nps_Boundaries.zip
- Source Scale Denominator
- Type of Source Media Online
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator Office of the Under Secretary of Defense
- Publication Date 2007-04-23
- Publication Time
- Title installation_Boundaries
- Geospatial Data Presentation Form
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details This was provided by the Homeland Infrastructure Foundation-Level
Data (HIFLD) Working Group.
- Source Scale Denominator
- Type of Source Media Electronic Mail System
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator U.S. Department of Commerce, U.S. Census Bureau, Geography
Division
- Publication Date 2006
- Publication Time
- Title TIGER 2006fe county boundaries
- Geospatial Data Presentation Form vector digital data
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Online Linkage http://www.census.gov/geo/www/tiger/tiger2006fe/tgr2006fe.html
- Source Scale Denominator
- Type of Source Media Online Linkage
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator U.S. Department of Commerce, U.S. Census Bureau, Geography
Division
- Publication Date 2006
- Publication Time
- Title TIGER 2006fe Place boundaries
- Geospatial Data Presentation Form vector digital data
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Online Linkage http://www.census.gov/geo/www/tiger/tiger2006fe/tgr2006fe.html
- Source Scale Denominator
- Type of Source Media Online Linkage
- Source Time Period of Content
-
- 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
-
- Citation Information
-
- Originator U.S. Bureau of the Census (BOC)
- Publication Date 2000
- Publication Time
- Title U.S. State Boundaries
- Geospatial Data Presentation Form vector digital data
- Publication Information
-
- Publication Place
- Publisher
- Other Citation Details
- Online Linkage http://www.census.gov
- Source Scale Denominator
- Type of Source Media Online Linkage
- Source Time Period of Content
-
- 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
-
- Contact Information
-
- Contact Person Primary
-
- Contact Person Nicole Hackworth
- Contact Organization TechniGraphics, Inc.
- Contact Organization Primary
-
- Contact Organization
- Contact Person
- Contact Position Project Manager
- Contact Address
-
- Address Type Mailing and Physical Address
- Address 2000 Noble Drive
- City Wooster
- State or Province OH
- Postal Code 44691
- Country USA
- Contact Voice Telephone 330-263-6222
- Contact Facsimile Telephone
- Contact Electronic Mail Address nhackworth@tgstech.com
- Hours of Service 7:30am - 4:30pm, Monday - Friday, Eastern Time
- Contact Instructions
Back to Top
Spatial Data Organization Information
- Indirect Spatial Reference Method New Mexico (35)
- Direct Spatial Reference Method Vector
- Point and Vector Object Information
-
- SDTS Terms Description
-
- SDTS Point and Vector Object Type GT-polygon composed of rings
- Point and Vector Object Count 44
Back to Top
Spatial Reference Information
- Spatial Reference
-
- Name D_WGS_1984
- Code EPSG:4326
- URL http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4326
- Spatial Reference
-
- Name WGS_1984
- Code EPSG:4326
- URL http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4326
Back to Top
Entity and Attribute Information
- Detailed Description
-
- Entity Type
-
- Entity Type Label911 Public Safety Answering Point (PSAP) service area boundaries in New
Mexico
- Entity Type Definition 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.
- Entity Type Definition Source TGS
- Attribute
-
- Attribute Label FID
- Attribute Definition Internal feature number.
- Attribute Definition Source ESRI
- Attribute Domain Values
-
- Unrepresentable Domain Sequential unique whole numbers that are automatically generated.
- Attribute
-
- Attribute Label SHAPE
- Attribute Definition Feature geometry.
- Attribute Definition Source ESRI
- Attribute Domain Values
-
- Unrepresentable Domain Coordinates defining the features.
- Attribute
-
- Attribute Label ID
- Attribute Definition Unique identifier for feature.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label SECCLASS
- Attribute Definition Security classification of feature.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Enumerated Domain
-
- Enumerated Domain Value UNCLASSIFIED
- Enumerated Domain Value Definition Entity is unclassified.
- Enumerated Domain Value Definition Source TGS
- Attribute
-
- Attribute Label NAME
- Attribute Definition Name of the 911 Response District. If the name is unknown, TGS has
attributed this field with the same information found in the [PSAP_NAME]
attribute.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label PSAP_NAME
- Attribute Definition Name of the primary PSAP for the district. If the primary PSAP is unknown,
TGS has attributed this with the same information found in the [NAME] attribute.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label FCC_ID
- Attribute Definition FCC ID for the primary PSAP that serves the district.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label STATE_ID
- Attribute Definition State ID for the primary PSAP that serves the district.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label TELEPHONE
- Attribute Definition Ten (10) digit telephone number for entity formatted as
nnn-nnn-nnnn.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Only numeric digits are used.
- Attribute
-
- Attribute Label FAX
- Attribute Definition Ten (10) digit fax number for the primary PSAP for the district formatted
as nnn-nnn-nnnn. All alphabetic characters have been translated to the
corresponding numeric digit.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Phone numbers formatted as nnn-nnnn. Only numeric digits are used. The
first three (3) digits (the exchange) must form a valid combination with the
area code. A list of valid area code and exchange combinations can be
obtained from http://www.nanpa.com
- Attribute
-
- Attribute Label ADDRESS
- Attribute Definition Physical street address for the primary PSAP that serves the district. "PO
Box", "General Delivery", "Rural Route", and "Highway Contract" addresses are
not considered physical addresses and should not appear in this attribute. Some
areas do not have regular city style addressing so entities in those areas may
not have a street number. In such cases, the name of the road they are located
on is listed in this attribute. Some rural areas may not have named roads. In
these rare cases, this attribute will be blank.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label ADDRESS2
- Attribute Definition Location within physical address, e.g., floor, suite, building.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label CITY
- Attribute Definition The name of the city associated with the physical address for the primary
PSAP that serves the district.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label STATE
- Attribute Definition Two (2) character abbreviation for state associated with the physical
address of the primary PSAP that serves the district. In almost all cases, this
is the same as the state where the entity has been depicted geospatially.
However, there are cases, particularly where an entity is part of a larger
facility that cuts across state lines, where the entity's location may be
depicted in a state other than the one indicated in this attribute. Also, the
state in which an entity appears to be located may change depending on the scale
of the state boundaries theme being used.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Codeset Domain
-
- Codeset Name Official USPS Abbreviations - State Abbreviations
- Codeset Source United States Postal Service
http://www.usps.com/ncsc/lookups/usps_abbreviations.html
- Attribute
-
- Attribute Label ZIP
- Attribute Definition Five (5) digit USPS zip code associated with the physical address of the
primary PSAP that serves the district.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Codeset Domain
-
- Codeset Name USPS Address Information System - Domain is further restricted by
only allowing physical (non PO Box only) zip codes.
- Codeset Source United States Postal Service
- Attribute
-
- Attribute Label ZIPP4
- Attribute Definition Four (4) digit USPS zip code extension associated with the physical address
of the primary PSAP that serves the district. This attribute was automatically
assigned using the entity's physical address and USPS address information system
(AIS) data.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Codeset Domain
-
- Codeset Name USPS Address Information System (AIS) - ZIP9
- Codeset Source United States Postal Service
- Attribute
-
- Attribute Label COUNTY
- Attribute Definition Name of the largest county in which the district covers. The district may
not cover the entire county. If multiple counties are covered, the county with
the largest amount of coverage is represented.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Codeset Domain
-
- Codeset Name Geographic Names Information System (GNIS)
- Codeset Source US Department of the Interior - US Geologic Survey
- Attribute
-
- Attribute Label FIPS
- Attribute Definition Five (5) digit FIPS (Federal Information Processing Standards) Code for the
largest County or Counties which the district covers. The district may not cover
the entire county. If multiple counties are covered, the county fips with the
largest amount of coverage is represented. The first two (2) digits represent
the state and the last three (3) digits identify the county within the
state.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Codeset Domain
-
- Codeset Name Federal Information Processing Standards Publications - Counties
and Equivalent Entities of the U.S., Its Possessions, and Associated
Areas
- Codeset Source National Institute of Standards and Technology (NIST)
http://www.itl.nist.gov/fipspubs/co-codes/states.txt
- Attribute
-
- Attribute Label EMERGTITLE
- Attribute Definition Title of person or name of office for emergency point of contact.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label EMERGTEL
- Attribute Definition Ten (10) digit telephone number of emergency point of contact for the
primary PSAP that serves the District formatted as nnn-nnn-nnnn. All alphabetic
characters have been translated to the corresponding numeric digit.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Phone numbers, including area code, formatted as nnn-nnn-nnnn. A list of
valid area code and exchange combinations can be found at
http://www.nanpa.com
- Attribute
-
- Attribute Label EMERGEXT
- Attribute Definition Telephone extension for emergency point of contact for the primary PSAP
that serves the District.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
- Attribute
-
- Attribute Label NON911EMNO
- Attribute Definition Indicates if dialing 911 inside the area connects one with emergency
services.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Enumerated Domain
-
- Enumerated Domain Value Y
- Enumerated Domain Value Definition Indicates that dialing 911 inside the area does not connect one with
emergency services. These are areas where someone must dial a 7 or 10
digit number to get emergency services.
- Enumerated Domain Value Definition Source TGS
- Enumerated Domain Value N
- Enumerated Domain Value Definition Indicates that dialing 911 inside the area does not connect one with
emergency services and that it is necessary to dial a 7 or 10 digit
number to contact emergency services.
- Enumerated Domain Value Definition Source TGS
- Attribute
-
- Attribute Label NAICSCODE
- Attribute Definition NAICS (North American Industry Classification System) Code for entity.
NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's
primary function, regardless of if that is the function that qualified it to be
included in this dataset.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Codeset Domain
-
- Codeset Name North American Industry Classification System (NAICS
2002)
- Codeset Source US Census Bureau -
http://www.census.gov/epcd/www/naics.html
- Attribute
-
- Attribute Label NAICSDESCR
- Attribute Definition NAICS (North American Industry Classification System) Description for
entity. The "Index Entries" that appear on the NAICS webpage
(http://www.census.gov/epcd/www/naics.html) are being used to populate this
attribute as opposed to the "NAICS Title". While there is a one to one
correspondence between NAICS Codes and "NAICS Titles", there is a one to many
relationship between NAICS Codes and the "Index Entries". By using the "Index
Entries", we have placed the entities that make up this layer into more specific
categories; however, the user of this data should be aware that this was not the
intended purpose of these "Index Entries". The "Index Entries" were intended as
a way to search the NAICS database and as a way of enumerating ways in which
establishments falling under the given NAICS Code may be named. Thus, there are
often two or more "Index Entries" that are synonyms, for example: "Prisons" and
"Penitentiaries". In cases like this, we have standardized on one "Index Entry".
NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's
primary function, regardless of the function that qualified it to be included in
this dataset.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Enumerated Domain
-
- Enumerated Domain Value DISASTER PREPAREDNESS AND MANAGEMENT OFFICES, GOVERNMENT
- Enumerated Domain Value Definition DISASTER PREPAREDNESS AND MANAGEMENT OFFICES, GOVERNMENT - [NAICS
Code 922190]: This industry comprises government establishments
primarily engaged in public order and safety (except courts, police
protection, legal counsel and prosecution, correctional institutions,
parole offices, probation offices, pardon boards, and fire
protection).
- Enumerated Domain Value Definition Source U.S. Census Bureau
- Attribute
-
- Attribute Label WEB
- Attribute Definition Web address for the primary PSAP of the District.
- Attribute Definition Source TGS
- Attribute Domain Values
-
- Unrepresentable Domain Text
Back to Top
Distribution Information
- Distributor
- Resource Description Downloadable Data
- Distribution Liability The material on this site is made available as a public service. Maps and data are to be used for reference purposes only
and the Earth Data Analysis Center (EDAC), Resource Geographic Information System (RGIS) and The University of New Mexico
are not responsible for any inaccuracies herein contained. No responsibility is assumed for damages or other liabilities due
to the accuracy, availability, use or misuse of the information herein provided. Unless otherwise indicated in the documentation
(metadata) for individual data sets, information on this site is public domain and may be copied without permission; citation
of the source is appreciated.
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name ZIP
- Transfer Size 1
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.original.zip
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name ESRI Shapefile (shp)
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.shp
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name GML
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.gml
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name KML
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.kml
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name GeoJSON
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.geojson
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name JSON
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.json
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name Comma Separated Values (csv)
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.csv
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Standard Order Process
-
- Digital Form
-
- Digital Transfer Information
-
- Format Name MS Excel format (xls)
- Transfer Size 5
- Digital Transfer Option
-
- Online Option
-
- Computer Contact Information
-
- Network Address
-
- Network Resource Name https://gstore.unm.edu/apps/rgis/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.xls
- Access Instructions Download from Resource Geographic Information System (RGIS) at http://rgis.unm.edu.
- Fees None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu).
- Ordering Instructions Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Custom Order Process Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu
- Technical Prerequisites Adequate computer capability is the only technical prerequisite for viewing data in digital form.
Back to Top
Metadata Reference Information
- Metadata Date 2024-04-26
- Metadata Review Date
- Metadata Future Review Date
- Metadata Contact
-
- Contact Information
-
- Contact Person Primary
-
- Contact Person
- Contact Organization
- Contact Organization Primary
-
- Contact Organization Earth Data Analysis Center
- Contact Person
- Contact Position Clearinghouse Manager
- Contact Address
-
- Address Type mailing and physical address
- Address MSC01 1110
- Address 1 University of New Mexico
- City Albuquerque
- State or Province NM
- Postal Code 87131-0001
- Country USA
- Contact Voice Telephone 505-277-3622 ext. 230
- Contact Facsimile Telephone 505-277-3614
- Contact Electronic Mail Address clearinghouse@edac.unm.edu
- Hours of Service 0800 - 1700 MT, M-F -7 hours GMT
- Contact Instructions
- Metadata Standard Name FGDC Content Standards for Digital Geospatial Metadata
- Metadata Standard Version FGDC-STD-001-1998
- Metadata Time Convention
- Metadata Access Constraints
- Metadata Use Constraints
- Metadata Security Information
-
- Security Classification System
- Security Classification
- Security Handling Description
- Metadata Extensions
Back to Top