"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/27/2007 and the newest record dates from 04/23/2007.
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.
TGS PinPoint v.1.8.10.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/>
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.
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.
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.
(Excerpted from the National Incident Management System)
The values for this attribute were provided by Oregon and TGS did not verify these values.
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.
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.
The values for this attribute have not been verified by TGS.
The values for this attribute have not been verified by TGS.
The values for this attribute have not been verified by TGS.
The values for this attribute have not been verified by TGS.
The values for this attribute have not been verified by TGS.