HIGHWAY SAFETY INFORMATION SYSTEM
GUIDEBOOK FOR THE OHIO STATE DATA FILES

Prepared by

Forrest M. Council
University of North Carolina
Highway Safety Research Center
730 Airport Road, Suite 300
CB #3430
Chapel Hill, NC 27599-3430

Yusuf M. Mohamedshah
Rushi B. Patel
LENDIS Corporation
6300 Georgetown Pike
McLean, VA 22101

Prepared for
Federal Highway Administration
Office of Safety and Traffic Operations Research & Development
U.S. Department of Transportation
Washington, DC 20590

January 2004

Table of Contents

• INTRODUCTION
• DETAILS OF MAJOR FILES
  • The Accident File
  • The Roadway Inventory files
  • The Roadlog File
  • The Curve File
  • The Grade File
  • The Angle Points File
  • The Points File
  • Traffic Monitoring Procedures
  • Issue Related To Merging Of Files
• OHIO CONTACTS
• COMPOSITE LIST OF VARIABLES FOR ALL OHIO HSIS FILES
• ACCIDENT FILE
  • Accident Subfile
  • Vehicle Subfile
  • Injured Occupants Subfile
• ROADLOG SUBFILE
• POINT SUBFILE
• CURVES SUBFILE
• GRADES SUBFILE
• ANGLE POINT SUBFILE

INTRODUCTION

The Ohio data system that is provided to HSIS includes the following basic files:

• Accident data (Accident, vehicle and occupant)
• Roadway Inventory File
• State Supplemental Inventory, containing curve and grade data
• “Points” File (intersections, railroad grade-crossings, underpasses, etc.)

Data from all of these files are captured by HSIS. Raw file data are provided to the Highway Safety Research Center where they are retained as backup information. The documentation (variable listings, definitions, etc) for these raw files and for the SAS files that are developed from them is available at FHWA offices. The conversion programs developed by HSRC and LENDIS to convert the files into SQL and SAS formats are also available at the HSIS offices at FHWA.

Beginning in 1994, the HSIS system was converted to a relational database for internal use. This database, using a SYBASE system, stores the data received from Ohio and other states, and the data files for a given state are linked and manipulated using SQL language. However, this conversion from the original SAS-based system to the newer relational system is somewhat transparent to the end-user of the data since the output files produced by SYBASE for modeling and analysis will be SAS-formatted. (For user convenience, HSIS staff can convert these SAS output files into ASCII, Excel, dBase, etc.) As in the past, we have continued to produce SAS format libraries for each of the variables in each of the files. Because it is envisioned that the majority of analyses will utilize these SAS files and formats, this Guidebook will concern these SAS files – their formats, completeness, and quality. While single-variable tables for key variables from each file were published in the past as “Volume II”, this is no longer the case. Users may request specific single- or multiple-variable tables through the HSIS “Data Request” procedure found on this web site.

As noted above, the SAS accident data is in three separate subfiles, the first containing the basic accident information on a case-by-case basis, and then separate files containing information on vehicles and occupants in each accident case. The vehicle and occupant data can be linked to the basic accident data for specific cases using the accident case number. The accident subfile can be linked to the Roadlog file using three common variables – county, route number, and milepost.

Unlike an Accident file record that is referenced to a point on the roadway, each record on the Roadlog file contains information on a homogenous section of the roadway (i.e. a stretch of road which is consistent in terms of certain characteristics), with each new section being defined by a new beginning reference point. Each record on this Roadlog file contains current characteristics of the road system including surface type and width, shoulder and median information, lane information, etc. Information on curves and grades is captured in separate curve and grade files. The Curve File has data on all horizontal curves while the Grade File has information on grades greater than 3 percent. For curves having a degree of curvature greater than 90 degrees, Ohio designates them as “angle points” and that data is captured in a separate Angle Point File. Ohio doesn’t maintain a separate intersection inventory file. However, a “Points” file is available that contains point descriptors for a number of items including at-grade intersections, overpasses, underpasses, bridges etc.

Details of these accident and roadlog files are presented in the following section.

DETAILS OF MAJOR FILES

The Accident File

An accident is reported if it involves a personal injury or total property damage of $400 or more. However, in some cases crashes with damages below $400 are also recorded on accident report forms. The Ohio State Highway Patrol (SHP) and the local sheriff’s offices do most of the crash reporting in Ohio. Ohio doesn’t include accidents reported by citizens in their system. All police reports statewide are sent to the Ohio Department of Public Safety. Prior to 1997, the Department of Public safety was responsible for keypunching and location coding the accidents (after performing QC checks). After 1997, this task was outsourced to private contractors. (Note that 1997 is the first year of Ohio data in the HSIS system.)

All agencies across Ohio use the same accident report form to report accidents. A new form with major changes was introduced in 2000. In addition to this, as noted above, the State Highway Patrol began to outsource the data coding to private contractors in 1997. According to Ohio DOT staff, this may result in 2000 data being less accurate than in other years. Efforts are underway to convert 2000 data to old formats and make the data usable. Eventually, all the old data, even pre-2000 data, will be converted to new formats and made available. Presently, Ohio DOT has not determined when this will be accomplished. Hence the current HSIS captures three years of accident data, 1997 – 1999.

Approximately 375,000 crashes occur in Ohio statewide each year. The HSIS data set contains a subset of these accidents that occurred on the state-inventoried system. This data set includes between 65,000 - 70,000 accidents per year, between 120,000 - 127,000 vehicles per year and between 177,000 - 182,000 occupants per year for 1997, 1998 and 1999. Police officers reporting accident locate them within 0.01 miles of a given milepost. There are physical mileposts available on all rural state routes and some county routes, and on Interstates in all incorporated areas. It is estimated that about 10% of the accidents in the accident subfiles cannot be matched to segments on the roadlog file. Ohio DOT suspects outsourcing of the location coding to be the main reason for this. Since the majority of the HSIS analyses involve linkage with roadway data, a decision was made to delete these accidents from the accident subfiles. This results in approximately a 10 percent reduction in the total number of accidents (and vehicle and occupants) in the files.

In general, Ohio accident files capture information on all relevant variables. Our discussions with Ohio DOT staff revealed that they think the police make some errors in coding the angle, left turn, and head on crashes at intersections. They expect the new accident report forms being used in 2000 and later will correct this shortcoming since it provides a sequence of events and pre-crash maneuvers/directions. Also, due to the change in accident report form in 2000, a number of variables will be changed or added in the Ohio accident files in subsequent years.

Approximately 70 percent of the accidents on the linkable file are property damage only and 0.7 percent are fatal accidents. Approximately 53 percent vehicles are multi-vehicle in nature, while the remaining 47 percent are single-vehicle accidents of one type or the other.

An assessment of the completeness and accuracy of the data is based on conversations with OH staff and a series of single-variable tabulations run each year for key analysis variables. These quality-control runs allows the HSIS staff to examine both the percent uncoded for each variable and changes across time in the individual codes within each key variable. These yearly runs are performed on all formatted variables. These runs have consistently indicated that almost all of the variables in the three subfiles have very few uncoded and very few error codes. Where high numbers of uncoded cases or inconsistencies in codes are found, a “NOTE” has been included under the pertinent variable in the later SAS format sections.

In addition to the quality-control checks noted above, in order to further check the accuracy of some of the accident variables, a series of comparisons were made of variables that should have been somewhat similar on the accident subfiles according to their definitions (both within the same subfiles and across subfiles). For example, NUMPEDS variable is populated largely only when ACCTYPE is pedestrian. Again, if there are any cases in which variables are either less than totally consistent with other variables or have changed across time, a “NOTE” will be included in the SAS formats section that follows.

The Roadway Inventory files

The Ohio roadway inventory files contain current characteristics of the state road system for each year. These data are divided into five files within the HSIS system. The first is the basic roadway characteristics file (i.e. the “Roadlog”) containing information on the roadway mainline cross-section. The second is a Curve File, which contains information on each horizontal curve on any inventoried segments (except for curves of degree greater than 90 – see below). The third is the Grade File, which contains information on each vertical grade that is greater than 3 percent. Fourth is the Angle Points File, which has information on those curves that have a degree of curvature greater than 90 degrees. And fifth is the Points File, which contains point descriptors for a number of items such as at-grade intersections, railroad grade-crossings, etc. Ohio provides the curve and grade information in a single inventory file named “State Supplemental Inventory.” HSIS staff processes this inventory file and creates three separate files -- the curve file, the grade file and the angle point file. All the roadway inventory files are developed by the ODOT staff based on as-built plans. Updates on the file are done based on the respective project plans. In general the ODOT Roadway inventory office feels that the data is quite accurate.

