Techni Graphic Systems, Inc.North Carolina Geographic Information System (NCGIS)Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group20070621onemap.SDEADMIN.eoc2nd Quarter 2007vector digital dataeocwithheld
Emergency Operations Centers (EOC) in North Carolina
"The physical location at which the coordination of information and resources to support domestic incident management activities normally takes place. An EOC may be a temporary facility or may be located in
a more central or permanently established facility, perhaps at a higher level of organization within a jurisdiction. EOCs may be organized by major functional disciplines (e.g., fire, law enforcement, and medical services), by jurisdiction (e.g., Federal, State, regional, county, city, tribal), or some combination thereof."
(Excerpted from the National Incident Management System)
In instances where TGS could not verify the location of an Emergency Operations Center due to non-cooperation of the entity and to the exhaustion of all possible alternative resources, its location was depicted at the center of the service area.
In cases where an Emergency Operations Center has a mobile unit, TGS captured the location of the mobile unit as a separate record. This record represents where the mobile unit is stored.
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.
The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 03/28/2007 and the newest record dates from 05/04/2007.
Homeland Security
Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.
1. A resource for preparing, mitigating, responding to and recovering from an emergency.
2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster.
3. A resource for Emergency Management planning purposes.
4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster.
5. A resource for situational awareness planning and response for Federal Government events.
en2007032820070504The year (and optionally month, or month and day) for which the data set corresponds to the ground.ground conditionUnknown-84.115157-75.66329636.52660133.957164151024.428175908586.49582534447.405692308036.320123LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/Emergency managementCivil defenseISO 19115 Topic CategorystructureLCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/North CarolinaThere are no access constraints.There are no use constraints.Mike ThompsonTechni Graphic Systems, Inc.Director of Geospatial DatasetsMailing and Physical Address
2000 Noble Drive
WoosterOhio44691USA330-263-6222330-263-6294mthompson@tgstech.com8am - 5pm, Monday - Friday, Eastern TimeDODUnclassifiedUnclassifiedESRI ArcCatalog 9.1.0.722Feature Class
For entities that were contacted, the name, address, city, state, and five (5) digit zip code was verified to be correct as of the date indicated by the [CONTDATE] attribute. The existence of the entity was also verified, as well as whether or not it met the criteria for inclusion in this dataset. 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 all IDs are 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.
Basic Name Check: Entity name is not blank, and it 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.
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.
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.
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.
Zip Code Check: The zip code is five (5) or nine (9) numeric digits, and is listed in the postal database, is in the same state as indicated by the entity's [STATE] attribute.
Zip City Check: The entity's zip code and its city were verified to match according to the USPS Address Information System (AIS).
Collocation Check: Entities with different addresses must not share the exact same geospatial location.
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 "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.
This dataset is based on information provided by the North Carolina Geographic Information System (NCGIS) and the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group.
Administrative Locations: Locations that serve only an administrative purpose (e.g., purchasing, billing, budgeting) are intended to be excluded from this dataset, but a few may be included.
The geographic location of contacted entities was verified to be correct relative to the street data vendor and version as indicated by the [ST_VENDOR] and [ST_VERSION] attributes. The horizontal accuracy is indicated by the [GEOPREC] attribute. A value of "BLOCKFACE" indicates that the entity was geocoded on the correct block and correct side of the street. A value of "ONENTITY" indicates that the location is on the entity's facility as determined by USGS DOQQ imagery and that it is on the correct block and correct side of the street.Federal Emergency Management Agency (FEMA)200702"state_eoc"UnspecifiedElectronic Mail System200702publication dateFEMA_STATE_EOCThis was provided by the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group and was used as a source for Emergency Operations Centers in the United States.Department of Homeland Security/Federal Protective Service (DHS/FPS)20070213"HIFLD-CITY-EOC"UnspecifiedElectronic Mail System20070213publication dateDHS/FPS_CITY_EOCThis was provided by the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group and was used as a source for Emergency Operations Centers in the United States.North Carolina Geographic Information System (NCGIS)20070107"eoc"Unspecifiedvector digital datawithheldOnline20070107publication dateNC_EOCThis was used as a source for Emergency Operations Centers in North Carolina.NAVTEQ2006NAVSTREETS2006.4vector digital dataCD-ROM2006publication dateNAVTEQ_Streets_2006_Q4NAVTEQ streets were used as a reference in the automatic geocoding and manual geolocating of entities.
TGS Emergency Operations Centers Processing
>
1) Verified name, physical address, and phone number by contacting the entity or an authority responsible for the entity.
>
2) Determined or verified the geospatial location for the entity through contact with entity or authority responsible for entity. Entities were asked to describe their geospatial location relative to landmarks visible in ortho imagery.
>
3) In cases where an Emergency Operations Center has a mobile unit, TGS captured the location of the mobile unit as a separate record. This record represents where the mobile unit is stored.
>
4) All of the entities that were "completely verified" were reviewed by a TGS QC Technician. QC Technicians are trained to look for inconsistencies within the data and between the data and reference sources, such as imagery. Where inconsistencies exist, the TGS QC Technician re-verified the information by contacting the entity.
>
5) All of the entities that were "completely verified" were examined as an aggregate (e.g., not every record was examined individually) by a TGS QC2 Technician. The automated checks described above and in the Attribute_Accuracy_Report were used to find any inconsistencies that remained in the data. If necessary, information was re-verified.
>
6) NAICS Codes and NAICS Descriptions were assigned based on the entity name and on web research since this is information that can't be gathered over the phone.
>
7) Four digit United States Postal Service (USPS) zip code extensions were assigned based upon USPS Address Information System (AIS).
>
8) County names and county FIPS codes were assigned through a spatial join.
>
9) All text fields were set to all upper case.
>
10) Leading and trailing spaces were trimmed from all text fields.
>
11) Non printable and diacritic characters were removed from all text fields.
withheldwithheldwithheldwithheld20070621withheldNicole HackworthTechni Graphic Systems, Inc.Project ManagerMailing and Physical Address
2000 Noble Drive
WoosterOhio44691USA330-263-6222nhackworth@tgstech.com8am - 5pm, Monday - Friday, Eastern TimeMetadata imported.withheld20070803VectorSimpleFALSE107TRUEFALSENorth American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983NAD_1983_StatePlane_North_Carolina_FIPS_3200coordinate pairmeters0.0020480.002048Explicit elevation coordinate included with horizontal coordinates1.000000eoc
"The physical location at which the coordination of information and resources to support domestic incident management activities normally takes place. An EOC may be a temporary facility or may be located in
a more central or permanently established facility, perhaps at a higher level of organization within a jurisdiction. EOCs may be organized by major functional disciplines (e.g., fire, law enforcement, and medical services), by jurisdiction (e.g., Federal, State, regional, county, city, tribal), or some combination thereof".
(Excerpted from the National Incident Management System)
National Incident Management SystemFeature Class107SHAPEFeature geometry.ESRICoordinates defining the features.SHAPEGeometry800IDUnique identifier for feature.TGSTextIDString1000METLNKIDLink to Metadata - Currently this attribute is not used and is not populated.TGSTextMETLNKIDString2000FEATTYPEGeometry type of feature.TGSPOINTFeature is represented by point.TGSFEATTYPEString1000EOC_IDUnique identifier for feature provided by North Carolina.TGSTextEOC_IDString1000SECCLASSSecurity classification of feature.TGSUNCLASSIFIEDEntity is unclassified.TGSSECCLASSString3000onemap_sdeadmin_eoc_areaonemap.SDEADMIN.eoc.AREAString300NAMEName of entity.TGSTextNAMEString25400PHONESeven (7) digit telephone number for entity formatted as nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.TGSPhone 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.PHONEString800ADDRESSPhysical street address for entity. "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 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.TGSTextADDRESSString8000ADDRESS2Location within physical address, e.g., floor, suite, building.TGSTextADDRESS2String8000CITY
The name of the city associated with the entity's physical address. For physical addresses that the U.S. Postal Service (USPS) delivers to, this should be a "city" acceptable to the USPS as defined in their Address Information System (AIS). Sometimes the USPS does not deliver mail to a physical address but recognizes the location (i.e., they list the location as "undeliverable"). The cities associated with these locations are acceptable. In some cases, the USPS does not recognize individual physical addresses in a city; rather, they list the city as having "General Delivery". In these cases, the city and associated zip code are acceptable (the entity's [ADDRESS] attribute will contain a street address, not "general delivery"). The entity may not actually be located within the city limits of the "city" specified in its city field. Instead, it may actually be located within the city limits of another city. In some cases, the "city" that appears in this attribute may not even be a city in an administrative sense, but it is still an acceptable "city" to the USPS. An example of this is "Notre Dame, IN". There is no city in Indiana called "Notre Dame", but this is considered an acceptable city by the USPS for any delivery going to the University of Notre Dame which is actually located in the city of South Bend. "Notre Dame", like most USPS cities, is an easily recognized place, and it gives the user of the data a good general idea of where the entity is located (if the entity is located in a small municipality, the USPS "city" may be more recognizable than the name of the municipality), and it would be part of the address one would use to send a shipment to the entity's location. Using the USPS acceptable "city" also allows someone to do a logical consistency check between the zip code and the city by using the USPS AIS.
Sometimes an entity may report a city that is not accepted by the USPS, and although TGS has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset.
TGSTextCITYString12000STATETwo (2) character abbreviation for state associated with the entity's physical address. 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 boundary theme being used.TGSOfficial USPS Abbreviations - State AbbreviationsUnited States Postal Service http://www.usps.com/ncsc/lookups/usps_abbreviations.htmlSTATEString200ZIPFive (5) digit USPS zip code for entity's physical location.TGSUSPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes.United States Postal ServiceZIPString500ZIPP4Four (4) digit USPS zip code extension. This attribute was automatically assigned using the entity's physical address and USPS address information system (AIS) data.TGSUSPS Address Information System (AIS) - ZIP9United States Postal ServiceZIPP4String400COUNTYCounty name where entity is located.TGSGeographic Names Information System (GNIS)US Department of the Interior - US Geologic SurveyCOUNTYString5000FIPSFive (5) digit FIPS (Federal Information Processing Standards) Code for the County where entity is located. The first two (2) digits represent the state and the last three (3) digits identify the county within the state.TGSFederal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions, and Associated AreasNational Institute of Standards and Technology (NIST) http://www.itl.nist.gov/fipspubs/co-codes/states.txtFIPSString500DIRECTIONSDirections to entity location, or description of the entity's location.TGSTextDIRECTIONSString25400EMERGTITLETitle of person or name of office for emergency point of contact.TGSTextEMERGTITLEString4000EMERGPHONETen (10) digit telephone number of emergency point of contact formatted as nnn-nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.TGSPhone 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.EMERGPHONEString1200EMERGEXTTelephone extension for emergency point of contact.TGSTextEMERGEXTString1000CONTDATEDate entity was contacted by TGS.TGSDateCONTDATEDate800CONTHOWMethod by which entity was contacted.TGSPHONEEntity was contacted by phone.TGSFAXEntity was contacted by fax.TGSMAILEntity was contacted by mail.TGSEMAILEntity was contacted by email.TGSWEBEntity information was gathered and/or verified by official entity website as a last resort.TGSALT REFGeospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets.TGSCONTHOWString1000GEODATEDate entity was geocoded by TGS.TGSDateGEODATEDate800GEOHOWMethod by which entity was geocoded.TGSAUTOEntity was automatically geocoded.TGSMANUALEntity was manually geocoded.TGSADJUSTEDEntity was shifted by TGS to an updated set of NAVTEQ streets. This only applies if the entity was manually geocoded by TGS to a previous version of NAVTEQ streets.TGSPROVIDEDEntity was geocoded using coordinates provided by the state.TGSGEOHOWString1000NAICSCODENAICS (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.TGSNorth American Industry Classification System (NAICS 2002)US Census Bureau - http://www.census.gov/epcd/www/naics.htmlNAICSCODEString600NAICSDESCR
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.
TGSEMERGENCY PLANNING AND MANAGEMENT OFFICES, GOVERNMENTEMERGENCY PLANNING AND MANAGEMENT OFFICES, GOVERNMENT - [NAICS Code 922190]: Entities 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) are classified under this description. These establishments include the general administration of public order and safety programs.TGSNAICSDESCRString12000GEOLINKIDLink ID for the street segment to which entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] attributes for the street vendor and version that was used to geocode the entity.TGSTextGEOLINKIDString1000SOURCEOriginal source of entity record.TGSTGSEntity information was provided by TGS.TGSDHS/FPSEntity information was provided by the Department of Homeland Security/Federal Protective Service through the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group.TGSFEMAEntity information was provided by the Federal Emergency Management Agency through the Homeland Infrastructure Foundation-Level Data (HIFLD) Working GroupTGSNCGISEntity information was provided by the North Carolina Geographic Information System.TGSSOURCEString3200XLongitude in WGS 84 Decimal Degrees.TGS-180180WGS 84 Decimal DegreesXDouble8388YLatitude in WGS 84 Decimal Degrees.TGS-9090WGS 84 Decimal DegreesYDouble8388ST_VENDORIndicates name of vendor providing original street data used for geocoding.TGSNAVTEQNAVTEQ streets were used for geocoding.TGSTGSTGS drew in a new street segment that does not exist in the file supplied by NAVTEQTGS<BLANK>Entity was geocoded using coordinates provided by the state, therefore the street vendor is unknown.TGSST_VENDORString1000ST_VERSIONIndicates the year and quarter of streets used for geocoding.TGS2006Q44th Quarter 2006 NAVTEQ street data was used for geocoding.TGS<BLANK>Entity was geocoded using coordinates provided by the state, therefore the street version is unknown.TGSST_VERSIONString1000GEOPRECGeospatial precision.TGSBLOCKFACEEntity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION].TGSONENTITYEntity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs).TGSGEOPRECString3200PHONELOCIndicates whether the phone number in the phone field rings to the actual location of the entity.TGSYESPhone number rings to the actual entity location.TGSNOPhone number does not ring to the actual entity location. It may ring to an administrative office or central location.TGS<BLANK>Unknown - It is not known if the entity's phone number rings to the entity's location.TGSPHONELOCString300QC_QAOrganization that performed Quality Control/Quality Assurance on the record.TGSTGSTGS has performed Quality Control/Quality Assurance on the entity record.TGS<BLANK>The record has not had Quality Control/Quality Assurance performed by TGS.TGSQC_QAString300OBJECTIDOBJECTIDOID4100Internal feature number.ESRISequential unique whole numbers that are automatically generated.20070803Mike ThompsonTechni Graphic Systems, Inc.Director of Geospatial DatasetsMailing and Physical Address
2000 Noble Drive
WoosterOH44691USA330-263-6222330-263-6294mthompson@tgstech.com8am - 5pm, Monday - Friday, Eastern TimeThe person responsible for the metadata information.The organization responsible for the metadata information.FGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998enlocal time2007080308523400FALSE20220523144038002022052314415600eoc151024.428175908586.49582534447.405692308036.3201231002ProjectedGCS_North_American_1983NAD_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["NAD_1983_StatePlane_North_Carolina_FIPS_3200",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",609601.22],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-79.0],PARAMETER["Standard_Parallel_1",34.33333333333334],PARAMETER["Standard_Parallel_2",36.16666666666666],PARAMETER["Latitude_Of_Origin",33.75],UNIT["Meter",1.0],AUTHORITY["EPSG",32119]]</WKT><XOrigin>-37137499.999000192</XOrigin><YOrigin>-28547399.998846613</YOrigin><XYScale>7812.4999927240415</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0040960000038146975</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.01500000005000FGDCDownloadable DataMike ThompsonThe person responsible for the metadata information.Techni Graphic Systems, Inc.The organization responsible for the metadata information.Director of Geospatial Datasets330-263-6222330-263-62942000 Noble DriveWoosterOH44691USmthompson@tgstech.com8am - 5pm, Monday - Friday, Eastern Time20220523ArcGIS Metadata1.0withheldEnterprise Geodatabase Feature ClassEmergency Operation Centers2007-06-212nd Quarter 2007Techni Graphic Systems, Inc.North Carolina Geographic Information System (NCGIS)Homeland Infrastructure Foundation-Level Data (HIFLD) Working Groupvector digital data<DIV STYLE="text-align:Left;"><DIV><P><SPAN>Emergency Operations Centers (EOC) in North Carolina "The physical location at which the coordination of information and resources to support domestic incident management activities normally takes place. An EOC may be a temporary facility or may be located in a more central or permanently established facility, perhaps at a higher level of organization within a jurisdiction. EOCs may be organized by major functional disciplines (e.g., fire, law enforcement, and medical services), by jurisdiction (e.g., Federal, State, regional, county, city, tribal), or some combination thereof." (Excerpted from the National Incident Management System) In instances where TGS could not verify the location of an Emergency Operations Center due to non-cooperation of the entity and to the exhaustion of all possible alternative resources, its location was depicted at the center of the service area. In cases where an Emergency Operations Center has a mobile unit, TGS captured the location of the mobile unit as a separate record. This record represents where the mobile unit is stored. 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. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 03/28/2007 and the newest record dates from 05/04/2007.</SPAN></P></DIV></DIV>
Homeland Security
Use Cases: Use cases describe how the data may be used and help to define and clarify requirements.
1. A resource for preparing, mitigating, responding to and recovering from an emergency.
2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster.
3. A resource for Emergency Management planning purposes.
4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster.
5. A resource for situational awareness planning and response for Federal Government events.
Mike ThompsonTechni Graphic Systems, Inc.Director of Geospatial Datasets330-263-6222330-263-62942000 Noble DriveWoosterOhio44691USmthompson@tgstech.com8am - 5pm, Monday - Friday, Eastern TimeLCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/North CarolinaLCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/Emergency managementCivil defenseISO 19115 Topic CategorystructureEmergency managementCivil defensestructureNCNorth CarolinaDepartment of Information TechnologyDITCenter for Geographic Information and AnalysisCGIANC OneMap<DIV STYLE="text-align:Left;"><DIV><P><SPAN>https://www.nconemap.gov/pages/terms</SPAN></P></DIV></DIV>There are no access constraints.DODUnclassifiedESRI ArcCatalog 9.1.0.722true-84.115157-75.66329636.52660133.957164ground condition2007-03-282007-05-041-84.115157-75.66329636.52660133.957164See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.
This dataset is based on information provided by the North Carolina Geographic Information System (NCGIS) and the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group.
Administrative Locations: Locations that serve only an administrative purpose (e.g., purchasing, billing, budgeting) are intended to be excluded from this dataset, but a few may be included.
Metadata imported.withheldThis was provided by the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group and was used as a source for Emergency Operations Centers in the United States."state_eoc"FEMA_STATE_EOC2007-02UnspecifiedFederal Emergency Management Agency (FEMA)publication date2007-02This was provided by the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group and was used as a source for Emergency Operations Centers in the United States."HIFLD-CITY-EOC"DHS/FPS_CITY_EOC2007-02-13UnspecifiedDepartment of Homeland Security/Federal Protective Service (DHS/FPS)publication date2007-02-13This was used as a source for Emergency Operations Centers in North Carolina."eoc"NC_EOC2007-01-07UnspecifiedNorth Carolina Geographic Information System (NCGIS)vector digital datawithheldpublication date2007-01-07NAVTEQ streets were used as a reference in the automatic geocoding and manual geolocating of entities.NAVSTREETSNAVTEQ_Streets_2006_Q420062006.4NAVTEQvector digital datapublication date2006
TGS Emergency Operations Centers Processing
>
1) Verified name, physical address, and phone number by contacting the entity or an authority responsible for the entity.
>
2) Determined or verified the geospatial location for the entity through contact with entity or authority responsible for entity. Entities were asked to describe their geospatial location relative to landmarks visible in ortho imagery.
>
3) In cases where an Emergency Operations Center has a mobile unit, TGS captured the location of the mobile unit as a separate record. This record represents where the mobile unit is stored.
>
4) All of the entities that were "completely verified" were reviewed by a TGS QC Technician. QC Technicians are trained to look for inconsistencies within the data and between the data and reference sources, such as imagery. Where inconsistencies exist, the TGS QC Technician re-verified the information by contacting the entity.
>
5) All of the entities that were "completely verified" were examined as an aggregate (e.g., not every record was examined individually) by a TGS QC2 Technician. The automated checks described above and in the Attribute_Accuracy_Report were used to find any inconsistencies that remained in the data. If necessary, information was re-verified.
>
6) NAICS Codes and NAICS Descriptions were assigned based on the entity name and on web research since this is information that can't be gathered over the phone.
>
7) Four digit United States Postal Service (USPS) zip code extensions were assigned based upon USPS Address Information System (AIS).
>
8) County names and county FIPS codes were assigned through a spatial join.
>
9) All text fields were set to all upper case.
>
10) Leading and trailing spaces were trimmed from all text fields.
>
11) Non printable and diacritic characters were removed from all text fields.
2007-06-21Nicole HackworthTechni Graphic Systems, Inc.Project Manager330-263-62222000 Noble DriveWoosterOhio44691USnhackworth@tgstech.com8am - 5pm, Monday - Friday, Eastern TimeFEMA_STATE_EOCDHS/FPS_CITY_EOCNC_EOCNAVTEQ_Streets_2006Q4EOC107datasetEPSG4.2(3.0.1)