8/16/2000
D. Guenther, REO. Structure_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.
Fields in bold
are required for the Framework Clearinghouse.
Data Elements:
1. File Header Information:
This information pertains to all information being submitted. This describes a file transfer event,
describing all data submitted.
Note: Location coordinates will refer to the center point of the structure. Fields in bold are required for the Framework Clearinghouse.
Framework
Structure ID – To uniquely identify each structure. Source: Generated by Clearinghouse.
Field Name: STRUCTURE_ID. Type:
Integer. Size: 15
Agency
Structure ID – Unique ID from data source agency. Used to link framework data to agency data.
Field Name: LOCAL_STRUCTURE_ID. Type:
Character. Size: 35
Latitude
- The Latitude for the structure.
Field Name: X. Type: Integer. Size: 7.
Longitude
- The Longitude for the structure.
Field Name: Y. Type: Integer. Size: 7.
Elevation
- The elevation above mean sea level for the structure.
Field Name: Elevation. Type:
Integer. Size: 4.
Source
Information- General information as to the source of the data.
Field Name: SOURCE_INFORMATION. Type: Alpha.
Size: 240 characters.
Route Framework ID- To designate which route a structure is on. Route_Framework_ID is a system generated unique permanent identifier. As records are submitted to the Framework Clearinghouse a lookup based on supplied Local_Route_ID and Source will provide the unique ID. This ID may then be used by participants in sharing data across ownerships.
Field Name: ROUTE_FRAMEWORK_ID. Type: Integer. Size: 7 characters.
Local Route ID - The unique ID which the contributing agency has assigned to the
route.
Field Name: LOCAL_ROUTE_ID. Type: Alpha. Size: 50 characters.
Accumulated
Route Measurement - The milepost where the structure is located on the
route. Route mile accumulated from the
beginning of a route in the direction of a roadway
Field Name: ARM. Type: Real. Size:
999.99 (Where does this start?).
Structure
Class - Designation for the general type of structure (Valid: culvert,
bridge, ford or road blockage).
Field Name: STRUCTURE_CLASS. Type:
Alpha. Size: 25.
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 characters.
Owner 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 characters.
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.
Note: States and federal agencies do not seem to be tracking anchor points, but looking at reasons for relevance and importance. Are they necessary for sharing transportation data, or linking transportation framework to hydrography.
Culverts: In addition to the above attributes, culvert core data will include the following. (Note: when fish and hydro data needs are known they will be included):
Culvert
Type- The shape and material for the culvert. (Eg. Ellipse, concrete).
Field Name: TYPE. Type: Alpha. Size: 25.
Culvert
Size - The diameter or area of the culvert.
Field Name: SIZE. Type: integer. Size: 2.
Culvert
Length - The length of the structure.
Field Name: LENGTH. Type: integer. Size: 3.
Bridges: In addition to the above attributes, bridge core data will also include the following:
NBI
- The code assigned to all bridges and dams under the National Bridge
Inventory.
Field Name: NBI. Type:
Integer. Size: 5
Fish passage and hydrography attributes: In addition to the location information above, these structures will include fisheries and hydrography information as determined by the agency specialists. This section is a place holder for this information to be attached to the transportation framework information set. This information will then be linked to the hydrography framework as well.
Example:
Fish_Passage – A Y/N field describing whether fish can pass this barrier.
Fish_Species – The species related to fish passage. Code value based on scientific name.