FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION VERSION 2007 TITLE: PUBLIC USE AIRPORT RUNWAYS Geodataset Name: RUNWAY_2007 Geodataset Type: SHAPEFILE Geodataset Feature: Polyline Feature Count: 220 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): U.S. Department of Transportation, Bureau of Transportation Statistics SCALE OF ORIGINAL SOURCE MAPS: Unknown DATE OF AUTOMATION OF SOURCE: 2007 GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: RUNWAY_2007.DBF
ITEM NAME | WIDTH | TYPE | N. DECIMAL DEGREES |
OBJECTID
|
4 | OID | --- |
LOCID
|
4 | String | --- |
SITENO
|
11 | String | --- |
FULLNAME
|
42 | String | --- |
FAA_ST
|
2 | String | --- |
UNIQUE_ID
|
18 | String | --- |
RWY_ID
|
7 | String | --- |
RWY_LEN
|
5 | String | --- |
RWY_WITH
|
4 | String | --- |
RWY_SFC_TY
|
12 | String | --- |
RWY_SFC_TR
|
5 | String | --- |
PAV_CLASS_
|
11 | String | --- |
RWY_LIGHTS
|
5 | String | --- |
STFIPS
|
2 | String | --- |
ST_POSTAL
|
2 | String | --- |
VERSION
|
2 | String | --- |
DESCRIPT
|
50 | String | --- |
FGDLAQDATE
|
8 | Date | --- |
AUTOID
|
4 | Number | --- |
SHAPE
|
4 | Geometry | --- |
SHAPE.LEN
|
0 | Double | --- |
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). |
|
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. |
|
UNIQUE_ID |
Site number concatenate with the Runway ID |
|
RWY_ID |
Runway unique identification code. For example: 01/19; 18L/36R (parallel runways); H1 (helipad); N/S (north/south); ALL/WAY (sealane); B1 (baloonport). |
|
RWY_LEN |
The physical runway length, to the nearest foot. (Ex. 3500) |
|
RWY_WITH |
The physical runway width, to the nearest foot. (Ex. 100) |
|
RWY_SFC_TY |
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)
|
|
RWY_SFC_TR |
Runway Surface treatment
|
|
PAV_CLASS_ |
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. |
|
RWY_LIGHTS |
Runway lights edge intensity
|
|
STFIPS |
The 2-character FIPS code of the State or State equivalent |
|
ST_POSTAL |
Runway state post office code |
|
VERSION |
The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed. |
|
DESCRIPT |
GeoPlan added field based on FULLNAME |
|
FGDLAQDATE |
Date GeoPlan acquired data from source |
|
AUTOID |
Unique ID added by GeoPlan |
|
SHAPE |
Feature geometry. |
|
SHAPE.LEN |
Length in meters |
All linear features in this data set are straight lines. RWY_ID is the unique identifier for each record in the dataset. There may be more than one runway (RWY_ID) located at a single airport. Airports can be individually identified by the landing facility location identifier (LOCID) or by the site number (SITE_NO) 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. |
|
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 18 January 2007). 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 |
THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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 |
National Transportation Atlas Database (NTAD): http://www.bts.gov/ http://www.bts.gov/help/national_transportation_atlas_database.html |
The creation of this geospatial data layer was completed by RITA/BTS in February 2007. This Shapefile was derived from textual data on the FAA National Airspace System Resource Aeronautical Data CDROM, effective 18 January 2007. 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: 2007 |
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 (RITA/BTS) FAA-NASRAD 400 7th Street, SW Room 4117 Washington, District of Columbia 20590 202-366-DATA |
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