West Virginia Public Use Airports

Metadata also available as - [Parseable text] - [SGML]

Metadata:
Identification_Information:
Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics, (comp.)
Publication_Date: 1998
Title: West Virginia Public Use Airports
Publication_Information:
Publication_Place: Washington, DC
Publisher: Bureau of Transportation Statistics
Larger_Work_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics
Publication_Date: 1998
Title: North American Transportation Atlas Data
Publication_Information:
Publication_Place: Washington, DC
Publisher: Bureau of Transportation Statistics
Online_Linkage: <URL:http://www.wvgis.wvu.edu>
Description:
Abstract:
This dataset is a subset (state of WV only) of the Public-Use Airport database available from the Bureau of Transportation Statistics. The Public-Use Airports database is a geographic point database of aircraft landing facilities in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the landing facility, current usage including enplanements and aircraft operations, congestion levels and usage categories. This metadata record was copied from the Bureau of Transportation Statistics and modified slightly for use with the WV dataset.
Purpose:
The database provides locational and attribute information for use in national and regional cartographic and spatial analysis applications.

Time_Period_of_Content:
Time_Period_Information:
Multiple_Dates/Times:
Single_Date/Time:
Calendar_Date: 199510
Single_Date/Time:
Calendar_Date: 199509
Single_Date/Time:
Calendar_Date: 199412
Single_Date/Time:
Calendar_Date: 199409
Currentness_Reference:
ground conditions and annual summaries

Status:
Progress: Complete
Maintenance_and_Update_Frequency: Annually

Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -83.0
East_Bounding_Coordinate: -77.5
North_Bounding_Coordinate: 41.0
South_Bounding_Coordinate: 37.0

Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: point
Theme_Keyword: transportation
Theme_Keyword: airport
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: West Virginia
Place_Keyword: US Territories

Access_Constraints: None

Use_Constraints:
None. Acknowledgment of the Bureau of Transportation Statistics North American Transportation Atlas Data would be appreciated in products derived from these data.

Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Robert Waksman
Contact_Organization: Volpe Center
Contact_Address:
Address_Type: mailing and physical address
Address: Service Assessment Division, DTS-49
Address: 55 Broadway
City: Cambridge
State_or_Province: Massachusetts
Postal_Code: 02142
Contact_Voice_Telephone: 1 617 494 2588
Contact_Facsimile_Telephone: 1 617 494 3260
Contact_Electronic_Mail_Address: waksman@volpe2.dot.gov

Data_Set_Credit:
The data set was compiled by the Volpe National Transportation Systems Center under sponsorship of the Bureau of Transportation Statistics.

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Airport attributes were obtained from four different Federal Aviation Administration (FAA) sources: the National Flight Data Center Airport Master Record (NFDC 5010) database; the National Plan of Integrated Airport Systems (NPIAS) database; the Air Carrier Activity Information System (ACAIS) database, and the Terminal Area Forecast (TAF) file. Each database has its own collection and quality control procedures, and all are maintained by separate offices in FAA. Where two or more of the databases included a similar attribute field, an assessment was made as to which value was more current and/or more accurate based on its data collection procedures. Attributes derived from the same source are grouped together.

For each ASCII attribute file a corresponding dBase format attribute file is supplied. Due to the requirement for the file name extension 'dbf', the Attribute file number is included in the file name prefix (AIRPORT.T02 contains the same attributes as AIRPORT2.DBF).

In all attribute files, a number of the attributes contain 'blank' in addition to the values enumerated in the domain.

In attribute file two (AIRPORT.T02), the National Emergency Status field (NAT_EMER_STAT) contains values not enumerated in the domain. It is a composite field that may contain multiple values separated by '/'. The non-enumerated values include: 3, X, N, 8/N, and 'blank'.

Although some records were modified, the data provider supplied no modification date(s), nor any change code in the REVISION field.

Logical_Consistency_Report:
All point records are represented by a single coordinate pair and a unique feature identifier -- the landing facility's location identifier (LOCID) assigned by the FAA. Attribute data is matched to specific point records using this LOCID.

