TechniGraphics, Inc. 20080409 vector digital data psap withheld 911 Public Safety Answering Point (PSAP) service area boundaries in North Carolina 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. en 20070910 20080331 The year (and optionally month, or month and day) for which the data set corresponds to the ground. ground condition Complete Unknown -84.422158 -75.416580 36.617274 33.723388 123998.528433 930348.588500 9868.458156 318099.573234 LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov Telephone Emergency reporting systems Boundaries ISO 19115 Topic Category Boundaries location LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov North Carolina None None Mike Thompson TechniGraphics, Inc. Director of Geospatial Datasets Mailing and Physical Address

3351 Eastbrook Drive

Fort Collins CO 80525 USA 970-224-4996 970-224-3001 mthompson@tgstech.com 8am - 5pm, Monday - Friday, Mountain Time DOD Unclassified Unclassified ESRI ArcCatalog 9.3.1.3000 Feature Class 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. 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" 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. This dataset is not topologically correct, nor will it be consistent with any single other source. TGS research 2007 Unspecified Online 2007 publication date 911_Response_Districts This was used as a source of 911 Response Districts in the United States. North Carolina Center for Geographic Information and Analysis 20070803 Unspecified Electronic Mail System 20070803 publication date NC_Response_Districts This was used as a reference for 911 Response Districts in North Carolina. The North Carolina Department of Transportation Geographic Information Systems Unit 200706 Unspecified withheld Online 200706 publication date NC_Municipal_Boundaries This was used as a reference to locate municipal boundaries of 911 Response Districts in North Carolina. National Atlas of the United States 20071015 Unspecified http://nationalatlas.gov/atlasftp.html Online 20071015 publication date ind_res_boundaries This was used as a reference to locate Indian Reservations boundaries in the United States. National Park Service 20050601 Unspecified withheld Online 20050601 publication date nat_park_boundaries This was used as a reference to locate National Park boundaries in the United States. Office of the Under Secretary of Defense 20070423 Unspecified This was provided by the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group. Electronic Mail System 20070423 publication date installation_boundaries This was used as a reference to locate Military Installation boundaries in the United States. U.S. Department of Commerce, U.S. Census Bureau, Geography Division 2006 2006 First Edition vector digital data http://www.census.gov/geo/www/tiger/tiger2006fe/tgr2006fe.html Online Linkage 2006 publication date TIGER_County_Boundaries TIGER Boundaries were used as a reference to locate county boundaries of the 911 Response Districts. U.S. Department of Commerce, U.S. Census Bureau, Geography Division 2006 2006 First Edition vector digital data http://www.census.gov/geo/www/tiger/tiger2006fe/tgr2006fe.html Online Linkage 2006 publication date TIGER_Place_Boundaries TIGER Boundaries were used as a reference to locate city boundaries of the 911 Response Districts in the United States. U.S. Bureau of the Census (BOC) 2000 Unspecified vector digital data http://www.census.gov Online Linkage 2000 publication date U.S. State Boundaries State Boundaries were used to determine seaward boundaries of the United States. 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". North Carolina - 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. > withheld withheld withheld withheld withheld withheld withheld withheld withheld 20080409 withheld Nicole Hackworth TechniGraphics, Inc. Project Manager Mailing and Physical Address

2000 Noble Drive

Wooster OH 44691 USA 330-263-6222 nhackworth@tgstech.com 7:30am - 4:30pm, Monday - Friday, Eastern Time Metadata imported. withheld 20090727 14345100 Vector Simple FALSE 137 TRUE FALSE coordinate pair 0.000433 0.000433 meters North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 GCS_North_American_1983 NAD_1983_StatePlane_North_Carolina_FIPS_3200 Explicit elevation coordinate included with horizontal coordinates 1.000000 psap 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. TGS Feature Class 137 OBJECTID OBJECTID OID 4 10 0 Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. SHAPE Feature geometry. ESRI Coordinates defining the features. SHAPE Geometry 8 0 0 ID Unique identifier for feature. TGS Text ID String 10 0 0 SECCLASS Security classification of feature. TGS UNCLASSIFIED Entity is unclassified. TGS SECCLASS String 30 0 0 NAME 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. TGS Text NAME String 254 0 0 PSAP_NAME 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. TGS Text PSAP_NAME String 254 0 0 FCC_ID FCC ID for the primary PSAP that serves the district. TGS Text FCC_ID String 10 0 0 STATE_ID State ID for the primary PSAP that serves the district. TGS Text STATE_ID String 10 0 0 TELEPHONE Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn. TGS Only numeric digits are used. TELEPHONE String 12 0 0 FAX 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. TGS 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 FAX String 12 0 0 ADDRESS 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. TGS Text ADDRESS String 80 0 0 ADDRESS2 Location within physical address, e.g., floor, suite, building. TGS Text ADDRESS2 String 80 0 0 CITY The name of the city associated with the physical address for the primary PSAP that serves the district. TGS Text CITY String 120 0 0 STATE 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. TGS Official USPS Abbreviations - State Abbreviations United States Postal Service http://www.usps.com/ncsc/lookups/usps_abbreviations.html STATE String 2 0 0 ZIP Five (5) digit USPS zip code associated with the physical address of the primary PSAP that serves the district. TGS USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box only) zip codes. United States Postal Service ZIP String 5 0 0 ZIPP4 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. TGS USPS Address Information System (AIS) - ZIP9 United States Postal Service ZIPP4 String 4 0 0 COUNTY 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. TGS Geographic Names Information System (GNIS) US Department of the Interior - US Geologic Survey COUNTY String 254 0 0 FIPS 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. TGS Federal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions, and Associated Areas National Institute of Standards and Technology (NIST) <http://www.itl.nist.gov/fipspubs/co-codes/states.txt> FIPS String 254 0 0 EMERGTITLE Title of person or name of office for emergency point of contact. TGS Text EMERGTITLE String 40 0 0 EMERGTEL 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. TGS 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 EMERGTEL String 12 0 0 EMERGEXT Telephone extension for emergency point of contact for the primary PSAP that serves the District. TGS Text EMERGEXT String 10 0 0 NON911EMNO Indicates if dialing 911 inside the area connects one with emergency services. TGS Y 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. TGS N 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. TGS NON911EMNO String 1 0 0 NAICSCODE 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. TGS North American Industry Classification System (NAICS 2002) US Census Bureau - http://www.census.gov/epcd/www/naics.html NAICSCODE String 6 0 0 NAICSDESCR 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. TGS DISASTER PREPAREDNESS AND MANAGEMENT OFFICES, GOVERNMENT 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). U.S. Census Bureau NAICSDESCR String 120 0 0 WEB Web address for the primary PSAP of the District. TGS Text WEB String 100 0 0 st_area(shape) st_area(shape) Double 0 0 0 st_perimeter(shape) st_perimeter(shape) Double 0 0 0 NC CGIA Physical

