Emergency Operations Centers Florida

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: Florida Division of Emergency Management
Publication_Date: 20070615
Title: Emergency Operations Centers Florida
Edition: 2nd Quarter 2007
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Tallahassee, FL
Publisher: Florida Division of Emergency Management
Other_Citation_Details: State of Florida
Online_Linkage: www.floridadisaster.org/gis
Description:
Abstract:
This dataset contains Emergency Operations Centers (EOC) in the State of Florida. This dataset defines EOC's as "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. EOC’s 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/30/2007 and the newest record dates from 04/30/2007.
This dataset was created by TechniGraphics, Inc. for the Florida Division of Emergency Management.
Purpose:
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.
Supplemental_Information:
Florida Division of Emergency Management (FDEM) Home / Preparedness / Information Management / Critical Facilities <http://www.floridadisaster.org/gis/criticalfacilities/index.htm>
Critical Facilities
To assist in emergency response and planning, the GIS Lab, working with local, state, and federal agencies maintains shelters, emergency operations centers, critical facilities, and hazardous material facilities datasets.
"Critical facilities" are defined as those structures from which essential services and functions for victim survival, continuation of public safety actions, and disaster recovery are performed or provided. Shelters, emergency operation centers, public health, public drinking water, sewer and wastewater facilities are examples of critical facilities. Though not explicitly included in the definition, supporting life-line infrastructure essential to the mission of critical facilities must also be included in the inventory when appropriate.
"Critical infrastructure" is defined as those systems and assets, whether physical or virtual, so vital that the incapacity or destruction of such systems and assets would have a debilitating impact on security, economy, public health or safety, or any combination of these elements.
The domain of the GIS Lab is specifically related to "critical facilities", while working closely with Florida's Regional Domestic Security Task Forces to ensure a safe and secure Florida.
Several critical facilities data layers are maintained by other agencies, and the GIS Lab works closely with these agencies to make sure updated data is readily available. Examples include:
* Drinking Water Facilities - Florida Department of Environmental Protection * Environmental Health Facilities - Florida Department of Health * Fire Stations - Florida State Fire Marshal * Health Care Facilities - Agency for Health Care Administration * Petroleum Storage Tanks - Florida Department of Environmental Protection * Schools - Florida Department of Education * Solid Waste Facilities - Florida Department of Environmental Protection
Other data layers, like Hazardous Materials Facilities, Mobile Home Parks, and Hotel/Motels, while not specifically critical facilities, are facilities of interest for emergency managers, and the GIS Lab is also actively involved in facilitating access to these data layers.
Homeland Security Infrastructure Program
The Homeland Security Infrastructure Program (HSIP) is a collection of base map layers and homeland security related geospatial data. Currently, the emphasis of this program is on sharing and improving data to create uniform state & federal information. Working with contractors, the GIS Lab is providing data from state and local sources for QA/QC under the HSIP Freedom project.
* Correctional Facilities - delivered April 2007 * Emergency Operations Centers - July 2007 * Fire Stations - t.b.a. * Police Stations - t.b.a. * Emergency Medical Services - t.b.a. * Hospitals - t.b.a. * Urgent Care Facilities - t.b.a.
Emergency Management GIS Data Downloads
At this time, FDEM does not provide datasets for download, but may be contacted (Richard Butgereit 850-413-9907) for further information.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20070330
Ending_Date: 20070615
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.269239
East_Bounding_Coordinate: -79.950264
North_Bounding_Coordinate: 30.803191
South_Bounding_Coordinate: 24.688920
Keywords:
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: Emergency management
Theme_Keyword: Civil defense
Theme_Keyword: eoc
Theme_Keyword: emergency operations center
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: structure
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: society
Place:
Place_Keyword_Thesaurus:
LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) <http://authorities.loc.gov/>
Place_Keyword: Florida
Access_Constraints: NONE
Use_Constraints:
THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.
A note about data scale:
Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data.
1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger.
Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: <http://geoplan.ufl.edu/education.html>
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Mike Thompson
Contact_Organization: Techni Graphic Systems, Inc.
Contact_Position: Director of Geospatial Datasets
Contact_Address:
Address_Type: Mailing and Physical Address
Address: 2000 Noble Drive
City: Wooster
State_or_Province: Ohio
Postal_Code: 44691
Country: USA
Contact_Voice_Telephone: 330-263-6222
Contact_Facsimile_Telephone: 330-263-6294
Contact_Electronic_Mail_Address: mthompson@tgstech.com
Hours_of_Service: 8am - 5pm, Monday - Friday, Eastern Time
Contact_Instructions: <http://www.tgstech.com/>
Data_Set_Credit: FDEM and TechniGraphics, Inc.
Security_Information:
Security_Classification_System: DOD
Security_Classification: Unclassified
Security_Handling_Description: Unclassified
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.3000
Cross_Reference:
Citation_Information:
Other_Citation_Details:
TechniGraphics, Inc. <http://www.tgstech.com/gis.asp>
Florida Division of Emergency Management <http://www.floridadisaster.org/index.asp> <http://www.floridadisaster.org/gis>
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within the original data.
For entities that were contacted, the name, address, city, state, and five (5) digit zip codes were 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.
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.
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.
Area Code Distance Check: Area code (NPA) is valid and is within its area code boundary.
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.
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.
Logical_Consistency_Report:
See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency.
Completeness_Report:
This dataset is based on information provided by the Florida Department of Emergency Management (FLDEM) 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.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
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.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Florida Department of Emergency Management (FLDEM)
Publication_Date: 20070105
Title: "eoc_location"
Edition: Unspecified
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: <ftp://ftp.dca.state.fl.us/public>
Source_Scale_Denominator: N/A
Type_of_Source_Media: CD-ROM
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20070105
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: FDEM
Source_Contribution:
Spatial and Attribute Information
This was used as a source for Emergency Operations Centers in Florida.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Department of Homeland Security/Federal Protective Service (DHS/FPS)
Publication_Date: 20070213
Title: "HIFLD-CITY-EOC"
Edition: Unspecified
Type_of_Source_Media: online
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20070213
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: DHS/FPS_CITY_EOC
Source_Contribution:
Spatial and Attribute Information
This 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.
Source_Information:
Source_Citation:
Citation_Information:
Originator: NAVTEQ
Publication_Date: 2006
Title: NAVSTREETS
Edition: 2006.4
Geospatial_Data_Presentation_Form: vector digital data
Type_of_Source_Media: CD-ROM
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2006
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: NAVTEQ_Streets_2006_Q4
Source_Contribution:
Spatial and Attribute Information
NAVTEQ streets were used as a reference in the automatic geocoding and manual geolocating of entities during processing.
Process_Step:
Process_Description:
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.
Source_Used_Citation_Abbreviation: FL_EOC
Source_Used_Citation_Abbreviation: DHS/FPS_CITY_EOC
Source_Used_Citation_Abbreviation: NAVTEQ_Streets_2006Q4
Process_Date: 20070615
Source_Produced_Citation_Abbreviation: EOC
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Nicole Hackworth
Contact_Organization: Techni Graphic Systems, Inc.
Contact_Position: Project Manager
Contact_Address:
Address_Type: Mailing and Physical Address
Address: 2000 Noble Drive
City: Wooster
State_or_Province: Ohio
Postal_Code: 44691
Country: USA
Contact_Voice_Telephone: 330-263-6222
Contact_Electronic_Mail_Address: nhackworth@tgstech.com
Hours_of_Service: 8am - 5pm, Monday - Friday, Eastern Time
Process_Step:
Process_Description:
GeoPlan Center received the data via FTP from the Florida Division of Emergency Management (FDEM) on March 18, 2008. The original dataset was named: 2007_06_15_fl_eoc.shp
The original dataset projection was: Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Geographic: Latitude_Resolution: 0.000000 Longitude_Resolution: 0.000000 Geographic_Coordinate_Units: Decimal degrees Geodetic_Model: Horizontal_Datum_Name: D_WGS_1984 Ellipsoid_Name: WGS_1984 Semi-major_Axis: 6378137.000000 Denominator_of_Flattening_Ratio: 298.257224
The dataset was renamed to: fdem_eoc_jun07.shp
The dataset was reprojected to the FGDL Albers NAD83 HARN projection.
The dataset features were matched to their 1-kilometer United States National Grid (USNG) address via a spatial join, the USNG address can be found in the USNG_FL_1K field.
The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery.
How to Read a United States National Grid (USNG) Spatial Address <http://www.fgdc.gov/usng/how-to-read-usng/index_html>
Three additional fields were added. DESCRIPT field based on NAME FGDLAQDATE field based on the date the data was acquired by FGDL from the source. AUTOID field based on FID + 1, GeoPlan Center feature identification number.
Finally the attribute table was upper-cased and the metadata was updated.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20080319
Process_Step:
Process_Description: Data imported to ArcSDE and exported as a shapefile.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20080327
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: NAD 1983 2011 Florida GDL Albers
Albers_Conical_Equal_Area:
Standard_Parallel: 24.0
Standard_Parallel: 31.5
Longitude_of_Central_Meridian: -84.0
Latitude_of_Projection_Origin: 24.0
False_Easting: 400000.0
False_Northing: 0.0
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.0001
Ordinate_Resolution: 0.0001
Planar_Distance_Units: meter
Geodetic_Model:
Horizontal_Datum_Name: D NAD 1983 2011
Ellipsoid_Name: GRS 1980
Semi-major_Axis: 6378137.0
Denominator_of_Flattening_Ratio: 298.257222101
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: GIS.FWC.eoc_fdem_fl_point
Entity_Type_Definition: FDEM_EOC_JUN07.DBF
Entity_Type_Definition_Source: FDEM
Attribute:
Attribute_Label: OBJECTID_1
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: ID
Attribute_Definition: Unique identifier for feature.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: METLNKID
Attribute_Definition:
Link to Metadata - Currently this attribute is not used and is not populated.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: FEATTYPE
Attribute_Definition: Geometry type of feature.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: POINT
Enumerated_Domain_Value_Definition: Feature is represented by point.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: SECCLASS
Attribute_Definition: Security classification of feature.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: UNCLASSIFIED
Enumerated_Domain_Value_Definition: Entity is unclassified.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: NAME
Attribute_Definition: Name of entity.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: AREA_
Attribute_Definition: Three (3) digit telephone area code for entity.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain:
Valid area codes without punctuation. Only numeric digits are used. A list of valid area codes can be found at <http://www.nanpa.com>.
Attribute:
Attribute_Label: PHONE
Attribute_Definition:
Seven (7) digit telephone number for entity formatted as nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain:
Phone numbers formatted as nnn-nnnn. Only numeric digits are used. The first three (3) digits (the exchange) must form a valid combination with the area code. A list of valid area code and exchange combinations can be obtained from <http://www.nanpa.com>.
Attribute:
Attribute_Label: ADDRESS
Attribute_Definition:
Physical street address for 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.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: ADDRESS2
Attribute_Definition: Location within physical address, e.g., floor, suite, building.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: CITY
Attribute_Definition:
The name of the city associated with the 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.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: STATE
Attribute_Definition:
Two (2) character abbreviation for state associated with the 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.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Official USPS Abbreviations - State Abbreviations
Codeset_Source:
United States Postal Service <http://www.usps.com/ncsc/lookups/usps_abbreviations.html>
Attribute:
Attribute_Label: ZIP
Attribute_Definition: Five (5) digit USPS zip code for entity's physical location.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name:
USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes.
Codeset_Source: United States Postal Service
Attribute:
Attribute_Label: ZIPP4
Attribute_Definition:
Four (4) digit USPS zip code extension. This attribute was automatically assigned using the entity's physical address and USPS address information system (AIS) data.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: USPS Address Information System (AIS) - ZIP9
Codeset_Source: United States Postal Service
Attribute:
Attribute_Label: COUNTY
Attribute_Definition: County name where entity is located.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Geographic Names Information System (GNIS)
Codeset_Source: US Department of the Interior - US Geologic Survey
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
Five (5) digit FIPS (Federal Information Processing Standards) Code for the 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.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name:
Federal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions, and Associated Areas
Codeset_Source:
National Institute of Standards and Technology (NIST) <http://www.itl.nist.gov/fipspubs/co-codes/states.txt>
Attribute:
Attribute_Label: DIRECTIONS
Attribute_Definition:
Directions to entity location, or description of the entity's location.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: EMERGTITLE
Attribute_Definition:
Title of person or name of office for emergency point of contact.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: EMERGPHONE
Attribute_Definition:
Ten (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.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain:
Phone numbers, including area code, formatted as nnn-nnn-nnnn. A list of valid area code and exchange combinations can be found at <http://www.nanpa.com>.
Attribute:
Attribute_Label: EMERGEXT
Attribute_Definition: Telephone extension for emergency point of contact.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: CONTDATE
Attribute_Definition: Date entity was contacted by TGS.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Date
Attribute:
Attribute_Label: CONTHOW
Attribute_Definition: Method by which entity was contacted.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: PHONE
Enumerated_Domain_Value_Definition: Entity was contacted by phone.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: FAX
Enumerated_Domain_Value_Definition: Entity was contacted by fax.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MAIL
Enumerated_Domain_Value_Definition: Entity was contacted by mail.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: EMAIL
Enumerated_Domain_Value_Definition: Entity was contacted by email.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: WEB
Enumerated_Domain_Value_Definition:
Entity information was gathered and/or verified by official entity website as a last resort.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ALT REF
Enumerated_Domain_Value_Definition:
Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: GEODATE
Attribute_Definition: Date entity was geocoded by TGS.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Date
Attribute:
Attribute_Label: GEOHOW
Attribute_Definition: Method by which entity was geocoded.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: AUTO
Enumerated_Domain_Value_Definition: Entity was automatically geocoded.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: MANUAL
Enumerated_Domain_Value_Definition: Entity was manually geocoded.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ADJUSTED
Enumerated_Domain_Value_Definition:
Entity 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.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: PROVIDED
Enumerated_Domain_Value_Definition: Entity was geocoded using coordinates provided by the state.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: NAICSCODE
Attribute_Definition:
NAICS (North American Industry Classification System) Code for entity. NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's primary function, regardless of if that is the function that qualified it to be included in this dataset.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: North American Industry Classification System (NAICS 2002)
Codeset_Source: US Census Bureau - <http://www.census.gov/epcd/www/naics.html>
Attribute:
Attribute_Label: NAICSDESCR
Attribute_Definition:
NAICS (North American Industry Classification System) Description for entity. The "Index Entries" that appear on the NAICS webpage (<http://www.census.gov/epcd/www/naics.html>) are being used to populate this attribute as opposed to the "NAICS Title". While there is a one to one correspondence between NAICS Codes and "NAICS Titles", there is a one to many relationship between NAICS Codes and the "Index Entries". By using the "Index Entries", we have placed the entities that make up this layer into more specific categories; however, the user of this data should be aware that this was not the intended purpose of these "Index Entries". The "Index Entries" were intended as a way to search the NAICS database and as a way of enumerating ways in which establishments falling under the given NAICS Code may be named. Thus, there are often two or more "Index Entries" that are synonyms, for example: "Prisons" and "Penitentiaries". In cases like this, we have standardized on one "Index Entry".
NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's primary function, regardless of the function that qualified it to be included in this dataset.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: EMERGENCY PLANNING AND MANAGEMENT OFFICES, GOVERNMENT
Enumerated_Domain_Value_Definition:
EMERGENCY 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.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: GEOLINKID
Attribute_Definition:
Link 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.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Unrepresentable_Domain: Text
Attribute:
Attribute_Label: SOURCE
Attribute_Definition: Original source of entity record.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TGS
Enumerated_Domain_Value_Definition: Entity information was provided by TGS.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: DHS/FPS
Enumerated_Domain_Value_Definition:
Entity information was provided by the Department of Homeland Security/Federal Protective Service through the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: FLDEM
Enumerated_Domain_Value_Definition:
Entity information was provided by the Florida Department of Emergency Management (FLDEM).
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: X
Attribute_Definition: Longitude in WGS 84 Decimal Degrees.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: -180
Range_Domain_Maximum: 180
Attribute_Units_of_Measure: WGS 84 Decimal Degrees
Attribute:
Attribute_Label: Y
Attribute_Definition: Latitude in WGS 84 Decimal Degrees.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: -90
Range_Domain_Maximum: 90
Attribute_Units_of_Measure: WGS 84 Decimal Degrees
Attribute:
Attribute_Label: ST_VENDOR
Attribute_Definition:
Indicates name of vendor providing original street data used for geocoding.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NAVTEQ
Enumerated_Domain_Value_Definition: NAVTEQ streets were used for geocoding.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TGS
Enumerated_Domain_Value_Definition:
TGS drew in a new street segment that does not exist in the file supplied by NAVTEQ
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: <BLANK>
Enumerated_Domain_Value_Definition:
Entity was geocoded using coordinates provided by the state, therefore the street vendor is unknown.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: ST_VERSION
Attribute_Definition: Indicates the year and quarter of streets used for geocoding.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2006Q4
Enumerated_Domain_Value_Definition: 4th Quarter 2006 NAVTEQ street data was used for geocoding.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: <BLANK>
Enumerated_Domain_Value_Definition:
Entity was geocoded using coordinates provided by the state, therefore the street version is unknown.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: GEOPREC
Attribute_Definition: Geospatial precision.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: BLOCKFACE
Enumerated_Domain_Value_Definition:
Entity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION].
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: ONENTITY
Enumerated_Domain_Value_Definition:
Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs).
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: PHONELOC
Attribute_Definition:
Indicates whether the phone number in the phone field rings to the actual location of the entity.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: YES
Enumerated_Domain_Value_Definition: Phone number rings to the actual entity location.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: NO
Enumerated_Domain_Value_Definition:
Phone number does not ring to the actual entity location. It may ring to an administrative office or central location.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: <BLANK>
Enumerated_Domain_Value_Definition:
Unknown - It is not known if the entity's phone number rings to the entity's location.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: QC_QA
Attribute_Definition:
Organization that performed Quality Control/Quality Assurance on the record.
Attribute_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: TGS
Enumerated_Domain_Value_Definition:
TGS has performed Quality Control/Quality Assurance on the entity record.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: <BLANK>
Enumerated_Domain_Value_Definition:
The record has not had Quality Control/Quality Assurance performed by TGS.
Enumerated_Domain_Value_Definition_Source: TGS
Attribute:
Attribute_Label: USNG_FL_1K
Attribute_Definition:
Facility's 1-kilometer United States National Grid (USNG) address. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address Website - <http://www.fgdc.gov/usng/how-to-read-usng/index_html>
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: Based on NAME.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition: The date FGDL acquired the data from the Source.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: AUTOID
Attribute_Definition: GeoPlan feature identification number.
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Person:
Contact_Position:
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Voice_Telephone:
Contact_TDD/TTY_Telephone:
Contact_Facsimile_Telephone:
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>
Hours_of_Service:
Contact_Instructions:
Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED 'AS IS'. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.003
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
Metadata_Reference_Information:
Metadata_Date: 20070615
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Division of Emergency Management
Contact_Person: Richard Butgereit
Contact_Address:
Address_Type: mailing address
Address: 2555 Shumard Oak Boulevard
City: Tallahassee
State_or_Province: FL
Postal_Code: 32399-2100
Country: USA
Contact_Voice_Telephone: 850-413-9907
Contact_Electronic_Mail_Address: gis@em.myflorida.com
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Generated by mp version 2.9.12 on Fri Nov 08 14:56:08 2019