Completeness_Report:
Landing facilities in this database consist of those identified in the NFDC 5010 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. Because the NFDC 5010 database is the most comprehensive of the four FAA databases with respect to number of landing facilities, i.e., it contains data on all of the landing facilities in the airports database, attribute data associated with the other FAA databases may be missing from certain records, particularly those of smaller general aviation or military landing facilities.

In particular, in attribute file AIRPORT.T02 (NFDC), a blank in an attribute field for a particular landing facility could signify either that an entry is not applicable or that the data is missing. Only in some cases will the user of the data be able to determine which case applies. In attribute files AIRPORT.T01 (ACAIS), AIRPORT.T03 (NPIAS), and AIRPORT.T04 (TAF), a blank in an attribute field for a particular landing facility always indicates, unless otherwise noted, that the landing facility is not included in the particular database and that, therefore, there should not be any data on that attribute for that particular landing facility.

Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
This is based on coordinate data provided in the NFDC 5010 database. These coordinate data identify the approximate location of the Airport Reference Point (ARP) as reported by the landing facility on the NFDC 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. The records were loaded into a GIS and checked visually for any unusual or obviously erroneous locations. Grossly incorrect locations were repositioned using Census TIGER/Line files or USGS digital line graphs (DLG) as reference layers. No more than five records required repositioning in this manner. Further accuracy checks using the NTAD states database and the Digital Chart of the World as reference layers revealed no further positioning errors with the 1:100,000 NTAD database, but about five airports on islands appeared to be slightly in the ocean according to the 1:1,000,000 scale Digital Chart of the World. Comparison of the NTAD layout of Puerto Rico with that of the Digital Chart of the World revealed enough of an error in the Digital Chart of the World's location of Puerto Rico to think that Saint Thomas' airport, which appeared to be in the ocean according to the Digital Chart of the World, might really be on land, given the known high accuracy of most of the airport coordinates obtained from the NFDC 5010 database. Therefore, the few airports that appeared to be slightly off of their islands according to the Digital Chart of the World were left at their original coordinates.

When compared with the NTAD STATES database, approximately 120 airports appear to lie off-shore or not within the state boundary based upon the STFIPS Code attribute

Five facilities are identified as requiring additional review to properly locate the facilities. The facilities in question are: POINTID FEATURID STFIPS DESCRIPT 2498 ADW 24 Andrews AFB 3253 DC13 11 Walter Reed Forest Glen 5077 NK29 36 Southampton Village 5170 NY93 36 Charles Poletti 6492 WA65 53 Washington National Guard - Sinclai

For example, the Charles Poletti facility is coded as existing in New York state. The coordinates place it in Pennsylvania.

The airport points should carry the same longitude and latitude values as the airway segment endpoints (carrying the LOCID as FEATURID to match the points and nodes). In most cases they do. The longitude and latitude value for Denver International Airport (DEN) does not match the value for the associated node. Airport longitude, latitude point = -104.667002, 39.858408 Airway node longitude, latitude = -104.879755, 39.774292

Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Federal Aviation Administration
Publication_Date: 199509
Title:
National Flight Data Center Airport Master Record Database
Publication_Information:
Publication_Place: Washington, DC
Publisher: Federal Aviation Administration
Type_of_Source_Media: magnetic tape
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 199509
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: NFDC 5010
Source_Contribution:
Facility location, name and other identification, physical description, ownership, FAA certification, military and customs landing rights, number of runways and helipads.
Source_Information:
Source_Citation:
Citation_Information:
Originator: Federal Aviation Administration
Publication_Date: 199510
Title:
National Plan of Integrated Airport Systems Database
Publication_Information:
Publication_Place: Washington, DC
Publisher: Federal Aviation Administration
Type_of_Source_Media: online (restricted access)
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 199510
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: NPIAS
Source_Contribution:
airport capacity (hourly operations), congestion level, aircraft operations supported, Federal interest
Source_Information:
Source_Citation:
Citation_Information:
Originator: Federal Aviation Administration
Publication_Date: 199412
Title: Air Carrier Activity Information System
Publication_Information:
Publication_Place: Cambridge, MA
Publisher: Volpe Center
Type_of_Source_Media: online
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 199412
Source_Currentness_Reference: annual summary
Source_Citation_Abbreviation: ACAIS
Source_Contribution:
enplanements by aircraft category, hub size, service level
Source_Information:
Source_Citation:
Citation_Information:
Originator: Federal Aviation Administration
Publication_Date: 199410
Title: Terminal Area Forecast File
Publication_Information:
Publication_Place: Washington, DC
Publisher: Federal Aviation Administration
Type_of_Source_Media: online
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 199410
Source_Currentness_Reference: fiscal year summary
Source_Citation_Abbreviation: TAF
Source_Contribution:
aircraft operations by type, air traffic control tower type.

