FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: PUBLIC USE AIRPORT RUNWAYS IN FLORIDA - 2018 

Geodataset Name:       RUNWAY_2018
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         260
GENERAL DESCRIPTION:
This dataset is the Florida subset of the Airport Runways Database. The Airport Runways database is a geographic dataset of runways in the United States and US territories containing information on the physical characteristics of the runways. The runways in the dataset are runways associated with the airports in the companion airport data set. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product. This is an update to the runway_2015 layer. 
DATA SOURCE(S):                    U.S. Department of Transportation, Bureau of Transportation Statistics, Federal Aviation Administration
SCALE OF ORIGINAL SOURCE MAPS:     Unknown
GEODATASET EXTENT:                 State of Florida

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

FEATURE ATTRIBUTE TABLES: 

Datafile Name: RUNWAY_2018.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
SITENUMBER
15 String
STATEABBV
2 String
ID
10 String
LENGTH
8 Double
WIDTH
8 Double
PCN
15 String
LIGHTSEDGE
5 String
LENGTHSOUR
20 String
LENGTHSO_1
15 String
CAPACITYSI
8 Double
CAPACITYDU
8 Double
CAPACITY2D
8 Double
CAPACITY_1
8 Double
FULLNAME
40 String
DESCRIPT
40 String
FGDLAQDATE
36 Date
AUTOID
4 Integer
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item

Item Description





OBJECTID

Internal feature number.
















Shape

Feature geometry.
















SITENUMBER

A unique identifying number followed by an asterisk and the 'landing facility type' code.  The SITENUMBER forms the key to the airport records in the NFDC (5010) database.  Example: 04508.*A
















STATEABBV

State post office code
















ID

Runway unique identification code. For example: 01/19; 18L/36R (parallel runways); H1 (helipad); N/S (north/south); ALL/WAY (sealane); B1 (baloonport).
















LENGTH

Physical length of the runway (to the nearest foot)
















WIDTH

Physical width of the runway (to the nearest foot)
















PCN

Pavement Classification Number
















LIGHTSEDGE

Runway lights edge intensity
















LENGTHSOUR

Runway length source
















LENGTHSO_1

Runway length source date (mm/dd/yyyy)
















CAPACITYSI

Runway weight-bearing capacity for single wheel type landing gear (DC3, C47, F15, etc.)
















CAPACITYDU

Runway weight-bearing capacity for dual wheel type landing gear (BE1900, B737, A319, etc.)
















CAPACITY2D

Runway weight-bearing capacity for two dual wheels in tandem type landing gear (B707, etc.)
















CAPACITY_1

Runway weight bearing capacity for two dual wheels in tandem/two dual wheels in double tandem body gear type landing gear (B747, E4, etc.)
















FULLNAME

Official name of the runway's airport
















DESCRIPT

GeoPlan added field based on FULLNAME
















FGDLAQDATE

GeoPlan added field based on the date acquired from the source
















AUTOID

Unique ID added by GeoPlan
















SHAPE.LEN

Length 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.

























This data provides users with information about the runway locations 
and attributes for national 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















There are no access and use constraints. Acknowledgement
of the Office of the Assistant Secretary for Research
and Technology/Bureau of Transportation Statistics (BTS)
National Transportation Atlas Database (NTAD), and the
Federal Aviation Administration (FAA) 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: 














DATA LINEAGE SUMMARY: 








The GeoPlan Center took the following steps during the QA/QC process:
- Downloaded the dataset from BTS on 7/16/2018 using this link:
  https://osav-usdot.opendata.arcgis.com/
  (original dataset in shapefile format and in the WGS 1984 geographic
  coordinate system).
- Dataset projected into the FGDL Albers HPGN projection using
  WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida.
- Only features in Florida were desired, so a Select By Attribute was
  run and features with the STATEABBV field equal to FL were
  selected. These features were exported to a new layer.
- Any records with no spatial information were removed from the dataset. There
  were 792 records deleted that had no spatial information.
- The 2018 shapefile was missing the FULLNAME field. The previous layer
  runway_2015 was used to supply the FULLNAME information for this
  layer update. A join was run on the SITENUMBER fields from the two
  layers. The FULLNAME data from the runway_2015 layer was used to
  populate the FULLNAME field, which was added to the runway_2018
  layer. 
- DESCRIPT field added based on the FULLNAME field. Any records with
  no data in the FULLNAME field had their DESCRIPT field calculated as
  'NO DESCRIPT AVAILABLE'.
- Deleted field SHAPESTLEN
- FGDLAQDATE field added based on the date the dataset was downloaded
  from source.
- The longest record for each field was found and field character lengths
  were shortened to the appropriate shortest length possible.
- Uppercased fields and appropriate records in the dataset.
- Layer name changed from Runways.shp to runway_2018.shp.
Process Date: 20180717


Dataset copied.
Process Date: 20180730









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:




Bureau of Transportation Statistics, Federal Aviation Administration
BTS/FAA
1200 New Jersey Avenue, SE
Washington, DC
20590
800-853-1351


https://osav-usdot.opendata.arcgis.com/
answers@bts.gov










FGDL CONTACT:

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