Geodataset Name:       AVIATION_FEB07
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         1101

DATA SOURCE(S):                    University of Florida GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     Various
DATE OF AUTOMATION OF SOURCE:      20070226
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES:

Datafile Name: AVIATION_FEB07.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
UAID	Unique Area Identification Number
USID	Unique Site Identification Number
NPIAS	National Plan of Integrated Airport Systems (National Airport Strategic Plan, US FAA) NPIAS Number.
ACODE	FAA Code.
ASITE	A unique identifying number followed by an asterisk and the 'landing facility type' code. The SITE_NO forms the key to the airport records in the NFDC (5010) database.
STATUS	Facility Status. ACTIVE = Facility Active CLOSED = Facility Closed
NAME	Official Airport Name
ASSOC_CITY	Name of the city associated with the airport.
ADDRESS	Official Airport Address.
ADDRESS2	Official Airport Address Continued.
CITY	Official Airport City.
STATE	Official Airport State
ZIPCODE	Official Airport Zipcode.
PHONE	Official Airport Phone Number.
FAX	Official Airport Fax Number.
CONTACT_ID	Facility Contact ID.
CONTACT	Facility Primary Contact Number.
WEBSITE	Official Airport Website.
EMAIL	Official Airport Email Address.
COUNTY	Official Airport County.
SECTION	Facility Section Number.
TOWNSHIP	Facility Township Number.
RANGE	Facility Range Number.
HUB	Airport HUB Size. L = Large Hub - 6.5 million and above. M = Medium Hub - 6.5 million to 1.6 million. S = Small Hub - 1.6 million to 324,000. R = Non-Hub 324,000 and below.
AIRCAT	Airport Category. A = B = C = D =
OWNERSHIP	Type of Airport Facility Owner PUB = Publicly Owned PVT = Privately Owned MA = Air Force Owned MN = Navy Owned MR = Army Owned
USE	Facility Use -- Public or Private PUB = Public Use Airport Facility PVT = Private Use Airport Facility
TYPE	Landing Facility Type AIRPORT = Airport Facility BALLOONPORT = Balloon Launch and Landing Facility SEAPLANE BASE = Facility for sea plane operations GLIDERPORT = Facility for glider operations HELIPORT = Facility for helicopter operations STOLPORT = Short Take Off and Landing Facility ULTRALIGHT = Facility for ultralight operations
ASMSA	ASMSA Code.
REG_CODE	FAA Region where the facility is located ASO = Southern
FAA_DIST	FAA District or Field Office Code ORL = Orlando
DOT_DIST	Florida Department of Transportation District 1 = FDOT District 1 2 = FDOT District 2 3 = FDOT District 3 4 = FDOT District 4 5 = FDOT District 5 6 = FDOT District 6 7 = FDOT District 7
ELEVATION	Elevation in feet at the highest point on the centerline of the useable landing surface. Measured to the nearest foot with respect to mean sea level (MSL).
E_SOURCE	Elevation Information Source. ESTIMATED = Estimated Elevation SURVEYED = Surveyed Elevation.
ACREAGE	The number of acres the aviation facility covers.
CHART_SECT	Aeronautical chart on which the airport facility appears.
DIST_CITY	Distance from the central business district of the associated city to the airport in nautical miles (1 nautical mile = 6,080 feet). Measured to the nearest nautical mile.
DIR_CITY	Direction of airport from the central business district of the associated city. Measured to the nearest 1/8 compass pointN = North ENE = East Northeast ESE = East Southeast N = North NE = Northeast NNE = North Northeast NNW = North Northwest NW = Northwest S = South SE = Southeast SSE = South Southeast SSW = South Southwest SW = Southwest W = West WNW = West Northwest WSW = West Southwest
AIRPORT_AT	Airport Attendant Hours.
AIRPORT_LG	Airport Lighted.
AIRPORT_MK	Field Undefined By Source.
BEACON_CLR	Beacon Information.
WINDINDIC	Wind Indicator Available.
WINDNOTES	Wind Indicator Notes.
WINDLIGHT	Wind Indicator Lighted.
SEGCIR	Segmented Circle Available.
SEGLIGHT	Segmented Circle Lighted.
AIRPARK	Airpark Information.
NOTES	Facility Notes.
FARPART139	FAR Part 139 Certificated.
SYSVERSION	System Version.
SYSSTATUS	System Status.
SYSSOURCE	System Source.
COM_SERVE	Commercial Service.
SIS_NAME	Strategic Intermodal System (SIS) Name.
PVTAPPFAC	Private APP Facility.
REGEXP	Private APP Facility Registration Expiration Date.
HURRICANE	Hurricane Damage Notes.
NONCOMLAND	Non-Comm Landing.
NPIASFEDA	NPIAS / Fed Agreements.
FARPRT139I	FAR Part 139 Index.
ALAPPFAC	Undefined bySource.
CERT_TYPE	Airport Certification Type and Date - The format is a two-character code followed by a month/year (MM/YYYY) of certification.AS = Landing facilities having a full certificate under FAR Part 139 and receiving scheduled air carrier service from carriers certified by the Civil Aeronautics Board. The A, B, C, D, E identifies the aircraft rescue and fire fighting index for the landing facility, and the 'S' is for scheduled air carrier service. BS = Landing facilities having a full certificate under FAR Part 139 and receiving scheduled air carrier service from carriers certified by the Civil Aeronautics Board. The A, B, C, D, E identifies the aircraft rescue and fire fighting index for the landing facility, and the 'S' is for scheduled air carrier service. CS = Landing facilities having a full certificate under FAR Part 139 and receiving scheduled air carrier service from carriers certified by the Civil Aeronautics Board. The A, B, C, D, E identifies the aircraft rescue and fire fighting index for the landing facility, and the 'S' is for scheduled air carrier service. DS = Landing facilities having a full certificate under FAR Part 139 and receiving scheduled air carrier service from carriers certified by the Civil Aeronautics Board. The A, B, C, D, E identifies the aircraft rescue and fire fighting index for the landing facility, and the 'S' is for scheduled air carrier service. ES = Landing facilities having a full certificate under FAR Part 139 and receiving scheduled air carrier service from carriers certified by the Civil Aeronautics Board. The A, B, C, D, E identifies the aircraft rescue and fire fighting index for the landing facility, and the 'S' is for scheduled air carrier service. AU = Landing facilities having a full certificate under FAR Part 139 but not currently receiving scheduled service. BU = Landing facilities having a full certificate under FAR Part 139 but not currently receiving scheduled service. CU = Landing facilities having a full certificate under FAR Part 139 but not currently receiving scheduled service. DU = Landing facilities having a full certificate under FAR Part 139 but not currently receiving scheduled service. EU = Landing facilities having a full certificate under FAR Part 139 but not currently receiving scheduled service. LS = Landing facilities having limited certification under FAR Part 139 and receiving scheduled air carrier service. LU = Landing facilities having limited certification under FAR Part 139 and not currently receiving scheduled air carrier service. N = 'N' or a indicates the facility is not certified.
INTERNATIO	Customs international airport - Whether the landing facility has been designated by the U.S. Treasury as an international airport of entry for customs. Y = Yes N = No
CUST_LNDG	Customs Landing Rights Airport - Whether the landing facility has been designated by the U.S. Treasury as a customs landing rights airport (some landing facilities may have these rights for cargo only). Y = Yes N = No
JOINT_USE	Joint Use - Whether the landing facility has a military/civil joint use agreement that allows civil operations at a military airport or military operations at a civil airport.Y = Yes Y = Yes N = No
MIL_LNDG_R	Military Landing Rights - Whether the airport has entered into an agreement that grants landing rights to the military. Y = Yes N = No
MIL_INT	Military Emergency Interest - Military department(s) that maintains national emergency use interest in this civil facility. Data values in this field are one, two, or three alphanumeric codes indicating military emergency use interest, with each code in a series separated by a '/'.A = Air Force R = Army N = Navy X = None [applicable only where there is an entry in the National Emergency * Status [NAT_EMER] Field]
CNTL_TWR	Airport Control Tower located on the airport. Y = Yes N = No
S_ENG_GA	Based Single Engine General Aviation Aircraft
M_ENG_GA	Based Multi-engine general aviation aircraft
JET_EN_GA	Based Jet engine general aviation aircraft
HELICOPTER	Based Helicopters - General Aviation
OPER_GLIDE	Base Operational Gliders - general aviation
OPER_MIL	Based Military Aircraft - including helicopters
ULTRALIGHT	Based Ultralight aircraft - general aviation
COMM_SERV	Commercial Services - scheduled operations by CAB certified carriers or intrastate carriers and any scheduled commuter/cargo carriers (Annual Operations).
AIR_TAXI	Air Taxi operators carrying passengers, mail, or mail for revenue (Annual Operations).
LOCAL_OPS	General Aviation, Local Operations - Those operating in the local traffic pattern or within a 20 mile radius (Annual Operations).
ITIN_OPS_G	General Aviation - Itinerant Operations. Those general aviation operations (excluding commuter or air taxi) not qualifying as local (Annual Operations).
MIL_OPS	Military Aircraft Operations (Annual Operations).
L_SOURCE	Latitude and Longitude Location Information Source
LATITUDE	The latitude of the point expressed as a signed real number. This value is in decimal degrees with negative values indicating South latitude and positive values indicating North latitude.
LONGITUDE	The longitude of the point expressed as a signed real number. This value is in decimal degrees with negative values indicating West longitude and positive values indicating East longitude.
DOT_ENP	Total domestic enplanements (inbound plus outbound) - this field only valid for some airports.
AIRTRAN	AIRTRAN ID Number.
GDT	GDT ID Number.
FCC	GDT ID Number determines boundaries from runways.
EDIT_NOTE	Polygon Accuracy Accesment.
P_SOURCE	The Source of the Polygon information.
FGDLAQDATE	Date Geoplan acquired the data from the Source.
DESCRIPT	Based on 'NAME'
AUTOID	GeoPlan unique identification number.
SHAPE	Feature geometry.
SHAPE.AREA	Area in meters
SHAPE.LEN	Perimeter in meters