Process_Step:
Process_Description:
Selected attribute fields from the four FAA databases were merged based on the common LOCID.
Source_Used_Citation_Abbreviation:
NFDC 5010, NPIAS, ACAIS, TAF
Process_Date: 199601
Process_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Robert Waksman
Contact_Organization: Volpe Center
Contact_Address:
Address_Type: mailing and physical address
Address: Service Assessment Division, DTS-49
Address: 55 Broadway
City: Cambridge
State_or_Province: Massachusetts
Postal_Code: 02142
Contact_Voice_Telephone: 1 617 494 2588
Contact_Facsimile_Telephone: 1 617 494 3260
Contact_Electronic_Mail_Address: waksman@volpe2.dot.gov
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Point
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity Point
Point_and_Vector_Object_Count: 6734
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.000278
Longitude_Resolution: 0.000278
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1927
Ellipsoid_Name: Clarke 1866
Semi-major_Axis: 6378206.4
Denominator_of_Flattening_Ratio: 294.9787
Entity_and_Attribute_Information:
Overview_Description:
Entity_and_Attribute_Overview:
Information on attributes is stored in four separate files, one for each of the FAA source databases. A data dictionary and file formats for all attributes included in this database are provided in a separate document.
Entity_and_Attribute_Detail_Citation:
Documentation for the 1995 Public Use Airports Database, prepared by Robert Waksman, Volpe Center, Cambridge, MA, January 1996.

Detailed_Description:
Entity_Type:
Entity_Type_Label: AIRPORT.PNT
Entity_Type_Definition: Point Attribute Table
Entity_Type_Definition_Source:

Field Field Field Field Beg End Field Number Name Type Width Pos Pos Description 1 RECTYPE C 1 1 1 Record Type: Always 'P' 2 VERSION C 2 2 3 File Version Number 3 REVISION C 2 4 5 Record revision number 4 MODDATE I 8 6 13 Modification date for the point entity 5 POINTID I 10 14 23 Sequential Unique Point Identification 6 FEATURID C 10 24 33 Unique Identifier for the airport - LOCID 7 LONGITUD I 10 34 43 Longitude (6 implied decimal places) 8 LATITUDE I 10 44 53 Latitude (6 implied decimal places) 9 DESCRIPT C 35 54 88 Name or identification of the airport 10 STFIPS C 2 89 90 State FIPS Code

Detailed_Description:
Entity_Type:
Entity_Type_Label:
AIRPORT.T01 AIRPORT1.DBF
Entity_Type_Definition: Point Attribute Table
Entity_Type_Definition_Source:
Data originating from the Air Carrier Activity Information System (ACAIS) data file. Reformatted into an ASCII format for incorporation into a geographic information system.

Field Field Field Beg End Field Field Number Name Width Pos Pos Type Description 1 RECTYPE 1 1 1 C Record Type: Always 'T' 2 VERSION 2 2 3 C File Version Number 3 REVISION 2 4 5 C Record revision number 4 MODDATE 8 6 13 I Modification date for the Attribute 5 FEATURID 10 14 23 C Unique Identifier for the airport - LOCID 6 POINTID 10 24 33 I Sequential Unique Point Identification 7 ACAIS_AP 1 34 34 C ACAIS Airport 8 LCAC_ENP 8 35 42 I Large Certified Air Carrier Enplanements 9 COMM_ENP 8 43 50 I Commuter Enplanements 10 AT_ENP 8 51 58 I Air Taxi Enplanements 11 FFAC_ENP 8 59 66 I Foreign Flag Air Carrier Enplanements 12 IT_ENP 8 67 74 I In-transit Enplanements 13 TOT_ENP 8 75 82 I Total Enplanements 14 ENP_SAN 1 83 83 C Sanitized Enplanement Data 15 HUB_TYPE 1 84 84 C Hub Airport Type 16 SVC_LVL 2 85 86 C Facility Service Level