301 N. Wilmington Street, Suite 700

Raleigh North Carolina 27601-2825 U.S.A. Mailing

20322 Mail Service Center

Raleigh North Carolina 27699 U.S.A. (919) 733-2090 (919)715-0725 dataq@ncmail.net 8am to 5pm Phone and electronic mail preferred Natural Heritage Element Occurrences NCCGIA is charged with the development and maintenance of NC OneMap and, in cooperation with other mapping organizations, is committed to offering its users accurate, useful, and current information. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop this dataset may be reflected in the data supplied. The user must be aware of possible conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. NCCGIA does not support secondary distribution of this dataset without its current, compliant metadata record. The use of trade names or commercial products does not constitute their endorsement by NCCGIA or North Carolina State Government. ESRI shapefile (*.shp) withheld None. Download from www.nconemap.com is free of charge. Data can be customized on a cost-recovery basis. Contact dataq@ncmail.net or 919-733-2090 for more information. All formats available from www.nconemap.com are in ESRI shapefile. Other formats are available on a cost-recovery basis - contact dataq@ncmail.net or 919.733.2090 for more information. Format compatibility is the user's responsibility. 20090727 Present 20090727 Mike Thompson TechniGraphics, Inc. Director of Geospatial Datasets Mailing and Physical Address

3351 Eastbrook Drive