The Roadlog File

The ODOT Roadway Inventory section of the Office of Technical services is responsible for maintaining inventory of all public highway in Ohio, about 116,000 miles in total. Of these, there is detailed inventory information on approximately 19,500 miles of roadway, which is captured by HSIS and is shown in Table 1 below. This includes all functional classes of roads within the state system – Freeways, Arterials and collector, both rural and urban. This file contains information on approximately 1,500 miles of Interstates, 4,000 miles of U.S. Routes and 14,000 miles of State Routes. Currently there are five roadlog inventory files in the HSIS system, 1997 – 2001. (Note that the matching 2000 and 2001 accident data will be added to HSIS when received from ODOT.) Because a new record is generated each time any of the items in the file changes, the sections that are generated are fairly short, resulting in a large number of individual records. The approximately 19,500 miles of inventory information is divided into approximately 26,000 records, resulting in an average section length of 0.75 miles.

The file contains general cross section information related to travel way widths (indicated by surface widths and roadway widths), number of lanes, median width and other variables. All standard cross-section variables appear to be present except for individual measures of shoulder width (paved and unpaved) and shoulder type for each side (inside and outside) of the roadway in the 1997-2000 data. For these years, the total shoulder width for both sides can be calculated based on “Surface Width” and “Roadway Width” but not distributed to each side. From 2001 onwards, new variables are added that give inside and outside shoulder widths. Thus it is important to note here that the shoulder width variables available in the HSIS file are not populated for 1997 – 2000 data.

It is noted that in some cases, OH data has two different variables providing the same information. For example, surface type is described by the two different variables SURF_TYP and SRF_TYPF. This is because OH collects some additional variables that are required by FHWA for HPMS reporting or other purposes. Data analysis by HSIS staff and conversations with ODOT staff revealed that in general, where two variables explain the same characteristic, the non-FHWA required variable is more detailed and reliable due to the updating system. The only exception is for “access control,” where ODOT recommended the use of the FHWA variable. Appropriate notes are provided under each of these variables in the formats section that follows.

Unlike most states, OH data contains both the standard location variables -- County / Route / Beginning and Ending Mileposts -- and a link/node linear referencing system for each segment. However, since the crashes do not have link/node indicators, county/route/milepost is still used to locate the crashes on an individual roadway segment. The link/node referencing system allows the state to track and update information easily and accurately.

Traffic information in the form of Average Daily Traffic is included for each section on the file. This information is covered by three variables -- total AADT, AADT for passenger cars and trucks type A; and AADT for truck types B and C. A detailed description of the traffic count procedures in included below in the section “Traffic Monitoring Procedures.”

Two new variables, RODWYCLS and MVMT, have been created by HSIS staff in the roadway segment file of each of the HSIS states. The RODWYCLS (Roadway Class) variable is based on the combination of rural/urban, access control, number of lanes and median type variables. This variable classifies each roadway segment into one of ten roadway types described in the later “Format” section. This variable is also included as an accident-file variable by matching each crash to its corresponding roadway segment. The MVMT variable (Million Vehicle Miles of Travel) is calculated for each segment in the roadway file by multiplying the segment length, AADT and 365 days in a year, and dividing by one million. Both these variables were created in response to inquiries from data users, whose most frequent questions have concerned either crash frequencies or rates (per MVMT) for one or more of these roadway classes.

To assess the accuracy of roadway inventory variables in this roadlog file and the related files concerning points, curves and grades, we questioned the ODOT staff and examined a series of single-variable tables for key variables in each of the files. The ODOT staff feels that the overall quality of the variables in all the three files is very high. It should be noted that the data developed by ODOT is based on as-built plans and is updated systematically each year. Project plans are used for these updates. In addition, a field person in each highway district completes a “field sheet” to verify changes in the system each year and these are sent to the Roadway Inventory group for use in the computer file updates. This is a more extensive update system than in most HSIS states.

In addition to information received from ODOT staff, single-variable tabulations were run to examine the questions of reporting completeness and data accuracy. Here, study of percentage of “unknown”, “not applicable” and “not stated” values for more than 30 key variables in the Roadlog file indicate that, in general, the data are coded to a high degree of completeness. For most variables, there were no missing data. The data also appear to be quite consistent across years, and similar variables appear to have similar values. We also attempted to determine if there was consistency between pairs of similar variables found in the Inventory File. In general, there was. For example, the total mileage for divided highways appeared to be consistent with total mileage for segments having a valid median width. Notes are included for those few variables that were found to be inconsistent in the format section of the guidebook.

In general, based on both the interviews and the data comparisons conducted, the data are felt to be quite accurate. In the limited number of cases where possible inaccuracies or missing values were found or where more detailed definitions might be critical in future analyses, notes are included under the specific variables in the later format section.

The Curve File

The Curve File contains information on all horizontal curves present on the 19,500 miles of inventoried data present in the roadlog file. The total length of all curves present in this file is about 1,150 miles, which is captured by approximately 18,500 records, resulting in an average curve length of approximately 0.06 miles. The file currently contains information on curve length, degree of curve and direction of curve. The inventory group is currently examining the possibility of collecting ball-bank data for future inclusion. A segment on this file can be located using the begin milepost, end milepost, county, route number and station equation information – similar to the roadlog file. Again, as-built plans are used to create this file and project plans to update information, similar to what is followed for all the five roadway inventory files. Our discussions with Ohio staff indicated that, though the quality of data may be slightly inferior compared to the cross-section data, it is free of any major shortcomings.

The Grade File

The Grade File has information on all vertical grades greater than 3 percent. Total length of all grades present in this file is about 2,340 miles, which is captured by approximately 20,000 records, resulting in an average grade length of approximately 0.11 miles. The file currently contains information on the grade length, direction of grade and percent of grade. This file can be linked to the other files using the same location variables – county, route number, begin milepost, end milepost and station equation. Since the curve file and grade file are developed from the same inventory, the way in which these files are created and updated and the data quality are similar.

The Angle Points File

Sharp horizontal curves having degree of curvature greater than 90 degrees are designated by ODOT as “angle points”. All variables and the manner in which the file is developed remain similar to that of the Curve File. While even these sharp curves would have some curve length in reality, the segment length in this file is set to zero for all the records.

The Points File

Ohio doesn’t have a computerized intersection inventory file but has a “Points” file that contains point descriptors for a number of features including at-grade intersections, overpasses, underpasses, bridges, railroad crossings etc. The file has approximately 35,000 intersections, 3,600 interchanges, 4,700 bridges and 1,300 railroad grade-crossings.

For intersections and interchanges, the file contains a mainline milepost for all state-system crossing routes (i.e., all intersections or interchanges where an Interstate, State Route or U. S. Route crosses an Interstate, State Route or U. S. Route), and a mainline milepost for many intersections where a state-system road intersects with a county or local road or street. ODOT staff are continually updating the file by adding additional intersections with city or county crossing roads, but the file cannot be yet considered a census of all intersections. For all intersection of two state-system roads, there is location information for both the mainline and the crossing route, which makes it possible to link to roadlog inventory information (and accident information) on both intersecting routes. There is no information on signalization, channelization, type of intersections/interchanges etc. Ohio is making efforts to include this information in the future. There are approximately 63 interstate-to-interstate junctions, 3,200 state-to-state and 300 US route-to-US route intersections. Like all other roadway inventory file, this file has been developed from as-built plans and updated based on project plans.

Traffic Monitoring Procedures

The Traffic Monitoring Section of the Office Of Technical Services is in charge of collecting traffic counts information. This information is covered by three variables – total AADT, AADT for passenger vehicles, and AADT for medium and large trucks. These data are based on a combination of permanent counters that count traffic 24-hours each day for 365 days each year and a series of short-term counts conducted each year. Ohio has 47 automatic traffic recorders (ATRs) recording 24-hour, full-year data by vehicle class / length categories. There are 16 additional vehicle-length and classification sites, and 37 weight-in-motion sites. These data are used to develop seasonal and daily adjustment factors for the 11,500 short counts that are done on a three- year cycle. Each short count is for 48 hours. Ohio attempts to collect vehicle classification data during these short counts also. At times, only volume data is collected and the 48-hour period is shortened. In some cases only the number of axle impulses are counted. The ODOT districts are responsible for doing these short counts.

