HIGHWAY SAFETY INFORMATION SYSTEM GUIDEBOOK FOR THE OHIO STATE DATA FILES

SAS File Formats

Prepared by

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

Yusuf M. Mohamedshah
LENDIS Corporation
Turner Fairbank Highway Research Center
Federal Highway Administration
6300 Georgetown Pike
McLean, VA 22101-2296

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

Revised, August 2007

TABLE OF CONTENTS

• INTRODUCTION
• DETAILS OF MAJOR FILES
  • The Accident Files
  • 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
• ACCIDENT FILE
  • ACCIDENT SUBFILE
  • VEHICLE SUBFILE
  • INJURED OCCUPANTS SUBFILE
• ROADLOG FILE
• POINT FILE
• CURVES FILE
• GRADES FILE
• ANGLE POINT FILE

INTRODUCTION

(NOTE:  Changes from the previous edition of the Guidebook are shown in bold and italic.)

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 2004, the HSIS system was converted from SYBASE relational database to ORACLE relational database for internal use.   This ORACLE database stores the data received from California and other States, and the data files for a given State are linked and manipulated using SAS code.  However, this conversion from the original SAS-based system to the ORACLE relational system is somewhat transparent to the end-user of the data since the output files produced by ORACLE for modeling and analysis will be SAS formatted.  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. 

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 Files

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.

Approximately 380,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 approximately 150,000 accidents per year, approximately 270,000 vehicles per year and approximately 370,000 occupants per year. 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 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 has been changed or added in the Ohio accident files in subsequent years.

Approximately 75 percent of the accidents on the linkable file are property damage only and less than 0.5 percent are fatal accidents. Approximately 70 percent vehicles are multi-vehicle in nature, while the remaining 30 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 allow 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 nine roadlog inventory files in the HSIS system, 1997 – 2005. 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 29,000 records, resulting in an average section length of 0.67 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 58,000 intersections, 4,500 interchanges, 5,000 bridges and 1,800 railroad 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 is 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 200 interstate-to-interstate junctions, 6,000 state-to-state and 900 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 is 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

ACCIDENT FILE

LIST OF VARIABLES FOR THE OHIO ACCIDENT SUBFILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO STATE 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

NOTE: 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

NOTE: 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

NOTE: Accident Case Number. The first 4 digits show the accident year.  

CNTYRTE

        COUNTY ROUTE

NON-LABELED VARIABLE

NOTE: Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STATE_EQ. From year 2000, STATE_EQ is not required. Also RTE_SUFX became last digit of RTE_NBR.

COUNTY

         COUNTY

• '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'

DIRECTION

      DIRECTION 1

DIRECTION2

     DIRECTION 2

• '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'
• ' ' = 'NOT CODED'

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 - 95 = 'VEHICLES 9 TO 95 AT FAULT'
• 96 = 'INVALID UNIT'
• 97 = 'PEDESTRIAN AT FAULT'
• 98 = 'NO FAULT DETERMINED'
• 99 = 'ANIMAL AT FAULT'

FIPSMUNI

      FIPS CODE

NON-LABELED VARIABLE

FLIP_IND

       INDICATES DUPLICATE RECORD GENERATION

• '0' = 'NONE'
• '2' = 'SWITCHED ORIGINAL STREET ON/AT'
• '3' = 'MUNI-JUR FLIP ORIGINAL STREET ON/AT'
• '4' = 'OFFSET/OFFSET-DIRECTION USED WITH ASSUMPTIONS FOR LOGGING'
• '5' = 'CR/TR-JUR FLIP ORIGINAL STREET ON/AT'
• '6' = 'ORIGINAL RECORD'
• '7' = 'CROSS ROUTE DUPLICATE'
• 'R' = 'ROUTE CHANGED TO PRIORITY ROUTE'
• 'X' = 'KNOWN STREET-ON REPLACED WITH ROUTE NUMBER'

NOTE: Categories 6 and 7 apply for data generated before 2000.

FRWY_IND

       FREEWAY / NON-FREEWAY INDICATOR

• 'F' = 'FREEWAY'
• 'N' = 'NON-FREEWAY'

FUNCLS

         FUNCTIONAL CLASSIFICATION

• '01' = 'PRIN ART (RURAL INT)'
• '02' = 'PRIN ART (RURAL OTH)'
• '06' = 'MIN ART (RUR)'
• '07' = 'MJ COL (RUR)'
• '08' = 'MIN COL (RUR)'
• '09' = 'LOCAL (RURAL)'
• '11' = 'PRIN ART (URB INT)'
• '12' = 'PRIN ART (URB-FRWY & EXWY'
• '14' = 'PRIN ART (URBAN-OTHER)'
• '16' = 'MIN ART (URBAN)'
• '17' = 'COLLECTOR (URBAN)'
• '19' = 'LOCAL (URBAN)'
• '  ' = 'NOT CODED'

NOTE: Urban crashes increased considerably from 2000 onwards due to OH DOT’s better ability to locate the crashes in this area.

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’
• 99  = 'NOT CODED'

INTER_IND

      INTERSTATE HIGHWAY INDICATOR

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

JUR_TYPE

       JURISDICTION

• 'S' = 'RURAL STATE'
• 'M' = 'MUNICIPAL STREET'
• 'C' = 'COUNTY ROAD'
• 'T' = 'TOWNSHIP ROAD'
• 'H' = 'OHIO TURNPIKE'
• ' ' = 'NOT CODED'

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

NOTE: Milepost of crash in miles (XXX.XX).

MUNICODE

      MUNICIPALITY CODE

NON-LABELED VARIABLE

MVMT

           MILLION VEHICLE MILES OF TRAVEL

NON-LABELED VARIABLE

NHS

            NATIONAL HIGHWAY SYSTEM INDICATOR

• 'N' = 'NHS(REGULAR)'
• 'H' = 'CONGRESSIONAL CORRIDORS'
• 'S' = 'STRAHNET'
• 'C' = 'STRAHNET CONNECTORS'
• '2' = 'MAJOR AIRPORT'
• '3' = 'MAJOR PORT FACILITY'
• '4' = 'MAJOR AMTRAK STATION'
• '5' = 'MAJOR RAIL/TRUCK TERMINAL'
• '6' = 'MAJOR INTERCITY BUS TERMINAL'
• '7' = 'MJ PUB TRAN / MUL-MDL PAS TER'
• '8' = 'MAJOR PIPELINE TERMINAL'
• '9' = 'MAJOR FERRY TERMINAL'
• ' ' = 'NOT CODED'

NO_LANES

       NUMBER OF LANES

• . = 'MISSING'
• 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-DIV-HWY'

PEDS_INJ

       PEDESTRIANS INJURED

NON-LABELED VARIABLE.

NOTE: Variable added in 2000.

PEDS_KILLED

    PEDESTRIANS KILLED

NON-LABELED VARIABLE.

NOTE: Variable added in 2000.

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'
• . = 'NOT CODED'

PUBDMG

         PUBLIC PROPERTY DAMAGE

• ' ','N' = '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 = 'NOT STATED'
• 1 = 'DRY'
• 2 = 'WET'
• 3 = 'SNOW'
• 4 = 'ICE'
• 5 = 'MUD-SAND'
• 6 = 'OTHER ROAD CONDITION'

RODWYCLS

       ROADWAY TYPE

• '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'

NOTE: Urban crashes increased considerably from 2000 onwards due to OH DOT’s better ability to locate the crashes in this area.

RTE_NBR

        ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: From year 2000, this variable became 5 characters with first digit being ‘0’ and last digit as RTE_SUFX.

SAFTJUR

        ORIGINAL JURISDICTION CODED BY HIGHWAY SAFETY

NON-LABELED VARIABLE

SCH_WZON

       SPECIAL AREA CODE

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

SEVERITY

       CRASH SEVERITY (GENERATED)

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

SEVERITY_OH

    CRASH SEVERITY (ORIGINAL)

• 1 = 'FATAL'
• 2 = 'INJURY'
• 3 = 'PROPERTY DAMAGE'

SRC_RPT

        SOURCE OF REPORT

• '0' = 'SOURCE NOT STATED'
• '1' = 'POLICE SOURCE'
• '2' = 'HIGHWAY PATROL'
• '3' = 'CITY POLICE'
• '4' = 'SHERRIFF'
• '5' = 'NEWSPAPER'
• '6' = 'DEATH CERTIFICATE'
• '7' = 'TOWNSHIP'
• '8' = 'OTHER SOURCE'
• ' ' = 'NOT CODED'

STATE_EQ

       STATION EQUATION SORT FIELD

NON-LABELED VARIABLE

NOTE: Not required from year 2000.

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' = 'UNKNOWN'
• '1' = 'SUNDAY'
• '2' = 'MONDAY'
• '3' = 'TUESDAY'
• '4' = 'WEDNESDAY'
• '5' = 'THURSDAY'
• '6' = 'FRIDAY'
• '7' = 'SATURDAY'
• ' ' = 'NOT CODED'

LIST OF VARIABLES FOR THE OHIO VEHICLE SUBFILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO STATE VEHICLE SUBFILE

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

ACCYR

          ACCIDENT YEAR

NON-LABELED VARIABLE

ACTION

         ACTION

• 1 = 'NON-CONTACT'
• 2 = 'NON-COLLISION'
• 3 = 'STRIKING'
• 4 = 'STRUCK'
• 5 = 'BOTH STRIKING AND STRUCK'
• 6 = 'UNKNOWN'

NOTE: Variable added in 2000.

BODY

           BODY TYPE

• '2S' = 'TWO-DOOR'
• '4S' = 'FOUR-DOOR, LIMO'
• '2H' = 'TWO-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'

NOTES: (1) 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.

(2) Variable discontinued in 2000.

CASENO

         UNIQUE ACCIDENT CASE NUMBER

NON-LABELED VARIABLE

NOTE: Accident Case Number. The first 4 digits show the accident year.

CDL_CLASS

      TRUCK/BUS CDL CLASS

• '1' = 'CLASS A'
• '2' = 'CLASS B'
• '3' = 'CLASS C'
• '4' = 'CLASS M'
• '5' = 'CLASS D'

CONTRIB1

       CONTRIBUTING FACTOR OF VEHICLE

MOTORIST

• 01 = 'NONE'
• 02 = 'FAILURE TO YIELD'
• 03 = 'RAN RED LIGHT, OR STOP SIGN'
• 04 = 'EXCEEDED SPEED LIMIT'
• 05 = 'UNSAFE SPEED'
• 06 = 'IMPROPER TURN'
• 07 = 'LEFT OF CENTER'
• 08 = 'FOLLOWED TOO CLOSELY/ACDA'
• 09 = 'IMPROPER LANE CHANGE/DROVE OFF ROAD/IMPROPER PASSING'
• 10 = 'IMPROPER BACKING'
• 11 = 'IMPROPER START FROM PARKED POSITION'
• 12 = 'STOPPED OR PARKED ILLEGALLY'
• 13 = 'OPERATING VEHILCE IN ERRATIC, RECKLESS, CARELESS, GLIGENT OR AGGRESSIVE MANNER'
• 14 = 'SWERVING TO AVOID (DUE TO WIND, SLIPPERY SURFACE, VEHICLE, OBJECT, NON-MOTORIST IN ROADWAY, ETC)'
• 15 = 'FAILURE TO CONTROL'
• 16 = 'VISION OBSTRUCTION'
• 17 = 'DRIVER INATTENTION'
• 18 = 'FATIGUE/ASLEEP'
• 19 = 'OPERATING DEFECTIVE EQUIPMENT'
• 20 = 'LOAD SHIFTING/FALLING/SPILLING'
• 21 = 'OTHER IMPROPER ACTION'
• 22 = 'UNKNOWN'

NON-MOTORIST

