RGIS::c3e6f7a7-df4a-4954-9264-5fbedcdb63e0::ISO-19115:2003 eng; USA Director of Geospatial Datasets 970-224-4996 970-224-3001 3351 Eastbrook Drive Fort Collins CO 80525 USA mthompson@tgstech.com 8am - 5pm, Monday - Friday, Mountain Time pointOfContact 2014-06-16 ISO 19115 Geographic Information - Metadata ISO 19115 44 New Mexico (35) D_WGS_1984 revision http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4326 resourceProvider 4326 WGS_1984 revision http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::4326 resourceProvider 4326 HSIP E911 Public Safety Answering Point (PSAP) 2010-02-04T10:06:57 publication Downloadable Data TechniGraphics, Inc. originator 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. 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. Director of Geospatial Datasets 970-224-4996 970-224-3001 3351 Eastbrook Drive Fort Collins CO 80525 USA mthompson@tgstech.com 8am - 5pm, Monday - Friday, Mountain Time Telephone Emergency reporting systems Boundaries LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov New Mexico LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov Access Constraints: None. Use Constraints: None eng; USA health 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/ -109.050651333831 -103.002065330281 31.3323747296804 37.0002933647488 ground condition 2007-09-10 2008-03-31 true Entity and Attribute Information http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19110.xml http Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu ZIP 1 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.original.zip Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu ESRI Shapefile (shp) 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.shp Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu GML 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.gml Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu KML 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.kml Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu GeoJSON 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.geojson Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu JSON 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.json Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu Comma Separated Values (csv) 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.csv Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT distributor None. The files are available to download from Resource Geographic Information System (RGIS) (http://rgis.unm.edu). Contact Earth Data Analysis Center at clearinghouse@edac.unm.edu MS Excel format (xls) 5 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.xls http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/services/ogc/wms?SERVICE=wms&REQUEST=GetCapabilities&VERSION=1.1.1 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/services/ogc/wfs?SERVICE=wfs&REQUEST=GetCapabilities&VERSION=1.0.0 http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.shp http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.original.zip http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.gml http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.kml http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.geojson http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.json http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.csv http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/2008_04_09_nm_911_psap.derived.xls http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/FGDC-STD-001-1998.xml http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/FGDC-STD-001-1998.html http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19115:2003.xml http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19115:2003.html http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19119:WMS.xml http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19119:WFS.xml http://gstore.unm.edu/apps/rgisarchive/datasets/c3e6f7a7-df4a-4954-9264-5fbedcdb63e0/metadata/ISO-19110.xml 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" 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. 2008-04-09T00:00:00 Project Manager 330-263-6222 2000 Noble Drive Wooster OH 44691 USA nhackworth@tgstech.com 7:30am - 4:30pm, Monday - Friday, Eastern Time 911_Response_Districts NM_Response_Districts NM_County_Boundaries ind_res_boundaries nat_park_boundaries installation_boundaries TIGER_County_Boundaries TIGER_Place_Boundaries U.S. State Boundaries This was used as a source of 911 Response Districts in the United States. 911 Response Districts 911_Response_Districts 2007-01-01T00:00:00 TGS research publication date 2007-01-01 This was used as a source of 911 Response Districts in New Mexico. NM_PSAPS_Live NM_Response_Districts 2007-08-16T00:00:00 New Mexico Department of Health publication date 2007-08-16 This was used as a reference to locate county boundaries of 911 Response Districts in New Mexico. nm_cnty_rgis_20060523 NM_County_Boundaries 2007-08-16T00:00:00 New Mexico Department of Health publication date 2007-08-16 This was used as a reference to locate Indian Reservations boundaries in the United States. indlanp020 ind_res_boundaries 2007-10-15T00:00:00 National Atlas of the United States publication date 2007-10-15 This was used as a reference to locate National Park boundaries in the United States. nps_Boundaries nat_park_boundaries 2005-06-01T00:00:00 National Park Service publication date 2005-06-01 This was used as a reference to locate Military Installation boundaries in the United States. installation_Boundaries installation_boundaries 2007-04-23T00:00:00 Office of the Under Secretary of Defense publication date 2007-04-23 TIGER Boundaries were used as a reference to locate county boundaries of the 911 Response Districts. TIGER 2006fe county boundaries TIGER_County_Boundaries 2006-01-01T00:00:00 U.S. Department of Commerce, U.S. Census Bureau, Geography Division publication date 2006-01-01 TIGER Boundaries were used as a reference to locate city boundaries of the 911 Response Districts in the United States. TIGER 2006fe Place boundaries TIGER_Place_Boundaries 2006-01-01T00:00:00 U.S. Department of Commerce, U.S. Census Bureau, Geography Division publication date 2006-01-01 State Boundaries were used to determine seaward boundaries of the United States. U.S. State Boundaries U.S. State Boundaries 2000-01-01T00:00:00 U.S. Bureau of the Census (BOC) publication date 2000-01-01 Earth Data Analysis Center Clearinghouse Manager 505-277-3622 ext. 230 505-277-3614 MSC01 1110 1 University of New Mexico Albuquerque NM 87131-0001 USA clearinghouse@edac.unm.edu 0800 - 1700 MT, M-F -7 hours GMT custodian