To convert the short-term coverage counts to AADT, Ohio applies adjustments for seasonal differences in the daily traffic. For seasonal corrections, each coverage count location is assigned to one of the functional classes where permanent counters are located. The seasonal factors are based on averages from all ATRs in that group. Thus Ohio adjusts short-term counts to AADT using seasonal adjustment factors for each functional class.

When a road section is not counted during a given year, annual adjustment factors are developed and applied to the most recent prior year’s count. Ohio develops two types of annual adjustment factors – one that can be applied from year to year and second that is a cumulative adjustment factor that can be applied from any given year to the current year. Average growth factors are created each year for each functional class of roadway using ATR data and data from short counts for the current year. The adjustment factor applied to a particular uncounted section is based on its functional class. For sections where no prior AADT exists, AADT/mile averages by functional class are developed and then used in order to “fill in” the AADTs.

As noted earlier, some of the short AADT counts measure only the number of axles passing a particular location. To adjust that to the actual volume at that location, axle correction factors are applied. Axle correction factors are calculated by combining data from Automatic Traffic Recorders (ATR’s) and 48-hour vehicle classification counts. An average axle correction factor is calculated for each functional classification of highway. These factors are obtained by computing the total number of axles crossing a point and dividing that by the total number of vehicles. These factors are then applied to those short term AADT counts, which collects only the number of axles to get a count of the number of vehicles passing that section.

Significant improvements have been made in the quality and coverage of traffic data since 1997. There are some location-to-location differences in vehicle classifications in the short-term counts due to difference in vendor equipment, but they are moving to standardization. In general Ohio DOT staff is confident about the quality of traffic data.

Issue Related To Merging Of Files

As noted above, the accident data are subdivided into three subfiles – accident, vehicle and occupant. The Accident and Vehicle Subfiles can be linked together using the accident report number (i.e., CASENO). When linking the occupant subfile, the additional linking variable related to vehicle number (i.e., VEHNO) must match so that the occupants are associated with the vehicle in which they were traveling. To link vehicles with accidents, first sort both subfiles by CASENO. To link the Occupant file with the other two subfiles, first sort both the Vehicle subfile and Occupant subfile by case number and vehicle number. Next sort the Accident subfile by case number. Alternatively, the separate subfiles can be linked by specifying as SQL JOIN operation with the constraining condition that case number and vehicle number from each table are equal. SQL processing does not require the data to be pre-sorted and the output will not be in any particular sort order unless ORDER BY is specified.

The Accident Subfile can be linked to the Roadlog File using the CNTYRTE and MILEPOST variables in the crash record, and the CNTY_RTE, BEGMP and ENDMP variables in the Roadlog File. (Note that the “station equation” is included as part of county-route in the HSIS variables.) Similarly, the accident subfiles can be linked to Curve, Grade, and Angle Points using similar variables found in each respective file. To link the Accident File and the Points File, CNTYRTE and MILEPOST variables from the Accident file are matched with CNTY_RTE and MILEPOST variables of the Points File. To extract data on the intersecting (crossing) state-system route in the Points File, the Roadlog File can be linked to the XMILEPST and XCNTYRTE variables.

To prepare the Accident Subfile for linking with the Roadlog File using a SAS data step process, the analyst must sort both the Accident and the Roadway File into location order by CNTYRTE and MILEPOST on the Accident file and by CNTY_RTE and BEGMP on the roadlog file. Similar sorts would be done with other files to be merged. For the alternative SQL join, the analyst must specify an exact match on CNTYRTE and a range match where MILEPOST occurs between BEGMP and ENDMP. (Programs to accomplish this merging and division are available from HSIS staff at FHWA).

Finally, where appropriate and possible, a format that defines categories within a given variable has been developed for HSIS SAS variables. These categories are shown in the pages below. If you are an SAS user and wish to receive a formatting program that includes these SAS formats (with linkage to the pertinent variable name), please request these from the HSIS staff who provide the data file to you.

Ohio Contacts

State Computer files – Tom Ramsay (614) 752-5757

Mr. Ramsay is our main contact within the State of Ohio when questions arise concerning the Ohio state data files in general or the specifics of the accident data. He works within the Office of Roadway Safety and Mobility of the Ohio DOT. He should be the primary contact for all questions, and will direct questions he can’t answer to others.

Crash data and file linkage – Shirley Shokouhi (614) 644-8181

Ms. Shokouhi is the Systems Analyst in the Office of System Analysis and Planning who is responsible for Ohio DOT’s high crash location efforts and other safety-related analyses. As such, she is very knowledgeable about both the crash data and the linkage of crash data with other ODOT files.

Roadway Inventory data – Joe Hausman (614) 752-5732

Mr. Hausman is Section Manager, Roadway Inventory, within the ODOT Office of Technical Services. He is responsible for roadway inventory operations and files for all roadways in Ohio, and is the primary contact for details of the five ODOT inventory subfiles within the HSIS system. Additional information on the ODOT inventory data can be found at http://www.dot.state.oh.us/techservsite/offceorg/roadwayinfo/roadwayinfo.htm

COMPOSITE LIST OF VARIABLES FOR ALL OHIO HSIS FILES

ACCIDENT FILE

Accident Subfile

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO ACCIDENT SUBFILE

NOTE: SAS variable names and longer explanatory names are shown above each listing. (See Discussion for in formation on SAS formats.)

ACC_DATE

ACCIDENT DATE

NON-LABELED VARIABLE – Year/Month/Date of accident (YYYYMMDD)

ACCESS

ACCESS CONTROL

• 'N' = 'NO CONTROL OF ACCESS'
• 'L' = 'LIMITED CONTROL OF ACCESS'
• 'F' = 'FULL CONTROL OF ACCESS'
• ' ' = 'NOT CODED'

NOTE: Access control as defined by OH state. For example, ‘F’ indicates that Ohio DOT owns the access control and can change it whenever deemed required. The use of this variable may result in some difficulties and we recommend the use of FED_ACES, available in the roadlog file to get information on the access control of segments.

ACCTYPE

TYPE OF CRASH(FIRST HARMFUL EVENT)

• 00 = 'NOT-STATED'
• 01 = 'HEAD-ON'
• 02 = 'REAR-END'
• 03 = 'BACKING'
• 04 = 'SIDESWIPE-MEETING'
• 05 = 'SIDESWIPE-PASSING'
• 06 = 'ANGLE'
• 07 = 'PARKED-VEHICLE'
• 08 = 'PEDESTRIAN'
• 09 = 'ANIMAL'
• 10 = 'TRAIN'
• 11 = 'PEDALCYCLES'
• 12 = 'OTHER-NON-VEHICLE'
• 13 = 'FIXED-OBJECT'
• 14 = 'OTHER-OBJECT'
• 15 = 'FALLING-FROM-OR-IN-VEHICLE'
• 16 = 'OVERTURNING'
• 17 = 'OTHER-NON-COLLISION'

ACCYR

ACCIDENT YEAR

NON-LABELED VARIABLE – Year of Accident (YYYY)

ANGLE

TURN CRASH INDICATOR (GENERATED)

• 0 = 'NO TURN, NO ANGLE,OR NOT APPLICABLE'
• 1 = 'ANGLE COLLISION'
• 2 = 'ONE OR MORE VEH. TURNING FROM SAME DIRECTION'
• 3 = 'ONE OR MORE VEH. TURNING FROM OPPOSITE DIRECT'

ANIMAL

ANIMAL TYPE

• 0 = 'ANIMAL NOT STATED'
• 1 = 'DEER-HIT'
• 2 = 'FARM-ANIMAL-HIT'
• 3 = 'OTHER-ANIMAL'

CASENO

UNIQUE ACCIDENT CASE NUMBER

NON-LABELED VARIABLE – Accident Case Number

NOTE: digits 1-4 = YEAR OF ACCIDENT

CNTYRTE

COUNTY ROUTE

NON-LABELED VARIABLE – Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STATE_EQ

COUNTY

COUNTY CODE