• 23 = 'NONE'
• 24 = 'IMPROPER CROSSING'
• 25 = 'DARTING'
• 26 = 'LYING AND/OR ILLEGALLY IN ROADWAY'
• 27 = 'FAILURE TO YIELD RIGHT OF WAY'
• 28 = 'NOT VISIBLE (DARK CLOTHING)'
• 29 = 'INATTENTIVE'
• 30 = 'FAILURE TO OBEY TRAFFIC SIGNS, SIGNALS, OR OFFICER'
• 31 = 'WRONG SIDE OF THE ROAD'
• 32 = 'OTHER'
• 33 = 'UNKNOWN'
• 34 = 'RAN RED LIGHT'
• 35 = 'RAN STOP OR YEILD SIGN'
• 36 = 'IMPROPER PASSING'
• 37 = 'IMPROPER LANE CHANGE'
• 40 = 'DROVE OFF ROAD REASON UNKNOWN'
• 41 = 'OTHER DRIVER ERROR'
• 42 = 'VEHICLE DEFECT'
• 43 = 'PAVEMENT DEFECT'
• 44 = 'SHOULDER DEFECT'
• 45 = 'DEBRIS ON ROAD'
• 46 = 'DOWNED TRAFFIC SIGN DEVICE'
• 47 = 'ANIMAL ACTION'
• 48 = 'PEDESTRIAN ACTION'

NOTE: Categories 34-37 and 40-48 apply to data generated before 2000.

DAMAGE

         VEHICLE DAMAGE SEVERITY (VDS)

• 01 = 'NONE'
• 02 = 'CENTER FRONT'
• 03 = 'RIGHT FRONT'
• 04 = 'RIGHT SIDE'
• 05 = 'RIGHT REAR'
• 06 = 'REAR CENTER'
• 07 = 'LEFT REAR'
• 08 = 'LEFT SIDE'
• 09 = 'LEFT FRONT'
• 10 = 'TOP AND WINDOWS'
• 11 = 'UNDER CARRIAGE'
• 12 = 'LOAD/TRAILER'
• 13 = 'TOTAL (ALL AREAS)'
• 14 = 'OTHER'
• 15 = 'UNKNOWN'

NOTE: Variable added in 2000.

DAMSEV

         VEHICLE DAMAGE SCALE

• 1 = 'NONE'
• 2 = 'NON-FUNCTIONAL DAMAGE'
• 3 = 'FUNCTIONAL DAMAGE'
• 4 = 'DISABLING DAMAGE'
• 5 = 'SEVERE'
• 6 = 'UNKNOWN

DAMSEV2

        VEHICLE DAMAGE SCALE

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

NOTE: Variable discontinued in 2000.

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'
• .  = 'UNCODED'

NOTE: Variable discontinued in 2000.

DL_CLASS

       DL CLASS

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

NOTE: Variable discontinued in 2000.

DL_STATE

       STATE

NON-LABELED VARIABLE

DLCOUNTY

       COUNTY

NOTE: See listings under accident 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-HIGH = 'ERROR CODES'

DRV_FLAG

       DRIVER PRESENCE

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

NOTE: Variable discontinued in 2000.

DRV_INJ

        DRIVER INJURY

• 1 = 'NO INJURY'
• 2 = 'POSSIBLE INJURY'
• 3 = 'NON- INCAPACITATING INJURY'
• 4 = 'INCAPACITATING INJURY'
• 5 = 'FATAL INJURY'
• 6 = 'UNKNOWN'

DRV_REST

       DRIVER SAFETY EQUIPMENT

MOTORIST

• 01 = 'NON USED (MOTORIST)'
• 02 = 'SHOULDER BELT ONLY (MOTORIST)'
• 03 = 'LAP BELT ONLY (MOTORIST)'
• 04 = 'SHOULDER/LAP BELT (MOTORIST)'
• 05 = 'CHILD SAFETY SEAT (MOTORIST)'
• 06 = 'MC HELMET USED (MOTORIST)'
• 07 = 'USE UNKNOWN (MOTORIST)'

NON-MOTORIST

• 08 = 'NONE USED (NON-MOTORIST)'
• 09 = 'HELMET USED (NON-MOTORIST)'
• 10 = 'PROTECTIVE PADS (NON-MOTORIST)'
• 11 = 'REFLECTIVE CLOTHING (NON-MOTORIST)'
• 12 = 'LIGHTING (NON-MOTORIST)'
• 13 = 'OTHER (NON-MOTORIST)'
• 14 = 'UNKNOWN (NON-MOTORIST)'

DRV_SEX

        DRIVE SEX

• 'U' = 'UNKNOWN'
• 'M' = 'MALE'
• 'F' = 'FEMALE'

EMER_USE

       IN EMERGENCY RESPONSE

• 1 = 'NO'
• 2 = 'YES'
• 3 = 'UNKNOWN'

NOTE: Variable added in 2000.

EVENT1

         SEQUENCE OF EVENTS 1

EVENT2

         SEQUENCE OF EVENTS 2

EVENT3

         SEQUENCE OF EVENTS 3

EVENT4

         SEQUENCE OF EVENTS 4

NON-COLLISION

• 01 = 'OVERTURN/ROLLOVER'
• 02 = 'FIRE/EXPLOSION'
• 03 = 'IMMERSION'
• 04 = 'JACKKNIFE'
• 05 = 'CARGO/EQUIPMENT LOSS/SHIFT'
• 06 = 'EQUIPMENT FAILURE'
• 07 = 'SEPERATION OF UNITS'
• 08 = 'RAN OFF ROAD RIGHT'
• 09 = 'RAN OFF ROAD LEFT'
• 10 = 'CROSS MEDIAN/CENTERLINE'
• 11 = 'DOWNHILL RUNAWAY'
• 12 = 'OTHER NON-COLLISION'
• 13 = 'UNKNOWN NON-COLLISION'

COLLISION W/PERSON, VEHICLE, OR OBJECT NOT FIXED

• 14 = 'PEDESTRIAN'
• 15 = 'PEDALCYCLE'
• 16 = 'RAILWAY VEHILCE'
• 17 = 'ANIMAL - FARM'
• 18 = 'ANIMAL - DEER'
• 19 = 'ANIMAL - OTHER'
• 20 = 'MOTOR VEHICLE IN TRANSPORT'
• 21 = 'PARKED MOTOR VEHICLE'
• 22 = 'WORK ZONE MAINTENANCE EQUIPMENT'
• 23 = 'OTHER MOVABLE OBJECT'
• 24 = 'UNKNOWN MOVABLE OBJECT'

COLLISION WITH FIXED OBJECT

• 25 = 'IMPACT ATTENUATOR/CRASH CUSHION'
• 26 = 'BRIDGE OVERHEAD STRUCTURE'
• 27 = 'BRIDGE PIER OR ABUTMENT'
• 28 = 'BRIDGE PARAPET'
• 29 = 'BRIDGE RAIL'
• 30 = 'GUARDRAIL FACE'
• 31 = 'GUARDRAIL END'
• 32 = 'MEDIAN BARRIER'
• 33 = 'HIGHWAY TRAFFIC SIGN POST'
• 34 = 'OVERHEAD SIGN POST'
• 35 = 'LIGHT/LUMINARIES SUPPORT'
• 36 = 'UTILITY POLE'
• 37 = 'OTHER POST, POLE OR SUPPORT'
• 38 = 'CULVERT'
• 39 = 'CURB'
• 40 = 'DITCH'
• 41 = 'EMBANKMENT'
• 42 = 'FENCE'
• 43 = 'MAILBOX'
• 44 = 'TREE'
• 45 = 'OTHER FIXED OBJECT'
• 46 = 'WORK ZONE MAINTENANCE EUIPMENT'
• 47 = 'UNKNOWN FIXED OBJECT'
• 48 = 'OTHER'
• 49 = 'UNKNOWN'

NOTE: Variables added in 2000.

F_HARM

         FIRST HARMFUL EVENT

• 1 = 'EVENT 1'
• 2 = 'EVENT 2'
• 3 = 'EVENT 3'
• 4 = 'EVENT 4'
• 5 = 'UNKNOWN'

FIRE

           FIRE

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

NOTE: Variable discontinued in 2000.

GVWR

           TRUCK/BUS WEIGHT

• 1 = '<= 10000 LBS'
• 2 = '10001-26000 LBS'
• 3 = 'MORE THAN 26000 LBS'

HAZMAT

         HAZARDOUS MATERIAL RELEASED

• 1 = 'NO'
• 2 = 'YES'
• 3 = 'NOT APPLICABLE'
• 4 = 'UNKNOWN'

NOTE: Variable added in 2000.

HAZPLACD

       HAZARDOUS MATERIAL PLACARD

• 1 = 'NO'
• 2 = 'YES'
• 3 = 'UNKNOWN'

NOTE: Variable added in 2000.

INSURFLG

       VEHICLE INSURED

• 1 = 'VEHICLE INSURED'
• 2 = 'VEHICLE NOT INSURED'
• 3 = 'NOT CODED'

LOC_VEH

        NON-MOTORIST LOCATION PRIOR TO IMPACT

• 01 = 'MARKED CROSSWALK AT INTERSECTION'
• 02 = 'AT INTERSECTION BUT NO CROSSWALK'
• 03 = 'NON-INTERSECTION CROSSWALK'
• 04 = 'DRIVEWAY ACCESS CROSSWALK'
• 05 = 'IN ROADWAY'
• 06 = 'NOT IN ROADWAY'
• 07 = 'MEDIAN (BUT NO ON SHOULDER)'
• 08 = 'ISLAND'
• 09 = 'SHOULDER'
• 10 = 'SIDEWALK'
• 11 = 'WITHING 10 FEET OF ROADWAY (BUT NOT SHOULDER, MEDIAN, SIDEWALK OR ISLAND)'
• 12 = 'BEYOND 10 FEET OF ROADWAY (WITHIN TRAFFICWAY)'
• 13 = 'OUTSIDE TRAFFICWAY'
• 14 = 'SHARED USE PATHS OR TRAILS'
• 15 = 'UNKNOWN'

MAKE

           MAKE OF VEHICLE

NON-LABELED VARIABLE

MISCACT1

       PRE-CRASH ACTIONS

MOTORIST

• 01 = 'MOVEMENTS ESSENTIALLY STRAIGHT HEAD'
• 02 = 'BACKING'
• 03 = 'CHANGING LANES'
• 04 = 'OVERTAKING/PASSING'
• 05 = 'TURNING RIGHT'
• 06 = 'TURNING LEFT'
• 07 = 'MAKING U-TURN'
• 08 = 'ENTERING TRAFFIC LANE'
• 09 = 'LEAVING TRAFFIC LANE'
• 10 = 'PARKED'
• 11 = 'SLOWING/STOPPED IN TRAFFIC'
• 12 = 'DRIVERLESS'
• 13 = 'OTHER'
• 14 = 'UNKNOWN'

NON-MOTORIST

• 15 = 'ENTERING/CROSSING IN SPECIFIED LOCATION'
• 16 = 'WALKING, RUNNING, JOGGING, PLAYING, CYCLING'
• 17 = 'WORKING'
• 18 = 'PUSHING VEHICLE'
• 19 = 'APPROACHING/LEAVING VEHICLE'
• 20 = 'PLAYING/WORKING ON VEHICLE'
• 21 = 'STANDING'
• 22 = 'OTHER'
• 23 = 'UNKNOWN'

NOTE: Variable added in 2000.

MODEL

          MODEL OF VEHICLE

NON-LABELED VARIABLE

MOSTHARM

       MOST HARMFUL EVENT

• 1 = 'EVENT 1'
• 2 = 'EVENT 2'
• 3 = 'EVENT 3'
• 4 = 'EVENT 4'
• 5 = 'UNKNOWN'

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.

NUM_OCCS

       NUMBER OF OCCUPANTS

• 1 -  4 = '01 - 04'
• 5 - 10 = '05 - 10'
• 11 - 20 = '11 - 20'
• 21 - 50 = '21 - 50'
• 51 - HIGH = '> 50'

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'

NOTE: Variable discontinued in 2000.

ODT_ATFAULT

    ODOT-AT-FAULT-FLAG

NON-LABELED VARIABLE

ODT_PERSON_CNT

ODOT-PEOPLE-FOUND-COUNT

NON-LABELED VARIABLE

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'

POC1

           PUBLIC PROPERTY DAMAGE