Entity_Attribute_Information:

Detailed_Description:
Entity_Type:
Entity_Type_Label:
AIRPORT.T02 AIRPORT2.DBF
Entity_Type_Definition: Point Attribute Table
Entity_Type_Definition_Source:
Data originating from the National Flight Data Center (NFDC) file. Reformatted into an ASCII format for incorporation into a geographic information system.

Field Field Field Field Beg End Field Number Name Type Width Pos Pos Description 1 RECTYPE C 1 1 1 Record Type: Always 'T' 2 VERSION C 2 2 3 File Version Number 3 REVISION C 2 4 5 Record Revision Number 4 MODDATE I 8 6 13 Record Modification Date 5 FEATURID C 10 14 23 Unique Identifier for the airport - LOCID 6 POINTID I 10 24 33 Sequential Unique Point Identification 7 SITE_NUM C 11 34 44 Site Number 8 FAC_TYPE C 1 45 45 Facility Type 9 FAC_NAME C 42 46 87 Facility Name 10 CITY C 26 88 113 City location of the facility 11 COUNTY C 21 114 134 County location of the facility 12 STATE C 2 135 136 State Postal Code abbreviation for the facility 13 STFIPS C 2 137 138 State FIPS Code for the facility 14 CTY_FIPS C 3 139 141 County FIPS Code for the facility 15 FAA_REG C 3 142 144 FAA Region 16 FAC_USE C 2 145 146 Facility Use, public or private 17 OWN_TYPE C 2 147 148 Type of owner 18 OWN_NAME C 30 149 178 Name of owner 19 ELEVATION I 6 179 184 Elevation in feet 20 CBD_DIST I 3 185 187 Distance from the central business district 21 CERT_TYPE C 3 188 190 Type of certification 22 CERT_DATE C 5 191 195 Date of facility certification 23 CUST_INTL C 1 196 196 Customs International Airport 24 C_LDG_RTS C 1 197 197 Customs Landing Rights Airport 25 JOINT_USE C 1 198 198 Joint Use 26 MIL_RTS C 1 199 199 Military Landing Rights 27 NAT_EMER C 18 200 217 National Emergency Status 28 MIL_EMER C 6 218 223 Military Emergency Interest 29 B_MIL_AC I 2 224 225 Number of operational military aircraft based at the facility 30 RUN_NUM I 2 226 227 Number of runways at the facility 31 PAD_NUM I 2 228 229 Number of helicopter pads at the facility

Detailed_Description:
Entity_Type:
Entity_Type_Label:
AIRPORT.T03 AIRPORT3.DBF
Entity_Type_Definition: Point attribute table
Entity_Type_Definition_Source:
Data originating from the National Plan of Integrated Airport Systems (NPIAS) data file. Reformatted into an ASCII format for incorporation into a geographic information system

Field Field Field Field Beg End Field Number Name Type Width Pos Pos Description 1 RECTYPE C 1 1 1 Record Type: Always 'T' 2 VERSION C 2 2 3 File Version Number 3 REVISION C 2 4 5 Record Revision Number 4 MODDATE I 8 6 13 Attribute modification date 5 FEATURID C 10 14 23 Unique Identifier for the airport - LOCID 6 POINTID I 10 24 33 Sequential Unique Point Identification 7 NPIAS_AP C 1 34 34 NPIAS airport 8 VFRHRCAP I 4 35 38 Visual Flight Rule hourly capacity 9 IFRHRCAP I 4 39 42 Instrument Flight Rule hourly capacity 10 CONG_LVL C 1 43 43 Congestion Level 11 LNG_FLT C 1 44 44 Long Flight Category 12 AC_TYPE C 2 45 46 Aircraft Type 13 FED_LDG C 4 47 50 Federal Landing Interest

Entity_Attribute_Information:

Detailed_Description:
Entity_Type:
Entity_Type_Label:
AIRPORT.T04 AIRPORT4.DBF
Entity_Type_Definition: Point Attribute Table
Entity_Type_Definition_Source:
Data originating from the Terminal Area Forecast (TAF) file. Reformatted into an ASCII format for incorporation into a geographic information system.