• 'ADA' = 'ADAMS'
• 'ALL' = 'ALLEN'
• 'ASD' = 'ASHLAND'
• 'ATB' = 'ASHTABULA'
• 'ATH' = 'ATHENS'
• 'AUG' = 'AUGLAIZE'
• 'BEL' = 'BELMONT'
• 'BRO' = 'BROWN'
• 'BUT' = 'BUTLER'
• 'CAR' = 'CARROLL'
• 'CHP' = 'CHAMPAIGN'
• 'CLA' = 'CLARK'
• 'CLE' = 'CLERMONT'
• 'CLI' = 'CLINTON'
• 'COL' = 'COLUMBIANA'
• 'COS' = 'COSHOCTON'
• 'CRA' = 'CRAWFORD'
• 'CUY' = 'CUYAHOGA'
• 'DAR' = 'DARKE'
• 'DEF' = 'DEFIANCE'
• 'DEL' = 'DELAWARE'
• 'ERI' = 'ERIE'
• 'FAI' = 'FAIRFIELD'
• 'FAY' = 'FAYETTE'
• 'FRA' = 'FRANKLIN'
• 'FUL' = 'FULTON'
• 'GAL' = 'GALLIA'
• 'GEA' = 'GEAUGA'
• 'GRE' = 'GREENE'
• 'GUE' = 'GUERNSEY'
• 'HAM' = 'HAMILTON'
• 'HAN' = 'HANCOCK'
• 'HAR' = 'HARDIN'
• 'HAS' = 'HARRISON'
• 'HEN' = 'HENRY'
• 'HIG' = 'HIGHLAND'
• 'HOC' = 'HOCKING'
• 'HOL' = 'HOLMES'
• 'HUR' = 'HURON'
• 'JAC' = 'JACKSON'
• 'JEF' = 'JEFFERSON'
• 'KNO' = 'KNOX'
• 'LAK' = 'LAKE'
• 'LAW' = 'LAWRENCE'
• 'LIC' = 'LICKING'
• 'LOG' = 'LOGAN'
• 'LOR' = 'LORAIN'
• 'LUC' = 'LUCAS'
• 'MAD' = 'MADISON'
• 'MAH' = 'MAHONING'
• 'MAR' = 'MARION'
• 'MED' = 'MEDINA'
• 'MEG' = 'MEIGS'
• 'MER' = 'MERCER'
• 'MIA' = 'MIAMI'
• 'MOE' = 'MONROE'
• 'MOT' = 'MONTGOMERY'
• 'MRG' = 'MORGAN'
• 'MRW' = 'MORROW'
• 'MUS' = 'MUSKINGUM'
• 'NOB' = 'NOBLE'
• 'OTT' = 'OTTAWA'
• 'PAU' = 'PAULDING'
• 'PER' = 'PERRY'
• 'PIC' = 'PICKAWAY'
• 'PIK' = 'PIKE'
• 'POR' = 'PORTAGE'
• 'PRE' = 'PREBLE'
• 'PUT' = 'PUTNAM'
• 'RIC' = 'RICHLAND'
• 'ROS' = 'ROSS'
• 'SAN' = 'SANDUSKY'
• 'SCI' = 'SCIOTO'
• 'SEN' = 'SENECA'
• 'SHE' = 'SHELBY'
• 'STA' = 'STARK'
• 'SUM' = 'SUMMIT'
• 'TRU' = 'TRUMBULL'
• 'TUS' = 'TUSCARAWAS'
• 'UNI' = 'UNION'
• 'VAN' = 'VAN WERT'
• 'VIN' = 'VINTON'
• 'WAR' = 'WARREN'
• 'WAS' = 'WASHINGTON'
• 'WAY' = 'WAYNE'
• 'WIL' = 'WILLIAMS'
• 'WOO' = 'WOOD'
• 'WYA' = 'WYANDOT'

DIR_REF

DIRECTION FROM REFERENCE

• ' ' = 'NOT STATED'
• 'E' = 'EAST'
• 'N' = 'NORTH'
• 'S' = 'SOUTH'
• 'W' = 'WEST'

DIST_OFF

DISTANCE OFFSET

NON-LABELED VARIABLE

DISTRICT

DISTRICT

NON-LABELED VARIABLE

DIV_CODE

ROAD IDENTIFICATION

• 'D' = 'DIVIDED'
• 'U' = 'UNDIVIDED'

FAULT

VIOLATOR

• 1 = 'VEHICLE 1 AT FAULT'
• 2 = 'VEHICLE 2 AT FAULT'
• 3 = 'VEHICLE 3 AT FAULT'
• 4 = 'VEHICLE 4 AT FAULT'
• 5 = 'VEHICLE 5 AT FAULT'
• 6 = 'VEHICLE 6 AT FAULT'
• 7 = 'VEHICLE 7 AT FAULT'
• 8 = 'VEHICLE 8 AT FAULT'
• 9 - 97 = 'VEHICLES 9 TO 97 AT FAULT'
• 98 = 'NO FAULT DETERMINED'
• 99 = 'ANIMAL AT FAULT'

FIPSMUNI

FIPS CODE

NON-LABELED VARIABLE

FLIP_IND

INDICATES DUPLICATE RECORD GENERATION

• 0 = 'NONE'
• 1 = 'ORIGINAL RECORD'
• 2 = 'CROSS ROUTE DUPLICATE'

FUNCLS

FUNCTIONAL CLASSIFICATION

• '01' = 'Principal Arterial - Interstate (Rural)'
• '02' = 'Principal Arterial - Other (Rural)'
• '06' = 'Minor Arterial (Rural)'
• '07' = 'Major Collector (Rural)'
• '08' = 'Minor Collector (Rural)'
• '09' = 'Local (Rural)'
• '11' = 'Principal Arterial - Interstate (Urban)'
• '12' = 'Principal Arterial - Other Freeways and Expressway (Urban)'
• '14' = 'Principal Arterial - Other(Urban)'
• '16' = 'Minor Arterial (Urban)'
• '17' = 'Collector (Urban)'
• '19' = 'Local (Urban)'
• ' ' = 'OTHERWISE'

HOUR

HOUR OF DAY

• 00 = '12:00 MIDNIGHT - 12:59 AM'
• 01 = ' 1:00 AM - 1:59 AM'
• 02 = ' 2:00 AM - 2:59 AM'
• 03 = ' 3:00 AM - 3:59 AM'
• 04 = ' 4:00 AM - 4:59 AM'
• 05 = ' 5:00 AM - 5:59 AM'
• 06 = ' 6:00 AM - 6:59 AM'
• 07 = ' 7:00 AM - 7:59 AM'
• 08 = ' 8:00 AM - 8:59 AM'
• 09 = ' 9:00 AM - 9:59 AM'
• 10 = '10:00 AM - 10:59 AM'
• 11 = '11:00 AM - 11:59 AM'
• 12 = '12:00NOON- 12:59 PM'
• 13 = ' 1:00 PM - 1:59 PM'
• 14 = ' 2:00 PM - 2:59 PM'
• 15 = ' 3:00 PM - 3:59 PM'
• 16 = ' 4:00 PM - 4:59 PM'
• 17 = ' 5:00 PM - 5:59 PM'
• 18 = ' 6:00 PM - 6:59 PM'
• 19 = ' 7:00 PM - 7:59 PM'
• 20 = ' 8:00 PM - 8:59 PM'
• 21 = ' 9:00 PM - 9:59 PM'
• 22 = '10:00 PM - 10:59 PM'
• 23 = '11:00 PM - 11:59 PM’

JUR_TYPE

JURISDICTION

• 'S' = 'RURAL STATE'
• 'M' = 'MUNICIPAL STREET'
• 'C' = 'COUNTY ROAD

LIGHT

LIGHT CONDITION

• 0 = 'LIGHT-NOT-STATED'
• 1 = 'DAYLIGHT'
• 2 = 'DAWN'
• 3 = 'DUSK'
• 4 = 'DARK-NO-LIGHTS'
• 5 = 'DARK-LIGHTED'
• 6 = 'OTHER'

LOC_CASE

LOCAL REPORT NUMBER

NON-LABELED VARIABLE

LOC_TYPE

LOCATION

• 0 = 'LOCATION-NOT-STATED'
• 1 = 'INTERSECTION'
• 2 = 'INTERSECTION-RELATED'
• 3 = 'DRIVEWAY-ACCESS'
• 4 = 'RAILROAD-CROSSING'
• 5 = 'BRIDGE-PASSING-OVER'
• 6 = 'BRIDGE-PASSING-UNDER'
• 7 = 'NON-INTERSECTION'
• 8 = 'PRIVATE-PROPERTY'

MILEPOST

MILEPOST

NON-LABELED VARIABLE – Milepost of crash in miles (XXX.XX)

MUNICODE

MUNICIPALITY CODE

NON-LABELED VARIABLE

MVMT

MILLION VEHICLE MILES OF TRAVEL (GENERATED)

NON-LABELED VARIABLE

NHS

NATIONAL HIGHWAY SYSTEM INDICATOR

• 0 = 'NOT NHS'
• 1 = 'NHS HIGHWAY'

NO_LANES

NUMBER OF LANES