USER NOTES:

This data is provided "as is". GeoPlan relied on the integrity of the original data layer's topology.

This data is provided "as is" by GeoPlan and is complete to our knowledge.

GeoPlan relied on the integrity of the attribute information within the original data.

The 2007 Aviation Facilities shapefile was created from the Public Use Airports database (point database) , GDT Airports (polygon database), and a FAD table. Airport boundaries were located using 2004 - 2006 (0.5 - 1ft) color imagery (available only for 1/3 of the state). Individual County Imagery Information: County Month Year Source Pixel Baker 12 2005 FDOT 1 ft Bay 11 2005 FDOT 1 ft Bradford 10-11 2005 FDOT 1 ft Brevard 02 2005 FDOT 1 ft Broward ? 2004 FDOR 1 ft Calhoun 12 2004 FDOT 1 ft Dade ? 2005 FDOR 1 ft Desoto 03 2004 FDOR 1 ft Dixie 03-04 2004 FDOT 1 ft Duval 03-04 2005 FDOT 1 ft Escambia 12 2004 FDOT 1 ft Flagler 04 2005 FDOT 1 ft Gadsden 11-01 2004/05 FDOT 1 ft Glades 01 2005 FDOR 1 ft Gulf 11-02 2005/06 FDOT 1 ft Hamilton 01 2005 FDOT 1 ft Hardee 03 2004 FDOR 1 ft Hendry 01 2005 FDOR 1 ft Highlands ? 2004 FDOR .5 ft Lafayette 03-04 2005 FDOT 1 ft Lee 01 2005 FDOR .5 ft Madison 10 2005 FDOT 1 ft Marion 10-11 2004 FDOT 1 ft Nassau 04 2005 FDOT 1 ft Okaloosa 10 2005 FDOT 1 ft Pasco ? 2004 FDOR 1 ft Putnam 12 2005 FDOT 1 ft Santa Rosa 07 2005 FDOT 1 ft Sarasota ? 2004 FDOR 1 ft St. Johns 03 2005 FDOR 1 ft Suwannee 01-03 2005 FDOT 1 ft Taylor 11 2004 FDOT 1 ft Walton 07 2005 FDOT 1 ft Where 0.5 - 1ft imagery did not exist 3m DOQQs from 1995 and 1999 were used for reference.

