Geodataset Name:       AIRPORTS_2008
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         862

DATA SOURCE(S):                    Federal Aviation Administration
SCALE OF ORIGINAL SOURCE MAPS:     Unknown
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  2008
TIME PERIOD OF CONTENT:            2008
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: AIRPORTS_2008.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
LOCID	A unique 3-4 character identifier assigned to the landing facility (i.e. airport).
SITE_NO	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. Example: 04508.*A
FULLNAME	Official Airport Name
FAA_ST	State Postal abbreviation, as coded by FAA
LAN_FA_TY	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
EFF_DATE	Information Effective Data (MM/DD/YYYY). This date coincides with the 56-day charting and publication cycle date.
FAA_REGION	FAA Region where the facility is located AAL = Alaska ACE = Central AEA = Eastern AGL = Great Lakes AIN = International ANE = New England ANM = Northwest Mountain ASO = Southern ASW = Southwest AWP = Western-Pacific
FAA_DISTRI	FAA District or Field Office Code
STATE_NAME	Airport's associated state or territory name, as coded by FAA.
ST_POSTAL	State Postal abbreviation, as coded by RITA/BTS
STFIPS	The 2-character FIPS code of the State or State equivalent, as coded by RITA/BTS
COUNTY_NAM	Name of the county or parish associated with the airport, as coded by FAA.
COUNTY_ST	Associated county's state (post office code) state where the associated county is located; may not be the same as the associated city's state code, as coded by FAA.
CITY_NAME	Name of the city associated with the airport, as coded by FAA.
OWNER_TYPE	Type of Airport Facility Owner PU = Publicly Owned PR = Privately Owned MA = Air Force Owned MN = Navy Owned MR = Army Owned
FAC_USE	Facility Use -- Public or Private PU = Public Use Airport Facility PR = Private Use Airport Facility
FAC_CYSTZP	City, State, and Zip code associated with the airport.
ELEV	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).
AERO_CHART	Aeronautical chart on which the airport facility appears.
CBD_DIST	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
CBD_DIR	Direction of airport from the central business district of the associated city. Measured to the nearest 1/8 compass point N = 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
ACT_DATE	Identifies the month and year that the facility was added to the NFDC airport database - only available for facilities opened since 1981 (MM/YYYY).
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 blank indicates the facility is not certified.
FED_AGREE	NASP/ Federal Agreement Code - a combination of 1 to 7 codes that indicate the type of federal agreements existing at the airport. N = National Plan of Integrated Airport Systems (NPIAS) B = Installation of Navigational Facilities on privately owned airports under F&E program G = Grant agreements under FAAP/ADAP/AIP H = Compliance with accessibility to the handicapped P = Surplus property agreement under Public Law 289 R = Surplus Property agreement under Regulation 16-WAA S = Conveyance under Section 16, Federal Airport Act of 1946 or Section 23, Airport and Airway Development Act of 1970 V = Advance Planning Agreement under FAAP X = Obligations assumed by transfer Y = Assurances pursuant to Title VI, Civil Rights Act of 1964 Z = Conveyance under Section 303(C), Federal Aviation Act of 1958 1 = Grant agreement has expired; however, agreement remains in effect as long as it is a public use facility 2 = Section 303(C) Authority from FAA Act of 1958 has expired; however, agreement remains in effect as long as it is a public use facility 3 = AP-4 Agreement under DLAND or DCLA has expired NONE = No Grant Agreement Exists
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 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	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).
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.
VERSION	The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed.
CY_06_ENP	Total domestic enplanements (inbound plus outbound) for calendar year 2006 - this field only valid for some airports.
DESCRIPT	FGDL added field based on FULLNAME
FGDLAQDATE	GeoPlan Acquisition Date
SHAPE	Feature geometry.
AUTOID	Unique ID added by GeoPlan

USER NOTES:

All point records in this dataset are represented by a single coordinate pair and two unique feature identifiers -- the landing facility location identifier (LOCID) and the site number (SITE_NO) assigned by the FAA. BTS quality checks were to cross reference the place dataset with the state dataset, to determine that the spatial data and attribute data were accurate.

unknown

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

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

Horizontal positional accuracy is based on coordinate data provided in the FAA National Airspace System Resource Aeronautical Dataset. These coordinate data identify the approximate location of the Airport Reference Point (ARP) as reported by the landing facility on the NFDC (National Flight Data Center) 5010 form. According to NFDC guidelines, the location of the ARP should be reported to a horizontal accuracy of one arc second of latitude and longitude. However, the accuracy of these reported coordinates are not verified by FAA. The records were loaded into a GIS and checked for any unusual or obviously erroneous locations.

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

None. Acknowledgment of the Federal Aviation Administration (FAA) and the Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) National Transportation Atlas Databases (NTAD) 2008 would be appreciated in products derived from these data.

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

REFERENCES:

Bureau Transportation Statistics: http://www.bts.gov

DATA LINEAGE SUMMARY:

The creation of this geospatial data layer was completed by RITA/BTS in February 2007. This Shapefile was built from textual data on the FAA National Airspace System Resource Aeronautical Data CDROM, effective 18 January 2008. Process Date: 2008 -The Geoplan Center received the dataset 8/5/2008. -Records were selected where "FIPS" = '12' to select only features in Florida. -Exported selection as a new layer -Reprojected data from GCS_WGS_1984 to Albers Conical Equal Area (Florida Geographic Data Library) -Added DESCRIPT field based on FULLNAME -Added FGDLAQDATE field and calculated to 8/5/2008 Process Date: 10/06/2008 Data imported to ArcSDE and exported as a shapefile. Process Date: 20081021

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:

Research and Innovative Technology Administration's Bureau of Transportation Statistics
BTS/RITA
1200 New Jersey Ave. SE
Washington, DC
20590
202-366-DATA


http://www.bts.gov/programs/geographic_information_services/
answers@bts.gov
Geospatial Information Program

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