FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION VERSION 2005 TITLE: FLORIDA FIRE STATIONS 2005 Geodataset Name: GC_FIRESTAT_SEP05 Geodataset Type: SHAPEFILE Geodataset Feature: POINT |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): University of Florida GeoPlan Center SCALE OF ORIGINAL SOURCE MAPS: Varies DATE OF AUTOMATION OF SOURCE: Sept. 2005 GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: GC_FIRESTAT_SEP05.DBF
ITEM NAME | WIDTH | TYPE | N. DECIMAL DEGREES |
FID
|
4 | OID | --- |
Shape
|
0 | Geometry | --- |
Status
|
1 | String | --- |
Score
|
4 | Number | --- |
Side
|
1 | String | --- |
NAME
|
100 | String | --- |
ADDRESS
|
65 | String | --- |
CITY
|
40 | String | --- |
ZIPCODE
|
9 | Number | --- |
PHONE
|
16 | String | --- |
TYPE
|
40 | String | --- |
OPERATING
|
80 | String | --- |
OP_CLASS
|
40 | String | --- |
SERVICES
|
40 | String | --- |
COMMON_USE
|
4 | String | --- |
USE
|
50 | String | --- |
YR_BUILT
|
4 | Number | --- |
DESCRIPT
|
100 | String | --- |
FLAG
|
5 | String | --- |
UPDATE_DAY
|
8 | Date | --- |
AUTOID
|
6 | Number | --- |
FGDLAQDATE
|
8 | Date | --- |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
FID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
Status |
ESRI item which denotes the status of the geocoded address whether it was matched or not). |
|
Score |
ESRI item which denotes the score with which the address was matched to a feature in the reference data. |
|
Side |
ESRI item which denotes the side of the street to which the address was matched (for geocoding service styles that can match an address to a particular side of a street). |
|
NAME |
Designation of fire department |
|
ADDRESS |
A description of a facility's physical location providing direction for delivery and provision of emergency services |
|
CITY |
City of facility's physical location |
|
ZIPCODE |
US postal delivery designation of facility's physical location |
|
PHONE |
The phone number of the fire station |
|
TYPE |
No description |
|
OPERATING |
The responsible organization for management and operation of a facility (e.g., public, private, quasi-public) |
|
OP_CLASS |
Classification of the operating entity |
|
SERVICES |
Services rendered not typical to the entity |
|
COMMON_USE |
Location of two or more uses in one facility or on common grounds so as to share common facilities |
|
USE |
Description of co-located use, if applicable |
|
YR_BUILT |
The year a structure was built for determining possible historical significance |
|
DESCRIPT |
FGDL added item based on Name |
|
FLAG |
Type of update that occurred
|
|
UPDATE_DAY |
The last day the file was updated |
|
AUTOID |
Internal ID # |
|
FGDLAQDATE |
The date FGDL aquired the data from the source. |
GeoPlan relied on the integrity of the attribute information within the original data. |
This dataset is a combination of fire station and EMS facility addresses from (1) the National Fire Department Census (source - US Fire Administration), (2) The Department of Health, (3) the Yellow Pages online, (4) and Super Pages online. Since only censused fire stations are included in the National Fire Census database, addresses were also obtained from the Yellow and Super Pages to insure a complete spatial representation of fire station locations. |
A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare not suitable for some project, analysis, or modelling 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:250000 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 analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html |
U.S. Fire Administration 16825 S. Seton Ave. Emmitsburg, MD 21727 (301) 447-1000 http://www.usfa.fema.gov/index.shtm About the National Fire Department Census: http://www.usfa.fema.gov/applications/fdonline/about.cfm Yellow Pages website: www.yellowpages.com Super Pages website: www.superpages.com Department of Health: http://www.hhs.gov/ |
The National Fire Department Census data was originally released by the U.S. Fire Administration (USFA) in 2005. GeoPlan downloaded this data in text file format and converted it to a dbf. Additional fire station locations were obtained from the online Yellow Pages in 2005. Addresses were manually selected and entered into a dbf. Both dbf's were checked for duplicate addresses and then combined into one dbf. The combined dbf was then geocoded against ARC Logistics Route GDT Roads and converted into a shapefile with the FGDL Albers HPGN map projection. Process Steps for US Fire Administration Data: -Downloaded National Fire Department Census data (registered fire station locations) in text file format from the US Fire Administration website: http://www.usfa.fema.gov/applications/fdonline/states.cfm -Converted the station locations text file to database file format Process Steps for Super Pages FL Cemetery Locations: -Searched for fire station addresses at http://www.superpages.com Selected fires station addresses under following categories: Health & Medicine * Public Health & Safety o Emergency Services + Fire Departments (1420) -Downloaded fire station information Process Steps for Yellow Pages Fire Station Locations: -Searched for fire station addresses in www.yellowpages.com -Selected fire station addresses under following categories: Justice, Public Order & Safety Fire Protection - Fire Department (1338) - Fire Department Volunteer (33) - Fire Protection County Government (250) - Fire Protection Local Government (310) - Fire Protection, State Government (41) -All addresses from sections above were copied and pasted into a text file, which was then formatted so that it could be imported into Excel and converted to a database file format. Process Steps for Both USFA and Yellow Pages data: -Both database files of station locations were weeded to remove duplicate addresses. -Both database files were combined -The addresses were geocoded against ARC Logistics Route GDT Roads -Shapefile created using FGDL Albers HPGN map projection Process Steps for Department of Health (DOH) EMS Facility Locations: Inserted Hardcopy data received from DOH into .DBF Process Steps for USFA, DOH, and Yellow Pages data: -All three database files of fire stations and EMS Facility locations were weeded to remove duplicate addresses. -All three database files were combined -The addresses were geocoded against ARC Logistics Route GDT Roads -Shapefile created using FGDL Albers HPGN map projection -This update consists of changes made to Volusia County, Florida in 2005. The old geocoded data was removed from the statewide layer and the newly acquired data was appended. The AUTOID was calculated for records containing no old AUTOID number. (A2) For Volusia County, FL the 2005 GC_FIRESTAT statewide geocoded point data was removed. This data was replaced with more accurate point data received directly from Volusia County and/or a company working with Volusia County in May of 2005. (A5) Some Information from the 2004 geocoded data set was retained; this data was retained for three reasons: 1. The Yellow Pages and Super Pages Online are paid advertising sites, some facilities may wish to discontinue their advertising with those companies but they may still exist at that address/location (i.e. Churches etc). 2. The address might have changed slightly (i.e. suite number, building number, or zip code) which may have affected the addresses ability to be geocoded with the 2005 GDT roads dataset. 3. The facility no longer exists. Because facilities in reasons one and two may still exist in the real world all the 2004 geocoded features that were not reproduced in the 2005 geocode update were re-geocoded against the 2005 GDT roads dataset. These facilities were then added to the 2005 geocoded dataset. Facilities that are part of this scenario are represented with a value of 'NIN' (Not In New) in the field called FLAG. -Added DESCRIPT field based on NAME -Socio-Cultural Effect data fields and definitions were added. FLAG, UPDATE_DAY, AUTOID, NAME, ADDRESS, CITY, ZIPCODE, OPERATING, OP_CLASS, SERVICES, COMMON_USE USE, YR_BUILT, FGDLAQDATE. -For facilities that previously existed the permanent auto identification number [auto id] was carried over from the 2004 SCE base data to the 2005 SCE updates. For new facilities autoids were created. -Total records = 1009 Process Date: 20050901 |
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: |
University of Florida GeoPlan Center GeoPlan 431 Architecture, PO Box 11570 Gainesville, FL 32611-570 |
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