The dataset provides users with information about airport locations and attributes and can be used for statewide and regional analysis applications.

This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan

This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan

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

REFERENCES:

Florida Aviation Database (FAD) http://www.florida-aviation-database.com/ FDOT Aviation Facilities Directory http://www.florida-aviation-database.com/scripts/fid/advanced.cfm?nocache=93862.3403113342 2007 Florida Airport Directory http://www.florida-aviation-database.com/library/projects/20070223024045/Airport_Dir_2007.pdf National Transportation Atlas Database - 2006 http://www.bts.gov/publications/national_transportation_atlas_database/2006/

DATA LINEAGE SUMMARY:

------------------------------------------------------------------------ Process Steps for Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) 2006 Public Use Airports Point AIRTRAN_2006.shp ------------------------------------------------------------------------ The creation of this geospatial data layer was completed by RITA/BTS in March 2006. This Shapefile was derived from textual data on the FAA National Airspace System Resource Aeronautical Data CDROM, effective 16 February 2006. The Apt.txt file was converted into three separate files using the UNIX command grep. The airport table structure was built in Oracle. It followed the structure of the landing facility data described in the Apt_rf.txt file. A control file was built for the desired airport data structure and SQL Loader was used to load the data into the database. The degrees, minutes, and seconds columns were converted into decimal degrees and ESRI products were used to create the airport point file. Process Date: 2006 Geoplan obtained the airport transportation facility locations from the CD-ROM National Transportation Atlas Database (NTAD) 2006. -Geoplan extracted this data in shapefile format and removed facilities not located in Florida. -The data was reprojected to FGDL Albers HPGN -DESCRIPT was added to the attribute table based on 'FULLNAME' -FGDLAQDATE was added to the attribute table Process Date: 20060905 ------------------------------------------------------------------------ Process Steps for Tele Atlas/GDT GDT AIRPORT Q3-2006 Polygon - 1:100,000 GDT_AIRPORTS_JUL06.shp ------------------------------------------------------------------------ Data originally released by Tele Atlas in July 2006 on DVD. When received, data was in the following projection: 1983 North American Datum (NAD83), Units: Decimal Degrees. Process Date: 20060701 GeoPlan, during the QA/QC process included the following aspects: (1) The data layer was renamed from flxxxap.shp to GDT_AIRPORTS_JUL06 (2) The data was reprojected to FGDL Albers HPGN map projection. (3) Added DESCRIPT item based on NAME field. (4) Added FGDLAQDATE. Process Date: 20060511 ------------------------------------------------------------------------ Process Steps for: 1995 Northwest Florida Water Management District Land Use and Cover 2000 St. John's Water Management District Land Use and Cover 2000 South West Florida Water Management District Land Use and Cover 2000 South Florida Water Management District Land Use and Cover Polygon - 1:12,000 LU95.shp and LU00.shp ------------------------------------------------------------------------ In 2004 GeoPlan downloaded this dataset from 3 of the 5 Water Management District websites: SJRWMD (http://sjr.state.fl.us/index.html) SWFWMD (http://www.swfwmd.state.fl.us) SFWMD (http://www.sfwmd.gov) The data was downloaded in shapefile format. Data from SJRWMD was in Universal Transverse Mercator (UTM), Zone 17, NAD83-90 (HPGN), meters. Data from SWFWMD was in Universal Transverse Mercator (UTM), Zone 17, NAD83-90, meters. Data from SFWMD was in StatePlane Florida East, NAD 1983 HARN, FIPS 0901 Feet. Each dataset was then projected to FGDL Albers HPGN.The shapefile was then loaded into SDE and appended into a statewide layer using ArcGIS 9.0. The layer was then exported to shapefile and clipped to county boundaries. Process Date: 20041000 Data was redownloaded from SFWMD 12/16/05. At this time all existing SFWMD data within LU00 was removed and replaced with updated data. Therefore, LU00 for FGDL Version 2004 will be more complete in Version 2005 for areas within SFWMD. Selected FLUCCS code equal to 811 Airports 8111 Commercial 8112 General Aviation 8113 Private 8114 Abandoned Process Date: 20060328 ------------------------------------------------------------------------ Process Steps for Florida Aviation Database (FAD) Access Database - Table(s) FAD.mdb - Tables contained (data_facility), (data_helipads), (data_Runways). ------------------------------------------------------------------------ This Access database containing three tables was obtained by contacting Tom Duncan Aviation Policy and Program Development Analyst Aviation Office Florida Department of Transportation Mail Station 46 605 Suwannee St. Tallahassee, FL 32399-0450 Web Page: http://www.dot.state.fl.us/aviation/index.htm Web Page: http://www.florida-aviation-database.com/ From here an Email was received from Tom Basnett, Panther International, LLC Containing the Access database and table information. The three Access tables were exported to Excel where they were converted to .xls files. These three Excel tables were then restructured to fit the built in ArcGIS field length restraints. The Excel tables where then converted back to .dbf files. Next the FAD Facilities .dbf was converted to point shapefile via the ADD X/Y tool. The features were projected to WGS84 and then reprojected to FGDL's Albers NAD83 HARN. Process Date: 20070226 ------------------------------------------------------------------------ Process Steps for GeoPlan Center Combination dataset ------------------------------------------------------------------------ This dataset was created by first combining several different air transportation source shapefiles into one reference shapefile. Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), 2006 Public Use Airports (Point) AIRTRAN_2006.shp Tele Atlas/GDT, GDT AIRPORT Q3-2006 (Polygon - 1:100,000) GDT_AIRPORTS_JUL06.shp Statewide Water Management District Land Use and Cover, (Polygon - 1:12,000) LU95.shp and LU00.shp Florida Aviation Database, Table - Converted to point layer (Lat/Long), then buffered by 30m. Source shapefiles containing point features were converted to polygon features, via a 30m buffer, before being added to the reference shapefile. The reference shapefile was then verified against 1999 3m DOQQs, and 1ft Color Imagery from 2004 - 2006. If the reference shapefile's geometry was inaccurate then it was edited, moved or an entirely new polygon was created for the site. If a new polygon was created then the P_SOURCE field in the final shapefile was noted by the [P_SOURCE] = 'GEOPLAN' After the spatial information was checked for each feature a note was made in the EDIT_NOTE field denoting how confident the examiner was that an air transportation facility existed in the area. Features with less than 80% confidence should be reexamined once new imagery becomes available. Next the updated polygon layer had its features associated with the correct corresponding record in the Florida Aviation Database (FAD) table, via the facility name and physical location. In addition to this some FAA table information was also retained from the AIRTRAN.shp for some of the corresponding polygons. A DESCRIPT field was added based on NAME. FGDLAQDATE field was added based on the date FGDL obtained the data from the Source. Process Date: 20070226

MAP PROJECTION PARAMETERS:

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 ARCH BLDG
Gainesville, Florida
32611



www.fgdl.org
image@fgdl.org

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