PUBLIC USE AIRPORT RUNWAYS IN FLORIDA - 2015

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator:

U.S. Department of Transportation, Bureau of Transportation Statistics, Federal Aviation Administration

Publication_Date: 201506

Title: PUBLIC USE AIRPORT RUNWAYS IN FLORIDA - 2015

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Washington, D.C.

Publisher:

U.S. Department of Transportation, Bureau of Transportation Statistics, Federal Aviation Administration

Other_Citation_Details: State of Florida

Online_Linkage:

<http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/subject_areas/geographic_information_services/index.html>

Larger_Work_Citation:

Citation_Information:

Originator:

Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)

Publication_Date: 201506

Title: National Transportation Atlas Databases (NTAD) 2015

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.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/subject_areas/geographic_information_services/index.html>

Description:

Abstract:

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 259 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 1 April 2014). This is an update to the runway_2014 layer.

Purpose:

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

Supplemental_Information:

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.

Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 201506

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: NONE

Theme_Keyword: airports

Theme_Keyword: landing

Theme_Keyword: aircraft

Theme_Keyword: runways

Theme:

Theme_Keyword_Thesaurus: NONE

Theme_Keyword: transportation

Place:

Place_Keyword_Thesaurus: GNIS

Place_Keyword: USA

Place_Keyword: United States

Place_Keyword: US

Place_Keyword: Florida

Stratum:

Stratum_Keyword_Thesaurus: None

Stratum_Keyword: air

Temporal:

Temporal_Keyword_Thesaurus: None

Temporal_Keyword: 2008

Temporal_Keyword: 2009

Temporal_Keyword: 2011

Temporal_Keyword: 2010

Temporal_Keyword: 2012

Temporal_Keyword: 2013

Temporal_Keyword: 2014

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) 2014 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: FAA National Headquarters, 800 Independence Avenue, S.W.

City: Washington

State_or_Province: D.C.

Postal_Code: 20591

Country: US

Contact_Voice_Telephone: 1-800-457-6656 x35442

Contact_Electronic_Mail_Address: answers@BTS.gov

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 Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.4000

Cross_Reference:

Citation_Information:

Originator:

Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)

Publication_Date: 201506

Title: National Transportation Atlas Databases (NTAD) 2015

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Washington, D.C.

Publisher:

U.S. Department of Transportation, Bureau of Transportation Statistics, Federal Aviation Administration

Other_Citation_Details:

National Transportation Atlas Database: <http://www.bts.gov/publications/national_transportation_atlas_database/>
Bureau of Transportation Statistics: <http://www.rita.dot.gov/bts/>

Online_Linkage:

<http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/subject_areas/geographic_information_services/index.html>

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

GeoPlan relied on the integrity of the attribute information within the original data.

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 site number (SITENUMBER) 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 1 April 2014). 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.

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: 201506

Title: FAA National Airspace System Resource Aeronautical Data

Edition:

FAA National Airspace System Resource Aeronautical Data (Effective 1 April 2014).

Geospatial_Data_Presentation_Form: tabular digital data

Publication_Information:

Publication_Place: Washington, DC

Publisher: Federal Aviation Administration (FAA)

Source_Scale_Denominator: Unknown

Type_of_Source_Media:

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: 201506

Source_Currentness_Reference: publication date

Source_Citation_Abbreviation: RITA/BTS/FAA

Source_Contribution: Spatial and Attribute Information

Process_Step:

Process_Description:

The creation of this geospatial data layer was completed by RITA/BTS in April 2014. This Shapefile was derived from textual data on the FAA National Airspace System Resource Aeronautical Data CDROM, effective 1 April 2014. 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: 20110101

Process_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization:

Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)

Contact_Person: Office of Geospatial Information Systems

Contact_Address:

Address_Type: mailing and physical address

Address: 1200 New Jersey Ave. S.E.

City: Washington

State_or_Province: DC

Postal_Code: 20590

Country: US

Contact_Voice_Telephone: 202-366-DATA

Contact_Electronic_Mail_Address: answers@bts.gov

Process_Step:

Process_Description:

In 2015 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 features where "STFIPS" = '12' to select features in Florida - When checking 2015 metadata for date, no date was found. Opened text file associated with runway.shp and found date of June 2015 at the end of the text file. Checked RUNWAY_2014.shp to compare dates and found a publication date of June 2014. - The original shapefile was projected in GCS_WGS_1984. Reprojected the shapefile to Albers Conical Equal Area (fgdl_square) using the WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida transformation. - Added DESCRIPT field based on FULLNAME - Added FGDLAQDATE field and populated it based on the date GeoPlan received the data - Restructured table by reducing field lengths to better suit data - Uppercased all fields
NOTE: Found that the margin of error was higher than 0.005 between 2015 and 2014 shapefiles because GeoPlan switched transformation methods in January of 2015. Tested this by transforming original 2015 data using the old transformation method and comparing it to the 2014 ETAT shapefile. Future transformation of this data should line up with the newest transformation.
2015 shapefile missing FULLNAME field. Used summary statistics to Compare unique IDs between the SITENUMBER field in runways_proj And SITENO in in RUNWAY_2014. All values determined to be unique. Joined table based on SITENUMBER and SITENO. Populated FULLNAME Field in runways_proj with FULLNAME from RUNWAY_2014. Removed Join.
Attribute table changed from 2014 to 2015. 2015 table missing some 2014 fields. Some field names changed. SITENUMBER = SITENO LIGHTSEDGE = RWYLGHTS STATEABBV = FAA_ST