• 01 = 'NONE'
• 02 = 'CENTER FRONT'
• 03 = 'RIGHT FRONT'
• 04 = 'RIGHT SIDE'
• 05 = 'RIGHT REAR'
• 06 = 'REAR CENTER'
• 07 = 'LEFT REAR'
• 08 = 'LEFT SIDE'
• 09 = 'LEFT FRONT'
• 10 = 'TOP AND WINDOWS'
• 11 = 'UNDERCARRIAGE'
• 12 = 'LOAD/TRAILER'
• 13 = 'TOTAL (ALL AREAS)'
• 14 = 'OTHER'
• 15 = 'UNKNOWN'

PUB_PROP

       PUBLIC PROPERTY DAMAGE

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

NOTE: Variable discontinued in 2000.

SPD_LIMT

       SPEED LIMIT OF ROAD

• 0 = 'POSTED-SPEED-NOT-STATED'
• 5 - 20 = 'POSTED-UNDER-TWENTY'
• 25 = 'POSTED-TWENTY-FIVE'
• 30 = 'POSTED-THIRTY'
• 35 = 'POSTED-THIRTY-FIVE'
• 40 = 'POSTED-FOURTY'
• 45 = 'POSTED-FOURTY-FIVE'
• 50 = 'POSTED-FIFTY'
• 55 = 'POSTED-FIFTY-FIVE'
• 56 - 65 = 'POSTED OVER FIFTY-FIVE'
• OTHER = 'ERROR/OTHER CODES';

NOTES: 5-20 Contains all speeds less than or equal to 20 recorded from 1997 to 1999.  56-65 Contains all speeds greater than or equal to 56 recorded from 1997 to 1999.

STRKN_VEH

      STRIKING VEHICLE

• 1 = 'NO UNDERRIDE OR OVERRIDE'
• 2 = 'UNDERRIDE, COMPARTMENT INTRUSION'
• 3 = 'UNDERRIDE, NO COMPARTMENT INRRUSION'
• 4 = 'UNDERRIDE, COMPARTMENT UNTRUSION UNKNOWN'
• 5 = 'OVERRIDE, MOTORVEHICLE IN TRANSPORT'
• 6 = 'OVERRIDE, OTHER VEHICLE'
• 7 = 'UNKNOWN'

TOWED

          TOWED FLAG

• 1 = 'YES'
• 2 = 'NO'

TRF_CNTL

       TRAFFIC CONTROL OF VEHICLE

• 00 = 'TRAFFIC CONTROL NOT STATED'
• 01 = 'NO CONTROLS'
• 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 = 'POLICE OFFICER'
• 12 = 'PAVEMENT MARKINGS'
• 13 = 'CROSSWALK LINES'
• 14 = 'WALK/DONT WALK SIGNAL'
• 15 = 'TRAFFIC CONTROL DEVICE INOPERATIVE, MISSING, OBSCURED'
• 16 = 'OTHER'
• 17 = 'NOT REPORTED'
• 20 = 'NO TRAFFIC CONTROL-DRIVER'
• 21 = 'NO TRAFFIC CONTROL-PEDESTRIAN'

NOTE: Categories 20 and 21 apply to data generated before 2000.

TRK_BODY

       CARGO BODY TYPE

• 01 = 'NOT APPLICABLE'
• 02 = 'BUS (9-15 INCLUDING DRIVER)'
• 03 = 'VAN/ENCLOSED BOX'
• 04 = 'GRAIN/CHIPS/GRAVEL'
• 05 = 'POLE'
• 06 = 'CARGO TANK'
• 07 = 'FLATBED'
• 08 = 'DUMP'
• 09 = 'CONCRETE MIXER'
• 10 = 'AUTO TRANSPORTER'
• 11 = 'GARBAGE/REFUSE'
• 12 = 'OTHER'
• 13 = 'UNKNON'

NOTE: Variable added in 2000.

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'

NOTE: Variable discontinued in 2000.

TRKAXLES

       NUMBER OF TRUCK AXLES

NON-LABELED VARIABLE

TRVL_SPD

       SPEED DETECTED

• 1 = 'STATED'
• 2 = 'ESTIMATED'

VEH_DISP

       VEHICLE DISPOSITION

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

VEH_N_FROM

     VEHICLE/NON-MOTORIST DIRECTION

VEH_N_TO

       VEHICLE/NON-MOTORIST DIRECTION TO

• 1 = 'NORTH'
• 2 = 'SOUTH'
• 3 = 'EAST'
• 4 = 'WEST'
• 5 = 'NE'
• 6 = 'NW'
• 7 = 'SE'
• 8 = 'SW'
• 9 = 'UNKNOWN'

VEH_SPEED_POST_2000

SPEED OF VEHICLE

• 0 = 'VEH-SPEED-NOT-STATED'
• 1 - 20 = 'UNDER 20'
• 21 - 25 = 'SPEED 21-25'
• 26 - 35 = 'SPEED 26-35'
• 36 - 45 = 'SPEED 36-45'
• 46 - 55 = 'SPEED 46-55'
• 56 - 65 = 'SPEED 56-65'
• 66 - 75 = 'SPEED 66-75'
• 76 -HIGH = 'OVER 75'

NOTE: Variable added in 2000.

VEH_SPEED_PRE_2000

  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)'

NOTE: Variable discontinued in 2000.

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 2000+'
• 05 = 'MINIVAN'
• 06 = 'SPORTS UTILITY VEHICLE'
• 07 = 'PICKUP-TRUCK'
• 08 = 'PANEL/VAN'
• 09 = 'SINGLE UNIT TRUCK 2 AXLES, 6 TIRES'
• 10 = 'SINGLE UNIT TRUCK > 3 AXLES'
• 11 = 'TRUCK-TRAILER'
• 12 = 'TRUCK-TRACTOR BOBTAIL'
• 13 = 'TRACTOR-SEMI-TRAILER'
• 14 = 'TRACTOR-DOUBLE-SHORT'
• 15 = 'TRACTOR-DOUBLE-LONG'
• 16 = 'FIFTH-WHEEL OR CONVERT DOLLY'
• 17 = 'TRACTOR TRIPLES'
• 18 = 'MOTORCYCLE'
• 19 = 'MOTORIZED-BICYCLE'
• 20 = 'SCHOOL-BUS'
• 21 = 'CHURCH-BUS'
• 22 = 'PUBLIC-BUS'
• 23 = 'OTHER BUS'
• 24 = 'POLICE-VEHICLE'
• 25 = 'FIRE-TRUCK'
• 26 = 'AMBULANCE-RESCUE'
• 27 = 'TAXI'
• 28 = 'MOTOR-HOME'
• 29 = 'TRAIN'
• 30 = 'FARM-VEHICLE'
• 31 = 'FARM-EQUIPMENT'
• 32 = 'SNOWMOBILE'
• 33 = 'CONSTRUCTION-EQUIPMENT'
• 34 = 'ALL OTHERS'
• 35 = 'ANIMAL-WITH-RIDER'
• 36 = 'ANIMAL-WITH-BUGGY'
• 37 = 'BICYCLE'
• 38 = 'PEDESTRIAN'
• 39 = 'PEDALCYCLIST'
• 40 = 'SKATER'
• 41 = 'OTHER NON-MOTORIST'
• 42 = 'UNKNOWN'
• 50 = 'STRAIGHT-TRUCK'
• 51 = 'TRACTOR DOUBLE TRAILER'
• 52 = 'MC-UP-TO-350CC'
• 53 = 'MC-351CC-750CC'
• 54 = 'MC-OVER-750CC'
• 55 = 'FULL SIZE PRE 2000'

NOTE: Categories 50-55 apply to data generated before 2000.

VEHYR

          VEHICLE MODEL YEAR

NON-LABELED VARIABLE

NOTE: Model Year of the Vehicle (YYYY).

VIN

            VIN NUMBER

NON-LABELED VARIABLE

NOTE: Vehicle Identification Number.

LIST OF VARIABLES FOR THE OHIO INJURED OCCUPANTS SUBFILE

NOTE:   This file contains information on all passengers plus injured (but not uninjured) drivers.

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO STATE INJURED OCCUPANTS 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'
• 100-999 = 'ERROR CODES'

AIRBAG

         AIRBAG

• 1 = 'NOT-DEPLOYED'
• 2 = 'DEPLOYED-FRONT'
• 3 = 'DEPLOYED-SIDE'
• 4 = 'DEPLOYED BOTH FRONT/SIDE'
• 5 = 'NOT APPLICABLE'
• 6 = 'UNKNOWN'

NOTE: Variable added in 2000.

AIRBAG_SW

      AIRBAG SWITCH

• 1 = 'NOT PRESENT'
• 2 = 'IN ON POSITION'
• 3 = 'IN OFF POSITION'
• 4 = 'UNKNOWN'

ALCOHOL_TEST_STATUS

ALCOHOL TEST STATUS

• 1 = 'NONE'
• 2 = 'TEST REFUSED'
• 3 = 'TEST GIVEN, CONTAMINATED SAMPLE/UNUSABLE'
• 4 = 'TEST GIVEN, RESULTS KNOWN'
• 5 = 'TEST GIVEN, RESULTS UNKNOWN'
• 6 = 'UNKNOWN'
• 7 = 'NO'
• 8 = 'YES'

NOTE: Categories 7 and 8 apply for data generated before 2000.

ALTSTTYP

       ALCOHOL TEST TYPE

• 1 = 'NONE'
• 2 = 'BLOOD'
• 3 = 'URINE'
• 4 = 'BREATH'
• 5 = 'OTHER'

BAC

            BLOOD ALCOHOL CONTENT IN %

NON-LABELED VARIABLE

CASENO

         UNIQUE ACCIDENT CASE NUMBER

NON-LABELED VARIABLE

NOTE: Accident Case Number. The first 4 digits show the accident year.

CIT_LOC_CDE

    CITATION LOCAL CODE

• 1 = 'NO'
• 2 = 'YES'

NOTE: Variable added in 2000.

CITATION

       CITATION GIVEN

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

NOTE: Variable discontinued in 2000.

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'
• ' ' = 'NOT CODED'

NOTE: Variable discontinued in 2000.

DL_STATE

       DL STATE

NON-LABELED VARIABLE

DLCOUNTY

       DL COUNTY

NOTE: See formats in the accident section of the guidebook.

DRG_RES1

       DRUG TEST 1 RESULT

DRG_RES2

       DRUG TEST 2 RESULT

• 1 = 'NONE'
• 2 = 'MARIJUANA'
• 3 = 'COCAINE'
• 4 = 'OPIATES'
• 5 = 'AMPHETAMNES'
• 6 = 'PCP'
• 7 = 'OTHER'
• 8 = 'UNKNOWN AT TIME OF REPORTING'

DRUG_INV

       DRUGS INVOLVED

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

NOTE: Variable discontinued in 2000.

DRUG_TEST_STATUS

    DRUGS TEST STATUS

• 1 = 'NONE'
• 2 = 'TEST REFUSED'
• 3 = 'TEST GIVEN, CONTAMINATED SAMPLE/UNUSABLE'
• 4 = 'TEST GIVEN, RESULTS KNOWN'
• 5 = 'TEST GIVEN, RESULTS UNKNOWN'
• 6 = 'UNKNOWN'
• 7 = 'NO'
• 8 = 'YES'

NOTE: Categories 7 and 8 apply for data generated before 2000.

DRUG_TEST_TYPE

     DRUG TEST TYPE

• 1 = 'NONE'
• 2 = 'BLOOD'
• 3 = 'URINE'
• 4 = 'OTHER'

EJECT

          EJECTED FROM VEHICLE

• . = 'NOT CODED'
• 1 = 'NOT EJECTED'
• 2 = 'TOTALLY EJECTED'
• 3 = 'PARTIALLY EJECTED'
• 4 = 'NOT APPLICABLE'
• 5 = 'UNKNOWN'
• 6 = 'TRAPPED'

NOTE: Category 6 applies for data generated before 2000.

HELMET

         HELMET USE

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

NOTE: Variable discontinued in 2000.

INJ

            OCCUPANT INJURY

• 1 = 'NO INJURY'
• 2 = 'POSSIBLE INJURY'
• 3 = 'NON-INCAPACITATING INJURY'
• 4 = 'INCAPACITATING INJURY'
• 5 = 'FATAL INJURY'
• 6 = 'UNKNOWN'

P_TYPE

         OCCUPANT TYPE

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

PHYSCOND

       PEDESTRIAN PHYSICAL CONDITION