• 1 = ' 1 Lane'
• 2 = ' 2 Lanes'
• 3 = ' 3 Lanes'
• 4 = ' 4 Lanes'
• 5 = ' 5 Lanes'
• 6 = ' 6 Lanes'
• 7 = ' 7 Lanes'
• 8 = ' 8 Lanes'
• 9 = ' 9 Lanes'
• 10 = '10 Lanes'
• 11 = '11 Lanes'
• 12 = '12 Lanes'

NUMPEDS

NUMBER OF PEDESTRIANS

NON-LABELED VARIABLE

NUMVEHS

NUMBER OF VEHICLES

NON-LABELED VARIABLE

ONOFF_RD

ON-OFF ROAD OCCURANCE

• 0 = 'OCCURANCE-NOT-STATED'
• 1 = 'ON-ROADWAY'
• 2 = 'OFF-LEFT-SIDE'
• 3 = 'OFF-RIGHT-SIDE'
• 4 = 'ON-OPPOSITE-LANE-DIVIDED-HIGHWAY'

POP_GRP

POPULATION

• 1 = 'RURAL VILLAGE POP. : 1 - 999'
• 2 = 'RURAL VILLAGE POP. : 1,000 - 2,499'
• 3 = 'URBAN CITY POP. : 2,500 - 4,999'
• 4 = 'URBAN CITY POP. : 5,000 - 9,999'
• 5 = 'URBAN CITY POP. : 10,000 - 24,999'
• 6 = 'URBAN CITY POP. : 25,000 - 49,999'
• 7 = 'URBAN CITY POP. : 50,000 AND OVER'
• 8 = 'RURAL COUNTY OR TOWNSHIP ROADS'
• 9 = 'RURAL STATE, US, IR, TURNPIKE ROUTE'

PUBDMG

PUBLIC PROPERTY DAMAGE

• ' ' = 'NO'
• 'Y' = 'YES'

RAMP

RAMP CODE

NON-LABELED VARIABLE

RD_CHAR1

CONTOUR OF ROADWAY

• 0 = 'CONTOUR-NOT-STATED'
• 1 = 'STRAIGHT-LEVEL'
• 2 = 'STRAIGHT-GRADE'
• 3 = 'CURVE-LEVEL'
• 4 = 'CURVE-GRADE'

RDSURF

ROAD CONDITION

• 0 = 'ROAD-NOT-STATED'
• 1 = 'ROAD-DRY'
• 2 = 'ROAD-WET'
• 3 = 'ROAD-SNOW'
• 4 = 'ROAD-ICE'
• 5 = 'ROAD-MUD-SAND'

RODWYCLS

ROADWAY TYPE (GENERATED)

• '01' = 'URBAN FREEWAYS'
• '02' = 'URBAN FREEWAYS < 4 LN'
• '03' = 'URBAN 2 LANE ROADS'
• '04' = 'URBAN MULTILANE DIVIDED NON FREEWAYS'
• '05' = 'URBAN MULTILANE UNDIVIDED NON FREEWAYS'
• '06' = 'RURAL FREEWAYS'
• '07' = 'RURAL FREEWAYS < 4 LN'
• '08' = 'RURAL 2 LANE ROADS'
• '09' = 'RURAL MULTILANE DIVIDED NON FREEWAYS'
• '10' = 'RURAL MULTILANE UNDIVIDED NON FREEWAYS'
• '99' = 'OTHERS'
• ' ' = 'NOT CODED'

NOTE: Created variable added to HSIS accident and roadway inventory files. See Discussion.

RTE_NBR

ROUTE NUMBER

NON-LABELED VARIABLE

SAFTJUR

ORIGINAL JURISDICTION CODED BY HIGHWAY SAFETY

NON-LABELED VARIABLE

SEVERITY

CRASH SEVERITY (GENERATED)

• '1' = 'FATAL'
• '2' = 'A INJURY'
• '3' = 'B INJURY'
• '4' = 'C INJURY'
• '5' = 'PROPERTY DAMAGE'

SPECAREA

SPECIAL AREA CODE

• 0 = 'SPECIAL-AREA-NOT-STATED'
• 1 = 'ROAD-CONSTRUCTION-MAINTENANCE-AREA'
• 2 = 'SCHOOL-ZONE'

SRC_RPT

SOURCE OF REPORT

NON-LABELED VARIABLE

STATE_EQ

STATION EQUATION SORT FIELD

NON-LABELED VARIABLE

STREET_1

STREET ON

NON-LABELED VARIABLE

STREET_2

STREET AT/CROSS ROUTE

NON-LABELED VARIABLE

TOT_KILL

TYPE 1 TOTAL KILLED

• 00 - 04 = '0 TO 4'
• 05 - 10 = '5 TO 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '51 OR MORE’

TOT_NON

TYPE 5 NO INDICATED INJURY

• 00 - 04 = '0 TO 4'
• 05 - 10 = '5 TO 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '51 OR MORE'

TOT_UNK

TYPE 0 INJURY NOT STATED

• 00 - 04 = '0 TO 4'
• 05 - 10 = '5 TO 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '51 OR MORE'

TOTAINJ

TYPE 2 SERIOUS VISIBLE INJURY

• 00 - 04 = '0 TO 4'
• 05 - 10 = '5 TO 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '51 OR MORE

TOTBINJ

TYPE 3 MINOR VISIBLE INJURY

• 00 - 04 = '0 TO 4'
• 05 - 10 = '5 TO 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '51 OR MORE

TOTCINJ

TYPE 4 NO VISIBLE INJURY

• 00 - 04 = '0 TO 4'
• 05 - 10 = '5 TO 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '51 OR MORE

TWNSHIP

TOWNSHIP ABBREVIATION

NON-LABELED VARIABLE

TYPE_BD

TYPE OF REFERENCE

• 'B' = 'COUNTY, TOWNSHIP BOUNDRIES'
• 'C' = 'CORP BOUNDRY'
• 'D' = 'DRIVEWAY'
• 'H' = 'HOUSE NUMBER'
• 'I' = 'INTERSECTION (WITHIN .10 MILES)'
• 'M' = 'MILEPOST'
• 'P' = 'PLACE WITH REFERENCE (SUCH AS BRIDGE OR RR)'
• 'R' = 'INTERSECTION REFERENCE (GREATER THAN .10 MILES)'
• 'X' = 'UNKNOWN'

WEATHER

WEATHER CONDITION

• 0 = 'WEATHER-NOT-STATED'
• 1 = 'NO-ADVERSE-WEATHER-COND'
• 2 = 'RAIN'
• 3 = 'SNOW'
• 4 = 'FOG'
• 5 = 'HEAVY-WIND'
• 6 = 'OTHER-WEATHER-CONDITION'

WEEKDAY

DAY OF WEEK

• 0 = 'DAY-NOT-STATED'
• 1 = 'SUNDAY'
• 2 = 'MONDAY'
• 3 = 'TUESDAY'
• 4 = 'WEDNESDAY'
• 5 = 'THURSDAY'
• 6 = 'FRIDAY'
• 7 = 'SATURDAY

Vehicle Subfile

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO VEHICLE SUBFILE

NOTE: SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)

BODY

BODY TYPE

• '2S' = 'TWO-DOOR'
• '4S' = 'FOUR-DOOR, LIMO'
• '2H' = 'TWO-DOOR HARDTOP'
• '4H' = 'FOUR-DOOR HARDTOP'
• 'SW' = 'STATION WAGON'
• 'CP' = 'CLUB COUPE'
• 'CN' = 'MISCELLANEOUS VEHICLES, CONVERTIBLE, RETRACTABLE HARDTOP, ROADSTER'
• 'DB' = 'DUNE BUGGY'
• 'AM' = 'AMBULANCE, HEARSE'
• 'HB' = 'HATCHBACK'
• 'JP' = 'JEEP'
• 'MC' = 'MOTORCYCLE'
• 'MS' = 'MOTORSCOOTER'
• 'MB' = 'MOTORBIKE'
• 'MP' = 'MOPED'
• 'BS' = 'BUSES, COMMERCIAL BUS'
• 'TK' = 'COMMERCIAL VEHICLES TRUCK, NON-COMMERCIAL VEHICLES TRUCK'
• 'FT' = 'FARM TRUCK'
• 'TR' = 'TRACTOR'
• 'TL' = 'TRAILERS, COMMERCIAL TRAILER, NON-COMMERCIAL TRAILER'
• 'TT' = 'TRAVEL TRAILER'
• 'MH' = 'MOTOR HOME'
• 'HT' = 'HOUSE TRAILER'
• 'HV' = 'HOUSE VEHICLE'
• 'HC' = 'HOUSE CAR'
• 'RA' = 'RECREATIONAL VEHICLES RECREATIONAL ALL-PURPOSE'
• 'RB' = 'RECREATIONAL MINI-BIKE AND TRAIL BIKE'
• 'RS' = 'RECREATIONAL SNOWMOBILE'
• 'BU' = 'BUS'
• 'CB' = 'CHRUCH BUS'
• 'SB' = 'SCHOOL BUS'
• 'SN' = 'SNOWMOBILE'
• 'TB' = 'TRANSIT BUS'
• 'VN' = 'VAN BUS'

