vector digital data Complete As needed -87.269238 -79.950264 30.803189 24.688920 None 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 Techni Graphic Systems, Inc. Mike Thompson Director of Geospatial Datasets unknown

2000 Noble Drive

Wooster Ohio 330-263-6222 330-263-6294 mthompson@tgstech.com http://www.tgstech.com/ FDEM and TechniGraphics, Inc. Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 TechniGraphics, Inc. http://www.tgstech.com/gis.asp Florida Division of Emergency Management http://www.floridadisaster.org/index.asp http://www.floridadisaster.org/gis Vector Entity point 95 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 FDEM_EOC_JUN07 FDEM_EOC_JUN07.DBF FDEM OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. ID Unique identifier for feature. TGS Text METLNKID Link to Metadata - Currently this attribute is not used and is not populated. TGS Text FEATTYPE Geometry type of feature. TGS POINT Feature is represented by point. TGS SECCLASS Security classification of feature. TGS UNCLASSIFIED Entity is unclassified. TGS NAME Name of entity. TGS Text AREA_ Three (3) digit telephone area code for entity. TGS Valid area codes without punctuation. Only numeric digits are used. A list of valid area codes can be found at http://www.nanpa.com. PHONE Seven (7) digit telephone number for entity formatted as 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. ADDRESS 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. TGS Text ADDRESS2 Location within physical address, e.g., floor, suite, building. TGS Text CITY 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. TGS Text STATE 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. TGS Official USPS Abbreviations - State Abbreviations United States Postal Service http://www.usps.com/ncsc/lookups/usps_abbreviations.html ZIP Five (5) digit USPS zip code for entity's physical location. TGS USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes. United States Postal Service ZIPP4 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. TGS USPS Address Information System (AIS) - ZIP9 United States Postal Service COUNTY County name where entity is located. TGS Geographic Names Information System (GNIS) US Department of the Interior - US Geologic Survey FIPS 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. 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 DIRECTIONS Directions to entity location, or description of the entity's location. TGS Text EMERGTITLE Title of person or name of office for emergency point of contact. TGS Text EMERGPHONE 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. 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. EMERGEXT Telephone extension for emergency point of contact. TGS Text CONTDATE Date entity was contacted by TGS. TGS Date CONTHOW Method by which entity was contacted. TGS PHONE Entity was contacted by phone. TGS FAX Entity was contacted by fax. TGS MAIL Entity was contacted by mail. TGS EMAIL Entity was contacted by email. TGS WEB Entity information was gathered and/or verified by official entity website as a last resort. TGS ALT REF Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets. TGS GEODATE Date entity was geocoded by TGS. TGS Date GEOHOW Method by which entity was geocoded. TGS AUTO Entity was automatically geocoded. TGS MANUAL Entity was manually geocoded. TGS ADJUSTED 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. TGS PROVIDED Entity was geocoded using coordinates provided by the state. TGS 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 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 EMERGENCY PLANNING AND MANAGEMENT OFFICES, GOVERNMENT 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. TGS GEOLINKID 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. TGS Text SOURCE Original source of entity record. TGS TGS Entity information was provided by TGS. TGS DHS/FPS Entity information was provided by the Department of Homeland Security/Federal Protective Service through the Homeland Infrastructure Foundation-Level Data (HIFLD) Working Group. TGS FLDEM Entity information was provided by the Florida Department of Emergency Management (FLDEM). TGS X Longitude in WGS 84 Decimal Degrees. TGS -180 180 WGS 84 Decimal Degrees Y Latitude in WGS 84 Decimal Degrees. TGS -90 90 WGS 84 Decimal Degrees ST_VENDOR Indicates name of vendor providing original street data used for geocoding. TGS NAVTEQ NAVTEQ streets were used for geocoding. TGS TGS TGS drew in a new street segment that does not exist in the file supplied by NAVTEQ TGS <BLANK> Entity was geocoded using coordinates provided by the state, therefore the street vendor is unknown. TGS ST_VERSION Indicates the year and quarter of streets used for geocoding. TGS 2006Q4 4th 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. TGS GEOPREC Geospatial precision. TGS BLOCKFACE Entity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION]. TGS ONENTITY Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs). TGS PHONELOC Indicates whether the phone number in the phone field rings to the actual location of the entity. TGS YES Phone number rings to the actual entity location. TGS NO Phone 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. TGS QC_QA Organization that performed Quality Control/Quality Assurance on the record. TGS TGS TGS has performed Quality Control/Quality Assurance on the entity record. TGS <BLANK> The record has not had Quality Control/Quality Assurance performed by TGS. TGS USNG_FL_1K 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 GeoPlan DESCRIPT Based on NAME. GeoPlan FGDLAQDATE The date FGDL acquired the data from the Source. GeoPlan AUTOID GeoPlan feature identification number. GeoPlan SHAPE Feature geometry. ESRI Coordinates defining the features. Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US For FGDL Software: http://www.fgdl.org/software.html Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html Web site: http://www.fgdl.org DOWNLOADABLE DATA 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. 20200302 Florida Division of Emergency Management Richard Butgereit mailing

2555 Shumard Oak Boulevard

Tallahassee FL 32399-2100 US 850-413-9907 gis@em.myflorida.com FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time