FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: PUBLIC USE AIRPORT RUNWAYS IN FLORIDA - 2013

Geodataset Name:       RUNWAY_2013
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         261
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 261 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 (Effective 17 March 2013). This is an update to the runway_2012 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: 20130715 TIME PERIOD OF CONTENT: 20130317 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: RUNWAY_2013.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
LOCID
4 String
SITENO
11 String
FULLNAME
50 String
FAA_ST
2 String
ID
7 String
Length
5 String
Width
4 String
SrfcType
12 String
SrfcTrtmnt
5 String
PaveClas
11 String
RwyLghts
5 String
STFIPS
254 String
STPostal
254 String
BaseLat
8 Double
BaseLong
8 Double
RecLat
8 Double
RecLong
8 Double
DESCRIPT
50 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.

LOCID A unique 3-4 character identifier assigned to the landing facility (i.e. airport).

SITENO 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 name of the runway's airport.

FAA_ST Airport's associated state or territory name.

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 The physical runway length, to the nearest foot. (Ex. 3500)

Width The physical runway width, to the nearest foot. (Ex. 100)

SrfcType Runway surface type and condition. (NOTE 1: Surface type can have one entry or a combination of two entries when the runway is composed of distinct sections.) (NOTE 2: The surface type is optionally followed by a condition indicator: G=Good Condition, F=Fair Condition, P=Poor Condition. Some valid examples for this attribute: ASPH-CONC, ASPH-F, ASPH-CONC-G)
CONC = Portland cement concrete

ASPH = Asphalt or bituminous concrete

SNOW = Snow

ICE = Ice

MATS = Pierced steel planking; landing mats; membranes

TREATED = Oiled; soil cement or lime stabilized

GRAVEL = Gravel; cinders; crushed rock; coral or shells; slag

TURF = Grass; sod

DIRT = Natural soil

WATER = Water


SrfcTrtmnt Runway Surface treatment
GRVD = Saw-cut or plastic grooved

PFC = Porous friction course

AFSC = Aggregate friction seal coat

RFSC = Rubberized friction seal coat

WC = Wire comb or wire tine

NONE = No special surface treatment


PaveClas Pavement Classification Number (PCN): A rating system that expresses the relative load carrying capacity of a pavement in terms of a standard single wheel load.

RwyLghts Runway lights edge intensity
HIGH = High

MED = Medium

LOW = Low

NSTD = Non-standard lighting system

NONE = No edge lighting system


STFIPS The 2-character FIPS code of the State or State equivalent

STPostal Runway state post office code

BaseLat Latitude of the base end of the runway.

BaseLong Longitude of the base end of the runway

RecLat Latitude of the reciprocal end of the runway

RecLong Longitude of the reciprocal end of the runway.

DESCRIPT GeoPlan added field based on FULLNAME

FGDLAQDATE The date GeoPlan acquired the data from the source.

AUTOID Unique ID added by GeoPlan

SHAPE.LEN Length in meters


USER NOTES:
All linear features in this data set are straight lines. ID is the 
unique identifier for each record in the dataset. There may 
be more than one runway (ID) located at a single airport. 
Airports can be individually identified by the landing facility 
location identifier (LOCID) or by the site number (SITENO) 
attribute. RITA/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
Landing facilities in this database consist of those identified in 
the NFDC 5527 database to be either publicly owned, or 
privately owned but open to the public, or owned by the U.S. 
military. The following landing facilities have been excluded: 
private landing facilities not open to the public, glider ports and 
ultra-light landing facilities, as well as landing facilities that do 
not have a current LOCID assigned to them.
GeoPlan relied on the integrity of the attribute information within
the original data.
The National Transportation Atlas Database is a set of nationwide geographic 
databases of transportation facilities, transportation networks, and associated 
infrastructure. These datasets include spatial information for transportation 
modal networks and intermodal terminals, as well as the related attribute 
information for these features. Metadata documentation, as prescribed by the 
Federal Geographic Data Committee, is also provided for each database. The 
data support research, analysis, and decision-making across all modes of 
transportation. They are most useful at the national level, but have major 
applications at regional, state, and local scales throughout the transportation 
community.

This data provides users with information about the runway locations 
and attributes for national and regional analysis applications.

Horizontal positional accuracy is based on coordinate data 
provided in the FAA National Airspace System Resource 
Aeronautical Dataset (Effective 9 February 2012). 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.

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) 2012 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:
National Transportation Atlas Database:
http://www.bts.gov/publications/national_transportation_atlas_database/

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

DATA LINEAGE SUMMARY:
The creation of this geospatial data layer was completed 
by RITA/BTS in April 2013. This Shapefile was derived from 
textual data on the FAA National Airspace System Resource 
Aeronautical Data CDROM, effective 17 March 2013. The Apt.txt 
file was converted into three files using the UNIX command 
grep. The runway table structure was built in Oracle that 
followed the structure of the facility runway data described 
in the Apt_rf.txt file. A control file was built for the 
desired runway 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 runway linear dataset.
Process Date: 20110101

In July 2013 GeoPlan obtained the data from the Bureau of Transportation Statistics (BTS) in CDROM format. The data was in the following geographical coordinate system: WGS 1984 Datum, Units: Degrees. During the QA/QC process GeoPlan performed the following tasks: - Extracted the features where "STATEFIPS" = '12' to select features in Florida - Reprojected the data to FGDL Albers HPGN - Uppercased all fields - Added DESCRIPT field based on FULLNAME - Added a FGDLAQDATE field based on date GeoPlan acquired the data from the source - Renamed the dataset from runway to runway_2013 Process Date: 20140221
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/Bureau of Transportation Statistics
RITA/BTS/FAA
1200 New Jersey Ave. S.E.
Washington, D.C.
20590
202-366-DATA

http://www.bts.gov/programs/geographic_information_services/ answers@bts.gov National Transportation Atlas Database (NTAD) 2013

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