• 1 = 'NO INJURY'
• 2 = 'POSSIBLE INJURY'
• 3 = 'NON-INCAPACITATING INJURY'
• 4 = 'INCAPACITATING INJURY'
• 5 = 'FATAL INJURY'
• 6 = 'UNKNOWN'

REST1

          SAFETY EQUIPMENT

MOTORIST

• 01 = 'NON USED (MOTORIST)'
• 02 = 'SHOULDER BELT ONLY (MOTORIST)'
• 03 = 'LAP BELT ONLY (MOTORIST)'
• 04 = 'SHOULDER/LAP BELT (MOTORIST)'
• 05 = 'CHILD SAFETY SEAT (MOTORIST)'
• 06 = 'MC HELMET USED (MOTORIST)'
• 07 = 'USE UNKNOWN (MOTORIST)'

NON-MOTORIST

• 08 = 'NONE USED (NON-MOTORIST)'
• 09 = 'HELMET USED (NON-MOTORIST)'
• 10 = 'PROTECTIVE PADS (NON-MOTORIST)'
• 11 = 'REFLECTIVE CLOTHING (NON-MOTORIST)'
• 12 = 'LIGHTING (NON-MOTORIST)'
• 13 = 'OTHER (NON-MOTORIST)'
• 14 = 'UNKNOWN (NON-MOTORIST)'
• 15 = 'NOT STATED'
• 16 = 'AIR BAG'
• 17 = 'NONE INSTALLED' '

NOTE: Categories 15-17 apply for data generated before 2000.

SEATPOS

        SEATING POSITION

• .  = 'NOT CODED'
• 01 = 'FRONT - LEFT (MC DRIVER)'
• 02 = 'FRONT - MIDDLE'
• 03 = 'FRONT - RIGHT'
• 04 = 'SECOND - LEFT (MC PASS)'
• 05 = 'SECOND - MIDDLE'
• 06 = 'SECOND - RIGHT'
• 07 = 'THIRD - LEFT (MC PASSENGER/SIDE CAR)'
• 08 = 'THIRD - MIDDLE'
• 09 = 'THIRD - RIGHT'
• 10 = 'SLEEPER SECTION OF CAB'
• 11 = 'ENCLOSED CARGO AREA'
• 12 = 'UNENCLOSED CARGO AREA'
• 13 = 'TRAILING UNIT'
• 14 = 'EXTERIOR'
• 15 = 'OTHER'
• 16 = 'NON-MOTORIST'
• 17 = 'UNKNOWN'
• 20 = 'REAR LEFT'
• 21 = 'REAR CENTER'
• 22 = 'REAR RIGHT'
• 23 = 'HOOD / TRUNK / REAR OF VEHICLE'
• 24 = 'MOTORCYCLE FRONT'
• 25 = 'MOTORCYLCE REAR'
• 26 = 'PEDESTRIAN'

NOTE: Categories 20-26 apply for data generated before 2000.

SEX

            OCCUPANT GENDER

• 'M' = 'MALE'
• 'F' = 'FEMALE'
• 'U' = 'UNKNOWN'

SOB_TST

        ALCOHOL INVOLVED

• . = 'NOT CODED'
• 1 = 'NONE'
• 2 = 'YES-ALCOHOL SUSPECTED'
• 3 = 'YES-HBD NOT IMPAIRED'
• 4 = 'YES-DRUGS SUSPECTED'
• 5 = 'YES-ALCOHOL/DRUGS SUSPECTED'
• 6 = 'UNKNOWN'
• 7 = 'HBD ABILITY IMPAIRED'
• 0 = 'ALCOHOL NOT STATED'

NOTE: Categories 0 and 7 apply for data generated before 2000.

TAKEN_BY

       INJURED TAKEN BY

• 1 = 'NONE'
• 2 = 'EMS'
• 3 = 'POLICE'
• 4 = 'OTHER'
• 5 = 'UNKNOWN

NOTE: Variable added in 2000.

TRAPPED

        TRAPPED

• 1 = 'NOT TRAPPED'
• 2 = 'EXTRICATED BY MECHANICAL MEANS'
• 3 = 'FREED BY NON-MESHANICAL MEANS'
• 4 = 'UNKNOWN'

NOTE: Variable added in 2000.

VEHNO

          VEHICLE NUMBER

NON-LABELED VARIABLE

NOTE: Linkage Variable.

LIST OF VARIABLES FOR THE OHIO ROADLOG FILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO ROADLOG FILE

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

AADT

           WEIGHTED AVERAGE TOTAL ADT

• .   = 'MISSING'
• 00000-000100  =  '0-100'
• 000101-000500 = ' 101-500'
• 000501-001000 = ' 501-1,000'
• 001001-002000 = '1,001-2,000'
• 002001-005000 = '2,001-5,000'
• 005001-010000 = '5,001-10,000'
• 010001-015000 = '10,000-15,000'
• 015001-020000 = '15,001-20,000'
• 020001-040000 = '20,001-40,000'
• 040001 - HIGH = '40,000 +'

NOTE: This variable gives the total AADT.

AADT_BC

        ADT FOR TYPE B AND C TRUCKS

• .   = 'MISSING'
• 00000-000100  =  '0-100'
• 000101-000500 = ' 101-500'
• 000501-001000 = ' 501-1,000'
• 001001-002000 = '1,001-2,000'
• 002001-005000 = '2,001-5,000'
• 005001-010000 = '5,001-10,000'
• 010001-015000 = '10,000-15,000'
• 015001-020000 = '15,001-20,000'
• 020001-040000 = '20,001-40,000'
• 040001 - HIGH = '40,000 +'

NOTE: This variable gives the AADT for medium and large trucks. This includes tractor or truck with semi-trailers and trucks with trailers; single unit trucks most generally with dual rear tires (may be greater than 2-axle units).

AADT_PT

        ADT FOR PASSENGER CARS AND A TYPE TRUCKS

• .   = 'MISSING'
• 00000-000100  =  '0-100'
• 000101-000500 = ' 101-500'
• 000501-001000 = ' 501-1,000'
• 001001-002000 = '1,001-2,000'
• 002001-005000 = '2,001-5,000'
• 005001-010000 = '5,001-10,000'
• 010001-015000 = '10,000-15,000'
• 015001-020000 = '15,001-20,000'
• 040001 - HIGH = '40,000 +'

NOTE: This variable gives the AADT for passenger cars and small trucks. This includes panel and pick-up trucks, motorized recreational vehicles and school buses.

AADT_YR

        YEARS OF ADT COUNTS

NON-LABELED VARIABLE

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 to get information on the access control of segments.

AREA_CDE

       AREA CODE

NON-LABELED VARIABLE

BEGMP

          BEGINNING MILE POST

NON-LABELED VARIABLE – Beginning milepost in miles (XXX.XX)

CNT_TLOG

       COUNTY TRUE LOG

NON-LABELED VARIABLE

NOTE: This field is the true log mileage for the route within the county.

CNTY_RTE

       COUNTY ROUTE

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

NOTE: From year 2000, STATE_EQ is not required. Also RTE_SUFX became last digit of RTE_NBR.

COUNTY

         COUNTY

NOTE: See listings under accident section of the guidebook.

DISTRICT

       DISTRICT

NON-LABELED VARIABLE

DIVIDED

        ROAD IDENTIFICATION

• ' ' = 'NOT CODED'
• 'D' = 'DIVIDED'
• 'U' = 'UNDIVIDED'

ENDMP

          END MILE POST

NON-LABELED VARIABLE

NOTE: Ending milepost in miles (XXX.XX).

FED_ACES

       FEDERAL ACCESS CONTROL

• '1' = 'MULTI-LANE; MEDIAN; ACCESS INTERCHANGE; NO DIRECT PRIVATE ACCESS CONTROL'
• '2' = 'ACCESS AT INTERCHANGE OR PUBLIC STREET NO DIRECT PRIVATE ACCESS ALLOWED UNLESS PROPERTY RETAINS DEEDED RIGHTS AND THEN ONLY FOR RIGHT TURN. (LEFT TURN MAY BE ALLOWED IN CERTAIN CIRCUMSTANCES)'
• '3' = 'NO DIRECT PRIVATE ACCESS IF PROPERTY HAS ANOTHER REASONABLE ALTERNATIVE ACCESS OR OPPORTUNITY TO OBTAIN SUCH ACCESS; WHEN ALLOWED, GENERALLY FOR RIGHT TURN'

NOTE: Data is accurate for segments falling under category “1” beginning from 1998. 1997 data appears to have some errors. It should be noted that category “1” represents all interstates or interstates look alike segments with no at grade intersections. The accuracy of segments falling under other access control categories (2, 3 or 4), is still being reviewed.

FED_FACI

       FHWA TYPE OF FACILITY

• '1' = 'ONE WAY ROADWAY'
• '2' = 'TWO WAY ROADWAY'
• '3' = 'ONE WY STRUCTURE (BRIDGE, TUNNEL ETC.)'
• '4' = 'TWO WY ST (BRIDGE, TUNNEL ETC.)'
• ' ' = 'NOT CODED'

NOTE: FHWA HPMS required item.

FED_MEDW

       FHWA MEDIAN WIDTH

NON-LABELED VARIABLE

NOTE: FHWA required Median width. OH collects this variable for FHWA purpose. We are not sure about the data quality of this variable and recommend the use of MED_WID for all purposes.

FED_SPSY

       FHWA SPECIAL SYSTEMS

• '00' = 'NOT ON A SPECIAL SYSTEM'
• '01' = 'ADD TO INTERSTATE SYSTEM (139 (C))'
• '02' = 'ADD TO INTERSTATE SYSTEM (PRE 03/09/84)'
• '03' = 'ADD TO INTERSTATE SYSTEM (POST 03/09/84)'
• '04' = 'FUTURE ADDITION TO THE INTERSTATE SYSTEM'
• '05' = 'SECTION 332'
• '06' = 'FUTURE SECTION 332'
• '08' = 'STRAHNET'
• '11' = 'APPALACHIAN DEV NET'
• '13' = 'INDIAN RESERVE ROADS AND BRIDGES'
• '15' = 'NATIONAL FOREST HIGHWAY SYSTEM'
• '16' = 'NATIONAL FORRST DEVELOPMENT ROADS AND TRAILS'
• '18' = 'NATIONAL PARK SERVICE PARDKWAY'
• '19' = 'NATIONAL PARK ROADS AND TRAILS'
• '  ' = 'NOT CODED'

NOTE: FHWA HPMS required item.

FIPS_CDE

       FIPS CODE (GENERATED FOR MUNI SECTIONS ONLY)

NON-LABELED VARIABLE

FUNC_CLS

       FUNCTIONAL CLASS

• '01' = 'PRINICIPAL ARTERIAL (RURAL INTERSTATE)'
• '02' = 'PRINICIPAL ARTERIAL (RURAL OTHERS)'
• '06' = 'MINOR ARTERIAL (RURAL)'
• '07' = 'MAJOR COLLECTOR (RURAL)'
• '08' = 'MINOR COLLECTOR (RURAL)'
• '09' = 'LOCAL (RURAL)'
• '11' = 'PRINCIPAL ARTERIAL (URBAN INTERSTATE)'
• '12' = 'PRINCIPAL ARTERIAL (URBAN-FREEWAY & EXPRESSWAY'
• '14' = 'PRINCIPAL ARTERIAL (URBAN-OTHER)'
• '16' = 'MINOR ARTERIAL (URBAN)'
• '17' = 'COLLECTOR (URBAN)'
• '19' = 'LOCAL (URBAN)'
• '  ' = 'NOT CODED'

HOV

            FHWA HOV VEHICLES

• 0 = 'NO HOV LANES'
• 1 = 'EXCLUSIVE HOV LANES'
• 2 = 'NORMAL THROUGH LANES AS HOV (SPECIFIC TIMES)'
• 3 = 'SHOULDER/PARKING LANES AS HOV (SPECIFIC TIMES)'
• . = 'NOT CODED'

NOTE: FHWA HPMS required item.

HPMS

           HPMS CODES

• 'D' = 'DONUT AREA HPMS'
• ' ' = 'NOT CODED'
• '*' = 'HPMS -- REGULAR'