NOTE: This variable shows 48 percent of the values to be missing. Also there are no formats available for the convectional 4-door automobile. Any analysis performed using this variable should take this in account.

CASENO

UNIQUE ACCIDENT CASE NUMBER

NON-LABELED VARIABLE – Accident Case Number

NOTE: digits 1-4 YEAR OF ACCIDENT

CONTRIB1

CONTRIBUTING FACTOR OF VEHICLE

• 01 = 'NO-DRIVER-ERRORS'
• 02 = 'FAILURE-TO-YIELD'
• 03 = 'EXCESSIVE-SPEED'
• 04 = 'FOLLOWING-TOO-CLOSE'
• 05 = 'RAN-RED-LIGHT'
• 06 = 'RAN-STOP-OR-YIELD-SIGN'
• 07 = 'IMPROPER-TURNING'
• 08 = 'IMPROPER-PASSING'
• 09 = 'IMPROPER-LANE-CHANGE'
• 10 = 'IMPROPER-BACKING'
• 11 = 'IMPROPER-START-FROM-PARKED-POSITION'
• 12 = 'STOPPED-PARKED-ILLEGAL'
• 13 = 'LEFT-OF-CENTER'
• 14 = 'FAILURE-TO-CONTROL'
• 15 = 'DRIVER-INATTENTION'
• 16 = 'DROVE-OFF-ROAD-REASON-UNKNOWN'
• 17 = 'OTHER-DRIVER-ERROR'
• 18 = 'VEHICLE-DEFECT'
• 19 = 'LOAD-SHIFT-FALL-SPILL'
• 20 = 'PAVEMENT-DEFECT'
• 21 = 'SHOULDER-DEFECT'
• 22 = 'DEBRIS-ON-ROAD'
• 23 = 'DOWNED-TRAFFIC-SIGN-DEVICE'
• 24 = 'VIEW-OBSTRUCTED'
• 25 = 'ANIMAL-ACTION'
• 26 = 'PEDESTRIAN-ACTION'

DAMAGE

VEHICLE DAMAGE SEVERITY (VDS)

• 0 = 'VDS-NOT-STATED'
• 1 = 'NON-FUNCTIONAL'
• 2 = 'FUNCTIONAL'
• 3 = 'DISABLING'

DAMSEV

VEHICLE DAMAGE SCALE

• 0 = 'SCALE-NOT-STATED'
• 1 = 'NO-DAMAGE'
• 2 = 'LIGHT-DAMAGE'
• 3 = 'MODERATE-DAMAGE'
• 4 = 'HEAVY-DAMAGE'

DIR_TRVL

DIRECTION OF VEHICLE

• 11 = 'NORTH TO NORTH'
• 12 = 'NORTH TO NORTHEAST'
• 13 = 'NORTH TO EAST'
• 14 = 'NORTH TO SOUTHEAST'
• 15 = 'NORTH TO SOUTH'
• 16 = 'NORTH TO SOUTHWEST'
• 17 = 'NORTH TO WEST'
• 18 = 'NORTH TO NORTHWEST'
• 19 = 'NORTH TO UNKNOWN'
• 21 = 'NORTHEAST TO NORTH'
• 22 = 'NORTHEAST TO NORTHEAST'
• 23 = 'NORTHEAST TO EAST'
• 24 = 'NORTHEAST TO SOUTHEAST'
• 25 = 'NORTHEAST TO SOUTH'
• 26 = 'NORTHEAST TO SOUTHWEST'
• 27 = 'NORTHEAST TO WEST'
• 28 = 'NORTHEAST TO NORTHWEST'
• 29 = 'NORTHEAST TO UNKNOWN'
• 31 = 'EAST TO NORTH'
• 32 = 'EAST TO NORTHEAST'
• 33 = 'EAST TO EAST'
• 34 = 'EAST TO SOUTHEAST'
• 35 = 'EAST TO SOUTH'
• 36 = 'EAST TO SOUTHWEST'
• 37 = 'EAST TO WEST'
• 38 = 'EAST TO NORTHWEST'
• 39 = 'EAST TO UNKNOWN'
• 41 = 'SOUTHEAST TO NORTH'
• 42 = 'SOUTHEAST TO NORTHEAST'
• 43 = 'SOUTHEAST TO EAST'
• 44 = 'SOUTHEAST TO SOUTHEAST'
• 45 = 'SOUTHEAST TO SOUTH'
• 46 = 'SOUTHEAST TO SOUTHWEST'
• 47 = 'SOUTHEAST TO WEST'
• 48 = 'SOUTHEAST TO NORTHWEST'
• 49 = 'SOUTHEAST TO UNKNOWN'
• 51 = 'SOUTH TO NORTH'
• 52 = 'SOUTH TO NORTHEAST'
• 53 = 'SOUTH TO EAST'
• 54 = 'SOUTH TO SOUTHEAST'
• 55 = 'SOUTH TO SOUTH'
• 56 = 'SOUTH TO SOUTHWEST'
• 57 = 'SOUTH TO WEST'
• 58 = 'SOUTH TO NORTHWEST'
• 59 = 'SOUTH TO UNKNOWN'
• 61 = 'SOUTHWEST TO NORTH'
• 62 = 'SOUTHWEST TO NORTHEAST'
• 63 = 'SOUTHWEST TO EAST'
• 64 = 'SOUTHWEST TO SOUTHEAST'
• 65 = 'SOUTHWEST TO SOUTH'
• 66 = 'SOUTHWEST TO SOUTHWEST'
• 67 = 'SOUTHWEST TO WEST'
• 68 = 'SOUTHWEST TO NORTHWEST'
• 69 = 'SOUTHWEST TO UNKNOWN'
• 71 = 'WEST TO NORTH'
• 72 = 'WEST TO NORTHEAST'
• 73 = 'WEST TO EAST'
• 74 = 'WEST TO SOUTHEAST'
• 75 = 'WEST TO SOUTH'
• 76 = 'WEST TO SOUTHWEST'
• 77 = 'WEST TO WEST'
• 78 = 'WEST TO NORTHWEST'
• 79 = 'WEST TO UNKNOWN'
• 81 = 'NORTHWEST TO NORTH'
• 82 = 'NORTHWEST TO NORTHEAST'
• 83 = 'NORTHWEST TO EAST'
• 84 = 'NORTHWEST TO SOUTHEAST'
• 85 = 'NORTHWEST TO SOUTH'
• 86 = 'NORTHWEST TO SOUTHWEST'
• 87 = 'NORTHWEST TO WEST'
• 88 = 'NORTHWEST TO NORTHWEST'
• 89 = 'NORTHWEST TO UNKNOWN'
• 91 = 'UNKNOWN TO NORTH'
• 92 = 'UNKNOWN TO NORTHEAST'
• 93 = 'UNKNOWN TO EAST'
• 94 = 'UNKNOWN TO SOUTHEAST'
• 95 = 'UNKNOWN TO SOUTH'
• 96 = 'UNKNOWN TO SOUTHWEST'
• 97 = 'UNKNOWN TO WEST'
• 98 = 'UNKNOWN TO NORTHWEST'
• 99 = 'UNKNOWN TO UNKNOWN'

DL_CLASS

CLASS

• 'A' = 'COMBINATION'
• 'B' = 'HEAVY STRAIGHT'
• 'C' = 'SMALL VEHICLE'
• 'D' = 'OPERATOR'
• 'F' = 'CHAUFFEUR'
• 'M1'= 'MOTORCYCLE ONLY'
• 'M2'= 'MOPED ONLY'
• 'M3'= 'THREE-WHEEL MOTORCYCLE ONLY'
• ' ' = 'NOT CODED'

DL_STATE

STATE

NON-LABELED VARIABLE

DLCOUNTY

COUNTY

NON-LABELED VARIABLE

NOTE: For formats look in the roadway section of the guidebook.

DRV_AGE

DRIVER AGE