Field Field Field Field Beg End Field Number Name Type Width Pos Pos Description 1 RECTYPE C 1 1 1 Record Type: Always 'T' 2 VERSION C 2 2 3 File Version Number 3 REVISION C 2 4 5 Record Revision Number 4 MODDATE I 8 6 13 Record modification date 5 FEATURID C 10 14 23 Unique Identifier for the airport - LOCID 6 POINTID I 10 24 33 Sequential Unique Point Identification 7 TAF_AP C 1 34 34 Terminal Area Forecast (TAF) Airport 8 AT_TYPE C 1 35 35 Air Tower Type 9 AC_IO I 8 36 43 Air Carrier Itinerant Operations 10 AT_IO I 8 44 51 Air Taxi Itinerant Operations 11 GA_IO I 8 52 59 General Aviation Itinerant Operations 12 MIL_IO I 8 60 67 Military Itinerant Operations 13 TOT_IO I 8 68 75 Total Itinerant Operations 14 GA_LOC_O I 8 76 83 Total local general aviation operations 15 MIL_LOC_O I 8 84 91 Total local military operations 16 TOT_LOC_O I 8 92 99 Total local operations 17 TOT_O I 8 100 107 Total operations

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: BTS Product Distribution Center
Contact_Address:
Address_Type: mailing and physical address
Address: 400 Seventh Street, SW
City: Washington
State_or_Province: District of Columbia
Postal_Code: 20590
Contact_Voice_Telephone: 1 202 366 DATA
Contact_Facsimile_Telephone: 1 202 366 3640
Contact_Electronic_Mail_Address: orders@bts.gov

Resource_Description:
North American Transportation Atlas Data 1998

Distribution_Liability: None

Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name:
BTS (Bureau of Transportation Statistics standard format for spatial data)
Format_Information_Content:
The BTS standard format for spatial data is an interim format for distributing geospatial digital data bases pending final approval for an SDTS Transportation Network Profile (TNP). The BTS standard format consists of a linked set of ASCII fixed record length files. File formats and data dictionary for the BTS standard format are described in the documents, "format.txt" and "datadict.txt". Copies of these documents are distributed on each North American Transportation Atlas Data CD-ROM in the "docs" directory.
File_Decompression_Technique:
No compression applied However, if using digital transfer online option, note access instructions.
Transfer_Size: 7.2 megabytes

Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: www.bts.gov/gis/ntatlas/usa.html

Access_Instructions:
Anyone with access to the Internet World Wide Web may connect to the BTS server. To access a specific database, go to the address listed above in the Network Resource Name. The visitor can create a "package" of the data set for download. The "package" can be in one of the following formats: .zip - an MS-DOS zip archive; .tgz - a gzip-ed unix tar archive; and .tar - a unix tar archive. Once the package is prepared, the visitor can download the package to their host computer.
Online_Computer_and_Operating_System:
Sun Ultra running Solaris 2.5.1 operating system.

Offline_Option:
Offline_Media: CD-ROM
Recording_Capacity:
Recording_Density: 650
Recording_Density_Units: megabytes
Recording_Format: ISO 9660
Compatibility_Information:
The NORTAD includes both MS-DOS/Windows and UNIX compatible format files on one CD-ROM

Fees: none
Ordering_Instructions:
Call, mail, fax, or e-mail BTS to request the North American Transportation Atlas Data 1998 CD-ROM. This and other BTS products may be ordered from the BTS Internet site (www.bts.gov/btsprod). Or download WV data at wvgis.wvu.edu.

Metadata_Reference_Information:
Metadata_Date: 199712
Metadata_Review_Date: 199802
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Bureau of Transportation Statistics
Contact_Address:
Address_Type: mailing address
Address: 400 Seventh Street, SW
City: Washington
State_or_Province: DC
Postal_Code: 20590
Contact_Voice_Telephone: 1 202 366 3282
Contact_Facsimile_Telephone: 1 202 366 3640
Contact_Electronic_Mail_Address: nortad@bts.gov
Metadata_Standard_Name:
FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Generated by mp version 2.7.33 on Mon Jan 26 08:52:26 2004