NOTE: An HPMS code indicates a section that was selected at random to be monitored periodically for changes, as defined in the FHWA HPMS field manual (HPMS = Highway Performance Monitoring System).

ID_CNTRL

       ID CONTROL CODE

• '0' = 'EQUATION'
• '1' = 'STATE LINE'
• '2' = 'COUNTY LINE'
• '3' = 'INTERCHANGE ROADWAYS'
• '4' = 'JUNCTION'
• '5' = 'OVERLAP'
• '9' = 'UNUSUAL POINT'
• 'Z' = 'ABANDONMENT'
• ' ' = 'NOT CODED'

INV_DTE

        INVENTORY DATE

NON-LABELED VARIABLE

JUR_TYPE

       JURISDICTION

• 'S' = 'STATE'
• 'H' = 'TURNPIKE'
• ' ' = 'NOT CODED'

LRS_BGPT

       LRS BEGINNING MILE POINT

NON-LABELED VARIABLE

LRS_BNDE

       LRS B NODE

• '0   ' = 'EQUATION'
• '1   ' = 'STATE LINE'
• '2   ' = 'COUNTY LINE'
• '3   ' = 'URBANIZED/URBAN AREA'
• '4   ' = 'INTERSECTION/JUNCTION'
• '5   ' = 'OVERLAP'
• '6   ' = 'INTERCHANGE'
• '7   ' = 'OVERPASS'
• '8   ' = 'NOT AN INT, CHANGE IN FUNC_CLS'
• '9   ' = 'LEAVE/REENTER'
• 'A   ' = 'THE TRUE BEG OR END OF A RTE'
• 'C   ' = 'NHS INTMDL ND (NO INT)'
• '    ' = 'NOT CODED';

NOTE: It is used to build the node/link files for the LRS (Linear Referencing System). Up to four attributes (in any sequence) may be coded for the node.  This field indicates the beginning of a node or the continuation of a node.

LRS_EDPT

       LRS ENDING MILE POINT

NON-LABELED VARIABLE

LRS_ENDE

       LRS END NODE

• '0  ' = 'EQUATION'
• '1  ' = 'STATE LINE'
• '2  ' = 'COUNTY LINE'
• '3  ' = 'URBANIZED/URBAN AREA'
• '4  ' = 'INTERSECTION/JUNCTION'
• '5  ' = 'OVERLAP'
• '6  ' = 'INTERCHANGE'
• '7  ' = 'OVERPASS'
• '8  ' = 'NOT AN INT, CHANGE IN FUNC_CLS'
• '9  ' = 'LEAVE/REENTER'
• 'A  ' = 'THE TRUE BEG OR END OF A RTE'
• 'C  ' = 'NHS INTMDL ND (NO INT)'
• '   ' = 'NOT CODED'

NOTE: It is used to build the node/link files for the LRS (Linear Referencing System). Up to four attributes (in any sequence) may be coded for the node.  This field indicates the ending of a node or the continuation of a node. The formats of these attributes are available with HSIS staff and will be provided upon request.

LRS_ID

         LRS Inventory Route Number (10 CHARAC) + LRS Sub-route Number

NON-LABELED VARIABLE

NOTE: This field is used for HPMS Item 7B in the conversion.  It is used as part of the LRS location identifier. If coded – record must be PAS (Principal Arterial System) or NHS (National Highway System) or Rural Minor Arterial (functional class is 06).

LRS_INRT

       LRS INVENTORY ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: This is a number used to uniquely identify a route within a county or perhaps throughout the state.

LRS_NDCN

       LRS NODE CODE (COUNTY)

• '  ' = 'NOT CODED'
• 'IN'= 'INDIANA'
• 'KY'= 'KENTUCKY'
• 'MI'= 'MICHIGAN'
• 'PA'= 'PENNSYLVANIA'
• 'WV'= 'WEST VIRGINIA'

LRS_NDNM

       LRS NODE NAME

NON-LABELED VARIABLE

NOTE: It is used to build the node/link files for the LRS (Linear Referencing System). It is comprised of a node code, node route, and a node sequence number. It is used to identify a node. An ‘*’ after the column numbers indicates that this field will be broken down into some individual fields immediately following this field. A ‘+’ after the column numbers indicates that this is a sub-field.

LRS_NDSQ

       LRS NODE SEQUENCE NUMBER

NON-LABELED VARIABLE

LRS_NRDE

       LRS NODE RTE DESIGNATION

NON-LABELED VARIABLE

LRS_SBRT

       LRS SUBROUTE NUMBER

NON-LABELED VARIABLE

NOTE: This is a number that uniquely identifies the AHEAD and BACK portions of an inventory route section where duplicate log points occur.

MED_TYPE

       FHWA MEDIAN TYPE

• '0' = 'NOT APPLICABLE'
• '1' = 'CURBED'
• '2' = 'POSITIVE BARRIER'
• '3' = 'UNPROTECTED'
• '4' = 'NONE'
• ' ' = 'OTHERWISE'

NOTE: This variable has usable data only for 2001. We checked the total mileage for divided segments and segments having valid median types and found that they were consistent for only 2001 data. The use of this variable for years before 2001 is not recommended.

MED_WID

        MEDIAN WIDTH

• 0 = 'NO WIDTH'
• 1-5 = '1 - 5'
• 6-10 = '6 - 10'
• 11-30 = '11 -30'
• 31-50 = '31 -50'
• 51-100 = '51-100'
• 101 - HIGH = '100 +'

NOTE: This field is coded for divided highways and is blank for undivided highways. For 1997 – 2000 data, 99 indicates 99 or higher. For future years median widths greater than 99 is available. This variable is to be used to get information on Median widths for all analysis.

MI_CLASS

       MILE CLASS (INCORPORATED/UNINCORPORATED)

• '1' = 'RURAL'
• '2' = 'MUNICIPAL (INCORPORATED)'
• '4' = 'RURAL AND MUNICIPAL (SPLIT)'
• ' ' = 'NOT CODED'

MUN_NAM

        MUNICIPALITY NAME

NON-LABELED VARIABLE

MVMT

           MILLION VEHICLE MILES OF TRAVEL (CREATED)

NON-LABELED VARIABLE

NHS_CDE

        NATIONAL HIGHWAY SYSTEM CODE

• 'N' = 'NHS (REGULAR)'
• 'H' = 'CONGRESSIONAL CORRIDORS'
• 'S' = 'STRAHNET'
• 'C' = 'STRAHNET CONNECTORS'
• '2' = 'MAJOR AIRPORT'
• '3' = 'MAJOR PORT FACILITY'
• '4' = 'MAJOR AMTRAK STATION'
• '5' = 'MAJOR RAIL/TRUCK TERMINAL'
• '6' = 'MAJOR INTERCITY BUS TERMINAL'
• '7' = 'MAJOR PUBLIC TRANSIT / MULTI-MODAL PAS TERMINAL'
• '8' = 'MAJOR PIPELINE TERMINAL'
• '9' = 'MAJOR FERRY TERMINAL'
• ' ' = 'NOT CODED'

NOTE: NHS replaces the old Federal-Aid system. All interstate routes are coded ‘N’. Codes 2-9 (intermodal connectors) are new for June 1997 FHWA HPMS submittal.

NHS_INTR

       NHS INTERMODAL NUMBER

NON-LABELED VARIABLE

NOTE: This field will be used to uniquely identify each NHS intermodal route.

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'

PAS_NHS

        PAS/NHS INTERSECTION MARKER

• '#' = 'PAS-NHS INTERSECTION'
• ' ' = 'NOT A PAS NHS INTERSECTION'

NOTE: This field in needed for the Linear Referencing System (LRS) reporting required by HPMS.

PAV_ROUG

       PAVEMENT ROUGHNESS

NON-LABELED VARIABLE

PAVECOND

       PAVEMENT CONDITION

• '00'-'10' = 'PCR 0-1'
• '11'-'20' = 'PCR 1-2'
• '21'-'30' = 'PCR 2-3'
• '31'-'40' = 'PCR 3-4'
• '41'-'50' = 'PCR 4-5'

PK_LANES

       PEAK LOAD LANES

NON-LABELED VARIABLE

NOTE: Peak lanes are the prevailing number of thru lanes carrying traffic during peak hours of use.

POP_GRP

        POPULATION

• ' ' = 'NOT APPLICABLE'
• '0000' - '0009' = '0 - 900'
• '0010' - '0025' = '1,000 - 2,500'
• '0026' - '0050' = '2,600 - 5,000'
• '0051' - '0100' = '5,100 - 10,000'
• '0101' - '0250' = '10,100 - 25,000'
• '0251' - '0500' = '25,100 - 50,000'
• '0501' - '1000' = '50,100 - 100,000'
• '1001' - '2500' = '10,100 - 250,000'
• '2500' - '9999' = '250,000 - 999,900'

NOTE: Population figure is in hundreds. This variable is populated only when MI_CLASS = 2 (Municipal).

RD_WIDTH

       ROADWAY WIDTH THRU LANES N/MEDIANS

• 00 = '00'
• 01-15 = '01 - 15'
• 16-18 = '16 - 18'
• 19-22 = '19 - 22'
• 23-25 = '23 - 25'
• 26-30 = '26 - 30'
• 31-40 = '31 - 40'
• 41-50 = '41 - 50'
• 51-60 = '51 - 60'
• 61-80 = '61 - 80'
• 81-99 = '81 - 99'
• 99 - HIGH = '99 & HIGHER'

NOTE: Highway surface width plus shoulders (in feet). Median width is not included. For 1997 – 1999 data category 99 indicates 99 or higher. For future years observations on roadway widths greater than 99 is available.

RODWYCLS

       ROADWAY TYPES (CREATED)

• '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'

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

RTE_NBR

        STATE ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: From year 2000, this variable became 5 characters with first digit being ‘0’ and last digit as RTE_SUFX.

RTE_SUFX

       STATE ROUTE NUMBER SUFFIX

• 'A' = 'ALTERNATE'
• 'B' = 'BYPASS'
• 'C' = 'SPUR OR CONNECTOR'
• 'D' = 'DIR ALT(1ST WITHIN CNTY)'
• 'E' = 'EAST'
• 'F' = 'DIR ALT(2ND WITHIN CNTY)'
• 'G' = 'DIR ALT(3RD WITHIN CNTY)'
• 'I' = 'INTERCHANGE ROADWAY'
• 'J' = 'AWAITING FINAL DISPOSITION'
• 'K' = 'TURNPIKE'
• 'N' = 'NORTH'
• 'P' = 'PROPOSED (NOT BUILT)'
• 'R' = 'REGULAR'
• 'S' = 'SOUTH'
• 'T' = 'TEMPORARY'
• 'W' = 'WEST'

NOTE: Code ‘I’ is for a route within an interchange used to connect ramps.

RTE_TYPE

       ROUTE TYPE (GENERATED)

• 1 = 'INTERSTATE'
• 2 = 'U.S. ROUTE'
• 3 = 'STATE ROUTE'

RURUID

         POPULATION (OVER/UNDER 5000) GENERATED

• ' ' = 'NOT CODED'
• 'O' = 'OVER (POP >= 5000)'
• 'U' = 'UNDER (POP < 5000)'

NOTE: This variable is populated only when MI_CLASS = 2(Municipal).

SCENIC

         SCENIC BYWAYS

• 'S' = 'STATE SCENIC BYWAY'
• 'N' = 'NATIONAL SCENIC BYWAY'
• 'A' = 'ALL AMERICAN ROAD'
• ' ' = 'NOT CODED'

SEG_LNG

        SEGMENT LENGTH

NON-LABELED VARIABLE – Length of section in miles (XXX.XX)

SEQ_NBR

        SEQUENCE NUMBER

NON-LABELED VARIABLE

NOTE: Variable added in 2005.

SHWD_LEFT_INSIDE

    SHOULDER LEFT INSIDE

SHWD_LEFT_OUTSIDE

   SHOULDER LEFT OUTSIDE

SHWD_RIGHT_INSIDE

   SHOULDER RIGHT INSIDE

SHWD_RIGHT_OUTSIDE

  SHOULDER RIGHT OUTSIDE