• 00 ='NOT STATED'
• 01 ='INFANT - 1 YR'
• 02-04 ='02-04 YRS'
• 05-10 ='05-10 YRS'
• 11-14 ='11-14 YRS'
• 15 =' 15 YRS'
• 16 =' 16 YRS'
• 17 =' 17 YRS'
• 18 =' 18 YRS'
• 19 =' 19 YRS'
• 20 =' 20 YRS'
• 21-25 ='21-25 YRS'
• 26-30 ='26-30 YRS'
• 31-35 ='31-35 YRS'
• 36-45 ='36-45 YRS'
• 46-55 ='46-55 YRS'
• 56-65 ='56-65 YRS'
• 66-89 ='66-89 YRS'
• 90-99 =' 90+ YRS'
• 100-HIGHER = 'ERROR CODES'

DRV_FLAG

DRIVER PRESENCE

• '1' = 'OPERATING VEHICLE'
• '2' = 'PARKED'
• '3' = 'DRIVERLESS'
• '4' = 'HIT-AND-RUN'
• '5' = 'NON-CONTACT'
• 'P' = 'PEDESTRIAN'

DRV_INJ

DRIVER INJURY

• 1 = 'FATAL INJURY'
• 2 = 'SERIOUS VISIBLE (INCAPACITATING) INJURY'
• 3 = 'MINOR VISIBLE INJURY'
• 4 = 'NON VISIBLE (CLAIMED) INJURY'
• 5 = 'NO INJURY'
• 0 = 'NOT STATED'

DRV_SEX

DRIVE SEX

• ' ' = 'NOT-STATED'
• 'M' = 'MALE'
• 'F' = 'FEMALE'

FIRE

FIRE

• 1 = 'NO FIRE'
• 2 = 'FIRE DUE TO CRASH'
• 3 = 'OTHER FIRE'

INSURFLG

VEHICLE INSURED

• 'N' = 'VEHICLE NOT INSURED'
• 'Y' = 'VEHICLE INSURED'
• -BLANK- = 'NOT CODED'

MAKE

MAKE OF VEHICLE

NON-LABELED VARIABLE

MODEL

MODEL OF VEHICLE

NON-LABELED VARIABLE

MOVMNT

MOVEMENT OF VEHICLE

• 00 = 'NOT STATED'
• 01 = 'GOING STRAIGHT'
• 02 = 'TURNING RIGHT'
• 03 = 'TURNING LEFT'
• 04 = 'TURNING ON RED LIGHT'
• 05 = 'MAKING U-TURN'
• 06 = 'STOPPED TO TURN'
• 07 = 'STOPPED IN TRAFFIC'
• 08 = 'PARKING / UNPARKING'
• 09 = 'PARKED'
• 10 = 'BACKING'
• 11 = 'PASSING'
• 12 = 'CHANGING LANES'
• 13 = 'MERGING / EXITING RAMP'
• 14 = 'OUT OF CONTROL'
• 15 = 'SWERVING'
• 16 = 'DRIVERLESS VEHICLE'
• 17 = 'OTHER DRIVER ACTION'
• 18 = 'CROSSING AT INTERSECTION'
• 19 = 'CROSSING - NOT AT INTERSECTION'
• 20 = 'WALKING WITH TRAFFIC'
• 21 = 'WALKING AGAINST TRAFFIC'
• 22 = 'PLAYING IN ROADWAY'
• 23 = 'WORKING ON ROADWAY'
• 24 = 'ENTERING / LEAVING VEHICLE'
• 25 = 'PUSHING / WORKING ON VEHICLE IN ROADWAY'
• 26 = 'OTHER - IN ROADWAY'
• 27 = 'ON SHOULDER OR SIDEWALK'

NOTE: Codes 1-17 are for driver actions and 18 onwards are for pedestrian actions.

NUMVEH

NUMBER OF VEHICLES

NON-LABELED VARIABLE

OBJECT1

OBJECT STRUCK BY VEHICLE

• 00 = 'OBJECT-NOT-STATED'
• 01 = 'NOTHING-STRUCK'
• 02 = 'UTILITY-POLE'
• 03 = 'TRAFFIC-SIGN'
• 04 = 'BRIDGE-OR-CULVERT'
• 05 = 'GUARDRAIL'
• 06 = 'FENCE'
• 07 = 'TREE'
• 08 = 'SHRUBBERY'
• 09 = 'CURB'
• 10 = 'DITCH'
• 11 = 'EMBANKMENT'
• 12 = 'BUILDING'
• 13 = 'MAILBOX'
• 14 = 'CONSTRUCTION-BARRICADE'
• 15 = 'FIRE-HYDRANT'
• 16 = 'OTHER-FIXED OBJECT'

OWNERID

VEHICLE OWNERSHIP

• 0 = 'OWNER-NOT-STATED'
• 1 = 'CITY-OWNED'
• 2 = 'COUNTY-OWNED'
• 3 = 'STATE-OWNED'
• 4 = 'FEDERAL-OWNED'
• 5 = 'PRIVATELY-OWNED'
• 6 = 'MILITARY-OWNED'
• 7 = 'OTHER-PUBLIC-OWNED'
• 8 = 'STATE-HIGHWAY-PATROL'

PUB_PROP

PUBLIC PROPERTY DAMAGE

• 'N' = 'NO PUBLIC PROPERTY DAMAGE'
• 'Y' = 'PUBLIC PROPERTY DAMAGED'

SPEED

ESTIMATED SPEED OF VEHICLE

• 0 = 'POSTED-SPEED-NOT-STATED'
• 1 = 'POSTED-UNDER-TWENTY'
• 2 = 'POSTED-TWENTY-FIVE'
• 3 = 'POSTED-THIRTY'
• 4 = 'POSTED-THIRTY-FIVE'
• 5 = 'POSTED-FOURTY'
• 6 = 'POSTED-FOURTY-FIVE'
• 7 = 'POSTED-FIFTY'
• 8 = 'POSTED-FIFTY-FIVE'
• 9 = 'POSTED OVER FIFTY-FIVE (65)'

TRF_CNTL

TRAFFIC CONTROL OF VEHICLE

• 00 = 'TRAFFIC-CONTROL-NOT-STATED'
• 01 = 'NO-TRAFFIC-CONTROL-DRIVER'
• 02 = 'STOP-SIGN'
• 03 = 'YIELD-SIGN'
• 04 = 'TRAFFIC-SIGNAL'
• 05 = 'TRAFFIC-FLASHERS'
• 06 = 'SCHOOL-ZONE'
• 07 = 'RAILROAD-CROSSBUCKS'
• 08 = 'RAILROAD-FLASHERS'
• 09 = 'RAILROAD-GATES'
• 10 = 'CONSTRUCTION-BARRICADES'
• 11 = 'TRAFFIC-OFFICER'
• 12 = 'PAVEMENT-MARKINGS'
• 13 = 'OTHER-TRAFFIC-CONTROL'
• 14 = 'NO-TRAFFIC-CONTROL-PEDESTRIAN'
• 15 = 'CROSSWALK-LINES'
• 16 = 'WALK-DONT-WALK-DEVICE'

TRK_LOAD

TYPE OF TRUCK LOAD

• 0 = 'TRUCK-LOAD-NOT-STATED'
• 1 = 'EMPTY'
• 2 = 'PERISHABLE-GOODS'
• 3 = 'GENERAL-FREIGHT'
• 4 = 'METAL-OR-HEAVY-MACHINERY'
• 5 = 'HAZARDOUS-GAS'
• 6 = 'HAZARDOUS-LIQUID'
• 7 = 'HAZARDOUS-SOLID'
• 8 = 'RADIOACTIVE-MATERIAL'

TRKAXLES

NUMBER OF TRUCK AXLES

NON-LABELED VARIABLE

VEH_DISP

VEHICLE DISPOSITION

• 0 = 'VEHICLE DISPOSITION NOT STATED'
• 1 = 'DRIVEN FROM SCENE'
• 2 = 'REMAINED AT SCENE'
• 3 = 'TOWED'

VEH_SPD

POSTED SPEED OF VEHICLE

• 0 = 'VEHICLE-SPEED-NOT-STATED'
• 1 = 'UNDER-20'
• 2 = 'SPEED-21-25'
• 3 = 'SPEED-26-35'
• 4 = 'SPEED-36-45'
• 5 = 'SPEED-46-55'
• 6 = 'SPEED-56-65'
• 7 = 'SPEED-66-75'
• 8 = 'OVER-75'
• 9 = 'SPEED-IS-STOPPED'

VEHCOND1

PRIMARY CONDITION 1

VEHCOND2

PRIMARY CONDITION 2

