20180612 15072100 1.0 North American Profile of ISO19115 2003 FALSE CrashMultiYear 002 7455695.747703 7628654.671260 610510.256562 783188.659121 1 Projected GCS_North_American_1983_HARN Linear Unit: Foot (0.304800) NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.6'><WKT>PROJCS["NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",8202099.737532808],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-120.5],PARAMETER["Standard_Parallel_1",44.33333333333334],PARAMETER["Standard_Parallel_2",46.0],PARAMETER["Latitude_Of_Origin",43.66666666666666],UNIT["Foot",0.3048],AUTHORITY["EPSG",2913]]</WKT><XOrigin>-111333600</XOrigin><YOrigin>-98152500</YOrigin><XYScale>3048</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2913</WKID><LatestWKID>2913</LatestWKID></ProjectedCoordinateSystem> 20190619 15025400 20190619 15025400 150000000 5000 ISO19139 Esri ArcGIS 10.6.1.9273 CrashMultiYear 002 1 -123.426020 -122.729716 45.792966 45.304490 Oregon Department of Transportation's (ODOT) crash database from the year 2009-2016 (most recent year relased by ODOT). crashes vehicle Oregon department transportation ODOT Washington County <DIV STYLE="text-align:Left;"><DIV><DIV>The metadata for this data was largely pulled (almost exclusively) from the ODOT 2017 Code Manual under their supporting files found here:https://www.oregon.gov/ODOT/Data/documents/CDS_Code_Manual.pdfThere are also some illustrations in there that might be useful.Please see the indivudual fields for an explanation for the values.This may not be the best place for this but...these are some query statements that can be used as create query layers in arcmap that pull out common types of crash data:Crashes -- Fatal/Severe (5 years):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfrom distribution.transpor.CRASHMULTIYEAR WHERE ((DATEPART(YEAR, CRASH_DT) in (SELECT max(DATEPART(year, CRASH_DT)) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-1) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-2) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-3) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-4) FROM distribution.TRANSPOR.CrashMultiYear))) AND (TOT_INJ_LVL_B_CNT > 0 OR TOT_INJ_LVL_C_CNT > 0) AND (TOT_FATAL_CNT > 0 OR TOT_INJ_LVL_A_CNT > 0)Crashes -- Minor Injury (5 years):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfrom distribution.transpor.CRASHMULTIYEAR WHERE ((DATEPART(YEAR, CRASH_DT) in (SELECT max(DATEPART(year, CRASH_DT)) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-1) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-2) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-3) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-4) FROM distribution.TRANSPOR.CrashMultiYear))) AND (TOT_INJ_LVL_B_CNT > 0 OR TOT_INJ_LVL_C_CNT > 0) and (TOT_FATAL_CNT = 0 and TOT_INJ_LVL_A_CNT = 0)Crashes -- Property Damage Only (5 years):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfrom distribution.transpor.CRASHMULTIYEAR WHERE ((DATEPART(YEAR, CRASH_DT) in (SELECT max(DATEPART(year, CRASH_DT)) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-1) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-2) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-3) FROM distribution.TRANSPOR.CrashMultiYear)) OR(DATEPART(YEAR, CRASH_DT) in (SELECT (max(DATEPART(year, CRASH_DT))-4) FROM distribution.TRANSPOR.CrashMultiYear))) AND (CRASH_SVRTY_LONG_DESC = 'Property Damage Only')Crashes 2016 (most recent):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfrom distribution.transpor.CRASHMULTIYEARWHERE DATEPART(YEAR, CRASH_DT) in (SELECT max(DATEPART(year, CRASH_DT)) FROM distribution.TRANSPOR.CrashMultiYear)Crashes -- 2015 (most recent -1):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfromdistribution.transpor.CRASHMULTIYEARwheredatepart(YEAR,CRASH_DT)in(SELECT (max(DATEPART(year,CRASH_DT))-1)FROM distribution.TRANSPOR.CrashMultiYear)Crashes -- 2014 (most recent -2):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfromdistribution.transpor.CRASHMULTIYEARwheredatepart(YEAR,CRASH_DT)in(SELECT (max(DATEPART(year,CRASH_DT))-2)FROM distribution.TRANSPOR.CrashMultiYear)Crashes -- 2013 (most recent -3):selectOBJECTID,CRASH_ID,CRASH_DT,CRASH_HR_NO,CRASH_SVRTY_LONG_DESC,TOT_FATAL_CNT,TOT_INJ_LVL_A_CNT,TOT_INJ_LVL_B_CNT,TOT_INJ_LVL_C_CNT,COLLIS_TYP_LONG_DESC,CRASH_TYP_LONG_DESC,CRASH_CAUSE_1_LONG_DESC,CRASH_CAUSE_2_LONG_DESC,CRASH_CAUSE_3_LONG_DESC,TRAF_CNTL_DEVICE_LONG_DESC,LGT_COND_LONG_DESC,RD_SURF_MED_DESC,WTHR_COND_LONG_DESC,TOT_PDO_CNT,EFFECTV_DT,SHAPEfromdistribution.transpor.CRASHMULTIYEARwheredatepart(YEAR,CRASH_DT)in(SELECT (max(DATEPART(year,CRASH_DT))-3)FROM distribution.TRANSPOR.CrashMultiYear)Also As part of the SPIS analysis, one must normalize the data into fatal, injury a, injury b, injury c, and pdo crashes counting the highest level in the crash as '1' for that incident this is the query to produce that:selectOBJECTID,CRASH_ID,SER_NO,CRASH_DT,IIF(TOT_FATAL_CNT >=1,1,0)asFATAL,IIF((TOT_INJ_LVL_A_CNT >=1 AND TOT_FATAL_CNT =0),1,0)as INJ_LVL_A,IIF((TOT_INJ_LVL_B_CNT >=1 ANDTOT_INJ_LVL_A_CNT =0 AND TOT_FATAL_CNT =0),1,0)as INJ_LVL_B,IIF((TOT_INJ_LVL_C_CNT >=1 AND TOT_INJ_LVL_B_CNT =0 AND TOT_INJ_LVL_A_CNT =0 ANDTOT_FATAL_CNT =0),1,0)as INJ_LVL_C,IIF((TOT_PDO_CNT >=1 AND TOT_INJ_LVL_C_CNT =0 AND TOT_INJ_LVL_B_CNT =0 AND TOT_INJ_LVL_A_CNT =0 AND TOT_FATAL_CNT =0),1,0)as PDO,Shapefrom distribution.transpor.CRASHMULTIYEARwheredatepart(YEAR,CRASH_DT)in(2014,2015,2016)</DIV></DIV></DIV> ODOT Feature Class dataset Simple FALSE 54075 TRUE FALSE 54075 CrashMultiYear Feature Class 54075 OBJECTID OBJECTID OID 4 10 0 Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 4 0 0 Feature geometry. ESRI Coordinates defining the features. CRASH_ID CRASH ID Integer 4 10 0 Crash ID is the unique identifier assigned to every crash by the Crash Data System, without regard to DMV Serial Number, County, or Year. It is not visible on the Data Entry Screen, because the system generates the ID number when the crash case is saved. The CRASH_ID field is the primary key field for the CRASH table, and one of several primary key fields in VHCL, PARTIC and other CDS data tables. ODOT SER_NO DMV Serial No String 5 0 0 An Accident Number is assigned to each crash by the Driver and Motor Vehicle Services (DMV) division. For the purposes of crash coding this number is referred to as a “Crash Serial Number”. The number is stamped on the accident report cover sheet of the case file. Serial Number, together with the County code, makes up the unique case identifier for each crash. Crashes within each county are numbered consecutively each year. For example, the DMV file number “03-1234” is made up of two parts: “03” represents the county code (in this case, Clackamas County), and “1234” is the Serial Number. The CDS data entry field is 5 characters long, so we add a leading zero and enter the number as “01234” in the data entry screen. DMV does not include the “county code” with the serial number on Multnomah County reports. Refer to the accident report cover sheet to find the name of the county in which the crash occurred. ODOT CRASH_DT CRASH Date Date 8 0 0 Crash Date is an eight-digit field that describes the date on which the crash occurred, as recorded on the police accident report (PAR) or on the driver report. The format of the crash date field is MMDDYYYY, where MM equals the two-digit month, DD equals the two-digit day, and YYYY equals the four-digit century and year. ODOT CRASH_HR_NO CRASH Hour String 2 0 0 Crash Hour is a two-digit code representing the hour in which the crash occurred based on military time. No rounding of time is used. ODOT CRASH_HR_LONG_DESC CRASH Hour Desc String 25 0 0 Long description for the hours range by the [CRASH_HR_NO] code ODOT CNTY_ID County Code String 2 0 0 County code is a two-digit code that identifies the county in which the crash occurred. The County code, together with the DMV “File” Number (i.e. the Serial Number) makes up the unique case identifier for each crash. ODOT CNTY_NM County Name String 50 0 0 Description field for the [CNTY_ID] code field ODOT CITY_SECT_ID City Code Integer 4 10 0 City is a three-digit code assigned to each incorporated city. An incorporated city is one that has been approved by an election, held in accordance with Statute (ORS Chapter 221). One code is assigned to each city, regardless of county boundary lines, except for the City of Portland. The City field is coded when the crash occurs inside the city limits of an incorporated city. Not all named locales are incorporated cities. They are considered unincorporated communities so no city codes are assigned to them so code them as “outside city limits”. Examples of unincorporated communities are Aloha, Clackamas, and Cedar Hills which fall within the Portland Urban Boundary. Leave this field blank for crashes that occur outside city limits. ODOT CITY_SECT_NM City Name String 25 0 0 Description field for the [CITY_SECT_ID] code field ODOT URB_AREA_CD Urban Area (FAUB) SmallInteger 2 5 0 Urban Area is a two-digit code that indicates whether the crash occurred within a Federal Aid Urban Transportation Boundary (FAUB). When determining this boundary, the city limits, current census information and major transportation facilities are taken into consideration. A large metropolitan urban area may encompass more than one city, and can cross county lines. The Portland Urban Area extends eastward from NW Portland to Troutdale, and southward to Marion County. Cities can lie partially inside and partially outside an urban boundary. Refer to the Crash Locator Tool (CLT), the automated milepoint logs (AMLs), or the “City – Urban Area” Cross-Reference Table for assistance in coding this field. ODOT URB_AREA_LONG_NM Urban Area Name (FAUB) String 50 0 0 Description field for the [URB_AREA_CD] code field ODOT FC_CD Functional Class Code String 2 0 0 Functional Classification groups streets and roadways by similar characteristics of mobility and/or land access. Functional classifications are categorized based on federal standards. This classification technique recognizes that individual roads and streets are dependent upon each other. Roads that occur inside a Federal Urban Area Transportation Boundary (FAUB) are considered “urban”. All others are considered rural, even in areas with populations greater than 5,000. It is extremely important to determine the actual crash location, and assign the crash to a particular road, before coding this and all other roadway elements. Effective for 2014 coding, grade-separated ramps carry the higher of the functional classifications they connect to. ODOT FC_DESC Functional Class Desc String 50 0 0 Description field for the [FC_CD] code field ODOT NHS_FLG NHS Flag SmallInteger 2 5 0 NHS indicates whether the highway on which the crash occurred is a part of the National Highway System. Prior to the federal surface transportation reauthorization “MAP-21”, only certain state highways and intermodal connectors were included in the National Highway System. MAP-21 expanded the NHS to include many high-volume local roads. The CAR Unit began collecting the NHS value for those roads in the 2013 crash file. NHS is depicted as a yellow border along the road linework in the CLT. ODOT RTE_ID Route ID String 5 0 0 Route Number which is physically posted along the highway. The Route Number is a political designation for certain travel routes. ODOT RTE_NM Route Name String 10 0 0 Description field for the [RTE_ID] code field. The concatenation of [RTE_TYP_CD] & [RTE_ID] ODOT RTE_TYP_CD Route Type String 2 0 0 The highway type code OR = Oregon Route IS = Interstate Route US = US Route ODOT HWY_NO Highway Num String 3 0 0 Highway Number represents the administrative number assigned to a state highway by ODOT. A state highway is: “…a land-based public way designated by the Oregon Transportation Commission as a highway for the purpose of vehicular travel. The State of Oregon commonly has, but may not have, all right, title, interest, jurisdiction, maintenance and control of the entire area within the highway right-of-way.” ODOT’s Highway Number is not always the same as the signed Route Number which is physically posted along the highway. The Route Number is a political designation for certain travel routes. Highway numbers and route numbers may be assigned to the same segment of roadway. ODOT HWY_MED_NM Highway Name String 30 0 0 Description field for the [HWY_NO] code field ODOT HWY_SFX_NO Highway Suffix String 2 0 0 Looks like a highway suffix? it is blank... ? RDWY_NO Roadway Num String 1 0 0 Roadway Number is a one-digit code used in conjunction with the Highway Number to make highway milepoints unique, and to specify the side of a divided highway on which the milepoint exists. Code this field for crashes that occur on the state highway system only, including connections and frontage roads. Leave this field blank for all other crashes. Code “1” is used when a crash occurs on an undivided highway, or on the “add” (increasing) mileage side of a divided highway or couplet. There is one exception: Interstate 5 milepoints decrease to the south. Even though the southbound lanes represent “non-add” mileage, I-5 Southbound is designated as Roadway 1. The northbound “add” mileage side is designated as Roadway 2. Code “2” is used when a crash occurs on: • The “non-add” (decreasing) mileage side of a divided highway, or • On the “non-add” (decreasing) mileage side of a couplet, or • On the non-add side of a frontage road. (Effective 2007) Code “5” is used when a crash occurs on land areas that have a surveyed alignment where a road is intended to be built. No paved surface exists yet. This mileage is considered "located", and is neither “add” nor “non-add”. Add vs. Non-Add Mileage Definitions Add-Mileage generally applies when milepoints have increasing values in the direction of travel. The term originated from the fact that the direction of increasing milepoints is used for mileage summarization, whereas separate roadways mileposted in the opposite direction are not counted in totals. Alignment means the horizontal and vertical design of a section of roadway. Couplet refers to the two one-way roadways of a divided highway, named differently, approximately parallel, with traffic flow in opposite directions, and separated by accessible land uses. On the reverse "non-add" mileage side, vehicular travel runs in the opposite direction from the side where the highway milepoints increase. The milepoints on this section of the highway still increase in the same direction as the rest of the highway, but the vehicle travels in the opposing direction. Oregon Route 99E, HIghway 72 in Salem, (Liberty Street NE and Commercial Street NE) is an example of a couplet. Liberty Street is the reverse side of the couplet, because Highway 72 milepoints increase southbound, though vehicular travel on Liberty Street is northbound. Non-Add Mileage applies to milepoints that decrease in the direction of travel. Non-add mileage is not included in highway mileage summarization. Roadway is the part of a trafficway designed, improved, and ordinarily used for vehicular travel. The boundary lines are the lateral limits of the traffic lanes. Parking lanes and shoulders are not part of the roadway. A parking lane ceases to exist and is considered a traffic lane when parking along a street is prohibited. ODOT HWY_COMPNT_CD HWY Component Code String 1 0 0 Highway Component is a one-digit code that describes the type of service the coded section of highway provides. Code this field only for crashes that occur on the state highway system. Leave this field blank for all other crashes. Code “0” is used when the crash occurs on the mainline non-couplet segments of highway. This refers to all roadways for a highway, excluding connections and frontage roads. (This is a slight variation to the way mainline is defined by ODOT terms and definitions, for the purposes of coding for the CAR Unit). Code “1” is used when the crash occurs on mainline highway segments that create a couplet, both add-mileage and non-add mileage roadways. The Highway Performance Monitoring System (HPMS) defines couplets as “composed of the two roadways of a divided highway; often named differently; approximately parallel with traffic flow in opposite directions; and separated by accessible land uses”. For non-intersectional crashes on couplets, limit the Number of Lanes to the “add” or “non-add” roadway on which the crash occurred. Do not add the number of lanes for both couplet roadways. Code “3” is used when the crash occurs on a frontage road. A frontage road is a road, secondary to and generally parallel to the mainline highway, providing service to abutting property and adjacent areas for control of access. A frontage road may or may not be connected to the highway it services. Code “6” is used when the crash occurs on a connection. A connection is a street or road, open to vehicular travel, (often an off or on ramp) which joins a road from the state highway system to any other road, entity, or to another state-owned road. A connection is usually much shorter than a spur or frontage road. Code “8” is a placeholder and has not yet been approved for use. ODOT HWY_COMPNT_LONG_DESC Highway Component Desc String 25 0 0 Description field for the [HWY_COMPNT_CD] code field ODOT MLGE_TYP_CD Mileage Type String 1 0 0 Mileage Type is used to make milepoints unique in areas where there are multiple occurrences of the same milepoint on a single highway. Leave this field blank for crashes that do not occur on the state highway system. Code “0” is used for Regular Mileage – Regular mileage represents any mileage that does not fall within any of the categories listed below. The majority of the highway system is regular mileage. Code “Z” is used for Overlapping Mileage. Overlapping (i.e. “Z”) Mileage is comprised of duplicate milepoints used on a new length of roadway constructed within a segment of road that already has existing milepoints. This occurs when a highway is lengthened anywhere between its beginning and ending milepoints. ODOT MLGE_TYP_LONG_DESC Mileage Type Desc String 20 0 0 Description field for the [MLGE_TYP_CD] code field ODOT RD_CON_NO Connection No String 1 0 0 Connection Number is a one-digit code that identifies an on-ramp, off-ramp, over-crossing or under-crossing roadway within an interchange. Connection numbers are assigned to each connection that belongs to a given highway within the interchange. Connection numbering re-starts at “1” for each additional highway; therefore, the same connection “numbers” may be assigned to a connection that belongs to a different highway in the same interchange. Refer to the streets database, system setups, or diagrams to find the connection number for those that are set up inside city limits. For areas outside city limits, refer to the automated milepoint logs (AMLs) or CAR Unit diagrams. ODOT MP_NO Milepoint Double 8 38 8 The milepost/milepoint value along the route ODOT LRS_VAL LRS String 20 0 0 The Linear Reference System (LRS) value is comprised of Trans-Info fields strung together, for specifying a highway segment. Linear reference systems provide a means of identifying the location of highway features by a relative measure (i.e. the milepoint). In GIS applications, the LRS is used with the milepoint to dynamically snap crashes to a point on a map, in lieu of using spatial coordinates. Leave this field blank for crashes on non-state roads. At this time, only state highways are assigned LRS values in the Crash Data System. The LRS is created by stringing together the values of seven different Trans-Info data elements, starting with a prefix of “0”. The LRS must be entered according to the chart below. There are 12 positions in the state highway LRS and each one must be filled in. This field became effective as of the 2009 code year. LRS values were loaded retroactively for 2007 and 2008 crashes. ODOT LAT_DEG_NO Latitude Degree Integer 4 10 0 Latitude Degrees ODOT LAT_MINUTE_NO Latitude Minute Integer 4 10 0 Latitude Minutes ODOT LAT_SEC_NO Latitude Second Double 8 38 8 Latitude Seconds ODOT LONGTD_DEG_NO Longitude Degree Integer 4 10 0 Longitude Degrees ODOT LONGTD_MINUTE_NO Longitude Minute Integer 4 10 0 Longitude Minutes ODOT LONGTD_SEC_NO Longitude Second Double 8 38 8 Longitude Seconds ODOT LAT_DD Latitude Decimal Deg Double 8 38 8 Latitude Decimal Degrees ODOT LONGTD_DD Longitude Decimal Deg Double 8 38 8 Longitude Decimal Degrees ODOT SEG_MRK_ID Segment Marker ID String 30 0 0 Segment Marker ID is a unique identifier assigned to an individual road segment in OR-Trans and is used to relate a crash to that segment. It is used in conjunction with Segment Point LRS Measure in GIS applications to enforce the co-incidence of a crash point and its specific location on a road segment line, in order to maintain the crash point at that location when linework is adjusted for correction or improvement. The value for this field is automatically loaded into the Crash Data Entry Screen from the Crash Locator Tool (CLT) when the CLT is used to import crash location data. Data for this field is available for year 2007 and later. ODOT SEG_PT_LRS_MEAS Segment LRS Measure Double 8 38 8 Segment Point LRS Measure* is a measure, expressed in feet, along an individual road segment that specifies the location of a crash on the segment. It is used in conjunction with Segment Marker ID in GIS applications to enforce the co-incidence of a crash point and the specific location on a road segment line, in order to maintain the crash point at that location in case linework is adjusted at a future date. The values for this field are calculated and supplied by a GIS analyst, and uploaded to the Crash table via a batch process. Data for this field is available for year 2007 and later. ODOT UNLOCT_FLG Unlocatable Flag SmallInteger 2 5 0 The Unlocatable Flag identifies crashes for which the location is unknown or for which linework does not exist in the GIS road network used for crash data entry. Code “0” indicates a crash location has been identified in the database. Code “1” indicates that either: • The crash report didn't provide enough information to identify the incident location, or • Linework didn't exist in the “OR-Trans” road network layer used for geocoding crash points at the time the case was coded. The process used to set the Unlocatable Flag will load default spatial coordinates in the Latitude and Longitude fields. These default coordinates represent a point off the road network but still within the local jurisdiction where the crash occurred. Set the Unlocatable Flag when coding: • A crash that occurred on a state highway or mile-pointed county road at an unknown milepoint (MP = 999.99), • A crash on a city street or non-milepointed county road where the nearest intersecting street is unknown, • A crash on a city street or non-milepointed county ODOT SPECL_JRSDCT_ID Special Jurisdiction ID String 2 0 0 Special Jurisdiction is used for crashes that occur on roads that are open to the public, but under the authority of an agency other than an incorporated city, county, or ODOT. Examples of special jurisdictions are: • National Forest Service • National Park Service • Bureau of Land Management (BLM) • State Forest Service • State Park Service • Reservations – (Native American Tribal Lands) • Miscellaneous non-county roads Enter the Special Jurisdiction code that corresponds to the area in which the crash occurred. When a value is entered in Special Jurisdiction, the data entry system enables the following fields: • Jurisdiction Group (this code is automatically supplied by data entry system) • Recreational / Other Road Number (modified Street Number field) • Intersecting Recreational / Other Road Number (modified Nearest Intersecting Street Number field) Special Jurisdiction is not used to code crashes that occur on State Highways, County Roads, or City Streets that run through a Special Jurisdiction. This field is only for roads that belong to the Special Jurisdiction. ODOT SPECL_JRSDCT_LONG_DESC Special Jurisdiction Desc String 50 0 0 Description field for the [SPECL_JRSDCT_ID] code field ODOT RECRE_RD_NM Recreational Rd Name String 15 0 0 The Street Number field changes to “Recreational Road Name” when a value is entered into the “Special Jurisdiction” field. The field length for Recreational Road is expanded to 15 characters. ODOT ISECT_RECRE_RD_NM Intersecting Rec Rd Name String 15 0 0 Intersecting Recreational Road Name. The Street Number field changes to “Recreational Road Name” when a value is entered into the “Special Jurisdiction” field. The field length for Recreational Road is expanded to 15 characters. ODOT AGY_ST_NO Street No String 7 0 0 The Street Number field length and coding instructions vary, depending on the local government and road jurisdiction for the crash, and if the crash location is “intersectional”. Street Number codes are found in the Set-up Books, the CDS Streets database, or County Road log books. Code Street Number for all crashes, except those on state highways outside city limits. Never enter “00000” in the Street Number field. For non-intersectional crashes, the value entered in the Street Number field represents the road on which the crash occurred. For intersectional crashes involving city streets or non-milepointed county roads, enter the smallest street number of the two roads being coded. This practice simplifies coding and avoids complex hierarchical rules. ODOT ST_FULL_NM Street Name String 28 0 0 Full name of the street for the crash location ODOT ISECT_AGY_ST_NO Intersecting Street No String 7 0 0 The "Nearest Intersecting Street" is the road closest to the road that was coded in the “Street Number” field, belonging to the same jurisdiction, and preferably on the same side of the road. This is always true when coding physically divided state highways such as Interstate 5. For roads that are not physically divided, it is permissible to enter the nearest intersecting street from the other side of the road. When no intersecting road exists within the same jurisdiction, it is permissible to code the nearest cross-street from a neighboring jurisdiction. Enter REF in the “Diag” field of the Intersection Set-up. For Intersectional crashes, enter the larger of the two street codes in the 2nd Street Number field for crashes that occur on city streets, state highways inside city limits, non-milepointed county roads, and milepointed Lane County roads. Leave this field blank when coding crashes that occurred: • On state highways outside of city limits • On milepointed county roads (other than Lane County) ODOT ISECT_ST_FULL_NM Intersecting Street Name String 28 0 0 Full name of the closest intersecting street to the crash location ODOT ISECT_SEQ_NO Intersection Sequence No SmallInteger 2 5 0 The Intersection Sequence Number identifies which junction of the same two roads has been coded. The number increases for roads that intersect more than once, such as “loops”, “circles” and roads that intersect each other at two points more than 50 feet apart. The default value for Intersection Sequence Number is “1”. Intersection sequence numbers are generally assigned in the order of occurrence of the intersecting roads, from south to north (for north/south roads), or west to east (for east/west roads). ODOT FROM_ISECT_DSTNC_QTY Distance from Intersection Integer 4 10 0 This field represents the distance a crash occurred from the nearest intersecting roadway. It is only coded for crashes that occur on city streets, non-milepointed county roads, Lane County roads, and special jurisdiction roads. Coding instructions vary depending on the jurisdiction. For city streets, the code represents a measurement in feet. For non-milepointed county roads, Lane County roads, and special jurisdiction roads, the code represents a measurement in hundredths of a mile. Using the Crash Locator Tool (CLT) aerial imagery, begin the measurement at the curb line of the nearest intersecting road, and end the measurement at the crash location. (The presence and orientation of a crosswalk has no bearing on where the measurement begins.) Enter the resulting value into the Data Entry screen. Four digits are required in this field, so enter leading zeros when necessary. Enter “0000” for intersectional crashes inside city limits, non-milepointed county roads, and Lane County roads. ODOT CMPSS_DIR_CD Direction from Intersection String 1 0 0 The Direction from Nearest Intersection value represents the compass direction from the crash to the nearest intersection. The compass transparency image depicted above is placed over the center of the nearest intersection on a map or diagram, with the North arrow oriented to. The section in which the crash location falls indicates the Direction from Nearest Intersection, and the Vehicle Movement “From/To” directions. Use Code “0” for the following situations: • For non-intersectional crashes on milepointed county roads (except for Lane County) • For non-intersectional crashes on state highways outside city limits • For all other cases when the direction from the nearest intersecting street is unknown. Use Code “9” for crashes that occur at the center of an intersection (“Location of Impact” quadrants 1, 2, 3 or 4). This rule applies to all road types. For intersectional crashes that occur in “Location of Impact” quadrants 5 or 6, enter the Direction code relative to the center of the intersection. ODOT CMPSS_DIR_SHORT_DESC Direction from Intersection Desc String 2 0 0 Description field for the [CMPSS_DIR_CD] code field ODOT POST_SPEED_LMT_VAL Posted Speed String 2 0 0 Posted Speed represents the regulatory speed posted for the section of road on which the crash occurred. This field is only coded when information regarding posted speed is available from the PAR, AML, or loaded from the Crash Locator Tool (CLT). For all other situations, leave this field blank. On state highways, if the posted speed on the PAR conflicts with the ODOT highway inventory (AML, CLT), use the speed provided by the highway inventory. The exception to this rule is for highways where a work zone has temporarily changed the posted speed. For all other roads, use the speed listed on the PAR. ODOT RD_CHAR_CD Rd Character Code String 1 0 0 Road Character refers to the alignment, contour, structure, or other distinctive feature that describes the roadway at the crash location. The proper coding of this data element is critical to the crash record, since this element controls the analysis between intersectional crashes and non-intersectional crashes. Intersectional Crashes Use Code “1” for all intersectional crashes. This rule applies to all road jurisdictions (city streets, county roads, and state highways). Intersectional crashes are never coded to zones 7 or 8. Definition: Any crash that occurs within the limits (the extended curb lines) of the intersection of two or more roads, or any crash that occurs outside the center of the intersection, within location of impact zones 5 or 6, and as a direct result of some maneuver at or because of the intersection, will be classed as intersectional and so coded. Additional Rules for “Intersectional” Crashes Conditions surrounding an accident that occurred outside the limits of an intersection must justify the classification of “intersection”. Rear-End Collisions at Intersections Rear-end collisions involving a vehicle first in line at the intersection should be coded as intersectional. Turning Maneuvers at Intersections A crash involving a turning movement is classified as “intersectional” when the crash results from the turning movement and the impact is within location of impact zones 5 or 6. When the point of impact is beyond location of impact zones 5 or 6, the turning movement should have been completed and the Road Character should be coded as “non-intersectional”. Pedestrian Collisions at Intersections If a pedestrian is struck while crossing from one corner of an intersection to another, code the Character of Road as intersectional. If a pedestrian is struck while crossing within a marked or unmarked crosswalk at the intersection, code Road Character as intersectional. Complex Intersections Complex intersections and interchanges are areas where more than one road character exists. This could be an intersection that occurs at a curve or on an overpass/bridge etc. When an intersectional crash occurs at a complex intersection, the Road Character is coded as intersection. Other road characters that exist at the intersection and are relevant to the crash should be identified through the Event field or Related Flags. Non-intersectional crashes that occur outside the intersection, but are related to movement or control of traffic through the intersection, may be “Intersection-Related”. See page 63 for information on Intersection-Related crashes. Non-Intersectional Crashes Crashes that don’t meet the definition of “intersectional” are “non-intersectional”. Non-intersectional crashes can occur within the area of a complex intersection or interchange, on a curve, bridge, etc. In such cases, the Road Character field must be coded as the curve, bridge, etc. rather than as an intersection. Code “2” is used for crashes at driveways or alley access. Code “3” is used for crashes on straight roads that don’t involve transitioning lanes, driveways, turn-outs, hills, bridges, curves, or tunnels. Code “4” is used for crashes involving a lane transition. Code “5” is used for crashes involving a horizontal curve. Code “6” is used for crashes involving an “open access” or turnout, i.e, a space adjacent to a road where vehicles may pull off to enable other vehicles to pass. Code “7” is used for crashes that occur on a grade, vertical slope, hill, etc.. Code “8” is used for crashes that occur on or under a bridge structure. Code “9” is used for crashes that occur inside a tunnel. More than one Road Character may exist at a crash location. For example, a crash may occur at a driveway on a hill, or on a curve built into a tunnel. In order to maintain consistency in how this field is coded by the data entry team, the following rules assign priority. Intersections: If a crash occurs within an intersection as a result of a maneuver at or because of the intersection, code 1 takes precedence. Driveways or alley access: When a crash involves a movement into or out of a driveway or alley access, code 2 takes precedence. Bridge over-crossings and under-crossings: When a crash occurs on or under a bridge, code 8 takes precedence. Grade (Hill) vs. Curve: When a crash location is on a vertical grade with a curve, code 7 takes precedence, unless the police report specifies that the driver failed to negotiate the curve. Grade (Hill) vs. Turnout: When a crash involves a turnout on a grade, code 6 takes precedence. Tunnel: If a crash occurs in a tunnel, code 9 takes precedence. ODOT RD_CHAR_LONG_DESC Rd Character Desc String 30 0 0 Description field for the [RD_CHAR_CD] code field ODOT OFF_RDWY_FLG Off Roadway Flag SmallInteger 2 5 0 Off Roadway is a “yes / no” field that indicates where the crash occurred in relation to the roadway. This field should be coded according to the location of the first harmful event. Crashes are considered “off roadway” if the first harmful event occurs outside the travel portion of the road (i.e. on the shoulder, roadside, parking lanes, etc.) Definition: “Roadway” is the part of a trafficway designed, improved, and ordinarily used for vehicular travel. The boundary lines are the lateral limits of the traffic lanes. Parking lanes and shoulders are not part of the roadway. A parking lane ceases to exist and is considered a traffic lane when parking along a street is prohibited. Code “0” is used when the first harmful event of the crash occurred on the roadway. When a vehicle overturns on the roadway first and continues its path off-road, the crash is considered to have occurred “on the roadway”. Collisions with over-crossing structures are considered to be “on the roadway” if the structure was hit while the vehicle was traveling directly under it and within the travel lane. Code “1” is used when the first harmful event of the crash occurred off the roadway. Crashes that occur with solid median barriers are considered “off roadway”, as are crashes that occur on an earth, grass median. ODOT ISECT_TYP_CD Intersection Type String 1 0 0 Intersection Type is a one-digit code that indicates the way in which two or more roads meet or cross. Code this field for “intersectional” crashes only (refer to Character of Road for definition on page 56. For all other crashes, leave this field blank. Code “0” is only used when the intersecting street is unknown and there is no description provided about the intersection type. Code “1” is used for cross-type intersections. Code “2” is used for two-legged intersections. Code “3” is used for three-legged intersections. Code “4” is used for four-legged intersections, and for cross-streets that are off-set by 50 feet or less and are controlled by a common traffic control device. Code “5” is used for five-legged intersections. Code “6” is used for six-legged intersections. Codes “7”, “8” and “9” are available for rare intersections with more legs. ODOT ISECT_TYP_SHORT_DESC Intersection Type Desc String 7 0 0 Description field for the [ISECT_TYP_CD] code field ODOT ISECT_REL_FLG Intersection Related Flag SmallInteger 2 5 0 Intersection Related is a yes / no field that indicates whether a "non-intersectional" crash occurred as a result of movement or control of traffic through a nearby intersection. Code “0” is used for “intersectional” crashes, and for non-intersectional crashes that are not related to the movement or control of traffic through a nearby intersection. Code “1” is used for non-intersectional crashes that result from an activity, behavior, or control related to the movement of traffic units through an intersection. ODOT RNDABT_FLG Roundabout Flag SmallInteger 2 5 0 Roundabout is a yes / no field that indicates whether or not a crash is related to the movement or control of traffic through a roundabout or traffic circle. Use Code “0” when the crash location is not at a traffic circle or roundabout. The Crash Data Entry screen defaults to Code “0”. Use Code “1” when the crash occurred at a traffic circle or roundabout. Roundabout – a circular intersection with yield control for all entering traffic, channelized approaches, counter-clockwise circulation around a central island, and appropriate geometric curvature to ensure that travel speeds on the circulatory roadway are typically less than 30 mph. Traffic Circle – an older-style circular intersection with channelized approaches, but that does not mandate a yield control for all entering traffic. ODOT DRVWY_REL_FLG Driveway Related Flag SmallInteger 2 5 0 Driveway Related is a yes / no field that indicates whether a crash is due to the movement of traffic or activity at a driveway or alley access but did not involve the traffic units using the driveway. If Character of Road is driveway, this field must be coded “0”. Code “0” is used when the crash is not related to the movement of traffic into, out of, or across a driveway or alley access, even if a driveway or alley access exists at the crash location. Code “1” is used when the crash is due to the movement of traffic or activity at a driveway or alley access but did not involve the traffic units using the driveway. If a crash involves a traffic unit that is using a driveway at an intersection, then Character of Road = 1 (Intersection) and Driveway Related = 1 (Yes). If a driveway exists at an intersection, but is not being used, Character of Road = 1 (Intersection) and Driveway Related = 0 (No). ODOT LN_QTY Number of Lanes SmallInteger 2 5 0 Number of Lanes is a two-digit code that represents the total number of travel lanes for the involved road. Code all the travel lanes for both directions of travel, even if the crash occurred on a divided highway (a code change from coding procedures used prior to 2003). The only exception to this rule is for crashes on HPMS couplets on state highways. For HPMS couplets, limit the number of lanes to the roadway on which the crash occurred. Continuous left turn lanes are not included in the count of travel lanes, unless the crash involved the continuous left turn lane. ODOT TURNG_LEG_QTY Number of Turning Legs Integer 4 10 0 Number of Turning Legs is a two-digit code that indicates the number of turning legs at an intersection where a crash occurs. Turn lanes are not coded in this field. Turning Leg (configuration recognized in crash coding) is a travel lane for channelizing traffic at right-angles most commonly found at an intersection (not to be mistaken for a right turn lane). A common form of turning leg is noted by a triangular shaped island, raised curb, or painted, that separates right-turning traffic from through traffic at an intersection. ODOT MEDN_TYP_CD Median Type Code String 1 0 0 Median Type is a one-digit code that indicates the type of separation that divides opposing traffic along a roadway. Code “0” is used for continuous left turn lanes, highway couplets, and paved/painted medians. Code “1” is used for metal guard rails, concrete barriers, curbing, planters or other fixed barriers separating opposing directions of traffic on one roadbed. Code “2” is used for roadways divided by earth or vegetation which may include a cable or guard rail in the center. When using Vehicle Level Action Code 029 (vehicle crossed, plunged over, or through median barrier) or 033 (vehicle crossed earth or grass median), use the Digital Video Log (DVL) or aerial imagery to verify the correct median type has been coded. ODOT MEDN_TYP_LONG_DESC Median Type Desc String 50 0 0 Description field for the [MEDN_TYP_CD] code field ODOT IMPCT_LOC_CD Location of Impact String 2 0 0 Location of Impact is a two-digit code that describes where the first harmful event occurred in relation to the roadway. Coding of this field is influenced by the following factors. Instructions for each situation are presented in their own sections below: • The crash is intersectional • The crash is not intersectional and occurred on a city street • The crash is not intersectional and occurred on a state highway • The crash is not intersectional and occurred on a county road or other jurisdiction Please see pages 74-84 of the Code Manual for detailed illustrations: https://www.oregon.gov/ODOT/Data/documents/CDS_Code_Manual.pdf#page=90 ODOT CRASH_TYP_CD Crash Type Code String 1 0 0 Crash Type is a one-character field that identifies the first harmful event. ODOT CRASH_TYP_LONG_DESC Crash Type Desc String 75 0 0 Description field for the [CRASH_TYP_CD] code field ODOT COLLIS_TYP_CD Collision Type Code String 1 0 0 Collision Type is a one-character alphanumeric code. It refers to the angle or direction of impact between vehicles based on their intended path of travel, or to the type of first impact (i.e. Non-Collision, Fixed Object, Pedestrian, etc.). Therefore, any attempted maneuver to avoid the collision is not relevant to the coding of this field. Coding Priority If a vehicle is performing more than one of the movements bulleted below, at the same time, the priority for coding Vehicle Movement is as follows: 1. Parking 2. Backing 3. Turning 4. Stopped If a vehicle strikes a pedestrian as the first harmful event, enter Code “0” (Pedestrian) in this field, and enter Code “3” in the Crash Type field. (This rule does not apply to crashes in which a pedestrian is struck subsequent to the first harmful event; i.e., a “sub-ped” crash. See Event code 005 for such cases). If Crash Type = “8” (Fixed Object) and Collision Type = “9” (Fixed Object), then Off Roadway Flag must be coded as “1” (Off Road), except for when the following Event codes are used: 049 – Bridge girder (horizontal structure overhead) 063 – Tree branch or other vegetation overhead, etc. 064 – Wire or cable across or over the road 073 – Other bump (not speed bump), pothole or pavement irregularity 074 – Other overhanging object (highway sign, signal head, etc.); not bridge 127 – Rock slide or land slide ODOT COLLIS_TYP_LONG_DESC Collison Type Desc String 30 0 0 Description field for the [COLLIS_TYP_CD] code field ODOT CRASH_SVRTY_CD Crash Severity Code String 1 0 0 Crash Severity is classified according to the type of injury sustained in the crash. For example, if there were two injuries and one fatality, it is a fatal Crash, enter Crash Severity code “2”. If there were no injuries, it is a “property damage only” crash. Enter Crash Severity code “5”. Effective for 2015 crash data entry, “Property damage only” was discontinued as an option for “Crash Severity” for Pedestrian and Pedalcycle-Involved motor vehicle crashes. There is no legal requirement, nor option, for bicyclists and pedestrians to report when they’re involved in a crash. In the absence of formal reporting from these participants, a decision had to be made regarding their injury severity. It was determined that, as vulnerable road users, bicyclists and pedestrians must receive at least a “possible injury” in collisions with motor vehicles. Therefore, the Crash Severity value for non-fatal crashes in which pedestrians or pedalcyclists are struck is code “4”. Fatal Crash is a motor vehicle crash that results in fatal injuries to one or more persons. For purposes of Motor Vehicle Crash Classification, death must occur within 30 days. (See ANSI D16.1-2007, definition 3.1.3, “Time of Classification”.) Crashes that result from deliberate intent, suicide, homicide (not negligent homicide) and non-traffic are not included. Crashes that occur on private property or in parking lots are only coded when they involve entering or exiting the roadway. Non-Fatal Injury Crash is a motor vehicle crash that results in any injury not resulting in death. Property Damage Only (PDO) crash is a motor vehicle crash in which there is no injury to any person, but damage occurred to a motor vehicle, other road vehicle, or to other property, including injury to domestic animals. ODOT CRASH_SVRTY_LONG_DESC Crash Severity Desc String 25 0 0 Description field for the [CRASH_SVRTY_CD] code field ODOT WTHR_COND_CD Weather Condition String 1 0 0 Weather Condition represents the atmospheric conditions at the time of the crash. In Oregon, we experience heavy rain, and then the sky will clear. This creates a situation where the weather conditions can be clear but the road conditions can be wet. This combination of codes will trigger a yellow warning flag in the data entry system, but in this scenario, the coding is correct. ODOT WTHR_COND_LONG_DESC Weather Desc String 10 0 0 Description field for the [WTHR_COND_CD] code field ODOT RD_SURF_COND_CD Road Surface Condition String 1 0 0 Road Surface Condition represents the condition of the travel lanes at the time of the crash. When a crash occurs in a tunnel, the predominant weather condition outside is coded. However, this could create a situation where the Weather Condition is coded “rain” and the Road Surface Condition is coded “dry”. This combination of codes will produce a yellow warning flag in the data entry system, but in this scenario, the coding is correct. If there is a conflict between ice and snow, and the crash report indicates that the vehicle slid on ice, code the Road Surface Condition as Ice. ODOT RD_SURF_MED_DESC Road Surface Condition Desc String 10 0 0 Description field for the [RD_SURF_COND_CD] code field ODOT LGT_COND_CD Light Condition String 1 0 0 Light Condition represents the amount of ambient light available at the time of the crash. The code used for Light Condition should be compatible with the time of year and hour of day, unless special circumstances exist. Do not use Code “0” – Unknown, unless Crash Hour is also unknown. If light conditions are not stated on the driver report or PAR, refer to the chart below to determine the most appropriate code. ODOT LGT_COND_LONG_DESC Light Condition Desc String 30 0 0 Description field for the [LGT_COND_CD] code field ODOT TRAF_CNTL_DEVICE_CD Traffic Control Device Code String 3 0 0 Traffic Control Device (TCD) is a three-digit code that indicates the predominant control present at the crash location. More than one traffic control may be present (for example, a yield sign and a traffic signal at the same intersection), so code the control that is most pertinent to the crash. A police officer or flagger (Code 11) controlling traffic takes precedence over other controls. Images of some traffic control devices are depicted in the “Samples” section below. For more examples, refer to the Oregon Driver Manual. ODOT TRAF_CNTL_DEVICE_LONG_DESC Traffic Control Device Desc String 50 0 0 Description field for the [TRAF_CNTL_DEVICE_CD] code field ODOT TRAF_CNTL_FUNC_FLG TCD Functioning SmallInteger 2 5 0 Traffic Control Device Functional is a yes/no field that indicates if the Traffic Control Device coded was functional at the time of the crash. For 2016 crash data entry, when using a default entry screen for PDO crashes, a default value of 1 is loaded. However, the field is not disabled, and the value may be changed. Code “0” is used when the traffic control device is present but is not functioning correctly. Code “1” is the default code. It is used when: • A traffic control is known to be present and is known to be functioning properly • A traffic control is known to be present but no information is available on whether the device is functioning properly • No information exists on the presence of traffic control devices (assuming that if one exists, it is functioning correctly) ODOT INVSTG_AGY_CD Investigating Agency String 1 0 0 Investigating Agency indicates whether law enforcement was present at the scene; if a police crash report has been received and, if so, which agency reported the crash. ODOT INVSTG_AGY_LONG_DESC Investigating Agency Desc String 50 0 0 Description field for the [INVSTG_AGY_CD] code field ODOT SCHL_ZONE_IND School Zone Indicator String 1 0 0 School Zone is a one-digit code that indicates the crash occurred: • On a road adjacent to school grounds and that is marked by signs indicating a school zone with words, symbols, or a combination of words and symbols that give notice to the presence of the school zone • In a crosswalk that is not adjacent to school grounds but that is marked by such signs This definition of “School Zone” is found in ORS 801.462. Code “0” is used when information clearly indicates that the crash did not occur inside a designated school zone. Code “1” is used when information clearly indicates that a crash occurred inside a school zone. Code “9” is used when information indicates that a designated school zone exists near the area of the crash, but it is unknown if the crash occurred within the designated school zone boundaries. Leave this field blank if no information is available on the existence of a designated school zone. See “Traffic Control Device” for images of school zone signs. ODOT WRK_ZONE_IND Work Zone Indicator String 1 0 0 Work Zone is a one-digit code that indicates if the crash occurred in a work zone. A work zone is an area identified by advance warning where road construction, repair, maintenance, or utility work is being done on or adjacent to a highway, regardless of whether or not workers are present. For CDS, road construction, repair, maintenance or utility work includes, but is not limited to, the setting up and dismantling of cones, barriers or advance warning systems. If no information is available on the existence of a work zone, leave this field blank. Code “0” is used when information from the driver or police report clearly indicates that no work zone was present. Code “1” is used when information on the driver or police report clearly indicates that a crash occurred inside a work zone, or where road construction, maintenance, utility work, cones or flaggers are present. Code “9” is used when information indicates that a work zone exists near the area of the crash, but it is unknown if the crash occurred within the work zone boundaries. ODOT ALCHL_INVLV_FLG Alcohol Involved Flag SmallInteger 2 5 0 Alcohol-Involved Flag is a system-generated code indicating whether an active participant* in the crash had been using alcohol. The data entry system populates this field based on the values coded to the Participant Level BAC Test Results and Alcohol Use Reported fields. *An “active participant” is a person who was in a position of control during the crash: a driver, pedestrian, pedal-cyclist or other non-motorist. Code “0” is generated when no active participants were reported to have been drinking, and no positive BAC test result was received for any active participant. Code “1” is generated when at least one active participant was reported to have been drinking, or a positive BAC test result (.01 or higher) was received for any active participant. Note: Prior to 2003, BAC test result information was collected for fatally injured participants only. Non-fatally injured participants were flagged as to whether or not they had been drinking, but actual BAC values were not reported. As of 2003, the Crash Data System includes BAC test results on all participants for whom the information is received. The increase in alcohol-involvement figures for 2003 and later years represents, at least in part, an improvement in data collection and reporting, rather than an actual increase in alcohol-involved traffic crashes. ODOT DRUG_INVLV_FLG Drug Involved Flag SmallInteger 2 5 0 Drug-Involved is a system-generated code indicating whether an active participant* in the crash was reported to have used drugs. The data entry system populates this field based on the Participant Level Drug Use Reported field. *An “active participant” is a person who was in a position of control during the crash: a driver, pedestrian, pedal-cyclist or other non-motorist. Code “0” is generated when no active participants were reported to have used drugs. Code “1” is generated when at least one active participant was reported to have used drugs. Note: Prior to 2003, drug-involvement was summarized along with alcohol data, and was not broken out separately in the Crash Data System. As of 2003, the Crash Data System reports drug involvement for all participants for whom the information is received. ODOT CRASH_SPEED_INVLV_FLG Speed Involved Flag SmallInteger 2 5 0 Speed-Involved Flag exists on the Crash Level as a system-generated value. This field indicates whether or not a driver involved in the crash was exceeding the posted speed, driving too fast for conditions, or speed racing. The data entry system populates this field based on the Vehicle Speed Flag, the Participant Error field, and the Crash or Participant Cause fields. ODOT CRASH_HIT_RUN_FLG Hit and Run Flag SmallInteger 2 5 0 Hit and Run is a system-generated code indicating that a participant fled the scene of the crash, on foot or in a vehicle. It is populated according to the values coded in the Vehicle and Participant Level Hit and Run fields. *Effective for 2016 crash data entry, information on Hit and Run is no longer collected for Property Damage Only crashes. PDO default values for vehicles and participants cause the Crash level flag to be set to “0”. ODOT POP_RNG_CD Population Range Code String 1 0 0 Population Range is a system-generated code that represents the estimated number of persons living in the incorporated area in which the crash occurred. This field is only populated for crashes that occur in incorporated cities. Codes are based on annual estimates published by Portland State University. ODOT POP_RNG_MED_DESC Population Range Desc String 20 0 0 Description field for the [POP_RNG_CD] code field ODOT RD_CNTL_CD Rd Control Code String 1 0 0 Road Control is a system-generated code that identifies the governmental jurisdiction over the road on which the crash occurred. Urban areas are based on Federal Aid Urban Transportation Boundaries (FAUB), which is typically updated every 10 years at the time of the national census. Code “1” is generated for crashes on city streets inside Portland city limits. Code “2” is generated for crashes on state highways located inside Portland city limits. Code “3” is generated for crashes on city streets that are inside city limits (other than Portland) and FAUB. Both conditions must be met. Code “4” is generated for crashes on state highways located inside city limits (other than Portland) and FAUB. Both conditions must be met. Code “5” is generated for crashes on state highways located outside FAUB. Code “6” is generated for crashes on streets under county jurisdiction that are outside city limits and outside FAUB. Both conditions must be met. Code “7” is generated for crashes on streets that are inside incorporated city limits but outside FAUB. Code “8” is generated for crashes on state highways located outside city limits but inside FAUB. Code “9” is generated for crashes on county roads that are outside city limits but inside FAUB. ODOT RD_CNTL_MED_DESC Rd Control Desc String 20 0 0 Description field for the [RD_CNTL_CD] code field ODOT REG_ID ODOT Region ID String 1 0 0 The Oregon Department of Transportation divides its highway operations into five geographical regions. Each region is responsible for developing and managing the construction of highway projects, plus the maintenance of state, federal, and interstate highways within its boundaries. Region maps can be found at: http://www.oregon.gov/odot/data/pages/maps.aspx Region 1 includes the Eastern portion of Washington County, Multnomah County, Clackamas County and most of Hood River County. Region 2 includes Clatsop County, Columbia County, Tillamook County, the Western portion of Washington County, Yamhill County, Polk County, Marion County, Lincoln County, Benton County, Linn County, and Lane County. Region 3 includes Coos County, Douglas County, Curry County, Josephine County, most of Jackson County and a small portion of Klamath County. Region 4 includes a small portion of Hood River County, Wasco County, Sherman County, Gilliam County, Jefferson County, Wheeler County, Crook County, Deschutes County, a small portion of Jackson County, most of Klamath County, and Lake County. Region 5 includes Morrow County, Umatilla County, Union County, Wallowa County, Grant County, Baker County, Harney County, and Malheur County. Data for this field is available for years 2007 and later. ODOT DIST_ID ODOT District ID String 3 0 0 There are 14 ODOT Maintenance Districts across the state. Each District is responsible for the day to day maintenance and operation of the state highways in their geographic area. District 1 includes all or portions of Clatsop County, Columbia County, Tillamook County and the Western portion of Washington County. District 2B includes all or portions of Washington County, Multnomah County and a portion of Clackamas County. District 2C includes all or portions of Multnomah County, Hood River County and Clackamas County. District 3 includes all or portions of Yamhill County, Polk County, Marion County, Linn County and Lane County. District 4 includes all or portions of Tillamook County, Polk County, Lincoln County, Benton County and Linn County. District 5 includes all or portions of Linn County, Lane County, and Klamath County. District 7 includes all or portions of Douglas County, Coos County, and Curry County. District 8 includes all or portions of Douglas County, Josephine County, Jackson County, and Klamath County. District 9 includes all or portions of Wasco County, Sherman County, Gilliam County, Morrow County, and Wheeler County. District 10 includes all or portions of Jefferson County, Wheeler County, Deschutes County, Crook County, Harney County, Klamath County and Lake County. District 11 includes portions of Jackson County, Klamath County, Lake County, and Harney County. District 12 includes all or portions of Morrow County, Umatilla County, Union County, Gilliam County, Wheeler County, and Grant County. District 13 includes all or portions of Umatilla County, Wallowa County, Union County, Grant County, and Baker County. District 14 includes all or portions of Grant County, Baker County, Harney County, and Malheur County. Data for this field is available for year 2007 and later. ODOT TOT_VHCL_CNT Total Vehicles Integer 4 10 0 The number of vehicles involved in this crash, excluding phantom or other non-contact vehicles. This derived field is calculated based on the number of vehicle records entered for this crash. ODOT TOT_FATAL_CNT Total Deaths Integer 4 10 0 The number of people killed as a result of this crash. This derived field is calculated based on the number of participant records with a Participant Injury Severity value of 1. ODOT TOT_INJ_LVL_A_CNT Total Serious Injuries Integer 4 10 0 The number of people who were seriously injured (but not killed) in this crash. This derived field is calculated based on the number of participant records with a Participant Injury Severity value of 2. ODOT TOT_INJ_LVL_B_CNT Total Moderate Injuries Integer 4 10 0 The number of people who were moderately injured in this crash. This derived field is calculated based on the number of participant records with a Participant Injury Severity value of 3. ODOT TOT_INJ_LVL_C_CNT Total Minor Injuries Integer 4 10 0 The number of people who received minor injuries in this crash. This derived field is calculated based on the number of participant records with a Participant Injury Severity value of 4. ODOT TOT_INJ_CNT Total Non-Fatal Injuries Integer 4 10 0 The number of people who were injured in the crash (not fatally). This derived field is calculated based on the number of participant records with a Participant Injury Severity value of 2 (Serious Injury), 3. (Moderate Injury), or 4 (Minor/Possible Injury). ODOT TOT_UNINJD_AGE00_04_CNT Total Un-injured Age 00-04 Integer 4 10 0 The number of children, newborn to age 4, who were involved in the crash but were not injured. This derived field is calculated based on the number of participant records where Age is between 01 and 04 and Injury Severity = 7. ODOT TOT_OCCUP_CNT Total Vehicle Occupants Integer 4 10 0 The number of vehicle occupants involved in the crash. This derived value is computed based on the sum of the Vehicle Level “Occupant Count” field for all vehicles in this crash. (That value is, in turn, derived from the sum of the vehicle occupants that were using / were not using / or have an unknown use of safety equipment.) Note: It is assumed that this summary value will include, at the minimum, all the Participants that have a Participant Type Code of “0”, “1”, or “2”. However, since uninjured passengers over the age of 4 are not captured at the Participant level, and we cannot merely sum the participant information to get the total number of vehicle occupants. Instead, we must rely on the values that the coder entered at the vehicle level, indicating how many total occupants were / were not using safety equipment, or for which the use of safety equipment is unknown. Those values are intended to capture information for all occupants, whether or not they were coded at the participant level. ODOT TOT_UNINJD_PER_CNT Total Un-injured Persons Integer 4 10 0 The number of all persons involved in the crash who were not injured. This derived field is calculated based on the total number of persons involved (TOT_PER_INVLV_CNT), minus the number of persons injured (TOT_INJ_CNT) and killed (TOT_FATAL_CNT). ODOT TOT_PED_CNT Total Pedestrians Integer 4 10 0 The number of pedestrians involved in this crash. This derived field is calculated based on the number of participant records where Participant Type is 3, 4 or 5. ODOT TOT_PED_FATAL_CNT Total Pedestrian Deaths Integer 4 10 0 The number of pedestrians killed as a result of this crash. This derived field is calculated based on the number of pedestrians (Participant Type = 3, 4 or 5.) in the crash that had a Participant Injury Severity value of 1 (Fatality). ODOT TOT_PED_INJ_CNT Total Pedestrian Injuries Integer 4 10 0 The number of pedestrians who were non-fatally injured in this crash. This derived field is calculated based on the number of pedestrians (Participant Type = 3, 4 or 5.) in the crash that had a Participant Injury Severity value of 2 (Major Injury), 3 (Intermediate Injury), or 4 (Minor Injury). ODOT TOT_PEDCYCL_CNT Total Pedal-cyclists Integer 4 10 0 The number of participants in a crash that were pedal-cyclists. This derived field is calculated based on the number of participants in the crash that have a Participant Type of 6 or 7. ODOT TOT_PEDCYCL_FATAL_CNT Total Pedal-cyclist Deaths Integer 4 10 0 The number of pedalcyclists killed as a result of the crash. ODOT TOT_PEDCYCL_INJ_CNT Total Pedal-cyclist Injuries Integer 4 10 0 The number of persons with a Participant Type = 6 or 7 (Pedal-cyclist) that were injured in this crash. This derived field is calculated based on the number of Pedal-cyclists (Participant Type = 6 or 7) in the crash that had a Participant Injury Severity value of 2 (Major Injury), 3 (Intermediate Injury), or 4 (Minor Injury). ODOT TOT_UNKNWN_CNT Total Unknown Non-Motorists Integer 4 10 0 The number of participants in a crash that were an unknown type of non-motorist. This derived field is calculated based on the number of participants in the crash that have a Participant Type of 9. ODOT TOT_UNKNWN_FATAL_CNT Total Unknown Non-Motorist Deaths Integer 4 10 0 The number of other or unknown non-motorist fatalities that occurred in this crash. This derived field is calculated based on the number of participant records where (Participant Type = 9) in the crash that had a Participant Injury Severity value of 1 (Fatality). ODOT TOT_UNKNWN_INJ_CNT Total Unknown Non-Motorist Injured Integer 4 10 0 The number of persons with a Participant Type = 9 (unknown non-motorist) that were injured in this crash. This derived field is calculated based on the number of Unknown Non-motorists (Participant Type = 9) in the crash that had a Participant Injury Severity value of 2 (Major Injury), 3 (Intermediate Injury), or 4 (Minor Injury). ODOT TOT_PER_INVLV_CNT Total Persons Involved Integer 4 10 0 The number of persons involved in the crash, including un-injured persons for whom no “participant” record is created. This derived value is computed based on the sum of the Total Pedestrian Count + Total Pedalcyclist Count + Total Unknown Count + Total Occupant Count. ODOT TOT_SFTY_EQUIP_USED_QTY Total Safety Equip Used Integer 4 10 0 The number of participants in a crash that were using available safety equipment at the time of the crash. This derived field is calculated based on two items: • The sum of the "Vehicle Safety Equipment Used Qty" on all vehicles that are coded in this crash, plus • The number of Pedalcyclists (Participant Type Code = “6”) where the value of the Safety Equipment Use Code = “6”, indicating that the Pedalcyclist properly used a helmet at the time of the crash. Other safety equipment usage by Pedalcyclists or safety equipment usage by Pedestrians (such as helmet usage by pedestrians using a skateboard) is not counted since that usage is not mandated by legislation. Note: It is assumed that the "Vehicle Safety Equipment Used Quantity" will include, at the minimum, all the Participants that have a Participant Type Code of 0, 1, or 2 that were correctly using available safety equipment. However, since uninjured passengers over the age of 4 are not captured at the participant level, we cannot merely sum the participant information to get the total number of vehicle occupants using safety equipment. Instead, we must rely on the values that the Coder entered at the vehicle level. That value is intended to capture information for all vehicle occupants, whether or not they were coded at the participant level. ODOT TOT_SFTY_EQUIP_UNUSED_QTY Total Safety Equip Un-used Integer 4 10 0 The number of participants in a crash for whom safety equipment was available at the time of the crash, but it was not used. This derived field is calculated based on two items: • The sum of the "Vehicle Safety Equipment Unused Qty" on all vehicles that are coded in this crash, plus • The number of Pedalcyclists (Participant Type Code = “6”) where the value of the Safety Equipment Use Code = “5”, indicating that the Pedalcyclist either did not use a helmet, or used one improperly at the time of the crash. The lack of other safety equipment usage by Pedalcyclists, or safety equipment usage by Pedestrians (such as helmets not being used by pedestrians using a skateboard) is not counted since that usage is not mandated by legislation. Note: It is assumed that the "Vehicle Safety Equipment Unused Quantity" will include, at the minimum, all the Participants that have a Participant Type Code of “0”, “1”, or “2” that were not using or were incorrectly using available safety equipment. However, since uninjured passengers over the age of 4 are not captured at the Participant level, we cannot merely sum the participant information to get the total number of vehicle occupants that were not using safety equipment. Instead, we must rely on the values that the coder entered at the vehicle level. That value is intended to capture information for all vehicle occupants, whether or not they were coded at the Participant level. ODOT TOT_SFTY_EQUIP_USE_UNKNWN_QTY Total Safety Equip Unknown if Used Integer 4 10 0 This element contains the total number of participants in a crash where it is not known (or not reported) if safety equipment was used. This derived field is calculated based on two items: • The sum of the "Vehicle Safety Equipment Use Unknown Qty" on all vehicles that are coded in this crash, plus • The number of Pedalcyclists (Participant Type Code = 6) where the value of the Safety Equipment Use Code = 9, indicating that it is unknown whether or not the Pedalcyclist used a helmet at the time of the crash. Other unknown safety equipment usage by Pedalcyclists or unknown safety equipment usage by Pedestrians (such as helmet usage by pedestrians using a skateboard) is not counted since that usage is not mandated by legislation. Note: It is assumed that the "Vehicle Safety Equipment Use Unknown Quantity" will include, at the minimum, all the Participants that have a Participant Type Code of 0, 1, or 2 for which the usage of safety equipment is unknown. However, since uninjured passengers over the age of 4 are not captured at the Participant level, we cannot merely sum the participant information to get the total number of vehicle occupants with unknown safety equipment usage. Instead, we must rely on the values that the Coder entered at the vehicle level. That value is intended to capture information for all vehicle occupants, whether or not they were coded at the Participant level. ODOT CRASH_MO_NO Crash Month String 2 0 0 Crash Date is an eight-digit field that describes the date on which the crash occurred, as recorded on the police accident report (PAR) or on the driver report. The format of the crash date field is MMDDYYYY, where MM equals the two-digit month, DD equals the two-digit day, and YYYY equals the four-digit century and year. The year is automatically inserted by the electronic data entry system, but may be modified by the Crash Data Technician. When the exact day of the crash is unknown and there is a missing persons report mentioned in the report, code the date the person went missing. If no missing persons report is mentioned, use the date of the police report. ODOT CRASH_DAY_NO Crash Day String 2 0 0 Crash Date is an eight-digit field that describes the date on which the crash occurred, as recorded on the police accident report (PAR) or on the driver report. The format of the crash date field is MMDDYYYY, where MM equals the two-digit month, DD equals the two-digit day, and YYYY equals the four-digit century and year. The year is automatically inserted by the electronic data entry system, but may be modified by the Crash Data Technician. When the exact day of the crash is unknown and there is a missing persons report mentioned in the report, code the date the person went missing. If no missing persons report is mentioned, use the date of the police report. ODOT CRASH_YR_NO Crash Year String 4 0 0 Crash Date is an eight-digit field that describes the date on which the crash occurred, as recorded on the police accident report (PAR) or on the driver report. The format of the crash date field is MMDDYYYY, where MM equals the two-digit month, DD equals the two-digit day, and YYYY equals the four-digit century and year. The year is automatically inserted by the electronic data entry system, but may be modified by the Crash Data Technician. When the exact day of the crash is unknown and there is a missing persons report mentioned in the report, code the date the person went missing. If no missing persons report is mentioned, use the date of the police report. ODOT CRASH_WK_DAY_CD Day of Week String 1 0 0 Day of the week the crash occured ODOT CRASH_CAUSE_1_CD Crash Cause 1 Code String 20 0 0 Cause is a two-digit code that represents the circumstance(s) most responsible for the occurrence of the crash. Enter the codes that explain why the crash happened, in the order of predominance. A Cause field is also available on the Vehicle and Participant Levels, to specify the vehicle or participant that precipitated the crash, when applicable. Each crash must have at least one Cause code entered on the Crash Level, but up to three are allowed. Code “5” is used when the vehicle is straddling the center line or driving on wrong side of an undivided two way road. Code “10” is used when a driver error was a factor in the crash, but no other cause code applies. Code “12” is used when improper driving was not a factor in the crash, and no other Cause code applies. For example: • Deer jumps out in front of vehicle, leaving driver no time to react • Passenger, animal or insect. etc., interfered with driver Code “15” is used when the vehicle is traveling on the wrong side of a divided roadway or traveling the wrong direction on a one way road. Code “34” is used only when the PAR states that the crash involved aggressive driving. It must not be used based solely on witness statements. Code “35” is used when collateral damage results from an act of road rage. Do not use this code when the collision is a road rage incident, which falls under Deliberate Intent. Road rage incidents are excluded from the Crash Data System. Do not use codes 34 or 35 without approval from the Code Team Leader. ODOT CRASH_CAUSE_1_LONG_DESC Crash Cause 1 Desc String 50 0 0 Description field for the [CRASH_CAUSE_1_CD] code field ODOT CRASH_CAUSE_2_CD Crash Cause 2 Code String 20 0 0 Cause is a two-digit code that represents the circumstance(s) most responsible for the occurrence of the crash. Enter the codes that explain why the crash happened, in the order of predominance. A Cause field is also available on the Vehicle and Participant Levels, to specify the vehicle or participant that precipitated the crash, when applicable. Each crash must have at least one Cause code entered on the Crash Level, but up to three are allowed. Code “5” is used when the vehicle is straddling the center line or driving on wrong side of an undivided two way road. Code “10” is used when a driver error was a factor in the crash, but no other cause code applies. Code “12” is used when improper driving was not a factor in the crash, and no other Cause code applies. For example: • Deer jumps out in front of vehicle, leaving driver no time to react • Passenger, animal or insect. etc., interfered with driver Code “15” is used when the vehicle is traveling on the wrong side of a divided roadway or traveling the wrong direction on a one way road. Code “34” is used only when the PAR states that the crash involved aggressive driving. It must not be used based solely on witness statements. Code “35” is used when collateral damage results from an act of road rage. Do not use this code when the collision is a road rage incident, which falls under Deliberate Intent. Road rage incidents are excluded from the Crash Data System. Do not use codes 34 or 35 without approval from the Code Team Leader. ODOT CRASH_CAUSE_2_LONG_DESC Crash Cause 2 Desc String 50 0 0 Description field for the [CRASH_CAUSE_2_CD] code field ODOT CRASH_CAUSE_3_CD Crash Cause 3 Code String 20 0 0 Cause is a two-digit code that represents the circumstance(s) most responsible for the occurrence of the crash. Enter the codes that explain why the crash happened, in the order of predominance. A Cause field is also available on the Vehicle and Participant Levels, to specify the vehicle or participant that precipitated the crash, when applicable. Each crash must have at least one Cause code entered on the Crash Level, but up to three are allowed. Code “5” is used when the vehicle is straddling the center line or driving on wrong side of an undivided two way road. Code “10” is used when a driver error was a factor in the crash, but no other cause code applies. Code “12” is used when improper driving was not a factor in the crash, and no other Cause code applies. For example: • Deer jumps out in front of vehicle, leaving driver no time to react • Passenger, animal or insect. etc., interfered with driver Code “15” is used when the vehicle is traveling on the wrong side of a divided roadway or traveling the wrong direction on a one way road. Code “34” is used only when the PAR states that the crash involved aggressive driving. It must not be used based solely on witness statements. Code “35” is used when collateral damage results from an act of road rage. Do not use this code when the collision is a road rage incident, which falls under Deliberate Intent. Road rage incidents are excluded from the Crash Data System. Do not use codes 34 or 35 without approval from the Code Team Leader. ODOT CRASH_CAUSE_3_LONG_DESC Crash Cause 3 Desc String 50 0 0 Description field for the [CRASH_CAUSE_3_CD] code field ODOT CRASH_EVNT_1_CD Crash Event 1 Code String 20 0 0 Event is a three-digit code that describes an incident or situation contributing to or involved in the crash. Events generally represent occurrences of injury or damage to a person or property, but they may also identify other crash factors. On the Crash Level, enter the Events that relate to the overall crash, in the order of occurrence. Up to three Event codes are allowed. If more than three events occur, code the three most significant events in relation to the crash. Code 103 – Work Zone Worker may be pedestrians, motor vehicle occupants, or “other non-motorist” if using equipment inside barriers or off road. Code the Participant Type field accordingly, and use code 103 in the Participant Event field as well, to enable reporting of Work Zone Worker attributes (i.e. gender, age, non-motorist location, etc.) Events specific to Vehicles and Participants are specified on those levels as well, for reporting purposes. ODOT CRASH_EVNT_1_LONG_DESC Crash Event 1 Desc String 75 0 0 Description field for the [CRASH_EVNT_1_CD] code field ODOT CRASH_EVNT_2_CD Crash Event 2 Code String 20 0 0 Event is a three-digit code that describes an incident or situation contributing to or involved in the crash. Events generally represent occurrences of injury or damage to a person or property, but they may also identify other crash factors. On the Crash Level, enter the Events that relate to the overall crash, in the order of occurrence. Up to three Event codes are allowed. If more than three events occur, code the three most significant events in relation to the crash. Code 103 – Work Zone Worker may be pedestrians, motor vehicle occupants, or “other non-motorist” if using equipment inside barriers or off road. Code the Participant Type field accordingly, and use code 103 in the Participant Event field as well, to enable reporting of Work Zone Worker attributes (i.e. gender, age, non-motorist location, etc.) Events specific to Vehicles and Participants are specified on those levels as well, for reporting purposes. ODOT CRASH_EVNT_2_LONG_DESC Crash Event 2 Desc String 75 0 0 Description field for the [CRASH_EVNT_2_CD] code field ODOT CRASH_EVNT_3_CD Crash Event 3 Code String 20 0 0 Event is a three-digit code that describes an incident or situation contributing to or involved in the crash. Events generally represent occurrences of injury or damage to a person or property, but they may also identify other crash factors. On the Crash Level, enter the Events that relate to the overall crash, in the order of occurrence. Up to three Event codes are allowed. If more than three events occur, code the three most significant events in relation to the crash. Code 103 – Work Zone Worker may be pedestrians, motor vehicle occupants, or “other non-motorist” if using equipment inside barriers or off road. Code the Participant Type field accordingly, and use code 103 in the Participant Event field as well, to enable reporting of Work Zone Worker attributes (i.e. gender, age, non-motorist location, etc.) Events specific to Vehicles and Participants are specified on those levels as well, for reporting purposes. ODOT GIS_PRC_DT GIS Processing Date String 10 0 0 The date when the GIS team processed the crash database table into a spatial (GIS) format ODOT EFFECTV_DT Effective Date String 4 0 0 The year the crash is effective for ODOT TOT_PDO_CNT Total Property Damage Only Integer 4 10 0 Indicates with either a 1 (yes) or 0 (no) if the crash that occured was property damage only (no injuries). This field is added by Washington County Traffic Engineering as part of the Safety Priority Index System (SPIS) calculation and scoring. A crash is counted as a '1' if there are no injuries or fatalities involved in the crash. So, it is basically: If TOT_FATAL_CNT=0 and TOT_INJ_LVL_A_CNT=0 TOT_INJ_LVL_B_CNT=0 and TOT_INJ_LVL_C_CNT = 0 Then TOT_PDO_CNT = '1' Else TOT_PDO_CNT = '0' Washington County CRASH_EVNT_3_LONG_DESC Crash Event 3 Desc String 75 0 0 Description field for the [CRASH_EVNT_3_CD] code field ODOT 20190619 EPSG 6.13(9.0.0) Traffic Engineering GIS Analyst Washington County, Department of Land Use & Transportation, Traffic Engineering GIS Analyst