Tualatin River Watershed Data Dictionary
Metadata for CULV_HWY
Table of Contents
Identification_Information
Abstract
Purpose
Supplemental Information
Data_Quality_Information
Spatial_Data_Organization_Information
Entity_and_Attribute_Information
Detailed Description
Overview
Distribution_Information
Metadata_Reference_Section
Identification_Information
Citation_Information
Originator:
Publication_Date:
Title:
Description
Abstract
Highway culverts
Purpose
To meet the expanding needs of our users, the Transportation Inventory
and Mapping unit has computerized the milepoint log to create the
Automated Milepoint Log (AML).
Since its creation in 1986, the system has expanded to include
information from other ODOT units. To reflect the broad range of
information contained in the new system, the name of the project was
changed from AML to Integrated Transportation Information System (ITIS).
Automated production allows us to provide more timely milepoint logs
with detailed information and the flexibility to add data as new needs are
identified.
The following pages cover the various fields and their meanings on the
enclosed report. If further assistance is required, please contact us
at 503/986-4250.
Supplemental_Information
Procedures_Used
Revisions
Reviews_Applied_to_Data
Related_Spatial_and_Tabular_Data_Sets
References_Cited
TRANSPORTATION DEVELOPMENT BRANCH
Transportation Inventory & Mapping
Mill Creek Office Park
555 13th St. N.E.
Salem, Oregon 97310
Notes
Time_Period_of_Content
Currentness_Reference
Status
Progress: UNKNOWN
Maintenance_and_Update_Frequency
Spatial_Domain
Bounding_Coordinates
West_Bounding_Coordinate: -123.38087239
East_Bounding_Coordinate: -122.65720221
North_Bounding_Coordinate: 45.73548889
South_Bounding_Coordinate: 45.31180306
Keywords
Theme
Theme_Keyword_Thesaurus: None
Theme_Keyword: state highway culverts, oregon, roads
Place
Place_Keyword_Thesaurus: None
Place_Keyword: Tualatin River Watershed
Stratum
Stratum_Keyword_Thesaurus: None
Stratum_Keyword:
Temporal
Temporal_Keyword_Thesaurus: None
Temporal_Keyword:
Access_Constraints
Use_Constraints
Data_Set_Credit
Security_Information
Security_Classification_System: None
Security_Classification: UNCLASSIFIED
Security_Handling_Description: None
Native_Data_Set_Environment: Windows_NT Windows_NT, ARC/INFO version 7.1.1
Cross_Reference: None
Data_Quality_Information
Attribute_Accuracy
Attribute_Accuracy_Report: See Entity_Attribute_Information
Quantitative_Attribute_Accuracy_Assessment
Attribute_Accuracy_Value: See Explanation
Attribute_Accuracy_Explanation:
Attribute accuracy is described, where present, with each
attribute defined in the Entity and Attribute Section.
Logical_Consistency_Report: Point features present.
Completeness_Report
Positional_Accuracy
Horizontal_Positional_Accuracy
Horizontal_Positional_Accuracy_Report:
Vertical_Positional_Accuracy
Vertical_Positional_Accuracy_Report:
Lineage: See Supplemental_Information for overview.
Process_Steps
Process_Step
Process_Description: JON PROJECT COVER CULV_HWY /A1/TUALATIN/DATA/INFRA/CULV_HWY
Source_Used_Citation_Abbreviation:None
Process_Date: 19980206
Process_Time: 1358
Source_Produced_Citation_Abbreviation: None
Process_Step
Process_Description: JON BUILD /A1/TUALATIN/DATA/INFRA/CULV_HWY_83 POINT
Source_Used_Citation_Abbreviation:None
Process_Date: 19980206
Process_Time: 1358
Source_Produced_Citation_Abbreviation: None
Process_Step
Process_Description: JON RENAME CULV_HWY_83 CULV_HWY
Source_Used_Citation_Abbreviation:None
Process_Date: 19980206
Process_Time: 1358
Source_Produced_Citation_Abbreviation: None
Process_Step
Process_Description: MIKE COPY /A1/TUALATIN/DATA/INFRA/CULV_HWY CULV_HWY
Source_Used_Citation_Abbreviation:None
Process_Date: 19980824
Process_Time: 1040
Source_Produced_Citation_Abbreviation: None
Process_Step
Process_Description: KEITH DOCUMENT CULV_HWY UPDATE KEITH
Source_Used_Citation_Abbreviation:None
Process_Date: 19980922
Process_Time: 1039
Source_Produced_Citation_Abbreviation: None
Cloud_Cover
Spatial_Data_Organization_Information
Direct_Spatial_Reference_Method: Point
Point_and_Vector_Object_Information
SDTS_Terms_Description
SDTS_Point_and_Vector_Object_Type: Point
Point_and_Vector_Object_Count: 327
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 0
SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains'
Point_and_Vector_Object_Count: 0
Spatial_Reference_Information
Horizontal_Coordinate_System_Definition
Planar
Grid_Coordinate_System
Grid_Coordinate_System_Name: State_Plane_Coordinate_System
Zone_Number: 5076
Planar_Distance_Units: FEET
Geodetic Model
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: GRS1980
Entity_and_Attribute_Information
Detailed_Description
Entity_Type
Entity_Type_Label:
Entity_Type_Definition:
Entity_Type_Definition_Source:
Attribute:
Attribute_Label:
Attribute_Definition:
Attribute_Definition_Source:
Attribute_Domain_Values
Enumerated_Domain
Enumerated_Domain_Value:
Enumerated_Domain_Value_Definition
Enumerated_Domain_Value_Definition_Source:
Overview_Description
Entity_and_Attribute_Overview
THE FOLLOWING INFORMATION APPEARS IN THE FILE:
RD_ID (Official OSHD Highway number )
________________________________________________________
MP_NO MILE (MILEPOINT)
A number that represents the distance in miles from the original
beginning of the highway. This distance is measured along the
contours of the traveled roadway. If this number is derived from
plans, photos, drawings, or other non-field documentation, then it
represents level measurement and will remain so until field verification.
__________________________________________________________
MP_DESC_SEQ_CD sequencing number used to sort several attributes
at the same MP_NO.
___________________________________________________________
RDWY_ID (printed vertically on the report)
This is a one digit code used in conjunction with the highway
number and milepoint to identify the alignment on which the milepoint exists.
Following is a list of valid roadbed codes.
1 Milepoint exists on the primary roadbed. This will be
on the add-mileage alignment of the highway.
2 Milepoint exists on the non-add alignment.
3 Milepoint exists on Split roadway (on the add-mileage
alignment.)
4 Milepoint exists on Split roadway (on the non-
add mileage alignment.)
5 This milepoint indicates the mileage is on a
roadway not yet built and considered located. This
mileage is neither add nor non-add.
MLGE_TYPE
Mileage types are used to make milepoints unique in areas where there
are multiple occurrences of mileposting on a single highway.
Following is a list of valid prefixes:
Y Spur mileage. A highway spur is a short off-shoot of
an established highway.
Z Overlapping mileage. When a road is lengthened in
the middle due to realignment, Z-mileage is created.
T Temporary mileage. Mileage on a temporary traveled
route, usually due to a detour or highway under
construction.
________________________________________________________________
OVLAP_MLGE_CD
Milepoint overlapping code is used only in conjunction with mlge_type of Z.
It indicates a unique series of overlapping Z mileage. The first occurrence
of Z mileage will have a ovlap_code of 1, the second occurrence will have a
ovlap_code of 2, etc.
RDWY_CD_1 through RDWY_CD_5
These are codes made up of 5 individual fields with independent meanings
used to show attributes and jurisdiction alone the roadway. They indicate
the direction and jurisdiction of intersecting roads, culverts, structures,
demographic boundaries and much more. There is a positional centerline
which represents the center of that roadbed. For valid roadway codes are:
The roadway codes serve as visual guides of intersections, connections,
boundaries and structures along a road. The roadway field consists of five
bytes or positions, starting with position 1 on the left. Reading up the page,
as milepoints increase, positions 1 and 2 refer to the left hand side of the roa
Positions 4 and 5 refer to the right hand side of the road. Position 3 is not
specific to one side of the road. All five positions work together to give a
complete picture of the roadway at a given milepoint.
There are two sets of roadway codes which have a specific purpose and do
not comply with the values below, they are BB|BB and EE|EE which represent
the beginning and ending of a highway respectively.
Positions 1 and 5
Codes in positions 1 and 5 define "jurisdiction" of an intersecting road or a
boundary. Some jurisdiction codes, such as # for railroad, or T for trail,
simply identify a type of intersecting attribute, rather than jurisdiction.
ROAD WAY CODES CONT:
JURISDICTION CODES (RDWY_CD_1 and/ or RDWY_CD_5 )
CODE MEANING
A State Land Board jurisdiction
B BLM road or BLM park
C City street or city limit
D Frontage road on right of way
E Connections on right of way
F National Forest Service road or national forest boundary
G Wildlife refuge boundary
H City park boundary
I National Indian Service rd. or Indian Res. boundary
J Public road or public jurisdiction
K County road or county park
L Locale or community
M National park boundary
N U.S. miscellaneous road
O Overcrossing summit, gasoline, state line, etc.
P Private road
R State forest road or State forest boundary
S State road or State park boundary
T Foot or bike trail
U Urban or urbanized boundary
V Tunnel (o-xing, u-xing, or jct. only)
W State wayside boundary
X Planned or future attribute
Z Unknown jurisdiction of named attribute
# Railroad
Positions 2 and 4
Codes in positions 2 and 4 supply further information about the jurisdiction
field, such as whether the attribute is being intersected at grade, or is passin
under or over the road. Also, whether the road is entering or leaving a
jurisdictional boundary.
ROAD WAY CODES CONT:
INFORMATIONAL CODES IN (RDWY_CD_2 and/ or RDWY_CD_4 )
CODE MEANING
E Entering (boundary, common alignment, tunnel, etc.)
G Gate across road
L Leaving (boundary, common alignment, tunnel, etc.)
O The road is crossing over something
U The road is crossing under something
Z An undefined attribute on the right of way
= The road is intersecting something at grade
/ The roadway is ahead or behind the milepoint
@ Boundary touches right of way or centerline
C Boundary continues on right-of-way
A Boundary angles toward centerline
ROAD WAY CODES CONT:
Position 3
The position 3 codes are not road side specific. They indicate whether the
road is on the ground or on a structure, whether it is crossing a waterway,
or passing through a tunnel, etc.
CENTERLINE CODES IN RDWY_CD_3
CODE MEANING
E Milepoint equation at this milepoint
S The road is starting to travel on a street named in description.
T The road is in a tunnel
W The road is crossing a waterway
1 Begin/end common alignment chargeable mileage
2 Begin/end common alignment non-chargeable mileage
3 Location of a three color traffic control signal
| Road is on the ground
+ Road is on a structure
A The indicated roadway is ahead
B The indicated roadway is behind the milepoint
C Named boundary is on, or touches centerline
P In a tunnel, named boundary runs down centerline
G On a structure, named boundary runs down centerline
Another set of codes is used to define the type of structure a road is passing
over. The structure symbol is located only at the middle milepoint of the
structure, except for structures 500 or more. These structures have a symbol
at the beginning, middle and end.
A W may be exchanged for the + in position 3 to indicate the center of the
waterway crossed.
STRUCTURE CODES (applies to entire 5 cha field)
CODE MEANING
-)+(- Culvert. Less than 72". Dimensions always in inches.
-|+|- Minor structure. 6 to 20, dimensions always in feet.
@|+|@ Cattlepass, pedestrian tunnel, or equip. pass. Less than 20.
=|+|= Major structure. Greater than 20 and less than 500 in length.
||+|| Begin/end structure 500 or longer.
>|+|< Center of structure 500 or longer.
ROAD WAY CODES CONT: STRUCTURE CODES
The length of a structure greater than 20 appears to the right of the symbol,
and is followed by the bridge number. Rather than bridge numbers, culverts
and minor structures have abbreviations representing the types of drainage
structures beneath the road. The abbreviations below appear to the right of
the minor structure and culvert symbols.
MP_DESC
This field describes the attribute found at the highway milepoint. Also include
in description fields are project numbers, comments about the surface, names
of intersecting roads, bridge numbers and lengths, and size of drainage
structures.
(structure codes in DESCRIPTION)
ALBC Aluminum Box Culvert SIPH Siphon
ARCH Arch Pipe SLAB Slab
BOX Box SPAP Structural Plate Arch
CIP Corrugated Iron Pipe CJP Corrugated Joint Pipe
STIB Steel I Beam CMP Corrugated Metal Pipe
STPI Steel Pipe on Concrete C.P. Concrete Pipe Casing
CULV Culvert STPP Structural Plate Pipe
FLUM Flume TBC Timber Box Culvert
FRTR Frame Trestle TBR Timber
MLPP Multiplate Pipe TBRT Timber Treated
PIPE Pipe TBRU Timber Untreated
RC Reinforced Concrete TDT Timber Drainage Tunnel
RCCL Reinforced Conc. Culv. RCBC Reinforced Conc. Box Culv.
RCDK Reinforced Conc. Deck RCDG Reinf. Conc. Deck Girder
RCMB Rein. Conc. Multi Beam RCDP Reinf. Conc. Deck Panel
CCL Conc. Culvert RCRF Reinf. Conc. Rigid Frame
STRUCTURE CODES (cont.)
OVERCROSSINGS (OVER 500)
307.70 ||+|| END STRUCTURE
307.59 >|W|< 1177 01377B OREGON SLOUGH
307.46 ||+|| BEG. STRUCTURE
Structures greater than 500 show a beginning, middle and end. The center
milepoint caries the structure number and length. The beginning and ending
milepoints carry the structure name.
(structure codes in DESCRIPTION) CONT:
MAJOR STRUCTURES (20-499)
182.60 =|W|= 0439 00624A Umatilla River
Above is an example of a major structure where the bridge is crossing a
waterway. The milepoint of the structure is also the center of the waterway,
which is why the W appears in position 3 at the same milepoint.
Below is another major structure. This bridge is crossing over railroad tracks
instead of water. Note the use of a duplicate milepoint (suffix) to show the
type of attribute being crossed.
183.70 #O+O# U.P.R.R.
183.70 =|+|= 0187 01628
197.62 #O|O# U.P.R.R.
197.62 VO|OV U.P.R.R.
The dimension given for these types of structures (overcrossings and major)
is dimension X (length)
MINOR STRUCTURES (6-19)
-|W|- RCBC 06X06 BEAR CREEK
@|+|@ CMP 06X06 CATTLEPASS
CULVERTS (36"-71")
-)W(- CMP 36"X036" MILL CREEK
-)W(- CMP 36"X048" IRRIGATION
Entity_and_Attribute_Detail_Citation: Not Available
Distribution_Information
Metadata_Reference_Section
Metadata_Date: 19980922
Metadata_Contact:
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: 19940608
Metadata_Time_Convention: Local Time
Metadata_Security_Information:
Metadata_Security_Classification_System: None
Metadata_Security_Classification: UNCLASSIFIED
Metadata_Security_Handling_Description: None
Last modified: 98-09-22.10:41:53.Tue
Licensing A project of Ecotrust