• 00 = 'NOT-STATED'
• 01 = 'TURN-SIGNALS'
• 02 = 'HEAD-LAMPS'
• 03 = 'TAIL-LAMPS'
• 04 = 'BRAKES'
• 05 = 'STEERING'
• 06 = 'TIRE-BLOWOUT'
• 07 = 'WORN-OR-SLICK-TIRES'
• 08 = 'TRAILER-EQUIPMENT'
• 09 = 'MOTOR'
• 10 = 'DISABLED-FROM-PRIOR-CRASH'
• 11 = 'OTHER-DEFECTS'

VEHNO

VEHICLE NUMBER

NON-LABELED VARIABLE

VEHSTATE

VEHICLE STATE

NON-LABELED VARIABLE

NOTE: Linkage Variable

VEHTYPE

VEHICLE TYPE

• 00 = 'VEHICLE-NOT-STATED'
• 01 = 'SUB-COMPACT'
• 02 = 'COMPACT'
• 03 = 'MID-SIZE'
• 04 = 'FULL-SIZE'
• 05 = 'PICKUP-TRUCK'
• 06 = 'PANEL-TRUCK'
• 07 = 'STRAIGHT-TRUCK'
• 08 = 'STRAIGHT-TRUCK-TRAILER'
• 09 = 'TRUCK-TRACTOR'
• 10 = 'TRACTOR-SEMI-TRAILER'
• 11 = 'TRACTOR-DOUBLE-TRAILER'
• 12 = 'MC-UP-TO-350CC'
• 13 = 'MC-351CC-750CC'
• 14 = 'MC-OVER-750CC'
• 15 = 'MOTORIZED-BICYCLE'
• 16 = 'SCHOOL-BUS'
• 17 = 'CHURCH-BUS'
• 18 = 'PUBLIC-BUS'
• 19 = 'POLICE-VEHICLE'
• 20 = 'FIRE-TRUCK'
• 21 = 'AMBULANCE-RESCUE'
• 22 = 'TAXI'
• 23 = 'MOTOR-HOME'
• 24 = 'TRAIN'
• 25 = 'FARM-VEHICLE'
• 26 = 'FARM-EQUIPMENT'
• 27 = 'SNOWMOBILE'
• 28 = 'CONSTRUCTION-EQUIPMENT'
• 29 = 'ANIMAL-WITH-RIDER'
• 30 = 'ANIMAL-WITH-BUGGY'
• 31 = 'BICYCLE'
• 32 = 'OTHER-VEHICLE'
• 33 = 'FIFTH-WHEEL-OR-HOT-SPOT'
• 34 = 'TRIPLE-TRAILER'
• P = 'PEDESTRIAN'

VEHYR

VEHICLE MODEL YEAR

NON-LABELED VARIABLE – Model Year of the Vehicle (YYYY)

VIN

VIN NUMBER

NON-LABELED VARIABLE – Vehicle Identification Number

Injured Occupants Subfile

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO INJURED OCCUPANT SUBFILE

NOTE: SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)

AGE

OCCUPANT AGE

• 00 = 'NOT STATED'
• 01 ='INFANT - 1 YR'
• 02-04 ='02-04 YRS'
• 05-10 ='05-10 YRS'
• 11-14 ='11-14 YRS'
• 15 =' 15 YRS'
• 16 =' 16 YRS'
• 17 =' 17 YRS'
• 18 =' 18 YRS'
• 19 =' 19 YRS'
• 20 =' 20 YRS'
• 21-25 ='21-25 YRS'
• 26-30 ='26-30 YRS'
• 31-35 ='31-35 YRS'
• 36-45 ='36-45 YRS'
• 46-55 ='46-55 YRS'
• 56-65 ='56-65 YRS'
• 66-89 ='66-89 YRS'
• 90-99 =' 90+ YRS'

ALC_TST

ALCOHOL TEST

• 'Y' = 'YES'
• 'N' = 'NO'
• ' ' = 'UNKNOWN'

BAC

BLOOD ALCOHOL CONTENT IN %

NON-LABELED VARIABLE

CASENO

UNIQUE ACCIDENT CASE NUMBER

NON-LABELED VARIABLE – Accident Case Number

NOTE: digits 1-4 = YEAR OF ACCIDENT

CITATION

CITATION GIVEN

• 'Y' = 'YES'
• 'N' = 'NO'
• ' ' = 'UNKNOWN'

DL_CLASS

DL CLASS

• 'A' = 'COMBINATION'
• 'B' = 'HEAVY STRAIGHT'
• 'C' = 'SMALL VEHICLE'
• 'D' = 'OPERATOR'
• 'F' = 'CHAUFFEUR'
• 'M1'= 'MOTORCYCLE ONLY'
• 'M2'= 'MOPED ONLY'
• 'M3'= 'THREE-WHEEL MOTORCYCLE ONLY'

DL_STATE

DL STATE

NON-LABELED VARIABLE

DLCOUNTY

DL COUNTY

NON-LABELED VARIABLE

NOTE: For formats see roadway section of the guidebook

DRUG_INV

DRUGS INVOLVED

• 0 = 'DRUGS-NOT-STATED'
• 1 = 'NO-DRUGS-DETECTED'
• 2 = 'USING-PRESCRIBED-DRUG'
• 3 = 'USING-ILLICIT-DRUG'

DRUG_TST

DRUG TEST

• 'Y' = 'YES'
• 'N' = 'NO'
• -BLANK- = 'UNKNOWN'

EJECT

EJECTED FROM VEHICLE

• 0 = 'EJECTION NOT STATED'
• 1 = 'NOT EJECTED'
• 2 = 'PARTIAL EJECTION'
• 3 = 'TOTAL EJECTION'
• 4 = 'TRAPPED'

HELMET

HELMET USE

• 0 = 'NOT STATED'
• 1 = 'NO HELMET'
• 2 = 'FULL COVERAGE HELMET'
• 3 = 'PARTIAL COVERAGE HELMET'
• 4 = 'OTHER TYPE HELMET'

INJ

OCCUPANT INJURY

• 0 = 'INJURY NOT STATED'
• 1 = 'FATAL INJURY'
• 2 = 'SERIOUS VISIBLE (INCAPACITATING) INJURY'
• 3 = 'MINOR VISIBLE INJURY'
• 4 = 'NON VISIBLE (CLAIMED) INJURY'
• 5 = 'NO INJURY'

P_TYPE

OCCUPANT TYPE

• 'D' = 'DRIVER'
• 'O' = 'OCCUPANT'
• 'P' = 'PEDESTRIAN'
• -BLANK- = 'UNKNOWN'

PHYSCOND

PEDESTRIAN PHYSICAL CONDITION

• 0 = 'CONDITION-NOT-STATED'
• 1 = 'NORMAL'
• 2 = 'SICK'
• 3 = 'FATIGUED'
• 4 = 'ASLEEP'
• 5 = 'BODY-DEFECT'
• 6 = 'OTHER-CONDITION'
• 7 = 'UNKNOWN'

REST1

SAFTEY EQUIPMENT

• 1 = 'NOT IN USE'
• 2 = 'NONE INSTALLED'
• 3 = 'SEAT BELT'
• 4 = 'HARNESS AND BELT'
• 5 = 'SHOULDER HARNESS'
• 6 = 'CHILD SAFETY SEAT'
• 7 = 'AIR BAG'
• 8 = 'NOT STATED'

SEATPOS

SEATING POSITION

• '0' = 'NOT STATED'
• '1' = 'FRONT LEFT'
• '2' = 'FRONT CENTER'
• '3' = 'FRONT RIGHT'
• '4' = 'REAR LEFT'
• '5' = 'REAR CENTER'
• '6' = 'REAR RIGHT'
• '7' = 'HOOD / TRUNK / REAR OF VEHICLE'
• '8' = 'MOTORCYCLE - FRONT'
• '9' = 'MOTORCYCLE - REAR'
• 'P' = 'PEDESTRIAN'

SEX

OCCUPANT GENDER

• -BLANK- = 'NOT-STATED'
• 'M' = 'MALE'
• 'F' = 'FEMALE'

SOB_TST

ALCOHOL INVOLVED

• 0 = 'ALCOHOL-NOT-STATED'
• 1 = 'NO-ALCOHOL-DETECTED'
• 2 = 'HBD-ABILITY-IMPAIRED'
• 3 = 'HBD-ABILITY-NOT-IMPAIRED'
• 4 = 'HBD-ABILITY-UNKNOWN'

VEHNO

VEHICLE NUMBER

NON-LABELED VARIABLE – Linkage Variable

ROADLOG Subfile