PUBLIC USE AIRPORT RUNWAYS IN FLORIDA - 2009

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Federal Aviation Administration
Publication_Date: 2009
Title: PUBLIC USE AIRPORT RUNWAYS IN FLORIDA - 2009
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher:
U.S. Department of Transportation, Bureau of Transportation Statistics
Other_Citation_Details: State of Florida
Online_Linkage: <http://www.bts.gov/programs/geographic_information_services/>
Larger_Work_Citation:
Citation_Information:
Originator:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Publication_Date: 2008
Title: National Transportation Atlas Databases (NTAD) 2008
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Online_Linkage: <http://www.bts.gov/gis/>
Description:
Abstract:
This dataset represents airport runway data for the state of Florida. This data was taken from The Airport Runways database which is a geographic dataset of runways in the United States and US territories containing information on the physical characteristics of the runways. The 6073 runways in the dataset are runways associated with the 20347 airports in the companion airport data set. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product (Effective 18 January 2009).
Purpose:
This data provides users with information about the runway locations and attributes for national and regional analysis applications.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2009
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.429040
East_Bounding_Coordinate: -79.872251
North_Bounding_Coordinate: 30.983191
South_Bounding_Coordinate: 24.492815
Keywords:
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: transportation
Place:
Place_Keyword_Thesaurus: none
Place_Keyword: Florida
Stratum:
Stratum_Keyword_Thesaurus: none
Stratum_Keyword: air
Temporal:
Temporal_Keyword_Thesaurus: none
Temporal_Keyword: 2009
Access_Constraints: NONE
Use_Constraints:
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.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Federal Aviation Administration (Aeronautical Information Services, ATA-100)
Contact_Address:
Address_Type: mailing and physical address
Address: 800 Independence Avenue, S.W.
City: Washington
State_or_Province: DC
Postal_Code: 20591
Country: USA
Contact_Voice_Telephone: 1-800-457-6656 x35442
Data_Set_Credit:
The Federal Aviation Administration (FAA) develops and maintains the textual data from which this geospatial layer was derived.
Security_Information:
Security_Classification: Unclassified
Native_Data_Set_Environment:
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.1.1850
Cross_Reference:
Citation_Information:
Originator:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Publication_Date: 2009
Title: National Transportation Atlas Databases (NTAD) 2009
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Other_Citation_Details:
Bureau Transportation statistics: <http://www.bts.gov/>
Online_Linkage:
<http://www.bts.gov/publications/national_transportation_atlas_database/2009/>
Larger_Work_Citation:
Citation_Information:
Publication_Information:

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within the original data.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: unknown
Logical_Consistency_Report:
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
Completeness_Report:
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.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
Horizontal positional accuracy is based on coordinate data provided in the FAA National Airspace System Resource Aeronautical Dataset (Effective 18 January 2008). 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.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: unknown
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Federal Aviation Administration
Publication_Date: 2009
Title: FAA National Airspace System Resource Aeronautical Data
Edition:
FAA National Airspace System Resource Aeronautical Data (Effective 18 January 2008)
Geospatial_Data_Presentation_Form: tabular digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher: Federal Aviation Administration (FAA)
Larger_Work_Citation:
Citation_Information:
Originator:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Publication_Date: 2008
Title: National Transportation Atlas Databases (NTAD) 2008
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Online_Linkage: <http://www.bts.gov/gis/>
Source_Scale_Denominator: Unknown
Type_of_Source_Media: cdrom
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2009
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: BTS/RITA/FAA-NASRAD
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
The creation of this geospatial data layer was completed by RITA/BTS in February 2008. This Shapefile was derived from textual data on the FAA National Airspace System Resource Aeronautical Data CDROM, effective 18 January 2008. 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.
Source_Used_Citation_Abbreviation: FAA-NASRAD
Process_Date: 2008
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Contact_Address:
Address_Type: mailing and physical address
Address: 400 7th Street, SW Room 4117
City: Washington
State_or_Province: DC
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 202-366-DATA
Contact_Electronic_Mail_Address: answers@bts.gov
Process_Step:
Process_Description:
-The Geoplan Center received the dataset 8/12/2009. -Records were selected where "STFIPS" = '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/12/2009 -Renamed the dataset from runway to runway_2009
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20090825
Process_Step:
Process_Description: Data imported to ArcSDE and exported as a shapefile.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20090911
Process_Step:
Process_Description: Dataset copied.
Source_Used_Citation_Abbreviation:
Server=delphi.geoplan.ufl.edu; Service=5151; User=etat; Version=SDE.DEFAULT
Process_Date: 20090911
Process_Time: 11171600

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 246

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 24.000000
Standard_Parallel: 31.500000
Longitude_of_Central_Meridian: -84.000000
Latitude_of_Projection_Origin: 24.000000
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.002048
Ordinate_Resolution: 0.002048
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: RUNWAY_2009
Entity_Type_Definition: RUNWAY_2009.DBF
Entity_Type_Definition_Source: RITA/BTS/FAA
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: LOCID
Attribute_Definition:
A unique 3-4 character identifier assigned to the landing facility (i.e. airport).
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: SITENO
Attribute_Definition:
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
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: FULLNAME
Attribute_Definition: Official name of the runway's airport.
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: FAA_ST
Attribute_Definition: Airport's associated state or territory name.
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: ID
Attribute_Definition:
Runway unique identification code. For example: 01/19; 18L/36R (parallel runways); H1 (helipad); N/S (north/south); ALL/WAY (sealane); B1 (baloonport).
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: LENGTH
Attribute_Definition: The physical runway length, to the nearest foot. (Ex. 3500)
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: WIDTH
Attribute_Definition: The physical runway width, to the nearest foot. (Ex. 100)
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: SRFCTYPE
Attribute_Definition:
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)
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: SRFCTRTMNT
Attribute_Definition: Runway Surface treatment
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: PAVECLAS
Attribute_Definition:
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.
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: RWYLGHTS
Attribute_Definition: Runway lights edge intensity
Attribute_Definition_Source: FAA
Attribute:
Attribute_Label: STFIPS
Attribute_Definition: The 2-character FIPS code of the State or State equivalent.
Attribute_Definition_Source: Unknown
Attribute:
Attribute_Label: STPOSTAL
Attribute_Definition: Runway state post office code.
Attribute_Definition_Source: USPS
Attribute:
Attribute_Label: BASELAT
Attribute_Definition: Latitude of the base end of the runway.
Attribute_Definition_Source: BTS
Attribute:
Attribute_Label: BASELONG
Attribute_Definition: Longitude of the base end of the runway
Attribute_Definition_Source: BTS
Attribute:
Attribute_Label: RECLAT
Attribute_Definition: Latitude of the reciprocal end of the runway
Attribute_Definition_Source: BTS
Attribute:
Attribute_Label: RECLONG
Attribute_Definition: Longitude of the reciprocal end of the runway.
Attribute_Definition_Source: BTS
Attribute:
Attribute_Label: VERSION
Attribute_Definition:
The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed.
Attribute_Definition_Source: RITA/BTS
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: Name of Runway (based on FULLNAME field)
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition: GeoPlan Acquisition Date
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: AUTOID
Attribute_Definition: Unique ID added by GeoPlan
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.LEN
Attribute_Definition: Length in meters
Attribute_Definition_Source: GeoPlan

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Person:
Contact_Position:
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Voice_Telephone:
Contact_TDD/TTY_Telephone:
Contact_Facsimile_Telephone:
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>
Hours_of_Service:
Contact_Instructions:
Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
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>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile
Format_Version_Date: 2008
File_Decompression_Technique:
No compression applied. However, if using digital transfer online option, note access instructions.
Transfer_Size: 2.113
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.bts.gov/gis/>
Access_Instructions:
The NTAD DVD can be ordered from the online bookstore at www.bts.gov. NTAD can also be downloaded from the Geographic Information Program web sit at <http://www.bts.gov/programs/geographic_information_services/>.
Offline_Option:
Offline_Media: DVD
Recording_Capacity:
Recording_Density: 650
Recording_Density_Units: megabytes
Recording_Format: ISO 9660
Fees: None
Ordering_Instructions:
Call (202-366-DATA), or E-mail (answers@bts.gov) RITA/BTS to request the National Transportation Atlas Databases (NTAD) 2008 DVD. The NTAD DVD can be ordered from the online bookstore at www.bts.gov. Individual datasets from the NTAD can also be downloaded from the Geographic Information Program web sit at <http://www.bts.gov/programs/gis/>.
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2009

Metadata_Reference_Information:
Metadata_Date: 20090924
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Research and Innovative Technology Administration's Bureau of Transportation Statistics
Contact_Person: Geographic Information Program
Contact_Address:
Address_Type: mailing and physical address
Address: 400 7th Street, SW Room 4117
City: Washington
State_or_Province: District of Columbia
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 202-366-DATA
Contact_Electronic_Mail_Address: answers@bts.gov
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Access_Constraints: None
Metadata_Use_Constraints: None
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.9.6 on Thu Sep 24 16:01:14 2009