DRAFT
9/19/2000
D. Guenther, REO. Core_Data
The following lists the agreed upon set of core data necessary for the
Transportation Framework project. All
data is linked to spatial information, which defines a route. A route is a user defined section of
road. This document will focus on
describing the core data attributes only.
For Framework spatial requirements please refer to the Transportation
Spatial Requirements document. For Framework data standards for transportation
structures, refer to the Framework Structures Core Data document.
These elements were developed consensus from the partners. Core data is data common to all
participating agency datasets. Core
data may not include all common data, but relative to broad scale needs.
Data Elements:
1. File Header Information: Required values are in bold type.
This information pertains to all information being submitted. It describes a file transfer event,
describing all data submitted.
Origination Date - Date the file or information is
submitted.
Field Name: ORIGINATION_DATE Type: Date.
Validation Date - Date the data is current.
Field Name: VALIDATION_DATE Type: Date.
Projection - The name of the projection which the line work was developed
in.
Field Name: PROJECTION. Type: Alpha. Size: 50.
Coordinate System - The coordinate system the line work was
developed in.
Field Name: COORDINATE_SYSTEM Type: Alpha. Size:
50.
Datum
- The geographic Datum the line work was developed in.
Field Name: DATUM. Type: Alpha. Size: 50.
2. Feature Attributes:
This information pertains to a specific data
element or record being submitted. Each
record will have a different set of data.
Road Location Information
Framework Unique Identifier - A system generated
unique permanent identifier. As records
are submitted to the Framework Clearinghouse each record will be assigned a
unique ID. This ID may then be used and
tracked by participants in sharing data across ownerships.
Field Name: FRAMEWORK_ID. Type: Integer. Size: 7.
Agency Unique Identifier - The unique ID which the contributing agency
has assigned to the feature.
Field Name: LOCAL_ID. Type: Alpha. Size: 50.
State
- Code for State where the road is located.
FIPS codes will be used.
Field Name: STATE. Type: Alpha. Size: 2.
County - County FIPS code for feature location. FIPS codes will be used.
Field Name: COUNTY. Type: Alpha. Size: 3.
Metadata Information
Feature Source Type - The compilation map or image source used when adding or updating transportation data.
These codes can
be found in the associated lookup table listed in Section 4 - Appendix.
Field Name: FEATURE_SOURCE_TYPE. Type: Alpha. Size: 25.
Feature
Source Date -
The compilation map or image source date used for the addition or update of
transportation data.
Example: 19990515 (CCYYMMDD = May 15, 1999)
Field Name: FEATURE_SOURCE_DATE. Type: Date. Size: Date.
Feature
Source Scale Number - Describes the scale denominator of the map or image
source for the transportation data additions or updates in the database. Exact scale can be input. The density of transportation features
displayed will vary by the base map scale.
Example: 24000
Field Name: FEATURE_SOURCE_SCALE_NUMBER. Type: Alpha. Size: 6.
Feature Accuracy Type - Describes the positional accuracy of the transportation data being added or updated in the database. Describes the correctness of the measurement. Use actual value eg. .001; 3; 100. All units are entered in meters.
Field Name: FEATURE_ACCURACY_TYPE. Type: Alpha. Size: 4.
Road Name - Road name(s) which have been assigned. Note: either NAME or Road_Number is required. If unknown then OWNER must be filled in as unknown.
Field Name: NAME. Type: Alpha. Size: 35.
Alternate Road Name - List of all other known names.
Field Name: ALTERNATE _NAME Type: Alpha. Size: 35.
Direction Prefix - Directional indication code (i.e NE).
Field Name: PREFIX. Type: Alpha. Size: 2.
Direction Suffix - Directional indication code (i.e NE).
Field Name: SUFFIX. Type: Alpha. Size: 2.
Road Number - Road numbers(s) which have been assigned. Note: either NAME or Road_NUMBER is required. If unknown then OWNER must be filled in as unknown.
Field Name: ROAD_NUMBER. Type: Alpha. Size: 15.
Alternate Road Number - List of all other known road numbers.
Field Name: ALTERNATE_ROAD_NUMBER. Type: Alpha. Size: 15.
Measure Method - Date and comment type description of how the FROM and TO measures were generated (ex. Odometer).
Field Name: MEASURE_METHOD. Type: Alpha. Size: 50.
From Milepost - The >FROM= milepost where the road segment value starts.
Field Name: FROM_MP. Type: Real. Size: 999.99
To Milepost - The >TO= milepost where the road segment value ends.
Field Name: TO_MP. Type: Real. Size: 999.99
From_ARM - The >FROM= milepost where the field measured Accumulated Route Mile (ARM) value starts.
Field Name: FROM_ARM. Type: Real. Size: 999.99
To ARM - The >TO= milepost where the field measured Accumulated Route Mile (ARM) value ends. Field Name: TO_ARM Field Name: Type: Real. Size: 999.99
Inventory Direction - The direction of the inventory (increasing or decreasing) for dual lane roads.
Field Name: DIRECTION. Type: Alpha. Size: 10.
Right Side Address Low - Lowest street address on the right side in direction of increasing addresses.
Field Name: RT_FROM_ADD. Type: Alpha. Size: 6.
Left Side Address Low - Lowest street address on the left side in direction of increasing addresses.
Field Name: LF_FROM_ADD. Type: Alpha. Size: 6.
Right Address High - Highest street address on the right side in direction of increasing addresses.
Field Name: RT_TO_ADD. Type: Alpha. Size: 6.
Left Address High - Highest street address on the left side in direction of increasing addresses.
Field Name: LF_TO_ADD. Type: Alpha. Size: 6.
Left Zip - Postal zip code on left side of feature in direction of increasing addresses.
Field Name: LZIP_TYPE. Type: Alpha. Size: 10.
Right Zip - Postal zip code on Right side of feature in direction of increasing addresses.
Field Name: RZIP_TYPE. Type: Alpha. Size: 10.
Owner Level - Jurisdictional level of owner of facility (see code list) (i.e. Federal).
Field Name: OWNED. Type: Alpha. Size: 1
Owner Name - Jurisdictional classification or name of facility owner (see code list) (i.e. Forest Service).
Field Name: OWNER. Type: Alpha. Size: 35.
Manager Level - Jurisdictional level of manager of facility (see code list) (i.e. Federal).
Field Name: MANAGED. Type: Alpha. Size: 1
Manager Name - Jurisdictional classification or name of facility manager (see code list) (i.e. Forest Service). Field Name: MANAGER. Type: Alpha. Size: 35.
Functional Classification - Functional classification (i.e. Interstate). This includes railroad and utility pipelines.
Field Name: FUNCCLS. Type: Alpha. Size: 35.
Functional Type - Functional type (i.e. U=Urban).
Field Name: FUNCTYP. Type: Alpha. Size: 1.
SOURCE - Jurisdictional level at which data originates (see code list) (i.e. Federal).
Field Name: SOURCE. Type: Alpha. Size: 1
Source Agency - Jurisdictional classification or name of agency that submits the data (see code list) (i.e. Forest Service).
Field Name: SOURCE_AG. Type: Alpha. Size: 35.
Road Status - Code for the management of the road. (Ex. R=Retired, O=Operating, P=Proposed).
Field Name: STATUS. Type: Alpha. Size: 1
Surface Type - The code showing surface type of the feature. (Ex. H=Hard Surface, G=Gravel, D=Dirt).
Field Name: SURFACE_TYPE. Type: Alpha. Size: 1.