|
RUNWAY / AIRFIELD
DATA |
|
|
LAYER: RUNWAY_LINE or RUNWAY_POLY |
|
|
DIRECTORY: AEDATA/facilities/runway_line.shp or runway_popy.shp |
|
|
DIRECTORY: Volusia.SDE/facilities/runway_line or runway_poly |
|
|
TYPE: LINE & POLYGON |
|
|
Shapefile is downloadable from http://www.volusia.org/gis/download.htm. |
||
|
Abstract: County airfield and
runway data. |
||
|
Update Frequency:
Annual check against FAA & NTAD databases. |
||
|
Spatial Domain |
||
|
West Coordinate: |
-81.359054 |
|
|
East Coordinate: |
-80.928748 |
|
|
North Coordinate: |
29.246552 |
|
|
South Coordinate: |
28.846581 |
|
|
Spatial Data Information |
||
|
Data Type: |
digital map |
|
|
Data Format: |
SDE Feature Class |
|
|
Data Projection: |
NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet |
|
|
FIELDS RUNWAY_LINE |
|
|
NAME |
DESCRIPTION |
|
LOCID |
LOCATION
ID |
|
FULLNAME |
AIRFIELD
NAME |
|
UNIQUE_ID |
RUNWAY
ID INFORMATION (SITE NUMBER + RWY_ID) |
|
FIPS |
STATE
FIPS CODE (12) |
|
SITE_NO |
SITE
NUMBER |
|
ST_POSTAL |
FL |
|
RWY_ID |
RUNWAY
ID INFORMATION 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 |
RUNWAY
LENGTH (IN FEET) |
|
RWY_WITH |
RUNWAY
WIDTH (IN FEET) |
|
RWY_SFC_TY |
RUNWAY
SURFACE MATERIAL 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_LIGHTS |
RUNWAY
LIGHTS EDGE INTENSITY (HIGH, MEDIUM, LOW, NONE) |
|
FIELDS RUNWAY_POLY |
|
|
NAME |
DESCRIPTION |
|
NAME |
AIRFIELD
NAME |
Access_Constraints: None
Use_Constraints:
None.
This agency acknowledges the Federal Aviation Administration (FAA) and the
Research and Innovative
Technology
Administration's Bureau of Transportation Statistics (RITA/BTS) National Transportation
Atlas
Databases
(NTAD) 2005 which was a significant source for these layers of data.