• 0 = 'ZERO'
• 1-3 = '1-3 FT'
• 4-6 = '4-6 FT'
• 7-9 = '7-9 FT'
• 10-13 = '10-13 FT'
• 14-99 = '14+ FT'
• . = 'NOT STATED';

SPDLIMT

        SPEED LIMIT

• 00 = 'SPEED LIMIT UNK'
• 01 - 05 = '01-05'
• 06 - 10 = '06-10'
• 11 - 15 = '11-15'
• 16 - 20 = '16-20'
• 21 - 25 = '21-25'
• 26 - 30 = '26-30'
• 31 - 35 = '31-35'
• 36 - 40 = '36-40'
• 41 - 45 = '41-45'
• 46 - 50 = '46-50'
• 51 - 55 = '51-55'
• 56 - 60 = '56-60'
• 61 - 65 = '61-65'
• 66 - 70 = '66-70'
• 71 - 75 = '71-75'
• 76 - 80 = '76-80'
• 81 - 85 = '81-85'

NOTE: Quality of data is questionable for 1997 to 1999.  Approximately 80 percent of the mileage in our system doesn’t have speed limit information for 1997 and 1998. For 1999, about 50 percent of mileage doesn’t have this information. For 2000 and 2001 data, this field covers about 99 percent of the mileage.

SRF_BAS

        STANDARD BASE CLASSIFICATION

• 'Z' = 'COMBINATION RIGID'
• 'X' = 'COMBINATION RIGID AND FLEXIBLE'
• 'T' = 'BRICK (RIGID)'
• 'R' = 'BRICK (FLEXIBLE)'
• 'P' = 'REINFORCED CONCRETE'
• 'N' = 'PLAIN CONCRETE'
• 'L' = 'PLANT MIX BITUMINOUS CONCRETE OR PENETRATION MACADAM'
• 'K' = 'WATER BOUND MACADAM'
• 'H' = 'RUBBLIZE AND ROLL CONCRETE'
• 'I' = 'STABILIZED (AGGREGATE BASE OR TRAFFIC COMPACTED)'
• 'E' = 'COMBINATION (FLEXIBLE)'
• 'F' = 'CRACK AND SEAT'
• ' ' = 'NOT CODED'

SRF_BASL

       LEFT SIDE SURFACE BASE TYPE

• 'Z' = 'COMBINATION RIGID'
• 'X' = 'COMBINATION RIGID AND FLEXIBLE'
• 'T' = 'BRICK (RIGID)'
• 'R' = 'BRICK (FLEXIBLE)'
• 'P' = 'REINFORCED CONCRETE'
• 'N' = 'PLAIN CONCRETE'
• 'L' = 'PLANT MIX BITUMINOUS CONCRETE OR PENETRATION MACADAM'
• 'K' = 'WATER BOUND MACADAM'
• 'H' = 'RUBBLIZE AND ROLL CONCRETE'
• 'I' = 'STABILIZED (AGGREGATE BASE OR TRAFFIC COMPACTED)'
• 'E' = 'COMBINATION (FLEXIBLE)'
• 'F' = 'CRACK AND SEAT'
• ' ' = 'NOT CODED'

SRF_BASR

       RIGHT SIDE SURFACE BASE CLASS TYPE

• 'Z' = 'COMBINATION RIGID'
• 'X' = 'COMBINATION RIGID AND FLEXIBLE'
• 'T' = 'BRICK (RIGID)'
• 'R' = 'BRICK (FLEXIBLE)'
• 'P' = 'REINFORCED CONCRETE'
• 'N' = 'PLAIN CONCRETE'
• 'L' = 'PLANT MIX BITUMINOUS CONCRETE OR PENETRATION MACADAM'
• 'K' = 'WATER BOUND MACADAM'
• 'H' = 'RUBBLIZE AND ROLL CONCRETE'
• 'I' = 'STABILIZED (AGGREGATE BASE OR TRAFFIC COMPACTED)'
• 'E' = 'COMBINATION (FLEXIBLE)'
• 'F' = 'CRACK AND SEAT'
• ' ' = 'NOT CODED'

SRF_TYPF

       SUMMARY OF FHWA SURFACE TYPE

• 'A' = 'PRIMITIVE ROAD'
• 'B' = 'UNIMPROVED ROAD'
• 'C' = 'GRADED AND DRAINED EARTH ROAD'
• 'E2'= 'GRAVEL ROAD'
• 'F' = 'BITUMINOUS (SURFACE TREATED)'
• 'G1'= 'MIX BITUMINOUS ROAD (BASE + SURFACE < 7 INCHES)'
• 'G2'= 'MIX BITUMINOUS ROAD (BASE + SURFACE >= 7 INCHES)'
• 'H1'= 'BITUMINOUS PENETRATION (BASE + SURFACE < 7 INCHES)'
• 'H2'= 'BITUMINOUS PENETRATION (BASE + SURFACE >= 7 INCHES)'
• 'I' = 'BITUMINOUS CONCRETE, ASPHALT, OR ROCK ASPHALT ROAD'
• 'J' = 'PCC ROAD'
• 'K' = 'BRICK ROAD'
• 'L' = 'BLOCK ROAD'
• ' ' = 'NOT CODED'

NOTE: This variable is collected for FHWA purposes. Though the codes are generally similar to SURF_TYP variable they do not match exactly. We recommend using SURF_TYP variable for all analysis.

SRF_TYPL

       LEFT SIDE STANDARD SURFACE CLASS

• 'A' = 'COMBINATION SURFACE'
• 'B' = 'BRICK'
• 'D' = 'REINFORCED CONCRETE'
• 'E' = 'PLAIN CONCRETE'
• 'G' = 'DENSE GRADED ASPHALTIC CONCRETE'
• 'I' = 'PENETRATION MACADAM'
• 'K' = 'OPEN GRADED ROAD MIX OR PUGMILL MIX'
• 'L' = 'SURFACE SEAL WITH COVER'
• 'S' = 'WOOD (BRIDGE DECK)'
• 'T' = 'STEEL PLATE (BRIDGE DECK)'
• ' ' = 'NOT CODED'

NOTE: Categories are same as standard surface type (SURF_TYP). It is populated only for divided segments or for those segments that have a combination base. Categories E, X or Z of SRF_BAS variable denote combination bases.

SRF_TYPR

       RIGHT SIDE SURFACE CLASS TYPE

• 'A' = 'COMBINATION SURFACE'
• 'B' = 'BRICK'
• 'D' = 'REINFORCED CONCRETE'
• 'E' = 'PLAIN CONCRETE'
• 'G' = 'DENSE GRADED ASPHALTIC CONCRETE'
• 'I' = 'PENETRATION MACADAM'
• 'K' = 'OPEN GRADED ROAD MIX OR PUGMILL MIX'
• 'L' = 'SURFACE SEAL WITH COVER'
• 'S' = 'WOOD (BRIDGE DECK)'
• 'T' = 'STEEL PLATE (BRIDGE DECK)'
• ' ' = 'NOT CODED'

NOTE: This variable is populated only for divided segments or for segments having a combination base. Combination bases are denoted by categories E, X or Z of standard Base classification variable (SRF_BAS). The codes of this SRF_TYPL and SRF_TYPR vary only when SURF_TYP is combined denoted by category A.

SRFTYPLL

       LEFT SIDE FHWA SURFACE TYPE

• 'A ' = 'PRIMITIVE ROAD'
• 'B ' = 'UNIMPROVED ROAD'
• 'C ' = 'GRADED AND DRAINED EARTH ROAD'
• 'E2'= 'GRAVEL ROAD'
• 'F ' = 'BITUMINOUS (SURFACE TREATED)'
• 'G1'= 'MIX BIT RD (BASE + SUR < 7 IN)'
• 'G2'= 'MIX BIT RD (BASE + SURF >= 7 IN)'
• 'H1'= 'BIT PEN (BASE + SURF < 7 IN)'
• 'H2'= 'BIT PEN (BASE + SURF >= 7 IN)'
• 'I ' = 'BC, A, OR RA ROAD'
• 'J ' = 'PCC ROAD'
• 'K ' = 'BRICK ROAD'
• 'L ' = 'BLOCK ROAD'
• '  ' = 'NOT CODED'

NOTE: This variable is collected for FHWA purposes. Though the codes are generally similar to SRF_TYPL, they don’t match exactly. We suggest that SRF_TYPL be used for all analysis.

SRFTYPLR

       FHWA RIGHT SIDE SURFACE TYPE

• 'A ' = 'PRIMITIVE ROAD'
• 'B ' = 'UNIMPROVED ROAD'
• 'C ' = 'GRADED AND DRAINED EARTH ROAD'
• 'E2'= 'GRAVEL ROAD'
• 'F ' = 'BITUMINOUS (SURFACE TREATED)'
• 'G1'= 'MIX BIT RD(BASE + SUR < 7 IN)'
• 'G2'= 'MIX BIT RD(BASE + SURF >= 7 IN)'
• 'H1'= 'BIT PEN (BASE + SURF < 7 IN)'
• 'H2'= 'BIT PEN (BASE + SURF >= 7 IN)'
• 'I ' = 'BC, A, OR RA ROAD'
• 'J ' = 'PCC ROAD'
• 'K ' = 'BRICK ROAD'
• 'L ' = 'BLOCK ROAD'
• '  ' = 'NOT CODED'

NOTE: The variable is collected for FHWA purposes. Though the codes are generally similar to SRF_TYPR, they don’t match exactly. We recommend that SRF_TYPR be used for all purposes.

STAT_EQ

        STATION EQUATION SORT FIELD

NON-LABELED VARIABLE

NOTES: (1) This sort code enables the records for a route to be sorted in the correct order (as the route would be driven).

(2) Variable discontinued in 2002.

STN_SUF

        STREET NAME SUFFIX

NON-LABELED VARIABLE

NOTE: Based on US Postal Service suffix abbreviations.  The street name field must be coded for this field to coded, except for suffix RAMP. For suffix RAMP, the street name field may be blank.

STR_PFX        STREET NAME DIRECTIONAL PREFIX

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

NOTE: This field is a directional prefix associated with the street name. The street name field must be coded for this field to be coded.

STRT_DIR

       STREET NAME DIRECTIONAL SUFFIX

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

NOTE: The street name field must be coded for this field to be coded.

STRT_NAM

       STREET NAME

NON-LABELED VARIABLE

NOTE: This name should correspond with maps and street signs.

SURF_TYP

       STANDARD SURFACE CLASSIFICATION

• 'A' = 'COMBINATION SURFACE'
• 'B' = 'BRICK'
• 'D' = 'REINFORCED CONCRETE'
• 'E' = 'PLAIN CONCRETE'
• 'G' = 'DENSE GRADED ASPHALTIC CONCRETE'
• 'I' = 'PENETRATION MACADAM'
• 'K' = 'OPEN GRADED ROAD MIX OR PUGMILL MIX'
• 'L' = 'SURFACE SEAL WITH COVER'
• 'S' = 'WOOD (BRIDGE DECK)'
• 'T' = 'STEEL PLATE (BRIDGE DECK)'
• ' ' = 'NOT CODED'

NOTE: This is the variable to be used to capture information on surface types for all analysis.

SURF_WID

       SURFACE WIDTH THRU LANES N/SHOULDERS

• 00 = '00'
• 01-15 = '01 - 15'
• 16-18 = '16 - 18'
• 19-22 = '19 - 22'
• 23-25 = '23 - 25'
• 26-30 = '26 - 30'
• 31-40 = '31 - 40'
• 41-50 = '41 - 50'
• 51-60 = '51 - 60'
• 61-80 = '61 - 80'
• 81-99 = '81 - 99'
• 99 - HIGH = '99 & HIGHER'

NOTE: Units are in feet. For 1997–1999, 99 indicates 99 or higher. For future years median widths greater than 100 feet are captured.

SURFWIDL

       LEFT SIDE SURFACE WIDTH IN FEET

• 00 = '00'
• 01-15 = '01 - 15'
• 16-18 = '16 - 18'
• 19-22 = '19 - 22'
• 23-25 = '23 - 25'
• 26-30 = '26 - 30'
• 31-40 = '31 - 40'
• 41-50 = '41 - 50'
• 51-60 = '51 - 60'
• 61-80 = '61 - 80'
• 81-99 = '81 - 99'
• 99 - HIGH = '99 & HIGHER'

