Geodataset Name:       GC_AVIATIONBND_JAN16
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         990

DATA SOURCE(S):                    University of Florida GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     Varies
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  20160114
TIME PERIOD OF CONTENT:            Begin Date: 20070226    End Date: 20160114
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: GC_AVIATIONBND_JAN16.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
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 UNKNOWN = Facility Status Unknown
PARCELID	Parcel Identification Number, derived from the 2014 statewide parcel layer.
NAME	Facility Name
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.
COUNTY	County of facility's physical location.
PHONE	The phone number of the facility.
TYPE	Landing Facility Type AIRPORT = Airport Facility SEAPLANE BASE = Facility for sea plane operations HELIPORT = Facility for helicopter operations STOLPORT = Short Take Off and Landing Facility ULTRALIGHT = Facility for ultralight operations
OWNER	Entity owner of the facility.
OPERATING	The responsible organization for management and operation of a facility (e.g., public, private, quasi-public).
OP_CLASS	Classification of the operating entity.
FDOT_SIS	Strategic Intermodal System (SIS).
REG_CODE	FAA Region where the facility is located.
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).
AIRPORT_LG	Airport Lighted.
FARPART139	FAR Part 139 Certificated.
COM_SERVE	Commercial Service.
NONCOMLAND	Non-Comm Landing.
NPIASFEDA	NPIAS / Fed Agreements.
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
CNTL_TWR	Airport Control Tower located on the airport. Y = Yes N = No
FSOURCE	Feature Spatial Source.
DATASOURCE	Feature Data/Tabular Source.
LAT_DD	Latitude in decimal degrees.
LONG_DD	Longitude in decimal degrees.
MGRS	Military Grid Reference System (MGRS) Coordinate of the Facility. The MGRS is the geocoordinate standard used by NATO militaries for locating points on the earth. The MGRS provides a means to represent any location on the surface of the Earth using an alphanumeric string. Hierarchical references are based on the Universal Transverse Mercator (UTM) coordinate system. The MGRS is used for the entire earth. http://mgrs-data.org/
GCID	The GeoPlan Center identification number that links this polygon feature layer with its corresponding point feature layer.
ACRES	Facility acreage.
DESCRIPT	Based on 'NAME'
FLAG	Type of update that occurred. NV = Not Verified V = Verified, in most cases this NAME field verification was based on ESRI/Google Imagery and Google Street View. The exact facilities boundaries are not verified and in many cases and only based on parcel boundaries.
UPDATE_DAY	The last day the file was updated by the Source.
FGDLAQDATE	The Date FGDL acquired the data from the Source.
AUTOID	Unique ID added by GeoPlan
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 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

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

REFERENCES:

Florida Aviation Database (FAD) http://www.florida-aviation-database.com/ FDOT Aviation and Spaceports Office http://www.dot.state.fl.us/aviation/ FDOT Florida Airport Directory http://www.dot.state.fl.us/aviation/directory.shtm National Transportation Atlas Database - 2015 http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/publications/national_transportation_atlas_database/2015/index.html

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 ------------------------------------------------------------------------ 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. ------------------------------------------------------------------------ Process Date: 20070226 The GeoPlan Center performed the following steps in order to create the January 2016 statewide aviation facilities boundaries data layer. GeoPlan removed all runway polygons. Please note all runway polygons can now be found in the new gc_runwaybnd layer. GeoPlan added facility boundaries for new aviation locations discovered through the BTS AIRPORTS_2015.shp layer http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/publications/national_transportation_atlas_database/2015/point Aviation facilities locations were checked using 2014 Parcels (Owner Information), imagery, and Google Street View and either marked as Verified or Not Verified in the FLAG field, please see the FLAG field Attribute Definition for more information. During the Spatial and Tabular QAQC duplicates were removed. Next GeoPlan Center performed the following attribute table adjustments. -Socio-Cultural Effect data fields were updated. -Upper cased all records. -Added DESCRIPT field based on NAME. -Added FGDLAQDATE field and populated it. Process Date: 20160114

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 Architecture BLDG, PO Box 115706
Gainesville, Florida
32611-5706



www.fgdl.org
data@fgdl.org
Kate Norris

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