Source_Used_Citation_Abbreviation: GeoPlan

Process_Date: 20150922

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: 259

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_2015

Entity_Type_Definition: RUNWAY_2015.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: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: SiteNumber

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_Domain_Values:

Codeset_Domain:

Codeset_Name: List of Official Airport Site Numbers

Codeset_Source: FAA

Attribute:

Attribute_Label: FULLNAME

Attribute_Definition: Official name of the runway's airport.

Attribute_Definition_Source: FAA

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: List of Official Airport Site Numbers

Codeset_Source: FAA

Attribute:

Attribute_Label: StateAbbv

Attribute_Definition: Runway state post office code

Attribute_Definition_Source: USPS

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name: List of Official U.S. State and Territory Postal Abbreviations

Codeset_Source: U.S. Post Office

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_Domain_Values:

Codeset_Domain:

Codeset_Name: List of Official Runway Codes

Codeset_Source: FAA

Attribute:

Attribute_Label: Length

Attribute_Definition: The physical runway length, to the nearest foot. (Ex. 3500)

Attribute_Definition_Source: FAA

Attribute_Domain_Values:

Unrepresentable_Domain: measured value

Attribute:

Attribute_Label: Width

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

Attribute_Definition_Source: FAA

Attribute_Domain_Values:

Unrepresentable_Domain: measured value

Attribute:

Attribute_Label: PCN

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

Attribute_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: R

Enumerated_Domain_Value_Definition: Pavement Type - Rigid

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: T

Enumerated_Domain_Value_Definition: Pavement Type - Flexible

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: A

Enumerated_Domain_Value_Definition: Subgrade Strength Level

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: B

Enumerated_Domain_Value_Definition: Subgrade Strength Level

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: C

Enumerated_Domain_Value_Definition: Subgrade Strength Level

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: D

Enumerated_Domain_Value_Definition: Subgrade Strength Level

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: E

Enumerated_Domain_Value_Definition: Subgrade Strength Level

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: F

Enumerated_Domain_Value_Definition: Subgrade Strength Level

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: W

Enumerated_Domain_Value_Definition: Tire Pressure Code

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: X

Enumerated_Domain_Value_Definition: Tire Pressure Code

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Y

Enumerated_Domain_Value_Definition: Tire Pressure Code

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Z

Enumerated_Domain_Value_Definition: Tire Pressure Code

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: T

Enumerated_Domain_Value_Definition: Technical

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: U

Enumerated_Domain_Value_Definition: Using Aircraft

Enumerated_Domain_Value_Definition_Source: FAA

Attribute:

Attribute_Label: LightsEdge

Attribute_Definition: Runway lights edge intensity

Attribute_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: HIGH

Enumerated_Domain_Value_Definition: High

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: MED

Enumerated_Domain_Value_Definition: Medium

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: LOW

Enumerated_Domain_Value_Definition: Low

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: NSTD

Enumerated_Domain_Value_Definition: Non-standard lighting system

Enumerated_Domain_Value_Definition_Source: FAA

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: NONE

Enumerated_Domain_Value_Definition: No edge lighting system

Enumerated_Domain_Value_Definition_Source: FAA

Attribute:

Attribute_Label: LengthSour

Attribute_Definition: Runway Length Source

Attribute_Definition_Source: FAA

Attribute:

Attribute_Label: LengthSo_1

Attribute_Definition: Runway Length Source Date (Mm/Dd/Yyyy)

Attribute_Definition_Source: FAA

Attribute_Domain_Values:

Unrepresentable_Domain: Date

Attribute:

Attribute_Label: CapacitySi

Attribute_Definition: Undefined by Source

Attribute:

Attribute_Label: CapacityDu

Attribute_Definition: Undefined by Source

Attribute:

Attribute_Label: Capacity2D

Attribute_Definition: Undefined by Source

Attribute:

Attribute_Label: Capacity_1

Attribute_Definition: Undefined by Source

Attribute:

Attribute_Label: STFIPS

Attribute_Definition: The 2-character FIPS code of the State or State equivalent

Attribute_Definition_Source: OST-R/BTS

Attribute_Domain_Values:

Codeset_Domain:

Codeset_Name:

Codes for the Identification of the States, the District of Columbia and the Outlying Areas of the United States, and Associated Areas, FIPS 5-2.

Codeset_Source:

U.S. Department of Commerce, National Institute of Standards and Technology

Attribute:

Attribute_Label: DESCRIPT

Attribute_Definition: GeoPlan added field based on FULLNAME

Attribute_Definition_Source: GeoPlan

Attribute:

Attribute_Label: FGDLAQDATE

Attribute_Definition: The date GeoPlan acquired the data from the source.

Attribute_Definition_Source: GeoPlan

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

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_Number: 2012

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/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) 2012 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 Office of Geospatial Information Systems website at <http://www.bts.gov/programs/geographic_information_services/>.

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: 201506

Metadata_Reference_Information:

Metadata_Date: 20151023

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization:

Research and Innovative Technology Administration/Bureau of Transportation Statistics

Contact_Person: National Transportation Atlas Database (NTAD) 2015

Contact_Address:

Address_Type: mailing and physical address

Address: 1200 New Jersey Ave. S.E.

City: Washington

State_or_Province: D.C.

Postal_Code: 20590

Country: US

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_Extensions:

Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>

Profile_Name: ESRI Metadata Profile