NOTE: This variable is populated for divided segments and segments with combination bases. For combination bases, this variable provides the width of one unit of combined base. Categories E, X and Z of variable SRF_BAS denote combination bases.

SURFWIDR

       RIGHT SIDE SURFACE WIDTH IN FEET

• 00 = '00'
• 01-15 = '01 - 15'
• 16-18 = '16 - 18'
• 19-22 = '19 - 22'
• 23-25 = '23 - 25'
• 26-30 = '26 - 30'
• 31-40 = '31 - 40'
• 41-50 = '41 - 50'
• 51-60 = '51 - 60'
• 61-80 = '61 - 80'
• 81-99 = '81 - 99'
• 99 - HIGH = '99 & HIGHER'

NOTE: This variable is populated for divided segments and segments with combination bases. For combination bases, this variable provides the width of base other than that provided by SURFWIDL. For all segments having valid observations, summation of SURFWIDL and SURFWIDR always equals to SURF_WID.

SYS_CLAS

       SYSTEM CLASS

• 'I' = 'INTERSTATE'
• 'M' = 'MAJOR THOROUGHFARE'
• 'A' = 'AUXILIARY, STATE'
• 'L' = 'LOCAL, STATE'
• ' ' = 'NOT CODED'

UPDT_YR

        UPDATE YEAR

NON-LABELED VARIABLE

NOTE: This code is the two digit year of update or change.

LIST OF VARIABLES FOR THE OHIO POINT FILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO POINT FILE

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

CHNG_YR

        RECORD CHANGE YEAR

NON-LABELED VARIABLE

NOTE: This is a four-digit year (yyyy).

CNTY_RTE

       COUNTY ROUTE

NON-LABELED VARIABLE

NOTE: Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STAT_EQ. From year 2000, STATE_EQ is not required. Also RTE_SUFX became last digit of RTE_NBR.

CNTYLOG

        COUNTY TRUE LOG

NON-LABELED VARIABLE

COUNTY

         COUNTY

NOTE: See listings under accident section of the guidebook. 

DESC

           LOCATION DESCRIPTION

NON-LABELED VARIABLE

NOTE: Refer to “Notes” for REC_TYPE variable for more information.

DISTRICT

       DISTRICT

NON-LABELED VARIABLE

LOG_SUFX

       LOG POPINT SUFFIX

NON-LABELED VARIABLE

MILEPOST

       LOG POINT

NON-LABELED VARIABLE

NOTE: Milepost of the point in miles (XXX.XX).

MUNI_CDE

       MUNICIPAL CODE

NON-LABELED VARIABLE

NOTE: This field is for the three digit municipality code (political jurisdiction).

OVRLDIR

        OVERLAP LOG DIRECTION

• '+' = 'ASCENDING ORDER'
• '-' = 'DESCENDING ORDER'

REC_TYPE

       RECORD TYPE

• 'A' = 'ROUTE BEGINNING'
• 'B' = 'SPLIT JURISDICTION'
• 'C' = 'CORPORATION LIMIT'
• 'E' = 'STATION EQUATION'
• 'F' = 'MISCELLANEOUS'
• 'G' = 'BRIDGE'
• 'I' = 'INTERSECTION (AT GRADE)'
• 'J' = 'BEGIN GAP'
• 'K' = 'END GAP'
• 'M' = 'MILEPOST'
• 'N' = 'RAILROAD UNDERPASS'
• 'O' = 'OVERPASS'
• 'R' = 'RAILROAD AT GRADE'
• 'U' = 'UNDERPASS'
• 'V' = 'RAILROAD OVERPASS'
• 'W' = 'WEIGH STATION/REST AREA RAMP'
• 'X' = 'END OVERLAP'
• 'Y' = 'BEGIN OVERLAP'
• 'Z' = 'END OF ROUTE'

NOTE: Categories F and W added in 1999.

The record types noted above define the types of records (e.g., beginning or route, beginning or gap) or facility (e.g., overpass, RR grade crossing) present at the given location. Details of the coding for these types area available from the HSIS staff upon request. However, since “at grade intersections” (Record type “I”) are of most interest to HSIS users, the following describes these intersection records. The location of the intersection on the mainline is specified by CNTY_RTE. The DESC variable contains the following information on the cross route and cross route log point.

Example: C0042Aclaremont

Position 1 – Prefix of the cross route.

Position 2-5 – Numeric route number of the cross route.

Position 6 – Route suffix of the cross route.

Position 7-32 – Alphabetic name of the cross route/street.

RTE_DIR

        ROUTE DIRECTION

• 'N ' = 'NORTH'
• 'S ' = 'SOUTH'
• 'E ' = 'EAST'
• 'W ' = 'WEST'
• 'NE' = 'NORTHEAST'
• 'NW' = 'NORTHWEST'
• 'SE' = 'SOUTHEAST'
• 'SW' = 'SOUTHWEST'

NOTE: This is a two character field representing the general direction of the route. The first position always reflects the legal logged (inventoried) direction of the route. The second position is used as a tendency direction. The first position can not change during the course of the route.

RTE_NBR

        STATE ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: From year 2000, this variable became 5 characters with first digit being ‘0’ and last digit as RTE_SUFX.

RTE_PREF

       STATE ROUTE PREFIX

• 'I' = 'INTERSTATE'
• 'U' = 'U.S. ROUTE'
• 'S' = 'STATE ROUTE'

NOTE: An alphabetic character designating the type of route.

RTE_SUFX

       STATE ROUTE SUFFIX

• 'A' = 'ALTERNATE'
• 'B' = 'BYPASS'
• 'C' = 'SPUR OR CONNECTOR'
• 'D' = 'DIR ALT (1ST WITHIN CNTY)'
• 'E' = 'EAST'
• 'F' = 'DIRECTIONAL ALTERNATE (2ND WITHIN COUNTY)'
• 'G' = 'DIRECTIONAL ALTERNATE (3RD WITHIN COUNTY)'
• 'I' = 'INTERCHANGE ROADWAY'
• 'J' = 'AWAITING FINAL DISPOSITION'
• 'K' = 'TURNPIKE'
• 'N' = 'NORTH'
• 'P' = 'PROPOSED (NOT BUILT)'
• 'R' = 'REGULAR'
• 'S' = 'SOUTH'
• 'T' = 'TEMPORARY'
• 'W' = 'WEST'

NOTE: Code 'I' is for a route within an interchange used to connect ramps

SEQ_NBR

        SEQUENCE NUMBER

NON-LABELED VARIABLE

NOTE: This field allows more than one record with the same record type, at the same log point.

SPECDESC

       SPECIAL DESCRIPTION

• 'R' = 'RIGHT'
• 'L' = 'LEFT'
• 'I' = 'INTERCHANGE'

NOTE: If this field is coded 'I', then the record type must be code 'O' or 'U'.

STAT_EQ

        STATE EQUATION SORT

NON-LABELED VARIABLE

NOTE: This sort code enables the records for a route to be sorted in the correct order (as the route would be driven).

STRT_SUF

       STREET SUFFIX

• 'AL' = 'ALLEY'
• 'AV' = 'AVENUE'
• 'BO' = 'BOULEVARD'
• 'CE' = 'CENTER'
• 'CI' = 'CIRCLE'
• 'CO' = 'COURT'
• 'DR' = 'DRIVE'
• 'EX' = 'EXPRESSWAY'
• 'HI' = 'HIGHWAY'
• 'LA' = 'LANE'
• 'PA' = 'PARKWAY'
• 'PI' = 'PIKE'
• 'PL' = 'PLACE'
• 'RO' = 'ROAD'
• 'SQ' = 'SQUARE'
• 'ST' = 'STREET'
• 'TE' = 'TERRANCE'
• 'TR' = 'TRAIL'
• 'TU' = 'TURNPIKE'
• 'VI' = 'VIADUCT'
• 'WA' = 'WAY'
• 'EB' = 'EAST BOUND'
• 'WB' = 'WEST BOUND'
• 'NB' = 'NORTH BOUND'
• 'SB' = 'SOUTH BOUND'
• 'PK' = 'UNKNOWN'

TRUE_LOG

       STATE ROUTE TRUE LOG

NON-LABELED VARIABLE

NOTE: This is a state based log point giving the physical mileage from a route's entry into the State or its beginning within the State. The mileage does not re-start at county boundaries and equations are eliminated.

XCNTYRTE

       CROSS ROAD COUNTY ROUTE

NON-LABELED VARIABLE

NOTE: Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STATE_EQ.

XLOG_SUF

       CROSS ROUTE LOG SUFFIX

• ' ' = 'OTHER'
• 'B' = 'BACK STATION'

NOTE: "B" is for back station, which indicates that the log point is within a station equation. It is used for an add equation.

XMILEPST

       CROSS ROUTE MILEPOST

NON-LABELED VARIABLE

NOTE: Milepost of the crossing route in miles (XXX.XX).

XRTE_NBR

       CROSS ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: If this field is coded, then the cross route prefix must be coded.

XRTE_SUF

       CROSS ROUTE SUFFIX

• 'A' = 'ALTERNATE'
• 'B' = 'BYPASS'
• 'C' = 'SPUR OR CONNECTOR'
• 'D' = 'DIR ALT (1ST WITHIN CNTY)'
• 'E' = 'EAST'
• 'F' = 'DIRECTIONAL ALTERNATE (2ND WITHIN CNTY)'
• 'G' = 'DIRECTIONAL ALTERNATE (3RD WITHIN CNTY)'
• 'I' = 'INTERCHANGE ROADWAY'
• 'J' = 'AWAITING FINAL DISPOSOTION'
• 'K' = 'TURNPIKE'
• 'N' = 'NORTH'
• 'P' = 'PROPOSED (NOT BUILT)'
• 'R' = 'REGULAR'
• 'S' = 'SOUTH'
• 'T' = 'TEMPORARY'
• 'W' = 'WEST'

NOTE: Code 'I' is for a route within an interchange used to connect ramps.

XRTEPREF

       CROSS ROUTE PREFIX

• 'I' = 'INTERSTATE'
• 'U' = 'U.S. ROUTE'
• 'S' = 'STATE ROUTE'
• 'C' = 'COUNTY ROUTE'
• 'T' = 'TOWNSHIP ROUTE'
• 'N' = 'NATURAL RESOURCES

NOTE: An alphabetic character designating the type of cross route. If this field is coded, then the cross route number must be coded. If this field is coded: 'I' or 'U' or 'S', then the cross route suffix and cross route log must be coded.

LIST OF VARIABLES FOR THE OHIO CURVES FILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO CURVES FILE

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

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 to get information on the access control of segments.

AREACODE

       AREA CODE

NON-LABELED VARIABLE

BEGMP

          BEGIN LOG POINT OF CURVE

NON-LABELED VARIABLE

NOTE: Beginning milepost of the curve in miles (XXX.XX).

CNTY_RTE

       COUNT ROUTE

NON-LABELED VARIABLE

NOTE: Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STAT_EQ. From year 2000, STATE_EQ is not required. Also RTE_SUFX became last digit of RTE_NBR.

COUNTY

         COUNTY

NOTE: See listings under accident section of the guidebook. 

DEG_CURV

       DEGREE OF CURVE

• 1 - 5 = '1 TO 5'
• 6 - 10 = '6 TO 10'
• 11 - 20 = '11 TO 20'
• 21 - 30 = '21 TO 30'
• 31 - HIGH = '> 30'

DESC

           DESCRIPTION

NON-LABELED VARIABLE

DIR_CURV

       DIRECTION OF CURVE

• 'LT' = 'LEFT'
• 'RT' = 'RIGHT'

DISTRICT

       DISTRICT

NON-LABELED VARIABLE

DIVIDED

        DIVIDED HIGHWAY INDICATOR

• ' ' = 'UNDIVIDED'
• '*' = 'DIVIDED'

ENDMP

          END LOG POINT OF CURVE

NON-LABELED VARIABLE

NOTE: Ending milepost of the curve in miles (XXX.XX).

FUNC_CLS

       FUNCTIONAL CLASS

