FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: FLORIDA FIRE STATIONS 2008 Geodataset Name: FDEM_FIREDEPT_SEP08 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 1746 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): Florida Division of Emergency Management SCALE OF ORIGINAL SOURCE MAPS: N/A GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: FDEM_FIREDEPT_SEP08.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
ID
|
50 | String |
SECCLASS
|
30 | String |
NAME
|
254 | String |
TELEPHONE
|
12 | String |
ADDRESS
|
80 | String |
ADDRESS2
|
80 | String |
CITY
|
120 | String |
STATE
|
2 | String |
ZIP
|
5 | String |
ZIPP4
|
4 | String |
COUNTY
|
50 | String |
FIPS
|
5 | String |
DIRECTIONS
|
254 | String |
EMERGTITLE
|
50 | String |
EMERGTEL
|
15 | String |
EMERGEXT
|
10 | String |
CONTDATE
|
36 | Date |
CONTHOW
|
10 | String |
GEODATE
|
36 | Date |
GEOHOW
|
10 | String |
NAICSCODE
|
6 | String |
NAICSDESCR
|
120 | String |
GEOLINKID
|
10 | String |
X
|
8 | Double |
Y
|
8 | Double |
ST_VENDOR
|
10 | String |
ST_VERSION
|
10 | String |
GEOPREC
|
32 | String |
PHONELOC
|
3 | String |
QC_QA
|
3 | String |
STATE_ID
|
50 | String |
FDID
|
32 | String |
FRST_MBRS
|
4 | Integer |
EMS_MBRS
|
4 | Integer |
TOTALPERS
|
4 | Integer |
NUMTRKS
|
4 | Integer |
NUMABUL
|
4 | Integer |
TOTAL_VEHI
|
4 | Integer |
NBR_STA
|
4 | Integer |
OWNER
|
50 | String |
LEVEL_
|
50 | String |
TYPE
|
50 | String |
SPECIALTY
|
254 | String |
EMSLICENSE
|
32 | String |
EMERPHONE
|
15 | String |
EMS
|
3 | String |
PERM_ID
|
40 | String |
GNIS_ID
|
32 | String |
USNG_FL_1K
|
10 | String |
DESCRIPT
|
100 | String |
FGDLAQDATE
|
36 | Date |
SHAPE
|
4 | Geometry |
AUTOID
|
4 | Integer |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
ID |
Unique identifier for feature. |
|
SECCLASS |
Security classification of feature.
|
|
NAME |
Name of entity. |
|
TELEPHONE |
Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn. |
|
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 field. Some areas do not have regular city style addressing, so entities in those areas may not have a street number. In such cases, the name of the road on which they are located is listed in this field. Some rural areas may not have named roads. In these rare cases, this field will be blank. |
|
ADDRESS2 |
Location within physical address, e.g., floor, suite, building. |
|
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] field 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 field 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. |
|
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 field. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used. |
|
ZIP |
Five (5) digit USPS zip code for entity's physical location. |
|
ZIPP4 |
Four (4) digit USPS zip code extension. These values are automatically assigned using the entity's physical address and USPS address information system (AIS) data. |
|
COUNTY |
County name where entity is located. |
|
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. |
|
DIRECTIONS |
Directions to entity location, or description of the entity's location. |
|
EMERGTITLE |
Title of person or name of office for emergency point of contact. |
|
EMERGTEL |
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. |
|
EMERGEXT |
Telephone extension for emergency point of contact. |
|
CONTDATE |
Date entity was contacted by TGS. |
|
CONTHOW |
Method by which entity was contacted.
|
|
GEODATE |
Date entity was geocoded by TGS. |
|
GEOHOW |
Method by which entity was geocoded.
|
|
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. |
|
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 field, 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 if that is the function that qualified it to be included in this dataset.
|
|
GEOLINKID |
Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] fields for the street vendor and version that was used to geocode the entity. |
|
X |
Longitude in WGS 84 Decimal Degrees. |
|
Y |
Latitude in WGS 84 Decimal Degrees. |
|
ST_VENDOR |
Indicates name of vendor providing original street data used for geocoding.
|
|
ST_VERSION |
Indicates the year and quarter of streets used for geocoding.
|
|
GEOPREC |
Geocoding precision.
|
|
PHONELOC |
Indicates whether the phone number in the [TELEPHONE] field rings to the actual location of the entity.
|
|
QC_QA |
Organization that performed Quality Control/Quality Assurance on the record.
|
|
STATE_ID |
State Fire Station Data ID. For states that contributed data, this field is populated with the unique ID used by the state to track Fire Stations. |
|
FDID |
A unique five-character identifier assigned by the state to identify a particular fire department within the state. The first two characters designate the county and the last three designate the department within the county. This identifier is only unique within each state, not nationwide. |
|
FRST_MBRS |
Total number of fire fighter members associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS |
|
EMS_MBRS |
Total number of EMS members associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS |
|
TOTALPERS |
Total number of members associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
NUMTRKS |
Total number of fire trucks associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
NUMABUL |
Total number of ambulances associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS |
|
TOTAL_VEHI |
Total number of vehicles associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
NBR_STA |
The total number of stations associated with the DEPARTMENT.
The values that this field is populated with came from individual states and have not been validated or checked by TGS |
|
OWNER |
The type of ownership for the entity.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
LEVEL_ |
Indicates the level of medical services provided.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
TYPE |
Type of employees.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
SPECIALTY |
Indicates any type of specialty unit available at the facility.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
EMSLICENSE |
License number for EMS agency provided by the state.
The values that this field is populated with came from individual states and have not been validated or checked by TGS. |
|
EMERPHONE |
Emergency Contact Number as provided by individual states. Some values also include telephone extensions and/or alternate telephone numbers. All alphabetic characters have been translated to the corresponding numeric digit.
The values in this field have not been verified by TGS. |
|
EMS |
Indicates if the entity also has EMS capabilities.
|
|
PERM_ID |
The unique permanent identifier of The National Structures Dataset.
The values in this field have not been verified by TGS. |
|
GNIS_ID |
The unique permanent identifier of the Geographic Names Information System that is up to eight (8) digits in length and unique within the nation.
The values in this field have not been verified by 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 |
|
DESCRIPT |
Based on the field NAME. |
|
FGDLAQDATE |
The date FGDL acquired the data from the Source. |
|
SHAPE |
Feature geometry. |
|
AUTOID |
Unique ID added by GeoPlan |
See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency. |
Administrative Locations: Locations that serve only an administrative function (e.g., a business office) are intended to be excluded from this dataset. Locations that serve both an administrative function as well as an operational function are included in the dataset. |
GeoPlan relied on the integrity of the attribute information within the original data. |
Fire Departments not having a permanent location are included, in which case their location has been depicted at the city/town hall or at the center of their service area if a city/town hall does not exist. This dataset includes those locations primarily engaged in forest or grasslands fire fighting, including fire lookout towers if the towers are in current use for fire protection purposes. This dataset includes both private and governmental entities. Fire fighting training academies are also included. Any location where fire fighters are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Fire Departments not having a permanent location are included, in which case their location has been depicted at the city/town hall or at the center of their service area if a city/town hall does not exist. This dataset includes those locations primarily engaged in forest or grasslands fire fighting, including fire lookout towers if the towers are in current use for fire protection purposes. This dataset includes both private and governmental entities. Fire fighting training academies are also included. This dataset is comprised completely of license free data. The Fire Station dataset and the EMS dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. 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] field. Based upon this field, the oldest record dates from 03/22/2005 and the newest record dates from 08/27/2008. |
Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1. An assessment of whether or not the total fire fighting capability in a given area is adequate. 2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can determine those entities that are able to respond the quickest. 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. |
The geographic location of entities was verified to be correct relative to the street data and version indicated by the [ST_VENDOR] and [ST_VERSION] fields. The horizontal accuracy is indicated by the [GEOPREC] field. A value of "BLOCKFACE" indicates the entity was geocoded on the correct street segment (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 street segment (block) and correct side of the street. Entities that are part of a larger institution (e.g., University Campus or Military Base) with "BLOCKFACE" precision may be located at the main entrance to the larger institution. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. Fire Departments not having a permanent location are depicted at the city/town hall or at the center of the town or service area if a city/town hall does not exist. |
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan |
None |
The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. 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 data sources. 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 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 |
Mike Thompson TechniGraphics, Inc. - Director of Geospatial Datasets mthompson@tgstech.com TechniGraphics, Inc. 3351 Eastbrook Drive Fort Collins, CO 80525 970-224-4996 8am - 5pm, Monday - Friday, Mountain Time http://www.tgstech.com/gis.asp Florida Division of Emergency Management http://www.floridadisaster.org/index.asp http://www.floridadisaster.org/gis |
1) The Fire Station dataset and the EMS dataset were merged into one working file. TGS processed as one file and then separated for delivery purposes. > 2) Entities were processed to determine or verify their name, physical address, city, state, five (5) digit zip code, phone number, and geospatial location. Entities that were contacted were also asked if they provided fire protection services, EMS services, or both. Entities not located on military bases were contacted and asked to describe their location relative to landmarks in reference data (mainly streets) and features visible in ortho imagery. A phone number was not available for some entities, so their information was verified using other verbal contacts made through a telephone call. > 3) Due to a request made by the Department of Defense, TGS made every effort to not contact military bases starting 03/27/2007 and ending 05/28/2008. During this time, entities located on military bases were verified through alternate resources, such as maps and ortho imagery. These records have not been contacted by TGS, and therefore, do not have directions. > 4) All text fields were set to all upper case. > 5) Leading and trailing spaces were trimmed from all text fields. > 6) Non printable and diacritic characters were removed from all text fields. > Process Date: 20080919 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
Florida Division of Emergency Management FDEM 2555 Shumard Oak Boulevard Tallahassee, FL 32399-2100 850-413-9907 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html