Bureau of Transportation Statistics, (BTS) 19990100 20010000 SHAPE http://www.bts.gov/ This dataset contains runways in the State of Florida and information on the physical characteristics of the runways. BTS strives to make high-quality data and information available for the transportation community and other individuals or groups interested in transportation. Strong leadership, planning, educational outreach, and the pursuit of a superior working team frame our vision. The 1991 Intermodal Surface Transportation Efficiency Act (ISTEA) established the Bureau of Transportation Statistics (BTS) for data collection, analysis, and reporting and to ensure the most cost-effective use of transportation-monitoring resources. We strive to increase public awareness of the nation's transportation system and its implications and improve the transportation knowledge base of decisionmakers. Federal Aviation Administration contributed facility locations, name and other identification, physical description, ownership, FAA certification, military and customs landing rights, number of runways and helipads. 19990100 Ground Condition Complete Irregular -87.429040 -79.872251 30.983191 24.492815 NONE Bureau of Transportation Statistics runways helipads seaplane bases NONE Florida Existing aitport runways and helipads NONE 1990's NONE THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale data sets 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 data sets are recommended for projects that are at the multi-county or regional level. 1:250000 scale data sets 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 analyses. 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 web pages at: http://www.geoplan.ufl.edu/education.html For more information, visit: http://www.bts.gov/ Bureau of Transportation Statistics, (BTS) 19990100 Map Horizontal positional accuracy is based on coordinate data provided in the NFDC 5010 database. These coordinate data dentify the approximate location of the Airport Reference Point (ARP) as reported by the landing facility on the NFDC 5010 form. According to NFDC guidelines, thelocation 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. Relied on the integrity of the attribute information within the original data layer. Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." Bureau of Transportation Statistics, (BTS) 19990100 Map N/A Map 19990100 Ground Condition BTS Data representing airport runways, helipads, and seaplane bases in the state of Florida. The process step describes, in general, the process used in the production of data sets. The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects: (1) Reprojected data to FGDL Albers (2) Set Tolerances to FGDL Standard (3) Dropped item featureid (repeat of featureid), and 'locid' (4) Moved descript to the end of table (5) Related attribute tables were joined 20000000 Albers Conical Equal Area 24.000000 31.500000 -84.000000 24.000000 400000.00000 0.00000 coordinate pair 0.001024 0.001024 METERS D_North_American_1983_HARN GRS1980 6378137.000000 298.257222 RUNWAY.DBF Database File None RECTYPE Record type, 'L' for line BTS record Unknown VERSION File version number, 03 Same Unknown REVISION Record revision number Same Unknown MODDATE Record modification date Same Unknown LINKID Unique sequential line identification Same Unknown FEATUREID Unique line identification Same Unknown ANODE Node identification for the beginning node of the line Same Unknown BNODE Node identification for the ending node of the line Same Unknown STFIPS1 Primary State FIPS Code Same Unknown STFIPS2 Secondary State FIPS Code Same Unknown SITE Unique airport identifier Same Unknown RWY_ID Runway Identifier e.g., 01/19; 18L/36R (parallel runways); H1 (helipad); N/S (north/south); ALL/WAY (seaplane). Same Unknown RWY_LEN Runway Length Same Unknown RWY_WDTH Runway Width Same Unknown RWY_SFC_TY Runway Surface Type Same CONC Portland cement concrete Same ASHP Asphalt or bituminous concrete Same SNOW Snow Same ICE Ice Same MATS Pierced steel planking; landing mats; membranes Same TREATED Oiled; soil cement or lime stabilized Same GRAVEL Gravel; cinders; crushed rock; coral or shells; slag Same TURF Grass; sod Same DIRT Natural soil Same WATER Water Same G Good Condition Same F Fair Condition Same P Poor Condition Same Unknown RWY_SFC_TR Runway Surface Treatment (GRVD - Saw-cut or plastic grooved) Same Unknown PCN Pavement Classification Number -rating system that expresses the relative load carrying capacity of a pavement in terms of a standard single wheel load. The rating is structured so that a pavement with a particular PCN value can support, without weight restrictions, an aircraft which has an aircraft classification number (ACN) equal to or less than the pavement's PCN value. The data format is: PCN / pavement_type/subgrade_strength /tire pressure / determination_method, where: PCN: a numerical value; Pavement type: R - Rigid F - Flexible; Subgrade strength: Letters A-F; Tire pressure code: Letters W-Z; Determination method: T - Technical, U - Using aircraft Same Unknown RWY_EDGE_L Runway Edge Light intensity Same HIGH High Same MED Medium Same LOW Low Same NSTD Non-standard lighting system Same NONE No edge lighting system Same Unknown MOD_CODE Modification Code Same DX Duplicate modification Same Unknown SITE_NO Airport Site Number Same Unknown BE_ID Runway Base End (BE) Identifier Same Unknown BE_TR_ALGN BE True Alignment, true magnetic heading of the base end of the runway, to the nearest degree Same Unknown BE_ILS_TP BE Instrument Landing System Same ILS instrument landing system Same MLS microwave landing system Same SDF simplified directional facility Same LOCALIZER localizer Same LDA localizer-type directional aid Same ISMLS interim standard microwave landing system Same ILS/DME instrument landing system / distance measuring equipment Same SDF/DME simplified directional facility / distance measuring equipment Same LOC/DME localizer / distance measuring equipment Same LOC/GS localizer / glide slope Same LDA/DME localizer-type directional aid / distance measuring equipment Same Unknown BE_TFC_PAT BE Right Hand Traffic Pattern Y - YES, N - No Same Unknown BE_TP_MKS BE Runway Markings Same PIR Precision Instrument Runway Same NPI Nonprecision Instrument Same BSC Basic Same NRS Numbers Only Same NSTD Nonstandard (other than numbers only) Same BUOY Buoys (Seaplane Base) Same STOL Short Takeoff and Landing Same NONE None Same Unknown BE_TP_MKS BE Runway Markings Same G Good Same F Fair Same P Poor Same Unknown BE_ARR_DEV BE Aircraft Arresting Device Same Unknown BE_ELEV BE Elevation Same Unknown BE_VGP_ANG BE Visual Glide Path Angle Same Unknown BE_VGS_IND BE - Visual Glide Slope Indicators Same S2L 2-Box SAVASI on Left Side of Runway Same S2R 2-Box SAVASI on Right Side of Runway Same V2L 2-Box VASI on Left Side of Runway Same V2R 2-Box VASI on Right Side of Runway Same V4L 4-Box VASI on Left Side of Runway Same V4R 4-Box VASI on Right Side Of Runway Same V6L 6-Box VASI on Left Side of Runway Same V6R 6-Box VASI on Right Side of Runway Same V12 12-Box VASI on Both Sides of Runway Same V16 16-Box VASI on Both Sides of Runway Same P2L 2-Lgt PAPI on Left Side of Runway Same P2R 2-Lgt PAPI on Right Side of Runway Same P4L 4-Lgt PAPI on Left Side of Runway Same P4R 4-Lgt PAPI on Right Side of Runway Same NSTD Nonstandard VASI System Same PVT Privately Owned Approach Slope Indicator Light System on A Public Use Airport that is Intended for Private Use Only Same VAS Non-Specific VASI System Same NONE No Approach Slope Light System Same N No Approach Slope Light System Same Unknown R_EQ BE - Visual Range Equipment Same T Touchdown Same M Midfield Same R Rollout Same N No RVR Available Same Unknown V_EQ BE - Visibility Value Equipment, indicates the presence of RVV equipment. Y - Yes, N - No Same Unknown P_LTG BE - Approach Light System Same ALSAF 3000 Foot High Intensity Approach Lighting System with Centerline Sequence Flashers. Same ALSF1 Standard 2400 Foot High Intensity Approach Lighting System with Sequenced Flashers, Category I Configuration. Same ALSF2 Standard 2400 Foot High Intensity Approach Lighting System with Sequenced Flashers, Category 2 Or 3 Configuration Same MALS 1400 Foot Medium Intensity Approach Lighting System Same MALSF 1400 Foot Medium Intensity Approach Lighting System with Sequenced Flashers Same MALSR 1400 Foot Medium Intensity Approach Lighting System with Runway Alignment Indicator Lights Same SSALS Simplified Short Approach Lighting System Same SSALF Simplified Short Approach Lighting with Sequenced Flashers Same SSALR 12-Box VASI on Both Sides of Runway Same NEON Neon Ladder System Same ODALS Omnidirectional Approach Lighting System Same LDIN Lead-In Light System Same MIL OVRN Military Overrun Same NSTD All Others Same NONE No Approach Lighting Is Available Same Unknown BE_REIL BE - Runway End Identifier Lights Y - Yes, N - No Same Unknown BE_CTR_LTS BE - Runway Centerline Lights Y - Yes, N - No Same Unknown BE_TD_LTS BE - Runway Touchdown Lights Y - Yes, N - No Same Unknown BE_CTL_OBJ BE - Controlling Object Description (e.g., trees, bldg, fence, none) Same Unknown BE_OBJ_LT BE - Controlling Object Marked/Lighting Same M Marked Same L Lighted Same ML Marked And Lighted Same N None Same Unknown BE_FAR_P77 FAA FAR Part 77 Same A(V) Utility runway with a visual approach Same B(V) Other than utility runway with a visual approach Same A(NP) Utility runway with a nonprecision approach Same C Other than utility runway with a nonprecision approach having visibility minimums greater than 3/4 mile Same PIR Precision Instrument Runway Same Unknown BE_OBJ_CL BE - Controlling Object Clearance Slope Same Unknown BE_OBJ_HT BE - Controlling Object Height Same Unknown BE_OBJ_DIS BE - Controlling Object Distance from runway end Same Unknown BE_OBJ_OS BE - Controlling Object Offset distance in feet from the runway centerline. Same Unknown RE_ID Reciprocal End (RE) Identifier Same Unknown RE_TR_ALGN RE True Alignment Same Unknown RE_ILS_TP RE Instrument Landing System Same ILS instrument landing system Same LOC/GS localizer / glide slope Same LOC/DME localizer / distance measuring equipment Same LOCALIZER localizer Same ILS/DME instrument landing system / distance measuring equipment Same Unknown RE_TFC_PAT RE Right Hand Traffic Pattern Y - YES, N - No Same Unknown RE_TP_MKS RE Runway Markings Same PIR Precision Instrument Runway Same NPI Nonprecision Instrument Same BSC Basic Same NRS Numbers Only Same NSTD Nonstandard (other than numbers only) Same BUOY Buoys (Seaplane Base) Same STOL Short Takeoff and Landing Same NONE None Same Unknown RE_CND_MKS RE Marking Condition Same G Good Same F Fair Same P Poor Same Unknown RE_ARR_DEV RE Aircraft Arresting Device. Indicates the type of jet arresting barrier installed at the far end of the reciprocal end of the runway (e.g., MA1, MA1A, BAK9, BAK6, E14, E15, E5, etc.) Same Unknown RE_ELEV RE Elevation Same Unknown RE_VGP_ANG RE Visual Glide Path Angle Same Unknown RE_VGS_IND RE Visual Glide Slope Indicators Same S2L 2-Box SAVASI on Left Side of Runway Same S2R 2-Box SAVASI on Right Side of Runway Same V2L 2-Box VASI on Left Side of Runway Same V2R 2-Box VASI on Right Side of Runway Same V4L 4-Box VASI on Left Side of Runway Same V4R 4-Box VASI on Right Side Of Runway Same V6L 6-Box VASI on Left Side of Runway Same V6R 6-Box VASI on Right Side of Runway Same V12 12-Box VASI on Both Sides of Runway Same V16 16-Box VASI on Both Sides of Runway Same P2L 2-Lgt PAPI on Left Side of Runway Same P2R 2-Lgt PAPI on Right Side of Runway Same P4L 4-Lgt PAPI on Left Side of Runway Same P4R 4-Lgt PAPI on Right Side of Runway Same NSTD Nonstandard VASI System Same PVT Privately Owned Approach Slope Indicator Light System on A Public Use Airport that is Intended for Private Use Only Same VAS Non-Specific VASI System Same NONE No Approach Slope Light System Same N No Approach Slope Light System Same TRIL Tri-color VASI on Left Side of Runway Same TRIR Tri-color VASI on Right Side of Runway Same PSIL Pulsating/Steady Burning VASI on Left Side of Runway Same PSIR Pulsating/Steady Burning VASI on Right Side of Runway Same PNIL System of Panels on Left Side of Runway that May or May Not Be Lighted Same PNIR System of Panels on Right Side of Runway that May or May Not Be Lighted Same Unknown RE_RVR_EQ RE Visual Range Equipment Same T Touchdown Same M Midfield Same R Rollout Same N No RVR Available Same Unknown RE_RVV_EQ RE Visibility Value Equipment indicates the presence of RVV equipment. Y - Yes, N - No Same Unknown RE_APP_LTG RE Approach Light System Same ALSAF 3000 Foot High Intensity Approach Lighting System with Centerline Sequence Flashers. Same ALSF1 Standard 2400 Foot High Intensity Approach Lighting System with Sequenced Flashers, Category I Configuration. Same ALSF2 Standard 2400 Foot High Intensity Approach Lighting System with Sequenced Flashers, Category 2 Or 3 Configuration Same MALS 1400 Foot Medium Intensity Approach Lighting System Same MALSF 1400 Foot Medium Intensity Approach Lighting System with Sequenced Flashers Same MALSR 1400 Foot Medium Intensity Approach Lighting System with Runway Alignment Indicator Lights Same SSALS Simplified Short Approach Lighting System Same SSALF Simplified Short Approach Lighting with Sequenced Flashers Same SSALR 12-Box VASI on Both Sides of Runway Same NEON Neon Ladder System Same ODALS Omnidirectional Approach Lighting System Same LDIN Lead-In Light System Same MIL OVRN Military Overrun Same NSTD All Others Same NONE No Approach Lighting Is Available Same Unknown RE_REIL RE Runway End Identifier Lights Y - Yes, N - No Same Unknown RE_CTR_LTS RE Runway Centerline Lights Y - Yes, N - No Same Unknown RE_TD_LTS RE Runway Touchdown Lights Y - Yes, N - No Same Unknown RE_CTL_OBJ RE Controlling Object Description Same Unknown RE_OBJ_LT RE Whether the controlling object is marked or lighted. Same M Marked Same L Lighted Same ML Marked And Lighted Same N None Same Unknown RE_FAR_P77 RE FAA FAR Part 77 Same A(V) Utility runway with a visual approach Same B(V) Other than utility runway with a visual approach Same A(NP) Utility runway with a nonprecision approach Same C Other than utility runway with a nonprecision approach having visibility minimums greater than 3/4 mile Same PIR Precision Instrument Runway Same Unknown RE_OBJ_CL RE Controlling Object Clearance Slope Same Unknown RE_OBJ_HT RE Controlling Object Height Same Unknown RE_OBJ_DIS RE Controlling Object Distance Same Unknown RE_OBJ_OS RE Controlling Object Offset distance in feet from the runway centerline Same Unknown DESCRIPT Name or identification for the runway's airport Same Unknown Operator FLORIDA GEOGRAPHIC DATA LIBRARY Physical

431 Architecture Building PO Box 115706

Gainesville Florida 32611-5706 (352) 3920997, Operator http://www.fgdl.org/fgdldocs/document/techsupp.htm 24 Hours / Day Please visit the web site, http://www.fgdl.org, for all questions or concerns. Florida Geographic Data Library is a product of the University of Florida GeoPlan Center with support from the Florida Department of Transportation and the Florida Department of Environmental Protection. THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE "MATERIALS") ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE "DATA PROVIDERS"). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED "AS IS". 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 MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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. 2001 Operator Physical

400 Seventh Street, SW

Washington DC 20590 1-202-366-3640 FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998