Fort Collins CO 80525 USA 970-224-4996 970-224-3001 mthompson@tgstech.com 8am - 5pm, Monday - Friday, Mountain Time The person responsible for the metadata information. The organization responsible for the metadata information. FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 en local time 20090727 14345100 FALSE 20220523 14421900 20220523 14463100 psap 123998.528433 930348.588500 9868.458156 318099.573234 1 002 Projected GCS_North_American_1983 NAD_1983_StatePlane_North_Carolina_FIPS_3200 <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.8.0'><WKT>PROJCS[&quot;NAD_1983_StatePlane_North_Carolina_FIPS_3200&quot;,GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433]],PROJECTION[&quot;Lambert_Conformal_Conic&quot;],PARAMETER[&quot;False_Easting&quot;,609601.22],PARAMETER[&quot;False_Northing&quot;,0.0],PARAMETER[&quot;Central_Meridian&quot;,-79.0],PARAMETER[&quot;Standard_Parallel_1&quot;,34.33333333333334],PARAMETER[&quot;Standard_Parallel_2&quot;,36.16666666666666],PARAMETER[&quot;Latitude_Of_Origin&quot;,33.75],UNIT[&quot;Meter&quot;,1.0],AUTHORITY[&quot;EPSG&quot;,32119]]</WKT><XOrigin>-37137499.999610193</XOrigin><YOrigin>-28547399.99991871</YOrigin><XYScale>9230.4583438358368</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.00086669585647850911</XYTolerance><ZTolerance>0.002</ZTolerance><MTolerance>0.002</MTolerance><HighPrecision>true</HighPrecision><WKID>32119</WKID><LatestWKID>32119</LatestWKID></ProjectedCoordinateSystem> Linear Unit: Meter (1.000000) 1.0 150000000 5000 FGDC Mike Thompson The person responsible for the metadata information. TechniGraphics, Inc. The organization responsible for the metadata information. Director of Geospatial Datasets 970-224-4996 970-224-3001 3351 Eastbrook Drive Fort Collins CO 80525 US mthompson@tgstech.com 8am - 5pm, Monday - Friday, Mountain Time 20220523 ArcGIS Metadata 1.0 NC CGIA (919) 733-2090 (919)715-0725 301 N. Wilmington Street, Suite 700 20322 Mail Service Center Raleigh Raleigh North Carolina North Carolina 27601-2825 27699 U.S.A. U.S.A. dataq@ncmail.net 8am to 5pm Phone and electronic mail preferred None. Download from www.nconemap.com is free of charge. 2009-07-27 ESRI shapefile (*.shp) All formats available from www.nconemap.com are in ESRI shapefile. Other formats are available on a cost-recovery basis - contact dataq@ncmail.net or 919.733.2090 for more information. Format compatibility is the user's responsibility. withheld NC CGIA (919) 733-2090 (919)715-0725 301 N. Wilmington Street, Suite 700 20322 Mail Service Center Raleigh Raleigh North Carolina North Carolina 27601-2825 27699 U.S.A. U.S.A. dataq@ncmail.net 8am to 5pm Phone and electronic mail preferred 2009-07-27 Data can be customized on a cost-recovery basis. Contact dataq@ncmail.net or 919-733-2090 for more information. withheld Enterprise Geodatabase Feature Class Public Safety Answering Point (PSAP) Service Area Boundaries 2008-04-09 TechniGraphics, Inc. vector digital data <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>911 Public Safety Answering Point (PSAP) service area boundaries in North Carolina 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.</SPAN></P></DIV></DIV></DIV> 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. Mike Thompson TechniGraphics, Inc. Director of Geospatial Datasets 970-224-4996 970-224-3001 3351 Eastbrook Drive Fort Collins CO 80525 US mthompson@tgstech.com 8am - 5pm, Monday - Friday, Mountain Time LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov North Carolina LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov Telephone Emergency reporting systems Boundaries ISO 19115 Topic Category Boundaries location Telephone Emergency reporting systems Boundaries location NC North Carolina Department of Information Technology DIT Center for Geographic Information and Analysis CGIA NC OneMap NCCGIA is charged with the development and maintenance of NC OneMap and, in cooperation with other mapping organizations, is committed to offering its users accurate, useful, and current information. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop this dataset may be reflected in the data supplied. The user must be aware of possible conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions specific to certain data. NCCGIA does not support secondary distribution of this dataset without its current, compliant metadata record. The use of trade names or commercial products does not constitute their endorsement by NCCGIA or North Carolina State Government. DOD Unclassified ESRI ArcCatalog 9.3.1.3000 true -84.422158 -75.416580 36.617274 33.723388 ground condition 2007-09-10 2008-03-31 1 -84.422158 -75.416580 36.617274 33.723388 <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>https://www.nconemap.gov/pages/terms</SPAN></P></DIV></DIV></DIV> 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" 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. This was used as a source of 911 Response Districts in the United States. 911 Response Districts 911_Response_Districts 2007 Unspecified TGS research publication date 2007 This was used as a reference for 911 Response Districts in North Carolina. psap-nc NC_Response_Districts 2007-08-03 Unspecified North Carolina Center for Geographic Information and Analysis publication date 2007-08-03 This was used as a reference to locate municipal boundaries of 911 Response Districts in North Carolina. MunicipalBoundaries_polys NC_Municipal_Boundaries 2007-06 Unspecified The North Carolina Department of Transportation Geographic Information Systems Unit withheld publication date 2007-06 This was used as a reference to locate Indian Reservations boundaries in the United States. indlanp020 ind_res_boundaries 2007-10-15 Unspecified National Atlas of the United States http://nationalatlas.gov/atlasftp.html 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-01 Unspecified National Park Service withheld 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-23 Unspecified Office of the Under Secretary of Defense This was provided by the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group. 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 2006 First Edition U.S. Department of Commerce, U.S. Census Bureau, Geography Division vector digital data http://www.census.gov/geo/www/tiger/tiger2006fe/tgr2006fe.html publication date 2006 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 2006 First Edition U.S. Department of Commerce, U.S. Census Bureau, Geography Division vector digital data http://www.census.gov/geo/www/tiger/tiger2006fe/tgr2006fe.html publication date 2006 State Boundaries were used to determine seaward boundaries of the United States. U.S. State Boundaries U.S. State Boundaries 2000 Unspecified U.S. Bureau of the Census (BOC) vector digital data http://www.census.gov publication date 2000 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". North Carolina - 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-09 Nicole Hackworth TechniGraphics, Inc. Project Manager 330-263-6222 2000 Noble Drive Wooster OH 44691 US nhackworth@tgstech.com 7:30am - 4:30pm, Monday - Friday, Eastern Time 911_Response_Districts NC_Response_Districts NC_Municipal_Boundaries ind_res_boundaries nat_park_boundaries installation_boundaries TIGER_County_Boundaries TIGER_Place_Boundaries U.S. State Boundaries NC_911 Public Safety Answering Point Boundaries Metadata imported. 2009-07-27T14:34:51 withheld 137 dataset EPSG 4.2(3.0.1)