• '01' = 'PRINCIPAL ARTERIAL (RURAL INTERSTATE)'
• '02' = 'PRINCIPAL ARTERIAL (RURAL OTHERS)'
• '06' = 'MINOR ARTERIAL (RURAL)'
• '07' = 'MAJOR COLLECTOR (RURAL)'
• '08' = 'MINOR COLLECTOR (RURAL)'
• '09' = 'LOCAL (RURAL)'
• '11' = 'PRINCIPAL ARTERIAL (URBAN INTERCHANGE)'
• '12' = 'PRINCIPAL ARTERIAL (URBAN-FREEWAY & EXPRESSWAY'
• '14' = 'PRINCIPAL ARTERIAL (URBAN-OTHER)'
• '16' = 'MINOR ARTERIAL (URBAN)'
• '17' = 'COLLECTOR (URBAN)'
• '19' = 'LOCAL (URBAN)'
• '  ' = 'NOT CODED'

INV_DATE

       YEAR OF CODING CHANGE

NON-LABELED VARIABLE

MILE_CLS

       MILE CLASS

NON-LABELED VARIABLE

NO_LANES

       NUMBER OF LANES

• . = 'MISSING'
• 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'

RTE_NBR

        STATE ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: From year 2000, this variable became 5 characters with first digit being ‘0’ and last digit as RTE_SUFX

RTE_SUFX

       STATE ROUTE SUFFIX

• 'A' = 'ALTERNATE'
• 'B' = 'BYPASS'
• 'C' = 'SPUR OR CONNECTOR'
• 'D' = 'DIRECTIONAL ALTERNATE (1ST WITHIN COUNTY)'
• 'E' = 'EAST'
• 'F' = 'DIRECTIONAL ALTERNATE (2ND WITHIN COUNTY)'
• 'G' = 'DIRECTIONAL ALTERNATE (3RD WITHIN COUNTY)'
• 'I' = 'INTERCHANGE ROADWAY'
• 'J' = 'AWAITING FINAL DISPOSITION'
• 'K' = 'TURNPIKE'
• 'N' = 'NORTH'
• 'P' = 'PROPOSED (NOT BUILT)'
• 'R' = 'REGULAR'
• 'S' = 'SOUTH'
• 'T' = 'TEMPORARY'
• 'W' = 'WEST'

NOTE: Code 'I' is for a route within an interchange used to connect ramps.

SEG_LNG

        SEGMENT LENGTH

NON-LABELED VARIABLE

NOTE: Length of curve in miles (XXX.XX).

SEQ_NBR

        SEQUENCE NUMBER

NON-LABELED VARIABLE

STAT_EQU

       STATION EQUATION SORT FIELD

NON-LABELED VARIABLE

SYS_CLAS

       SYSTEM CLASS

• 'I' = 'INTERSTATE'
• 'M' = 'MAJOR THOROUGHFARE'
• 'A' = 'AUXILIARY, STATE'
• 'L' = 'LOCAL, STATE'
• ' ' = 'NOT CODED'

LIST OF VARIABLES FOR THE OHIO GRADES FILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO GRADES FILE

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

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 to get information on the access control of segments.

AREACODE

       AREA CODE

NON-LABELED VARIABLE

BEGMP

          BEGIN LOG POINT OF CURVE

NON-LABELED VARIABLE

NOTE: Beginning milepost of the grade in miles (XXX.XX).

CNTY_RTE

       COUNTY ROUTE COUNTY + RTE_NBR + RTE_SUFX + STAT_EQ

NON-LABELED VARIABLE

NOTE: Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STAT_EQ. From year 2000, STATE_EQ is not required. Also RTE_SUFX became last digit of RTE_NBR.

COUNTY

         COUNTY

NOTE: See listings under accident section of the guidebook. 

DESC

           DESCRIPTION

NON-LABELED VARIABLE

DIR_GRAD

       DIRECTION OF GRADE

• '+' = 'UPGRADE'
• '-' = 'DOWNGRADE'

DISTRICT

       DISTRICT

NON-LABELED VARIABLE

DIVIDED

        DIVIDED HIGHWAY INDICATOR

• ' ' = 'UNDIVIDED'
• '*' = 'DIVIDED'

ENDMP

          END LOG POINT OF CURVE

NON-LABELED VARIABLE

NOTE: Ending milepost in miles (XXX.XX).

FUNC_CLS

       FUNCTIONAL CLASS

• '01' = 'PRINCIPAL ARTERIAL (RURAL INTERSTATE)'
• '02' = 'PRINCIPAL ARTERIAL (RURAL OTHERS)'
• '06' = 'MINOR ARTERIAL (RURAL)'
• '07' = 'MAJOR COLLECTOR (RURAL)'
• '08' = 'MINOR COLLECTOR (RURAL)'
• '09' = 'LOCAL (RURAL)'
• '11' = 'PRINCIPAL ARTERIAL (URBAN INTERCHANGE)'
• '12' = 'PRINCIPAL ARTERIAL (URBAN-FREEWAY & EXPRESSWAY'
• '14' = 'PRINCIPAL ARTERIAL (URBAN-OTHER)'
• '16' = 'MINOR ARTERIAL (URBAN)'
• '17' = 'COLLECTOR (URBAN)'
• '19' = 'LOCAL (URBAN)'
• '  ' = 'NOT CODED'

INV_DATE

       YEAR OF CODING CHANGE

NON-LABELED VARIABLE

MILE_CLS

       MILE CLASS

NON-LABELED VARIABLE

NO_LANES

       NUMBER OF LANES

• . = 'MISSING'
• 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'

PCT_GRAD

       PERCENT OF GRADE

• 1 - 3 = '1% to 3%'
• 4 - 5 = '4% to 5%'
• 6 - 8 = '6% to 8%'
• 9 - 10 = '9% to 10%'
• 11 - 15 = '11% to 15%'
• 16 - 99 = '> 15%'

RTE_NBR

        STATE ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: From year 2000, this variable became 5 characters with first digit being ‘0’ and last digit as RTE_SUFX.

RTE_SUFX

       STATE ROUTE SUFFIX

• 'A' = 'ALTERNATE'
• 'B' = 'BYPASS'
• 'C' = 'SPUR OR CONNECTOR'
• 'D' = 'DIR ALT (1ST WITHIN CNTY)'
• 'E' = 'EAST'
• 'F' = 'DIRECTIONAL ALTERNATE (2ND WITHIN COUNTY)'
• 'G' = 'DIRECTIONAL ALTERNATE (3RD WITHIN COUNTY)'
• 'I' = 'INTERCHANGE ROADWAY'
• 'J' = 'AWAITING FINAL DISPOSITION'
• 'K' = 'TURNPIKE'
• 'N' = 'NORTH'
• 'P' = 'PROPOSED (NOT BUILT)'
• 'R' = 'REGULAR'
• 'S' = 'SOUTH'
• 'T' = 'TEMPORARY'
• 'W' = 'WEST'

NOTE: Code 'I' is for a route within an interchange used to connect ramps

SEG_LNG

        SEGMENT LENGTH

NON-LABELED VARIABLE

NOTE: Length of grade in feet (XXX.XX).

SEQ_NBR

        SEQUENCE NUMBER

NON-LABELED VARIABLE

STAT_EQU

       STATION EQUATION SORT FIELD

NON-LABELED VARIABLE

SYS_CLAS

       SYSTEM CLASS

• 'I' = 'INTERSTATE'
• 'M' = 'MAJOR THOROUGHFARE'
• 'A' = 'AUXILIARY, STATE'
• 'L' = 'LOCAL, STATE'
• ' ' = 'NOT CODED'

LIST OF VARIABLES FOR THE OHIO ANGLE POINT FILE

SAS FORMAT DEFINITIONS FOR VARIABLES FROM THE OHIO ANGLE POINT FILE

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

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 to get information on the access control of segments.

AREACODE

       AREA CODE

NON-LABELED VARIABLE

BEGMP

          BEGIN LOG POINT OF CURVE

NON-LABELED VARIABLE

NOTE: Beginning milepost of the angle point in miles (XXX.XX). The value is same as ending milepost.

CNTY_RTE

       COUNTY ROUTE

NON-LABELED VARIABLE

NOTE: Linkage variable consisting of COUNTY + RTE_NBR + RTE_SUFX + STAT_EQ. From year 2000, STATE_EQ is not required. Also RTE_SUFX became last digit of RTE_NBR.

COUNTY

         COUNTY

NOTE: See listings under accident section of the guidebook. 

DEG_CURV

       DEGREE OF CURVE

• 1 - 5 = '1 TO 5'
• 6 - 10 = '6 TO 10'
• 11 - 20 = '11 TO 20'
• 21 - 30 = '21 TO 30'
• 31 - HIGH = '> 30'

DESC

           DESCRIPTION

NON-LABELED VARIABLE

DIR_CURV

       DIRECTION OF CURVE

• 'LT' = 'LEFT'
• 'RT' = 'RIGHT'

DISTRICT

       DISTRICT

NON-LABELED VARIABLE

DIVIDED

        DIVIDED HIGHWAY INDICATOR

• ' ' = 'UNDIVIDED'
• '*' = 'DIVIDED'

ENDMP

          END LOG POINT OF CURVE

NON-LABELED VARIABLE

NOTE: Ending milepost of the angle point in miles (XXX.XX). The value is same as beginning milepost.

FUNC_CLS

       FUNCTIONAL CLASS

• '01' = 'PRINCIPAL ARTERIAL (RURAL INTERSTATE)'
• '02' = 'PRINCIPAL ARTERIAL (RURAL OTHERS)'
• '06' = 'MINOR ARTERIAL (RURAL)'
• '07' = 'MAJOR COLLECTOR (RURAL)'
• '08' = 'MINOR COLLECTOR (RURAL)'
• '09' = 'LOCAL (RURAL)'
• '11' = 'PRINCIPAL ARTERIAL (URBAN INTERCHANGE)'
• '12' = 'PRINCIPAL ARTERIAL (URBAN-FREEWAY & EXPRESSWAY'
• '14' = 'PRINCIPAL ARTERIAL (URBAN-OTHER)'
• '16' = 'MINOR ARTERIAL (URBAN)'
• '17' = 'COLLECTOR (URBAN)'
• '19' = 'LOCAL (URBAN)'
• '  ' = 'NOT CODED'

INV_DATE

       YEAR OF CODING CHANGE

NON-LABELED VARIABLE

MILE_CLS

       MILE CLASS

NON-LABELED VARIABLE

NO_LANES

       NUMBER OF LANES

• . = 'MISSING'
• 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'

RTE_NBR

        STATE ROUTE NUMBER

NON-LABELED VARIABLE

NOTE: From year 2000, this variable became 5 characters with first digit being ‘0’ and last digit as RTE_SUFX.

RTE_SUFX

       STATE ROUTE SUFFIX

• 'A' = 'ALTERNATE'
• 'B' = 'BYPASS'
• 'C' = 'SPUR OR CONNECTOR'
• 'D' = 'DIRECTIONAL ALTERNATE (1ST WITHIN COUNTY)'
• 'E' = 'EAST'
• 'F' = 'DIRECTIONAL ALTERNATE (2ND WITHIN COUNTY)'
• 'G' = 'DIRECTIONAL ALTERNATE (3RD WITHIN COUNTY)'
• 'I' = 'INTERCHANGE ROADWAY'
• 'J' = 'AWAITING FINAL DISPOSITION'
• 'K' = 'TURNPIKE'
• 'N' = 'NORTH'
• 'P' = 'PROPOSED (NOT BUILT)'
• 'R' = 'REGULAR'
• 'S' = 'SOUTH'
• 'T' = 'TEMPORARY'
• 'W' = 'WEST'

NOTE: Code 'I' is for a route within an interchange used to connect ramps.

SEG_LNG

        SEGMENT LENGTH

NON-LABELED VARIABLE

NOTE: All the segment lengths are zero since it describes only a point.

SEQ_NBR

        SEQUENCE NUMBER

NON-LABELED VARIABLE

STAT_EQU

       STATION EQUATION SORT FIELD

NON-LABELED VARIABLE

SYS_CLAS

       SYSTEM CLASS

• 'I' = 'INTERSTATE'
• 'M' = 'MAJOR THOROUGHFARE'
• 'A' = 'AUXILIARY, STATE'
• 'L' = 'LOCAL, STATE'
• ' ' = 'NOT CODED'