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
Federal Highway Administration
Office of Safety and Traffic Operations Research &
Development
U.S. Department of Transportation
Washington, DC 20590
Revised, April 2009
(NOTE: Changes from the previous edition of the Guidebook are shown in bold and italic.)
The Illinois data system includes the following basic files:
The first two of these files are currently being captured in the 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 included in the Programmer’s Guidebook, which is 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 Illinois 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.
It is noted at this point that the "raw files" received from Illinois are less "raw" than in other States since the data do not come directly from police accident report forms or from basic roadway inventory files. Instead, Illinois has developed their own safety information system, which includes a number of data edits and quality checks. The "raw" files that we are receiving for HSIS are those files that have already undergone this series of checks and edits.
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. In the 1985-91 files, the Occupant subfile only includes data on injured occupants. From 1992 onwards, the occupant subfile contains both injured and uninjured occupants. The vehicle and injured-occupant data can be linked to the basic accident data for specific cases using the accident report number and vehicle number. The accident subfile can be linked to the Roadlog file using three common variables -- county, route, 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 homogeneous section of 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.
Due to established priorities of effort, HSRC staff did not work with the Bridge File or the Railroad Grade-Crossing File. As is the case with most States, the Bridge File data contains information on bridge structures across the State. The data is considered quite accurate since it is based on the Federal bridge inventory. In a similar fashion, the Railroad Grade Crossing File is a file containing information on all grade-crossings in the State, and is prepared and maintained according to FHWA requirements.
Details of the three Accident subfiles and the Roadlog file are presented in the following section.
All police departments collect the accident data statewide on a standard form. Prior to 1992, crashes were reported if they involved personal injury or total property damage of $250 or more. The property damage threshold increased to $500 on January 1, 1992. The form is sent to the Division of Traffic Safety where coders/editors first match motorist reports with police reports, then look up a location code from a series of maps and "locate" each crash, and then code the basic accident data into the files. (The location code also triggers a computer table "look-up" which allows Illinois to attach a variable related to the Federal functional class to the accident data. In other States, such a variable would only be found on the roadway inventory file since the investigating officer would not be able to distinguish the various system types.)
The Illinois accident report form changed significantly in 1993. This new "self-coding" form resulted in new variables, changes in codes for existing variables, and changes in the manner in which the data is processed. As expected, the data for the "transition year" (i.e., 1993) are perhaps not as accurate as the data for other years. However, Illinois staff has conducted extensive data edits and recodes to correct as many problems as possible. In most cases, the data received by HSIS were recoded to "old formats" by Illinois for the 1993 file. However, additional codes were added at times. In 1994, new codes will be used by Illinois. To continue to allow use of multiple years of data, HSIS staff has modified the new Illinois codes such that they can be integrated with the old HSIS codes. These changes are noted in the SAS format sections that follow.
Approximately 400,000 accidents per year are reported in Illinois. The HSIS data set contains the subset of 1985-2007 accidents that occurred on the State-inventoried system. Almost all of these accidents can be linked with the Roadlog file. This data set includes between 105,000 and 205,000 accidents per year over the twenty two-year range and between 205,000 and 380,000 vehicles records per year for the same range. There are between 27,000 and 52,000 occupant records per year during 1985 to1991, and between 74,000 and 130,000 records per year during the 1992-2007. This increase is due to inclusion of the uninjured occupants from 1992 onwards as discussed earlier. In general, the number of linkable accidents and related vehicles has decreased over time.
For consistency with other HSIS states, pedestrian/equestrian/pedalcycle accidents (which are a subset of the Illinois raw accident file) have been merged into the Vehicle subfile. A "vehicle" on the accident form which is actually a pedestrian, equestrian, or pedalcycle can be identified by VEHTYPE=98 in the variable related to "Type of Vehicle." The remaining 200,000 to 300,000 "unlinkable" accidents each year are predominantly those occurring on city streets or minor township roads. These roadways are inventoried to a lesser extent than are the higher order roadways, but this lower level inventory has not been obtained for HSIS use since the accident coders do not attach a specific location reference code to the accident reports for such locations.
In addition, because no inventory data exist for "toll roads" or “ramps” in the Roadlog File, these accidents (which were included in the HSIS accident files for 1985-87) cannot be linked with roadway data for analysis purposes. Since the majority of the HSIS analyses involve linkage with roadway data, a decision was made to delete these toll road accidents from the HSIS files beginning with 1988. In addition, a second decision was made to delete all “ramp” accidents from the files beginning with the 1993 files. This results in an approximate 10 percent decrease in the total number of accidents (and vehicles and occupants) in the files between the 1992 data and the 1993 data.
As with other States, not all accidents on the file are reported by police. Approximately 4.8 percent of the records on the original 1985-87 files were driver reports which have no corresponding police report, and thus the data from the driver report is punched directly into the system. An additional 11.2 percent of the early files are "desk reports" filed by the State Police, city police or county sheriffs. These desk reports are not the result of a direct investigation by an officer on the scene, but instead are based on information provided to an officer at a police headquarters. Thus, both the desk reports and the driver reports would be expected to be somewhat less accurate than the "normal" reports filed by investigating officers on the scene. Driver reports would be assumed to be even less accurate due to expected "self-reporting" biases in variables related to fault, driver condition, safety belt usage, or other variables related to vehicular laws. Examination of the data did indeed indicate far more "unknown" and "not stated" codes in these driver reports. Due to this possible bias, the large size of the sample even without these reports, and the subsequent elimination of these reports from all HSIS analyses conducted during the 1988-89 period, the driver and desk reports have been eliminated from 1988 and later Accident Files. It is strongly recommended that the remaining 1985-87 driver and desk reports be eliminated from all analyses.
Approximately 70 percent of the accidents on the linkable file are property damage only and 0.5 percent are fatal accidents. (Single-variable tables presented in a later section of this documentation provide further details of these breakdowns.) Approximately 82 percent of the accidents are multi-vehicle in nature, while the remaining 18 percent are single-vehicle accidents of one type or another. When reporting agency was examined, it appears that the Illinois files are slightly more biased to urban/suburban crashes than are some of the other HSIS states.
An assessment of the completeness and accuracy of the data is based on conversations with Illinois staff, use of the data in prior HSIS analysis efforts, and a series of single-variable tabulations run each year for key analysis variables. These quality-control runs allows the HSIS staff to examine both the percent uncoded for each variable and changes across time in the individual codes within each key variable. These yearly runs are performed on all the variables.
These runs have consistently indicated that almost all of the variables in the three subfiles have very few uncoded cases and very few error codes. The only significant differences noted across the coded categories appear to be the result of the new report form in 1993. 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 which should have been somewhat similar on the accident subfiles according to their definitions (both within the same subfile and across subfiles). These single-variable tabulations were also compared to HSIS staff knowledge of the North Carolina accident files to see if major (unexplained) discrepancies existed. In general, the comparisons indicated the files were quite accurate. For example, the rural and urban breakdown in the "Federal Functional Class" variable matched quite well with the rural and urban breakdown in the "Traffic way Class" variable. The counts under the variable related to "Total Injuries" matched quite well with the accident severity variable, and counts from the collision type variable matched well with what would be expected from the "Number of Vehicles" variable. Again, there are a few cases in which variables are either less than totally consistent with other variables or have changed across time (e.g., head-on and sideswipe codes under "Type of Collision" appear to indicate opposing vehicles directions immediately prior to impact rather than their initial direction.) Again, where found, a "NOTE" has been included in the SAS formats.
However, in general, analysis of the Illinois accident, vehicle, and occupant subfiles indicated that these files are quite accurate in almost all cases, are quite internally consistent, and, with few exceptions, have very few "not stated" cases. The only major inconsistencies are due to changes in codes in the 1993 data and the fact that uninjured occupants are included in the Occupant Subfile for 1992 and 1993. For more details of the changes in codes from 1993 onwards, please refer to the format files.
Supplemental data on a vehicle characteristics (e.g., engine information, air bag presence, wheel base, etc.) can be developed by decoding the VIN (Vehicle Identification Number) collected on crash forms by police agencies in some states. For Accident/Vehicle Files from 1987-94, formats for the decoded VIN files were included in the original Guidebooks, and separate VIN files were developed for each year of data for the states of Utah, Illinois, Michigan, and North Carolina. When a vehicle in the Vehicle File had a legitimate VIN, this decoding was done using the VINDICATOR program distributed by the Highway Loss Data Institute of IIHS (the Insurance Institute of Highway Safety). This detailed information could then be linked back with the vehicle file using the Accident Case Number and the Vehicle Number.
Because of the very limited use of the VIN data by researchers and difficulties we encountered with the decoding process after 1994, the VIN variable listing found in the original Guidebooks for these states has been removed from this version. However, HSIS continues to capture the VIN, and has the capabilities of decoding the VIN for users. For Illinois, decoded VIN information is available for 1987-96, and VINs for later years can be decoded upon request. For more information on this data, contact the HSIS staff.
As noted above, the Roadlog file contains current characteristics of the road system. It contains information on homogeneous sections of highway for approximately 16,000 miles of roadway, with approximately 1,700 miles of Interstate, 9,600 miles of other primary roadway, and 5,000 miles of secondary, county and township roads. Currently, there are twenty oneRoadlog files in the HSIS system -- 1987-2007. Beginning in 1997, IL DOT started sending us new roadway files based on a new referencing system. When the mileages by different roadway types were checked against the 1994 data it was found that there was some increase in the mileage for various categories for 1997, but the mileage remained consistent between 1997 and 2007 data. The IL DOT indicated that in these new files there are some coinciding routes that were causing an increase in the total mileage due to double counting. However, the crashes are always posted to the higher order routes if two routes coincide. Hence it was decided to eliminate the lower order coinciding routes using CON_CURR variable. This elimination of roadway segments made the total mileage comparable to previous years. These new roadlog files contain additional data on intersections, horizontal and vertical curves that is different from the previous year files. More detailed explanation of these new variables is given below. Table 1 below provides a categorization of all two-way paved mileage in the 2007 data.
It should be noted that the definition of "homogeneous section" is based on fifteen different variables -- number of lanes, access control, one-way/two-way operation, shoulder width, shoulder type, median width, median type, parking lane width, ADT, speed limit, vertical curve length, horizontal curve radius, and three variables related to political boundaries and city size. Thus, anytime one of these variables changes, a new section is started. However, it is also noted that a new section is not begun with changes in other variables -- pavement width and percent trucks, for example. The inventory file is updated yearly based on inventories performed by district field personnel. When a new section of roadway is planned, a "blank" record is put into the file indicating that a roadway section will be added, but no data is entered at this point. Once the roadway is completed and open for traffic, it is inventoried by the field personnel. The characteristics of the completed road are compared to those on the plans, and a listing of the true characteristics is sent back to headquarters to be entered in the inventory file.
| Roadway Category | Mileage |
| Urban Freeways | 748.81 |
| Urban Freeways < 4 Lanes | 15.77 |
| Urban Multilane Divided Non-Freeways | 1343.95 |
| Urban Multilane Undivided Non-Freeways | 861.26 |
| Urban 2 Lane Highways | 2375.16 |
| Rural Freeways | 1318.67 |
| Rural Freeways < 4 Lanes | 39.22 |
| Rural Multilane Divided Non-Freeways | 309.45 |
| Rural Multilane Undivided Non-Freeways | 34.14 |
| Rural 2 Lane Highways | 9681.44 |
| Other | 238.51 |
| Total | 16966.38 |
A similar updating procedure is carried out when improvements (such as 3R improvements) or modifications of the roadway are carried out. When a large-scale modification such as a lane widening or curve flattening is planned for a section of road, district engineers make note of the fact that the roadway inventory will have to be changed as soon as the road is completed. When the modification is completed, the field personnel inventory the new roadway; send the revised data to headquarters, and the data is entered into the inventory file. The file is then completely updated at the end of each year. (It is noted that the updated file is usually available around April 1 of the following year.)
The file contains approximately 80,000 to 160,000 records during the period 1987-2007, each representing a section of "homogeneous" roadway where characteristics remain constant. Thus, the average section length is about 0.15 mile. Approximately 60 % of the mileage is in non-municipal (rural) areas, and 70 % are two-lane roadways.
Note that prior to 1997, horizontal curvature information was captured on the roadlog file rather than on a separate "curvature" file. (As will be described below, a separate curvature file exist for 1997 and later years.) In those earlier years, curve section beginning and end points are defined somewhat differently from what might be expected. More specifically, when curvature changes within a given section (say from a tangent to some degree of curve), the section is ended (i.e., a new section is begun) at the Point of Intersection of the tangents (PI) of the horizontal curve, not at the beginning of the curve. The "old" section (which actually contains one-half the curve) contains no information on curvature variables. The new roadlog section, which begins at the PI, contains all of the descriptive information related to the curve such as deflection angle, direction, radius and length. In some sense, if one wished to be able to define exactly where the curve existed on a particular piece of highway, one would have to go to the reference point which exists at the mid-point of the curve and then "back-track" for half the length of the curve back into the preceding section.
Fortunately, this does not raise great problems if one is simply trying to link accidents with their respective curvature data since the DOT coders who "locate" the accidents always code all accidents on a given curve to the reference point for the PI. Thus, accidents can be linked to their respective curve information. The only exception that might cause some problems would be if an intersection fell within the curve itself. In this case, accidents, which the coders judge to be related to the intersection, would be coded to the intersection rather than to the PI of the curve. In summary, for years prior to 1997 information on horizontal curves is available in the roadlog file. From 1997 onwards, this information is available in a separate curvature file.
However, of significant importance from an analysis perspective is the fact that the only curves which have complete data on the file are those "potentially substandard" curves which have radii equal to or less than 2291.83 feet (approximately a 2.5 degree curve). Detailed data are not collected on flatter curves, although partial data (such as deflection angle or direction) may appear on the file if the district engineer wishes to have a "curve marker" there. It is also the case that information on curves is only collected in rural areas and is not collected on Interstate roadways where all curves are assumed to meet federal standards. However, there is some information on curves on Interstates, when a district engineer feels that the curve is sub-standard. However, this is neither a complete census nor a random sample and care should be exercised while using this data. Thus, it would appear that the most consistent curvature data would be on those curves where a radius is greater than 2291 feet, and the analyst must be aware that the range of curves available for analysis does not include the flatter (less than 2.5 degree) curves.
For all years, information on vertical grade and vertical curvature is also included on the Roadlog File. However for years prior to 1997 no beginning and ending milepost information is available. Hence linking crashes to vertical curves for these years is not possible. Also, similar to the horizontal curve data, preliminary analyses with the vertical grade and curve variables and subsequent conversations with Illinois staff indicated that these vertical variables are only coded in those cases in which the engineering staff considers the existing vertical curve to be "substandard" in nature. Thus, the vertical grade data is neither a full sample nor a random sample of the roadway, and care must be taken in using it in analyses.
As with the accident files, the assessment of accuracy and completeness of the Roadlog File data is based on input from Illinois staff, prior HSIS analyses with the data, and a series of single-variable tabulations for all variables in the file which are run and reviewed each time a new annual file is entered into the HSIS. In addition, traffic variables concerning the AADT and percent trucks, and alignment variables concerning horizontal curve deflection angle, radius, and direction and vertical curve length and entering/leaving grade are included.
The quality control runs consistently indicate that most of the variables contained very few uncoded or obviously miscoded values -- only one to three percent in most cases. There are some cases where a "zero" value may well be both a valid value and may indicate uncoded data (such as with surface condition rating), but even here the percent of sections coded as zero is less than one percent of the file. Where higher percentages of uncoded data or error codes have been found, a "NOTE" is included in the SAS format.
Further assessment of the accuracy of the data included comparison of the limited number of similar variables in the file. These comparisons, subsequent HSIS analyses with the files, and the update procedures described above lead to the conclusion that the roadway inventory data is quite accurate.
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 inquire from data users, whose most frequent questions have concerned either crash frequencies or rates (per MVMT) for one or more of these roadway classes.
HSIS staff has stopped labeling shoulder type and shoulder width variables as left and right shoulder type and shoulder width respectively from 1997 onwards. Instead, they are labeled as inside and outside shoulder types and shoulder widths. Further details along with the new variable names are given in the FORMAT section of this guidebook. This change in variable labeling is based on the definition provided in the IRIS manual if IL DOT.
As indicated earlier the Roadlog File contains information on AADT, percent trucks for 1990 and earlier, and commercial vehicle AADT for 1991 and later files. These data are developed in Illinois' traffic volume counting program, and 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 "coverage" counts conducted each year. Before 2001, Illinois had 49 automatic traffic recorders (ATRs), of which 21 were capable of collecting counts by vehicle class in accordance with FHWA's Scheme F. The ATR locations on the five different classes of roadway included seven on rural Interstate roadway, six locations on urban Interstate locations, 12 locations on other rural roadways, 19 locations on other urban routes, and five locations on “recreational” routes. From 2001, Illinois has 87 ATRs, of which 38 are capable of collecting counts by vehicle class in accordance with FHWA`s Scheme F. The ATR locations on the five different classes of roadway include 11 locations on rural interstate, 6 locations on urban interstate, 16 locations on other rural roadways, 49 locations on other urban routes, and five locations on “recreational” routes.
In addition to the ATR data, short term traffic counts on Interstate and primary highway systems are done on a 2 year cycle. Before 2000, during even-numbered years, portable counter devices were deployed in combination with pre established in pavement loop detectors. Typically, the counter devices were deployed during one week of the year at any given site. Short counts (e.g., 24- or 48 hour counts) were collected on Monday through Thursday only. It should be noted that a sample of Interstate sections was counted one week out of every four months. During odd-numbered years, the Illinois DOT conducted a comprehensive interchange ramp counting program on State Highways. These ramp counts were used to supplement ADT data for sections where the State did not have monitors (i.e., counter devices). In total, it was estimated that approximately 96 percent of the primary system is covered during each two-year cycle. From 2000, Illinois started using magnetic lane counters for 24-hour counts during every odd-numbered year. The magnetic lane counters provide volume as well as vehicle classification by length in three categories (passenger vehicles, single-units, multi-units). Using the magnetic lane counters allow IDOT to collect mainline data for all State primary routes, except the interstates in Chicago area. The Chicago area interstates are counted with loops by the Expressway Surveillance program and the Illinois Tollway Authority. Collecting the mainline data eliminates the need for ramp counting. Short counts (e.g., 24- or 48 hour counts) are collected on Monday through Thursday only. In total, an estimated 99 percent of the primary system is covered during each two-year cycle.
For other non primary roads (i.e., the "off" marked route system), Illinois collects 24-hour coverage counts in approximately 20 percent of the counties once every five years. However, the Northeast Counties are done every four years. With the exception of Cook County, which is also on a four-year cycle, urban areas within counties are counted on a five-year statewide cycle.
Before 2001, additional vehicle classification counts are conducted on HPMS sections. These were made at 300 locations over a three-year cycle (i.e., approximately 100 each year) to form a representative distribution for the State. The 300 HPMS sections use for classification have been eliminated from 2001 onwards. Instead of using HPMS sample locations, the use of the magnetic lane counts provides vehicle classification by length for the complete State Primary system every two years. Rather than sampling, system-wide truck VMT based on actual counts is used.
Finally, the districts often have need for additional traffic data. Consequently, when requested, the State collects 12 hour turning movement counts at intersection and other "special" traffic data to satisfy these needs.
To convert the short-term coverage counts to AADT, Illinois applies adjustments for seasonal differences in the daily traffic. For seasonal corrections, each coverage count location is assigned to one of the five categories of roadway where permanent counters are located as defined above. The seasonal factors are based on averages from all ATRs in that group.
When a road section is not counted during a given year, growth factors are developed and applied to the most recent prior year's count. Average growth factors are created each year for each functional class of roadway using ATR data and data from adjusted short counts for the current year. The growth factor applied to a particular uncounted section is based on its functional class. For sections where no prior AADT exist, AADT/mile averages by functional class are developed and then used in order to "fill in" the AADT's.
Finally, it should be noted that the percentages of truck-related "Heavy Commercial Volumes” included "two-axle trucks with six or more tires plus multi-axle vehicles", prior to 2001. Thus, while pick-ups and vans were excluded, this combination did include single trucks, tractor-semi combinations and buses. Thus, it couldn’t be considered a count of just the multiple unit (tractor-trailer) trucks that were found on the roadway system.
After 2001, Illinois’ implementation of the vehicle length for truck classification instead of axle classification was approved by FHWA and conforms the new Traffic Monitoring Guide. Illinois worked closely with FHWA during the time of research and testing on the different equipment that was looked at to solve Illinois needs. While the permanent ATR locations still collect the Scheme F categories, Illinois only uses the three categories (PV, SU, MU) for their publications and in-house use.
(Note that in 1997, Illinois stopped providing the intersection data as described in this section. For 1997 and later years, each roadway segment contains three sets of variables to indicate location, type and orientation of intersections. Further details are provided below each of the variables in the FORMAT section of this guidebook for roadlog file.)
The Illinois base roadway inventory file contains two types of records. First, homogeneous sections are defined by unique beginning and ending mileposts, with the two milepoints never being equal. Second, an intersection-location record is included for each intersection, which falls in a given homogeneous section. Thus, if three intersections fall within a given section, three records with mileposts between the original beginning and ending mileposts will be provided. These intersection-location records are defined by having the beginning and ending mileposts equal to each other.
In building the HSIS files, we have separated all intersection records into a separate file, with one such file corresponding to each yearly Roadlog File. Each record on this file contains the milepost (reference point) and all variables appearing on the Roadlog section file, and the data included refer to the section of roadway downstream from the intersection. Unfortunately, this file does not contain desirable intersection-related variables such as type of intersection (e.g., T or cross), entering traffic volumes, or traffic control type (although this latter variable may be available after 1989). However, this file can be used in two ways. First, if one were to desire to do an analysis of "clean" sections without intersection-related accidents being part of the analysis, the Intersection-Location subfile could be merged with the appropriate sections in the Roadlog file, and all accidents, which fall at the intersection milepoints, could be deleted. (Illinois codes all intersection-related accidents to the specific milepost of the intersection, even if they occur upstream or downstream.) Second, as noted above, if one wished to analyze variables which do not cause breaks in sections (such as surface width or percent trucks), then it would be possible to divide the existing sections into shorter sections, with a break occurring at each intersection. These shorter sections could then be merged back into longer sections with breaks only on variables of interest. Some programming has been developed to do such merging.
As indicated above, curvature information on “deficient curves” is captured on the Roadlog File prior to 1997. From 1997 onwards, HSIS Staff has extracted new curvature variables from the Roadlog File and created a horizontal curvature file. As in earlier years, these files continue to contain information on “deficient” horizontal curves. IL defines a curve to be “deficient” if its radius is less than 2291.83 feet (>= 2.5 degrees). Detailed data are not collected on flatter curves, although partial data (such as deflection angle or direction) may appear on the file if the district engineer wishes to have a "curve marker" there. It is also the case that information on curves is only collected in rural areas and is not collected on Interstate roadways where all curves are assumed to meet federal standards. However, the engineering staff has recorded some curves on the interstate system, which are captured in the data. As stated above, these curves on interstate are neither a random sample nor a complete census. The majority of reported curves occur on U. S. and State maintained routes. An annual file is available for years 1997 to 2007. On the average it contains 3,400 curves covering approximately 450 miles. Based on the values of radius of curve, degree of curve has been calculated and added to the file. Thus, this file includes information on the degree of curve, the direction of curve, length of curve and radius of curve.
As noted above, the Illinois accident data are subdivided into three subfiles -- accident, vehicle and occupant. These subfiles can be linked together using the "case number" variable (i.e., CASENO), which is present in each of the three files.
This variable includes the accident year. When linking the Occupant subfile, the additional linking variable "vehicle number" (i.e., VEHNO) must match so that the occupants are associated with the vehicle in which they were traveling. To link the Vehicle subfile with the Accident alone, first sort both subfiles by case number. 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 linked by specifying an 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 presorted and the output will not be in any particular sort order unless ORDER BY is specified.
The Accident subfile can then be linked with the Roadlog File using information related to county, route prefix/type (e.g., I, US, MN, etc.), route number and milepost on the route. The actual linkage variables on the Accident file, which are used in the merging operation, are CNTYRTE and MILEPOST. The linkage variables on the Roadlog File are BEGMP, ENDMP and CNTY_RTE. The CNTYRTE and CNTY_RTE variables are computed linkage keys, which are created by combining variables, related to county (COUNTY), route prefix (RTE_PREF), and route number (RTE_NBR).
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. For the alternative SQL join, the analyst must specify an exact match on CNTYRTE and CNTY_RTE from the Accident and Roadlog files, and a range match where MILEPOST occurs between BEGMP and ENDMP. (Programs to accomplish this merging are documented in the HSIS Programmer's Guidebook, available at FHWA.)
Finally, where appropriate and possible, a format, which defines categories within a given variable, has been developed for HSIS SAS variables. These categories are shown in the pages below. These formats have been saved in a format library, which can be provided to the user. As a naming convention, the "format name" is the same as the variable name; with the only exception being for certain character variables (in contrast with numeric variables). More specifically, a SAS format name has to be preceded by a "$" if the variable is character in nature. There is an 8-character length limit on both variable name and format name. In cases where the variable name is already eight characters in length, the addition of the preceding "$" would make the format name one character too long. In these cases, the format name is the same as the variable name except the final character of the variable name is dropped.
HSIS Liaison – Michael Gillette (217-524-9108) -- is the HSIS Liaison for Illinois. He is the Technology Support Unit Chief in the Bureau of Safety Engineering of the Illinois DOT and oversees all safety files.
State Computer files and Accident Data contact – Lori Midden (217-785-2736) -- Ms. Midden is our main contact within the State of Illinois when questions arise concerning the Illinois state data files in general or the specifics of the accident data. She is the Special Studies and Systems Manager within the Bureau of Safety Data and Data Services of the Illinois DOT. She should be the primary contact for all questions, and will direct questions she can't answer to others.
Roadlog Information – Andrew Gossrow (217-785-8511) -- Mr. Gossrow is the contact person for questions related to the specifics of the Roadlog file. He works within the Illinois DOT Bureau of Roadway Planning, and his office staff is responsible for all aspects of the inventory information including traffic and curvature data. In his absence, Mr. Rob Robinson (217) 785-2353 can provide information.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AADT | ANNUAL ADT | ROADLOG | NUM | 79 |
| AADT_YR | YEAR OF ADT | ROADLOG | CHA(4) | 79 |
| ACC_DATE | DATE OF ACCIDENT | ACCIDENT | NUM | 36 |
| ACCESS | ACCESS CONTROL | ROADLOG | NUM | 79 |
| ACCTYPE_POST_93 | TYPE OF COLLISION | ACCIDENT | NUM | 35 |
| ACCTYPE_PRE_93 | TYPE OF COLLISION | ACCIDENT | NUM | 35 |
| ACCYR | ACCIDENT YEAR | ACCIDENT | NUM | 36 |
| ACTION | ARREST | VEHICLE | CHA(7) | 53 |
| ADMINHWY | ADMINISTRATIVE HIGHWAY SYSTEM | ROADLOG | CHA(1) | 79 |
| AGE | OCCUPANT AGE | INJ. OCCUPANTS | NUM | 72 |
| AGENCY | INVESTIGATING AGENCY | ACCIDENT | NUM | 36 |
| AIRBAG | AIRBAG DRIVER | VEHICLE | CHA(1) | 53 |
| ALIGN_CODE | ALIGNMENT | ACCIDENT | NUM | 37 |
| APPR_NBR | APPURTENANCE NUMBER | ROADLOG | NUM | 79 |
| AT_FAULT | AT FAULT | VEHICLE | CHA(2) | 53 |
| AVAI_ROW | AVAILABLE RIGHT OF WAY | ROADLOG | CHA(1) | 80 |
| BADGE | BADGE CODE | ACCIDENT | NUM | 37 |
| BEAT_CDE | BEAT CODE | ACCIDENT | NUM | 37 |
| BEGMP | BEGIN MILEPOST | ROADLOG | NUM | 80 |
| BEGMP | BEGINNING MILE POST | DEFICIENT CURVE | NUM | 112 |
| BUILD_BY | BUILT BY | ROADLOG | CHA(1) | 80 |
| CASENO | ACCIDENT CASE NUMBER | ACCIDENT | CHA(11) | 37 |
| CASENO | ACCIDENT CASE NUMBER | INJ. OCCUPANTS | CHA(11) | 72 |
| CASENO | CASE NUMBER | VEHICLE | CHA(11) | 53 |
| CAUSE1 | CONTRIB FACTOR 1 | ACCIDENT | CHA(2) | 37 |
| CAUSE2 | CONTRIB FACTOR 2 | ACCIDENT | CHA(2) | 37 |
| CITY | CITY OR TOWNSHIP | ACCIDENT | NUM | 38 |
| CITY_TWNSHIP_FLG | CITY/TOWNSHIP FLAG | ACCIDENT | CHA(1) | 38 |
| CLS_TFWY | CLASS OF TRAFFICWAY | ACCIDENT | NUM | 38 |
| CNTY_RTE | COUNTY ROUTE NUMBER | DEFICIENT CURVE | CHA(7) | 112 |
| CNTY_RTE | COUNTY ROUTE NUMBER | ROADLOG | CHA(7) | 80 |
| CNTYRTE | COMPUTED LINKAGE KEY | ACCIDENT | CHA(7) | 39 |
| COL_TYPE | COLLISION TYPE | VEHICLE | CHA(2) | 53 |
| COMM_VEH | COMMERCIAL VEHICLE | VEHICLE | CHA(1) | 53 |
| COMM_VOL | COMMERCIAL VOLUME | ROADLOG | NUM | 80 |
| COMMDATE | DATE | ROADLOG | CHA(4) | 81 |
| COUNTY | COUNTY | ACCIDENT | NUM | 39 |
| COUNTY | COUNTY | ROADLOG | NUM | 81 |
| CRSH_LAT | CRASH LATITUDE | ACCIDENT | CHA(3) | 39 |
| CRSH_LONG | CRASH LONGITUDE | ACCIDENT | CHA(3) | 39 |
| CRSH_X_CORD | CRASH X COORDINATE | ACCIDENT | CHA(8) | 39 |
| CRSH_Y_CORD | CRASH Y COORDINATE | ACCIDENT | CHA(8) | 39 |
| CTY_CLS | CITY CLASS CODE | ACCIDENT | NUM | 39 |
| CURB1 | CURB TYPE | ROADLOG | NUM | 83 |
| CURV_CUT | CURVE CUT | ROADLOG | CHA(1) | 83 |
| CURV_LGT | CURVE LENGTH | DEFICIENT CURVE | NUM | 112 |
| CURV_RAD | CURVE RADIUS | DEFICIENT CURVE | NUM | 112 |
| CURV_RAD | CURVE RADIUS | ROADLOG | NUM | 83 |
| DAM_OTHR | PROPERTY DAMAGE OTHER THAN VEH |
ACCIDENT | NUM | 40 |
| DEF_ANGL | DEFLECTION ANGLE | ROADLOG | CHA(7) | 83 |
| DEG_CURV | DEGREE OF CURVATURE | DEFICIENT CURVE | NUM | 112 |
| DIR_CURV | DIRECTION OF CURVE | DEFICIENT CURVE | CHA(1) | 112 |
| DIR_CURV | HORIZONTAL CURVE DIRECTION | ROADLOG | CHA(1) | 83 |
| DIR_TRVL | DIRECTION OF TRAVEL | VEHICLE | NUM | 53 |
| DIST | DISTRICT | ACCIDENT | NUM | 40 |
| DISTRICT | ILL DISTRICT | ROADLOG | NUM | 84 |
| DIVIDED | TRAFFICWAY DESCRIPTION | ACCIDENT | NUM | 40 |
| DRV_ACTN | DRIVER ACTION | VEHICLE | CHA(2) | 54 |
| DRV_AGE | DRIVER AGE | VEHICLE | NUM | 54 |
| DRV_BAC | DRIVER ALCOHOL PERCENT | VEHICLE | NUM | 54 |
| DRV_BAC2 | 2ND SOBRIETY TEST RESULTS | VEHICLE | CHA(2) | 55 |
| DRV_CLAS | DRIVER CLASS | VEHICLE | CHA(4) | 55 |
| DRV_COND | DRIVER CONDITION NEW | VEHICLE | CHA(1) | 55 |
| DRV_DOB | DRIVER BIRTH DATE | VEHICLE | CHA(8) | 55 |
| DRV_EJCT | DRIVER EJECTION | VEHICLE | CHA(1) | 56 |
| DRV_IMAG | IMAGE NUMBER | VEHICLE | NUM | 56 |
| DRV_INJ | DRIVER EXTENT OF INJURY | VEHICLE | NUM | 56 |
| DRV_LST | DRIVER LICENSE STATE | VEHICLE | CHA(2) | 56 |
| DRV_REEL | REEL NUMBER | VEHICLE | CHA(4) | 56 |
| DRV_REST | DRIVER RESTRAINT USAGE | VEHICLE | NUM | 56 |
| DRV_RPT | DRIVER REPORT | VEHICLE | NUM | 57 |
| DRV_SEX | DRIVER SEX | VEHICLE | NUM | 57 |
| EJCT | OCCUPANT EJECTION | INJ. OCCUPANTS | CHA(1) | 72 |
| END_RTE | END OF ROUTE | ROADLOG | CHA(1) | 84 |
| ENDMP | END MILE POST | DEFICIENT CURVE | NUM | 113 |
| ENDMP | END MILEPOST | ROADLOG | NUM | 84 |
| EXST_ROW | EXISTING RIGHT OF WAY | ROADLOG | NUM | 84 |
| F_INVLOC | FIRST INVOLVEMENT LOCATION | VEHICLE | NUM | 57 |
| FAUL_HGHT | FAULT HEIGHT | ROADLOG | NUM | 84 |
| FED_AID | FEDERAL AID (IN LIEU) | ROADLOG | NUM | 84 |
| FED_CLAS | FEDERAL CLASSIFICATION | ACCIDENT | NUM | 40 |
| FIRE | VEH FUEL LEAKS AND FIRE | VEHICLE | NUM | 58 |
| FLD_NAM1 | FIELD REF NAME 1 | ACCIDENT | CHA(3) | 41 |
| FLD_NAM2 | FIELD REF NAME 2 | ACCIDENT | CHA(3) | 41 |
| FLD_NBR1 | FIELD REF NBR 1 | ACCIDENT | NUM | 41 |
| FLD_NBR2 | FIELD REF NBR 2 | ACCIDENT | NUM | 41 |
| FLD_TYPE | FIELD REF TYPE | ACCIDENT | NUM | 41 |
| FRST_INV | FIRST INVOLVEMENT | VEHICLE | NUM | 58 |
| FUNC_CLS | FUNCTIONAL CLASS | ACCIDENT | CHA(1) | 41 |
| FUNC_CLS | FUNCTIONAL CLASS | ROADLOG | NUM | 85 |
| HIT_RUN | HIT AND RUN | ACCIDENT | CHA(1) | 42 |
| HOR_BEG | HORIZONTAL CURVE BEGINNING MILEPOST |
ROADLOG | NUM | 85 |
| HOR_BEGMP | HORIZONTAL CURVE BEGIN MILEPOST |
ROADLOG | CHA(5) | 85 |
| HOR_END | HORIZONTAL CURVE END MILEPOST | ROADLOG | NUM | 85 |
| HOR_ENDMP | HORIZONTAL CURVE END MILEPOST |
ROADLOG | CHA(5) | 86 |
| HOUR | TIME OF ACCIDENT | ACCIDENT | NUM | 42 |
| HPMS_IND | HPMS INDICATOR | ROADLOG | CHA(1) | 86 |
| HPMS_SEC | HPMS SECTION | ROADLOG | NUM | 86 |
| HPMS_SEG | HPMS SECTION SEGMENT | ROADLOG | NUM | 86 |
| HPMS1 | HPMS SECTION ID | ROADLOG | NUM | 86 |
| HZM_IND | HAZARDOUS MATERIAL | VEHICLE | CHA(1) | 59 |
| IMAG_NBR | IMAGE NUMBER | ACCIDENT | NUM | 42 |
| INJ | DRV/OCC INJURY | INJ. OCCUPANTS | CHA(8) | 72 |
| INSHTP1 | INSIDE SHOULDER TYPE 1 | ROADLOG | CHA(1) | 86 |
| INSHTP2 | INSIDE SHOULDER TYPE 2 | ROADLOG | CHA(1) | 87 |
| INSHWD1 | INSIDE SHOULDER WIDTH 1 | ROADLOG | NUM | 87 |
| INSHWD2 | INSIDE SHOULDER WIDTH 2 | ROADLOG | NUM | 87 |
| INT_NAME | INTESECTING RTE NBR | ACCIDENT | NUM | 42 |
| INT_PREF | INTERSECT RTE PREFIX | ACCIDENT | NUM | 42 |
| INT_QUAD | INTERSECTION QUADRANT | ACCIDENT | NUM | 43 |
| INT_REL | INTERSECTION RELATED | ACCIDENT | CHA(1) | 43 |
| INT_TYPE | INTERSECTION FEATURE | ROADLOG | CHA(1) | 88 |
| INTOX | ALCOHOL INVOLVED | VEHICLE | CHA(1) | 59 |
| INV_DIR | INVENTORY DIRECTION | ROADLOG | CHA(1) | 88 |
| KEY_RTE_APPRTE | KEY ROUTE APPURTENANCE NUMBER | ROADLOG | NUM | 88 |
| KEY_RTE_APPURTCD | KEY ROUTE APPURTENANCE TYPE | ROADLOG | CHA(1) | 88 |
| KEY_RTE_SEQNBR | KEY ROUTE SEQUENCE NUMBER | ROADLOG | CHA(4) | 88 |
| KEY_RTE_STATION | KEY ROUTE STATION | ROADLOG | NUM | 89 |
| KEY_RTE_SUF_CDE | KEY ROUTE SUFFIX CODE | ROADLOG | CHA(1) | 89 |
| KEY_RTE_TYPCD | KEY ROUTE TYPE CODE | ROADLOG | CHA(1) | 89 |
| LANEWID | AVERAGE LANE WIDTH | ROADLOG | NUM | 89 |
| LIGHT | LIGHT CONDITION | ACCIDENT | NUM | 43 |
| LOC_TYPE | LOCATION TYPE | ACCIDENT | NUM | 43 |
| LPK_REST | PARKING RESTRICTIONS LEFT | ROADLOG | CHA(1) | 89 |
| LST_SECD | LATEST CONSTRUCTION SECTION D | ROADLOG | CHA(15) | 89 |
| LST_SECE | LATEST CONSTRUCTION SECTION E | ROADLOG | CHA(10) | 89 |
| LST_UPDT | DATE OF LAST UPDATE | ROADLOG | CHA(8) | 90 |
| MAIN_DIS | MAINTENANCE DISTRICT | ROADLOG | NUM | 90 |
| MAIN_SEC | MAINTENANCE SECTION | ROADLOG | CHA(6) | 90 |
| MAINTENC | MAINTENANCE | ROADLOG | NUM | 90 |
| MED_TYPE | MEDIAN TYPE | ROADLOG | NUM | 90 |
| MEDWID | MEDIAN WIDTH | ROADLOG | NUM | 90 |
| MILEPOST | MILE STATION | ACCIDENT | NUM | 44 |
| MISCACT1 | DRV MISC ACTN 1 CD | VEHICLE | NUM | 59 |
| MOSTHARM | VEHICLE MOST HARMFUL INVOLVEMENT |
VEHICLE | CHA(1) | 61 |
| MRK_BEG | MARKED BEGINNING | ROADLOG | NUM | 91 |
| MRK_RTE1 | MARKED ROUTE1 | ROADLOG | CHA(6) | 91 |
| MRK_RTE2 | MARKED ROUTE2 | ROADLOG | CHA(6) | 91 |
| MRK_RTE3 | MARKED ROUTE3 | ROADLOG | CHA(5) | 91 |
| MRK_RTE4 | MARKED ROUTE4 | ROADLOG | CHA(5) | 91 |
| MRK_RTNBR | MARKED ROUTE NUMBER | ROADLOG | NUM | 91 |
| MRKD_RTE_BEGMP | MARKED ROUTE BEGINNING MILEPOST | ROADLOG | NUM | 91 |
| MULTICNT | AVERAGE ANNUAL DAILY MULTI- UNIT VOLUME |
ROADLOG | NUM | 92 |
| MUNI_NAME | MUNICIPAL NAME | ROADLOG | CHA(20) | 92 |
| MVMT | MILLION VEHICLE MILES OF TRAVEL |
ACCIDENT | NUM | 44 |
| MVMT | MILLION VEHICLE MILES OF TRAVEL |
ROADLOG | NUM | 92 |
| NAT_HWY | NATIONAL HIGHWAY SYSTEM | ACCIDENT | CHA(1) | 44 |
| NEW_ONEWAY | NEW ONEWAY INDICATOR | ROADLOG | CHA(1) | 92 |
| NHS_CDE | NATIONAL HIGHWAY SYSTEM | ROADLOG | CHA(1) | 92 |
| NO_LANES | TOTAL NUMBER OF LANES | ROADLOG | NUM | 92 |
| NO_SPLNS | NUMBER OF SPECIAL LANES | ROADLOG | NUM | 93 |
| NON_ATTN | NON-ATTAINMENT AREA | ROADLOG | NUM | 93 |
| NUM_K | TOTAL KILLED IN VEHICLE | VEHICLE | NUM | 61 |
| NUM_OCC | NO. OF OCCUPANTS IN VEHICLE | VEHICLE | NUM | 61 |
| NUMINJ | TOTAL NUMBER INJURD IN | VEHICLE | NUM | 61 |
| VEHICLE | ||||
| NUMVEHS | TOT-NBR-VEHICLES | ACCIDENT | NUM | 44 |
| OCC_AIR | OCCUPANT AIR BAG | INJ. OCCUPANTS | CHA(1) | 73 |
| OCC_IMAG | IMAGE NUMBER | INJ. OCCUPANTS | NUM | 73 |
| OCC_REEL | REEL NUMBER | INJ. OCCUPANTS | NUM | 73 |
| ODM_MILE | ODOMETER MILE | ROADLOG | NUM | 93 |
| ODM_SIGN | ODOMETER SIGN | ROADLOG | CHA(1) | 93 |
| OLD_AADT | OLD AADT | ROADLOG | NUM | 93 |
| OLD_DATE | DATE | ACCIDENT | NUM | 44 |
| ONEWAY | ONEWAY INDICATOR | ROADLOG | NUM | 94 |
| OP_ID | OPERATOR ID | ACCIDENT | NUM | 45 |
| OPCRSNBR | OPPOSITE ROAD CRS NUMBER | ROADLOG | NUM | 94 |
| OPP_FAULT | OPPOSITE ROAD FAULT | ROADLOG | CHA(3) | 94 |
| OPP_PAVDIS | OPPOSITE ROAD PAVEMENT DISTRESS |
ROADLOG | CHA(10) | 94 |
| OPP_RUTDEPT | OPPOSITE ROAD RUT DEPTH | ROADLOG | CHA(3) | 94 |
| ORG_SECB | ORIGINAL CONSTRUCTION SEC B | ROADLOG | CHA(15) | 94 |
| ORG_SECC | ORIGINAL CONSTRUCTION SEC C | ROADLOG | CHA(5) | 94 |
| OUTSHTP1 | OUTSIDE SHOULDER TYPE 1 | ROADLOG | CHA(1) | 94 |
| OUTSHTP2 | OUTSIDE SHOULDER TYPE 2 | ROADLOG | CHA(1) | 95 |
| OUTSHWD1 | OUTSIDE SHOULDER WIDTH 1 | ROADLOG | NUM | 95 |
| OUTSHWD2 | OUTSIDE SHOULDER WIDTH 2 | ROADLOG | NUM | 96 |
| OVHOBSNR | OVERHEAD OBSTRUCTION NUMBER | ROADLOG | CHA(7) | 96 |
| PAV_DIST | PAVEMENT DISTRESS | ROADLOG | CHA(10) | 96 |
| PAVECOND | PRESENT SERVICE RATING | ROADLOG | NUM | 96 |
| PCNT_TRK | PERCENTAGE TRUCKS | ROADLOG | CHA(2) | 96 |
| PED_AGE | AGE OF THE PED/PEDALCYCLIST | VEHICLE | CHA(2) | 61 |
| PED_CLT | PED TYPE OF CLOTHING | VEHICLE | CHA(1) | 62 |
| PED_FLAG | PEDESTRIAN FLAG | VEHICLE | CHA(1) | 62 |
| PED_LOC | PED/PEDAL LOCATION | VEHICLE | CHA(1) | 62 |
| PED_OTH | PEDESTRIAN/OTHER | VEHICLE | NUM | 62 |
| PED_VIS | DRIVER VISION | VEHICLE | CHA(1) | 62 |
| PEDACT | PED/PEDALCYLIST ACTION/MOVEMENT |
VEHICLE | NUM | 63 |
| PERSON_TYP | PERSON TYPE | VEHICLE | NUM | 63 |
| PHYSCOND | DRIVER PHYSICAL CONDITION | VEHICLE | NUM | 63 |
| PLN_SEQ | PLANNING SEQUENCE | ROADLOG | NUM | 97 |
| POP_GRP | MUNICIPALITY POPULATION GROUP | ROADLOG | CHA(1) | 97 |
| POP_GRP | POPULATION GROUP | ACCIDENT | NUM | 45 |
| PRKLN_WD | PARKING LANE WIDTH | ROADLOG | NUM | 97 |
| PTCONT1 | POINT OF CONTACT #1 | VEHICLE | CHA(2) | 64 |
| RATE_DTE | MONTH-YR OF CONDITION RATING | ROADLOG | NUM | 97 |
| RD_DEF | ROAD DEFECTS | ACCIDENT | NUM | 45 |
| RD_DIST | TOWNSHIP/ROAD DISTRICT | ROADLOG | NUM | 97 |
| RD_STRUC | STRUCTURE NUMBER | ROADLOG | CHA(7) | 98 |
| RD_YEAR | YEAR ROAD CONSTRUCTED | ROADLOG | NUM | 98 |
| RDSURF | ROAD SURFACE | ACCIDENT | NUM | 45 |
| REEL_NBR | REEL NUMBER | ACCIDENT | NUM | 46 |
| REF_PNT | REFERENCE POINT | ROADLOG | CHA(15) | 98 |
| REF_PNT1 | REFERENCE POINT 1 | ROADLOG | CHA(20) | 98 |
| REF_PNT2 | REFERENCE POINT 2 | ROADLOG | CHA(20) | 98 |
| REF_PNT3 | REFERENCE POINT 3 | ROADLOG | CHA(20) | 98 |
| REF_PNTA | REFERENCE POINT A | ROADLOG | CHA(15) | 98 |
| REFPNT1A | REFERENCE POINT 1 TYPE | ROADLOG | CHA(2) | 98 |
| REFPNT2A | REFERENCE POINT 2 TYPE | ROADLOG | CHA(2) | 98 |
| REFPNT3A | REFERENCE POINT 3 TYPE | ROADLOG | CHA(2) | 98 |
| REFPT1IN | REFERENCE POINT 1 INTERSECTION | ROADLOG | CHA(1) | 99 |
| REFPT2IN | REFERENCE POINT 2 INTERSECTION | ROADLOG | CHA(1) | 99 |
| REFPT3IN | REFERENCE POINT 3 INTERSECTION | ROADLOG | CHA(1) | 99 |
| REPORT | REPORTABLE ACCIDENT | VEHICLE | CHA(1) | 64 |
| RESEV_RD | RESERVATION ROAD | ROADLOG | CHA(1) | 99 |
| RESIDLOC | RESIDENCE OF DRIVER | VEHICLE | NUM | 64 |
| REST1 | SAFETY EQUIPMENT | INJ. OCCUPANTS | NUM | 73 |
| REV_CDE | FORWARD/REVERSE CODE | ROADLOG | CHA(1) | 99 |
| RODWYCLS | ROADWAY CLASSIFICATION | ACCIDENT | CHA(2) | 46 |
| RODWYCLS | ROADWAY CLASSIFICATION | ROADLOG | CHA(2) | 99 |
| ROW | RIGHT OF WAY | ROADLOG | NUM | 99 |
| RPK_REST | PARKING RESTRICTION | ROADLOG | CHA(1) | 100 |
| RR_CRX | RAILROAD CROSS RIDEABILITY | ROADLOG | NUM | 100 |
| RRD_LNK | RAILROAD LINK NUMBER | ROADLOG | CHA(7) | 100 |
| RRX_ALP | RR CROSSING ALPA NBR | ACCIDENT | CHA(1) | 46 |
| RRX_DIRCD | RAILROAD DIRECTION CODE | ROADLOG | CHA(1) | 100 |
| RRX_NBR | RAILROAD CROSSING NUMBER | ACCIDENT | NUM | 46 |
| RRX_RIDE | RAILROAD CROSSING RIDEABILITY | ROADLOG | CHA(1) | 100 |
| RTE_APPURT | ROUTE APPURTENANCE | ROADLOG | NUM | 101 |
| RTE_NBR | ROUTE NUMBER | ACCIDENT | NUM | 46 |
| RTE_NBR | ROUTE NUMBER | ROADLOG | NUM | 101 |
| RTE_PREF | ROUTE PREFIX | ACCIDENT | NUM | 46 |
| RTE_SEGCD | ROUTE SEQUENCE NUMBER | ROADLOG | CHA(2) | 101 |
| RTE_STAT | ROUTE STATION | ROADLOG | NUM | 101 |
| RTE_STAT_END | ROUTE STATION END | ROADLOG | NUM | 101 |
| RTE_SUFX | ROUTE SUFFIX | ROADLOG | CHA(1) | 101 |
| RTE_TYPE | ROUTE TYPE | ACCIDENT | NUM | 47 |
| RTE_TYPE | ROUTE TYPE | ROADLOG | NUM | 101 |
| RURURB | RURAL / URBAN CODE | ROADLOG | NUM | 102 |
| RUT_DEPTIN | RUT DEPTH INDICATOR | ROADLOG | CHA(3) | 102 |
| S_INVLOC | SECOND INVOLVEMENT LOCATION | VEHICLE | NUM | 65 |
| S_RTENBR | SAF-MRK-ROUTE NUMBER | ROADLOG | NUM | 102 |
| S_RTETYP | SAF-MRK-ROUTE TYP | ROADLOG | NUM | 102 |
| SAF_CNTL | SAF-ACCESS-CNTL | ROADLOG | NUM | 102 |
| SAF_FASY | SAF-FASYS | ROADLOG | NUM | 103 |
| SAF_TWN | SAF-TWNSHP | ROADLOG | NUM | 103 |
| SEATPOS | SEATING POSITION | INJ. OCCUPANTS | NUM | 74 |
| SEG_LNG | SEGMENT LENGTH | DEFICIENT CURVE | NUM | 113 |
| SEG_LNG | SEGMENT LENGTH | ROADLOG | NUM | 103 |
| SEV_CDE | SEVERITY CODE | ACCIDENT | NUM | 47 |
| SEVERITY | COLLISION SEVERITY | ACCIDENT | NUM | 47 |
| SEX | OCCUPANT SEX | INJ. OCCUPANTS | NUM | 74 |
| SHLD_CON | SHOULDER CONDITION | ROADLOG | NUM | 103 |
| SND_INV | SECOND INVOLVEMENT | VEHICLE | NUM | 65 |
| SOB_TEST | FIRST SOBRIETY/CONDITION | VEHICLE | NUM | 65 |
| SPD_LIM2 | POSTED SPEED LIMIT (MINUS DIRECTION) | ROADLOG | NUM | 103 |
| SPD_LIMT | ROADWAY SPEED LIMIT | ROADLOG | NUM | 103 |
| SPEC_SYSM | SPECIAL SYSTEMS | ROADLOG | CHA(1) | 104 |
| SPEC_VEH | SPECIAL VEHICLE | VEHICLE | NUM | 65 |
| SPLN_TYP | LANES SPECIAL TYPE | ROADLOG | CHA(1) | 104 |
| SPLN_WID | LANES SPECIAL WIDTH | ROADLOG | NUM | 104 |
| STAT_DIR | PLAN STATION DIRECTION | ROADLOG | CHA(1) | 104 |
| STOU_IND | STRUCTURE OVER/UNDER IND | ROADLOG | CHA(1) | 105 |
| STR_ENDM | STRUCTURE END MILEPOST | ROADLOG | CHA(5) | 105 |
| STR_LNG | STRUCTURE LENGTH | ROADLOG | NUM | 105 |
| STRDIRCD | STRUCTURE DIRECTION CODE | ROADLOG | CHAR(1) | 105 |
| STRK_CDE | STRIKE STRUCK CODE | VEHICLE | CHA(1) | 66 |
| STRT_NAM | STREET-NAME | ROADLOG | CHA(15) | 105 |
| STRU_FAC | STRUCTURE FACILITY LOCATION | ROADLOG | CHA(20) | 105 |
| STRU_LNK | STRUCTURE LINK NUMBER | ROADLOG | NUM | 105 |
| SUF_CDE | SUFFIX CODE | ROADLOG | CHA(1) | 105 |
| SURF_RAT | SURFACE CONDITION RATING | ROADLOG | NUM | 106 |
| SURF_TYP | SURFACE TYPE – ROAD 1 | ROADLOG | NUM | 106 |
| SURF_WID | TOTAL SURFACE WIDTH | ROADLOG | NUM | 106 |
| SURF_YR | YEAR OF PRESENT SUF CONST | ROADLOG | CHA(2) | 107 |
| SURFDATE | YEAR OF PRESENT SUF CONST | ROADLOG | CHA(4) | 107 |
| T_INVLOC | THIRD INVOLVEMENT LOCATION | VEHICLE | NUM | 66 |
| TC_COND | TRAFFIC CONTROL CONDITION | ACCIDENT | NUM | 48 |
| THRD_INV | THIRD INVOLVEMENT | VEHICLE | NUM | 66 |
| TOT_INJ | OCCUPANTS INJURED | ACCIDENT | NUM | 48 |
| TOT_KILL | OCCUPANTS KILLED | ACCIDENT | NUM | 48 |
| TOT_NON | TOTAL NUMBER OF UNINJURED | ACCIDENT | NUM | 48 |
| TOTAINJ | NUM A INJ IN ACC | ACCIDENT | NUM | 48 |
| TOTBINJ | NUM B INJ IN ACC | ACCIDENT | NUM | 48 |
| TOTCINJ | NUM C INJ IN ACC | ACCIDENT | NUM | 48 |
| TOTINSHL | TOTAL IN SHOULDER | ROADLOG | NUM | 107 |
| TOTOTSHL | TOTAL OUT SHOULDER | ROADLOG | NUM | 107 |
| TOWAWAY | VEHICLE TOWED | VEHICLE | NUM | 66 |
| TOWNSHIP | TOWNSHIP | ACCIDENT | NUM | 49 |
| TRF_CNTL | TRAFFIC CONTROL | ROADLOG | CHA(1) | 107 |
| TRFCNTL | TYPE OF TRAFFIC CONTROL | ACCIDENT | NUM | 49 |
| TRK_RTE | DESIGNATED TRUCK ROUTE | ROADLOG | CHA(1) | 107 |
| URB_AREA | URBAN AREA | ROADLOG | NUM | 108 |
| VEH_MNAU | VEHICLE MANEUVER CODE | VEHICLE | CHA(2) | 67 |
| VEH_OCC | VEHICLE OCCUPANTS | VEHICLE | CHA(2) | 67 |
| VEHCOND1 | VEHICLE DEFECT | VEHICLE | CHA(2) | 67 |
| VEHNO | VEHICLE NUMBER | INJ. OCCUPANTS | NUM | 74 |
| VEHNO | VEHICLE NUMBER | VEHICLE | NUM | 68 |
| VEHTYPE | TYPE OF VEHICLE | VEHICLE | NUM | 68 |
| VEHYR | VEHICLE MODEL YEAR | VEHICLE | NUM | 69 |
| VER_BEGMP | VERTICAL GRADE BEGINNING MILEPOST | ROADLOG | CHA(5) | 108 |
| VER_ENDMP | VERTICAL END MILEPOST | ROADLOG | CHA(5) | 108 |
| VERT_APP | VERTICAL CURVE APPROACH GRADE | ROADLOG | NUM | 108 |
| VERT_BEG | VERTICAL CURVE BEGINNING MILEPOST | ROADLOG | NUM | 108 |
| VERT_END | VERTICAL CURVE END MILEPOST | ROADLOG | NUM | 109 |
| VERT_LEV | VERTICAL CURVE LEAVE GRADE | ROADLOG | NUM | 109 |
| VERT_LGN | VERTICAL CURVE LENGTH | ROADLOG | NUM | 109 |
| VERTAPPS | VERTICAL APPROACH SIGN | ROADLOG | CHA(1) | 110 |
| VERTLEVS | VERTICAL LEAVE SIGN | ROADLOG | CHA(1) | 110 |
| VIN | VIN CODE | VEHICLE | CHA(17) | 69 |
| VISION | VEHICLE VISUAL OBSTRUCTION | VEHICLE | CHA(2) | 69 |
| VOL_YR | YEAR OF HEAVY COMMERCIAL VOL | ROADLOG | NUM | 110 |
| WEATHER | WEATHER | ACCIDENT | NUM | 49 |
| WEEKDAY | DAY OF WEEK | ACCIDENT | NUM | 49 |
| WRK_ZONE_REL | WORKZONE RELATED | ACCIDENT | CHA(1) | 50 |
| XAADT | CROSSROAD AADT | ROADLOG | NUM | 110 |
| XCOMADT | CROSSROAD COMMERCIAL ADT | ROADLOG | NUM | 110 |
| XFUNC_CL | CROSS FUNCTIONAL CLASS | ROADLOG | NUM | 110 |
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| ACC_DATE | DATE OF ACCIDENT | ACCIDENT | NUM | 36 |
| ACCTYPE_POST_93 | TYPE OF COLLISION | ACCIDENT | NUM | 35 |
| ACCTYPE_PRE_93 | TYPE OF COLLISION | ACCIDENT | NUM | 35 |
| ACCYR | ACCIDENT YEAR | ACCIDENT | NUM | 36 |
| AGENCY | INVESTIGATING AGENCY | ACCIDENT | NUM | 36 |
| ALIGN_CODE | ALIGNMENT | ACCIDENT | NUM | 37 |
| BADGE | BADGE CODE | ACCIDENT | NUM | 37 |
| BEAT_CDE | BEAT CODE | ACCIDENT | NUM | 37 |
| CASENO | ACCIDENT CASE NUMBER | ACCIDENT | CHA(11) | 37 |
| CAUSE1 | CONTRIB FACTOR 1 | ACCIDENT | CHA(2) | 37 |
| CAUSE2 | CONTRIB FACTOR 2 | ACCIDENT | CHA(2) | 37 |
| CITY | CITY OR TOWNSHIP | ACCIDENT | NUM | 38 |
| CITY_TWNSHIP_FLG | CITY/TOWNSHIP FLAG | ACCIDENT | CHA(1) | 38 |
| CLS_TFWY | CLASS OF TRAFFICWAY | ACCIDENT | NUM | 38 |
| CNTYRTE | COMPUTED LINKAGE KEY | ACCIDENT | CHA(7) | 39 |
| COUNTY | COUNTY | ACCIDENT | NUM | 39 |
| CRSH_LAT | CRASH LATITUDE | ACCIDENT | CHA(3) | 39 |
| CRSH_LONG | CRASH LONGITUDE | ACCIDENT | CHA(3) | 39 |
| CRSH_X_CORD | CRASH X COORDINATE | ACCIDENT | CHA(8) | 39 |
| CRSH_Y_CORD | CRASH Y COORDINATE | ACCIDENT | CHA(8) | 39 |
| CTY_CLS | CITY CLASS CODE | ACCIDENT | NUM | 39 |
| DAM_OTHR | PROPERTY DAMAGE OTHER THAN VEH |
ACCIDENT | NUM | 40 |
| DIST | DISTRICT | ACCIDENT | NUM | 40 |
| DIVIDED | TRAFFICWAY DESCRIPTION | ACCIDENT | NUM | 40 |
| FED_CLAS | FEDERAL CLASSIFICATION | ACCIDENT | NUM | 40 |
| FLD_NAM1 | FIELD REF NAME 1 | ACCIDENT | CHA(3) | 41 |
| FLD_NAM2 | FIELD REF NAME 2 | ACCIDENT | CHA(3) | 41 |
| FLD_NBR1 | FIELD REF NBR 1 | ACCIDENT | NUM | 41 |
| FLD_NBR2 | FIELD REF NBR 2 | ACCIDENT | NUM | 41 |
| FLD_TYPE | FIELD REF TYPE | ACCIDENT | NUM | 41 |
| FUNC_CLS | FUNCTIONAL CLASS | ACCIDENT | CHA(1) | 41 |
| HIT_RUN | HIT AND RUN | ACCIDENT | CHA(1) | 42 |
| HOUR | TIME OF ACCIDENT | ACCIDENT | NUM | 42 |
| IMAG_NBR | IMAGE NUMBER | ACCIDENT | NUM | 42 |
| INT_NAME | INTESECTING RTE NBR | ACCIDENT | NUM | 42 |
| INT_PREF | INTERSECT RTE PREFIX | ACCIDENT | NUM | 42 |
| INT_QUAD | INTERSECTION QUADRANT | ACCIDENT | NUM | 43 |
| INT_REL | INTERSECTION RELATED | ACCIDENT | CHA(1) | 43 |
| LIGHT | LIGHT CONDITION | ACCIDENT | NUM | 43 |
| LOC_TYPE | LOCATION TYPE | ACCIDENT | NUM | 43 |
| MILEPOST | MILE STATION | ACCIDENT | NUM | 44 |
| MVMT | MILLION VEHICLE MILES OF TRAVEL |
ACCIDENT | NUM | 44 |
| NAT_HWY | NATIONAL HIGHWAY SYSTEM | ACCIDENT | CHA(1) | 44 |
| NUMVEHS | TOT-NBR-VEHICLES | ACCIDENT | NUM | 44 |
| OLD_DATE | DATE | ACCIDENT | NUM | 44 |
| OP_ID | OPERATOR ID | ACCIDENT | NUM | 45 |
| POP_GRP | POPULATION GROUP | ACCIDENT | NUM | 45 |
| RD_DEF | ROAD DEFECTS | ACCIDENT | NUM | 45 |
| RDSURF | ROAD SURFACE | ACCIDENT | NUM | 45 |
| REEL_NBR | REEL NUMBER | ACCIDENT | NUM | 46 |
| RODWYCLS | ROADWAY CLASSIFICATION | ACCIDENT | CHA(2) | 46 |
| RRX_ALP | RR CROSSING ALPA NBR | ACCIDENT | CHA(1) | 46 |
| RRX_NBR | RAILROAD CROSSING NUMBER | ACCIDENT | NUM | 46 |
| RTE_NBR | ROUTE NUMBER | ACCIDENT | NUM | 46 |
| RTE_PREF | ROUTE PREFIX | ACCIDENT | NUM | 46 |
| RTE_TYPE | ROUTE TYPE | ACCIDENT | NUM | 47 |
| SEV_CDE | SEVERITY CODE | ACCIDENT | NUM | 47 |
| SEVERITY | COLLISION SEVERITY | ACCIDENT | NUM | 47 |
| TC_COND | TRAFFIC CONTROL CONDITION | ACCIDENT | NUM | 48 |
| TOT_INJ | OCCUPANTS INJURED | ACCIDENT | NUM | 48 |
| TOT_KILL | OCCUPANTS KILLED | ACCIDENT | NUM | 48 |
| TOT_NON | TOTAL NUMBER OF UNINJURED | ACCIDENT | NUM | 48 |
| TOTAINJ | NUM A INJ IN ACC | ACCIDENT | NUM | 48 |
| TOTBINJ | NUM B INJ IN ACC | ACCIDENT | NUM | 48 |
| TOTCINJ | NUM C INJ IN ACC | ACCIDENT | NUM | 48 |
| TOWNSHIP | TOWNSHIP | ACCIDENT | NUM | 49 |
| TRFCNTL | TYPE OF TRAFFIC CONTROL | ACCIDENT | NUM | 49 |
| WEATHER | WEATHER | ACCIDENT | NUM | 49 |
| WEEKDAY | DAY OF WEEK | ACCIDENT | NUM | 49 |
| WRK_ZONE_REL | WORKZONE RELATED | ACCIDENT | CHA(1) | 50 |
NOTE: SAS variable names and longer explanatory names are shown above each listing. (See Discussion for in formation on SAS formats.)
TYPE OF COLLISION
NOTE: Variable added in 1993. For data belonging to previous years, see ACCTYPE_PRE_93.
TYPE OF COLLISION
NOTE: (1) Preliminary analysis has indicated that the "head-on" and sideswipe - opposite direction" codes refer to vehicle direction immediately prior to impact rather than initial direction. (2) Changes in the 1993 accident report form have resulted in minor shifts from code to code when compared to earlier files. (3) * Indicates the new formats that are followed from 1994 onwards. Only these codes are used to describe an accident from 1994 onwards as against the codes that were used previously. (4) ** Rear end moving and rear end stopped categories combined into one category Rear end crashes. (5) Variable discontinued in 1993. For data belonging to later years, see ACCTYPE_POST_93.
ACCIDENT YEAR
NON-LABELED VARIABLE
NOTE: The last 2 digits of year of accident.
DATE ACCIDENT OCCURRED
NON-LABELED VARIABLE
NOTE: MM/DD/YY for 1994 and 1995 and YY/MM/DD for others.
INVESTIGATING AGENCY
NOTE: Categories 5-8 represent “desk reports”, which have been removed from 1987 onwards.
ALIGNMENT
NOTE: Variable added in 2006.
BADGE CODE
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1997.
BEAT CODE
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1997.
ACCIDENT CASE NUMBER
NON-LABELED VARIABLE -- CASE NUMBER
CONTRIBUTORY CAUSE 1
CONTRIBUTORY CAUSE 2
NOTE: Because this variable is only filled out by the State Police, over 80% of the cases are coded "unknown".
CITY OR TOWNSHIP
NOTE: A number indicating the city. For a detailed list of cities and their corresponding numbers, contact HSIS staff.
CITY/TOWNSHIP FLAG
NOTE: Variable added in 2006.
CLASS OF TRAFFICWAY
NOTE: Data related to “toll roads” (“4” and “9”) couldn’t be linked to roadway variables. It has been deleted for all years of data.
COMPUTED LINKAGE KEY
NON-LABELED VARIABLE -- Computed variable used in linkage with Road log File. See Discussion.
COUNTY OF ACCIDENTS
'001-102' = COUNTY NUMBER
NOTE: See Roadlog file for county formats.
CRASH LATITUDE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
CRASH LONGITUDE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
CRASH X COORDINATE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
CRASH Y COORDINATE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
CITY CLASS CODE
NOTE: Variable added in 2004.
PROPERTY DAMAGE OTHER THAN VEH
DISTRICT NUMBER
NOTE: Variable discontinued in 1994.
TRAFFICWAY DESCRIPTION
NOTE: Variable added in 2006.
FEDERAL CLASSIFICATION
NOTE: The above formats are applicable until 1993. For later years, this variable is generated based on NAT_HWY and FUNC_CLS. If the road is federal aided (obtained from NAT_HWY) and is categorized as FUNC_CLS = 1 then this variable is coded as 11. If the road is non-federal aided and the road is categorized as FUNC_CLS = 1 then this variable is coded as 01. This is applicable to all values of FUNC_CLS.
FIELD REF NAME 1
FIELD REF NAME 2
NON-LABELED VARIABLES
NOTE: Variables discontinued in 1997.
FIELD REF NUMBER 1
FIELD REF NUMBER 2
NON-LABELED VARIABLES
NOTE: Variables discontinued in 1997.
FIELD REF TYPE
NON-LABELED VARIABLE
NOTE: Variables discontinued in 1997.
FUNCTIONAL CLASS
NOTE: This variable is attached from roadway segments.
HIT AND RUN
NOTE: Variable added in 1994.
TIME OF ACCIDENT
IMAGE NUMBER
NON-LABELED VARIABLE -- Internal use only
NOTE: (1) This variable was added in 1990 to aid Illinois DOT in the location of accident report forms. (2) Variable discontinued in 1995.
INTESECTING RTE NBR
NON-LABELED VARIABLE
NOTE: Variable discontinued in 2004.
INTERSECT RTE PREFIX
NON-LABELED VARIABLE
INTERSECTION QUADRANT
NOTE: (1) For years 1994 onwards, no formats available. All observations coded as 0. For prior years, most observations coded as 0. This variable should be used with caution. (2) Variable discontinued in 2004.
INTERSECTION RELATED
NOTE: Variable added in 1994.
LIGHT CONDITION
LOCATION TYPE
NOTE: There appears to be overlapping of categories when earlier years are compared to later years. Also categories 16 and 17 are not available for later years (1996 onwards). The distribution of observations is agreeable for later years. Exercise caution when using this variable for early as well later years.
MILE STATION
NON-LABELED VARIABLE
MILLION VEHICLE MILES OF TRAVEL
NON-LABELED VARIABLE
NOTE: Variable added in 2003.
NATIONAL HIGHWAY SYSTEM
NOTE: Variable added in 1994.
TOT-NBR-VEHICLES
DATE MM/DD/YY
NOTE: Variable added in 1994 and discontinued in 1996.
OPERATOR ID
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1995.
POPULATION GROUP
NOTE: (1) Do not use this variable to define "urban/rural". Instead use either the variable related to "federal functional" class"(FED_CLAS) or "traffic way class" (CLS_TFWY) as indicator of urban or rural location. (2) Variable discontinued in 2004.
ROAD DEFECTS
NOTE: Categories 11-15 apply to data before 2004.
ROAD SURFACE
NOTE: Categories 10-12 apply to data before 2004.
REEL NUMBER
NON-LABELED VARIABLE -- Internal use only
NOTE: (1) This variable was added in 1990 to aid Illinois DOT in the location of accident report forms. (2) Variable discontinued in 1995.
ROADWAY CLASSIFICATION
RR CROSSING ALPA NBR
NON-LABELED VARIABLE
NOTE: 99 per cent of observations coded as missing.
RAILROAD CROSSING NUMBER
NON-LABELED VARIABLE
NOTE: 99 per cent of observations coded as missing.
ROUTE NUMBER
NON-LABELED VARIABLE
ROUTE PREFIX - ACCIDENT VAR
NOTE: Variable added in 1994.
ROUTE TYPE
NOTE: Variable discontinued in 1994.
ACCIDENT SEVERITY
COLLISION SEVERITY
NOTE: This variable is not found in the Raw File. It was developed to produce more detail than the "severity code" (SEV_CDE) that has only three categories -- none, injury, fatal. The accident severity is based on the most severe occupant injury in the accident.
TRAFFIC CONTROL CONDITION
NOTE: Variable added in 1994.
OCCUPANTS INJURED
OCCUPANTS KILLED
TOTAL NUMBER OF UNINJURED PERSONS
NUM A INJ IN ACC
NUM B INJ IN ACC
NUM C INJ IN ACC
TOWNSHIP
NON-LABELED VARIABLE
TYPE OF TRAFFIC CONTROL
NOTE: Categories 15-16 apply to data before 2004.
WEATHER
NOTE: Category 8 applies to data before 2004.
DAY OF OCCURRENCE
NOTE: Variable discontinued in 2001.
WORKZONE RELATED
NOTE: Variable added in 2006.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| ACTION | ARREST | VEHICLE | CHA(7) | 53 |
| AIRBAG | AIRBAG DRIVER | VEHICLE | CHA(1) | 53 |
| AT_FAULT | AT FAULT | VEHICLE | CHA(2) | 53 |
| CASENO | CASE NUMBER | VEHICLE | CHA(11) | 53 |
| COL_TYPE | COLLISION TYPE | VEHICLE | CHA(2) | 53 |
| COMM_VEH | COMMERCIAL VEHICLE | VEHICLE | CHA(1) | 53 |
| DIR_TRVL | DIRECTION OF TRAVEL | VEHICLE | NUM | 53 |
| DRV_ACTN | DRIVER ACTION | VEHICLE | CHA(2) | 54 |
| DRV_AGE | DRIVER AGE | VEHICLE | NUM | 54 |
| DRV_BAC | DRIVER ALCOHOL PERCENT | VEHICLE | NUM | 54 |
| DRV_BAC2 | 2ND SOBRIETY TEST RESULTS | VEHICLE | CHA(2) | 55 |
| DRV_CLAS | DRIVER CLASS | VEHICLE | CHA(4) | 55 |
| DRV_COND | DRIVER CONDITION NEW | VEHICLE | CHA(1) | 55 |
| DRV_DOB | DRIVER BIRTH DATE | VEHICLE | CHA(8) | 55 |
| DRV_EJCT | DRIVER EJECTION | VEHICLE | CHA(1) | 56 |
| DRV_IMAG | IMAGE NUMBER | VEHICLE | NUM | 56 |
| DRV_INJ | DRIVER EXTENT OF INJURY | VEHICLE | NUM | 56 |
| DRV_LST | DRIVER LICENSE STATE | VEHICLE | CHA(2) | 56 |
| DRV_REEL | REEL NUMBER | VEHICLE | CHA(4) | 56 |
| DRV_REST | DRIVER RESTRAINT USAGE | VEHICLE | NUM | 56 |
| DRV_RPT | DRIVER REPORT | VEHICLE | NUM | 57 |
| DRV_SEX | DRIVER SEX | VEHICLE | NUM | 57 |
| F_INVLOC | FIRST INVOLVEMENT LOCATION | VEHICLE | NUM | 57 |
| FIRE | VEH FUEL LEAKS AND FIRE | VEHICLE | NUM | 58 |
| FRST_INV | FIRST INVOLVEMENT | VEHICLE | NUM | 58 |
| HZM_IND | HAZARDOUS MATERIAL | VEHICLE | CHA(1) | 59 |
| INTOX | ALCOHOL INVOLVED | VEHICLE | CHA(1) | 59 |
| MISCACT1 | DRV MISC ACTN 1 CD | VEHICLE | NUM | 59 |
| MOSTHARM | VEHICLE MOST HARMFUL INVOLVEMENT |
VEHICLE | CHA(1) | 61 |
| NUM_K | TOTAL KILLED IN VEHICLE | VEHICLE | NUM | 61 |
| NUM_OCC | NO. OF OCCUPANTS IN VEHICLE | VEHICLE | NUM | 61 |
| NUMINJ | TOTAL NUMBER INJURD IN VEHICLE |
VEHICLE | NUM | 61 |
| PED_AGE | AGE OF THE PED/PEDALCYCLIST | VEHICLE | CHA(2) | 61 |
| PED_CLT | PED TYPE OF CLOTHING | VEHICLE | CHA(1) | 62 |
| PED_FLAG | PEDESTRIAN FLAG | VEHICLE | CHA(1) | 62 |
| PED_LOC | PED/PEDAL LOCATION | VEHICLE | CHA(1) | 62 |
| PED_OTH | PEDESTRIAN/OTHER | VEHICLE | NUM | 62 |
| PED_VIS | DRIVER VISION | VEHICLE | CHA(1) | 62 |
| PEDACT | PED/PEDALCYLIST ACTION/MOVEMENT |
VEHICLE | NUM | 63 |
| PERSON_TYP | PERSON TYPE | VEHICLE | NUM | 63 |
| PHYSCOND | DRIVER PHYSICAL CONDITION | VEHICLE | NUM | 63 |
| PTCONT1 | POINT OF CONTACT #1 | VEHICLE | CHA(2) | 64 |
| REPORT | REPORTABLE ACCIDENT | VEHICLE | CHA(1) | 64 |
| RESIDLOC | RESIDENCE OF DRIVER | VEHICLE | NUM | 64 |
| S_INVLOC | SECOND INVOLVEMENT LOCATION | VEHICLE | NUM | 65 |
| SND_INV | SECOND INVOLVEMENT | VEHICLE | NUM | 65 |
| SOB_TEST | FIRST SOBRIETY/CONDITION | VEHICLE | NUM | 65 |
| SPEC_VEH | SPECIAL VEHICLE | VEHICLE | NUM | 65 |
| STRK_CDE | STRIKE STRUCK CODE | VEHICLE | CHA(1) | 66 |
| T_INVLOC | THIRD INVOLVEMENT LOCATION | VEHICLE | NUM | 66 |
| THRD_INV | THIRD INVOLVEMENT | VEHICLE | NUM | 66 |
| TOWAWAY | VEHICLE TOWED | VEHICLE | NUM | 66 |
| VEH_MNAU | VEHICLE MANEUVER CODE | VEHICLE | CHA(2) | 67 |
| VEH_OCC | VEHICLE OCCUPANTS | VEHICLE | CHA(2) | 67 |
| VEHCOND1 | VEHICLE DEFECT | VEHICLE | CHA(2) | 67 |
| VEHNO | VEHICLE NUMBER | VEHICLE | NUM | 68 |
| VEHTYPE | TYPE OF VEHICLE | VEHICLE | NUM | 68 |
| VEHYR | VEHICLE MODEL YEAR | VEHICLE | NUM | 69 |
| VIN | VIN CODE | VEHICLE | CHA(17) | 69 |
| VISION | VEHICLE VISUAL OBSTRUCTION | VEHICLE | CHA(2) | 69 |
ARREST
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1997.
DRIVER AIRBAG DEPLOYED
NOTE: (1) See DRV_REST. (2) Variable added in 1996.
AT FAULT
NON-LABELED VARIABLE
NOTE: Variable added in 1994.
ACCIDENT CASE NUMBER
NON-LABELED VARIABLE -- CASE NUMBER
COLLISION TYPE
NON-LABELED VARIABLE
NOTE: Variable added in 1994.
COMMERCIAL VEHICLE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
DIRECTION OF TRAVEL
NOTE: This appears to refer to direction immediately prior to impact rather than initial direction.
DRIVER ACTION
NOTE: Variable added in 1994.
DRIVER AGE
DRIVER ALCOHOL PERCENT
NOTE: (1) Test results are provided for only approximately 67% of Drivers noted as having been tested under DRIVER SOBRIETY TEST. This variable was combined with SOB_TEST on July 1, 1993. See DRV_BAC2. (2) Variable discontinued in 1993
2ND TEST RESULTS
NOTE: (1) Test results are provided for only approximately 67% of Drivers noted as having been tested under DRIVER SOBRIETY TEST. This variable was new as of July 1, 1993, combining information from DRV_BAC and SOB_TEST. (2)Variable added in 1993.
DRIVER CLASS
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
DRIVER CONDITION NEW
NOTE: Variable added in 1996.
DRIVER BIRTHDATE
NON-LABELED VARIABLE
NOTE: This variable contains a date with the following format MMDDYYYY.
DRIVER EJECTION
NOTE: Variable added in 1994.
IMAGE NUMBER
NON-LABELED VARIABLE -- Internal use only
NOTE: (1) This variable was added in 1990 to aid Illinois DOT in the location of accident report forms. (2) Variable discontinued in 1995.
DRIVER EXTENT OF INJURY
DRIVER LICENSE STATE
NON-LABELED VARIABLE
NOTE: Variable added in 1996.
REEL NUMBER
NON-LABELED VARIABLE -- Internal use only
NOTE: (1) This variable was added in 1990 to aid Illinois DOT in the location of accident report forms. (2) Variable discontinued in 1995.
DRIVER RESTRAINT USAGE
NOTE: (1) See “AIRBAG” for airbag data for 1996 and later years (2) This variable has a very high number of “not stated” codes and is characterized in general by poor data for years 1985 – 1991. (3) Categories 10-12 and 99 apply to data before 2004.
DRIVER REPORT
NOTE: Variable discontinued in 1997.
DRIVER SEX
INVOLVEMENT LOCATION
NOTE: Categories 7, 8, 10-14 and 17-19 apply to data before 2004.
VEH FUEL LEAKS AND FIRES
NOTE: Over 9 percent coded as "not stated".
FIRST INVOLVEMENT
NOTE: Categories 51-70 apply to data before 2004.
HAZARDOUS MATERIAL
NOTE: Variable added in 1994.
ALCOHOL INVOLVED
NOTE: (1) Data is very limited and very inaccurate. Illinois recommends that these data not be used in analyses. (2) Variable discontinued in 1995.
DRV MISC ACTN 1 CD
VEHICLE MOST HARMFUL INVOLVEMENT
NOTE: Variable added in 2006.
TOTAL KILLED IN VEHICLE
NUMBER OF OCCUPANTS IN VEH
NOTE: Variable added in 1994.
TOTAL NUMBER INJURED IN VEHICLE
PEDESTRIAN AGE
NOTE: Variable added in 1995.
PEDESTRIAN TYPE OF CLOTHING
NOTE: Variable added in 1994 and discontinued in 2004.
PEDESTRIAN FLAG
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
PED/PEDAL LOCATION
NOTE: Variable added in 2006.
PEDESTRIAN/OTHER
NOTE: (1) This variable is used to define units other than motor vehicles. It is left blank if the unit in question is a motor vehicle. (2) Variable discontinued in 2004.
DRIVER VISION
NOTE: Variable added in 2006.
PED/PEDALCYCLIST ACTION/MOVEMENT
NOTE: These codes are present only for units, which are not motor vehicles, i.e., when PED_OTH is coded as 1, 2, 3, or 4.
PERSON TYPE
NOTE: Variable added in 2006.
CONDITION OF DRIVER
NOTE: (1) “Not stated” appears to be absent from 1994 onwards data. In addition, the percentage of “had been drinking” appears to be lower than expected. (2) Variable discontinued in 2004.
POINT OF CONTACT #1
NOTE: Variable added in 1994.
REPORTABLE ACCIDENT
NOTE: Variable added in 1988.
RESIDENCE OF DRIVER
NOTE: Variable discontinued in 2004.
SECOND INVOLVEMENT LOCATION
Coding -- See F_INVLOC. Notes for F_INVLOC apply here too.
SECOND INVOLVEMENT
CODING -- SEE FRST_INV. Notes for FRST_INV apply here too.
FIRST SOBRIETY/CONDITION
NOTE: (1) This variable was combined with DRV_BAC on July 1, 1993. See DRV_BAC2. (2) Variable discontinued in 1995.
SPECIAL VEHICLE
NOTE: (1) Data related to vehicles carrying "hazardous materials"(i.e., codes 05 and 06) contain coding errors, particularly the 1985 data. All "hazard materials" data in all three years must be used with caution. In addition, codes were added and definitions changed slightly in 1988. Thus, certain truck-related categories are inconsistent across years. Care must be taken in analyses. (2) Categories 31-51 apply to data before 2004.
STRIKE STRUCK CODE
NOTE: Over 11 percent coded as "unknown" in early years. Unknown increased to 34% in the 1993 file and 68% in 1994 file. More recent years show values of unknown are close to 15%. Additional "garbage" codes are present.
3RD INVOLVMENT LOCATION
CODING – See F_INVLOC. Notes for F_INVLOC apply here as well.
THIRD INVOLVEMENT
CODING -- SEE FRST_INV. Notes for FRST_INV apply here as well.
VEHICLE TOWED
NOTE: (1) 1993 data are erroneous due to coding changes. Illinois staff indicates that the problem is in the last six months of 1993. (2) Variable added in 1988.
VEH MANEUVER CODE
NOTE: (1) Variable added in 1996. MISCACT1 provides similar information for years prior to 1996. This variable provides information on the vehicle maneuvers of the “vehicles” involved. For information on pedestrian maneuvers refer to variable MISCACT, which has limited information for 2000 and later years. (2) Categories 26 and 99 apply to data from 2004 onwards.
VEHICLE OCCUPANTS
NON-LABELED VARIABLE
NOTE: Variable added in 1994.
VEHICLE DEFECT
NOTE: Variable added in 1994.
REFERENCE NUMBER
NON-LABELED VARIABLE
NOTE: This is the number of vehicle on the accident report form. This variable is used to link to occupant file.
TYPE OF VEHICLE
NOTE: (1) Code "98" above is not found in the Illinois raw file but has been included in this variable to indicate those records which represent pedestrians, equestrians or pedal cyclists. In addition, use of codes "01" and "02" changed during 1989. The two codes must be collapsed in analyses involving 1989 data. (2) Categories 21-23 and 97 apply to data before 2004.
VEHICLE MODEL YEAR
VINA CODE
NON-LABELED VARIABLE -- No Raw File Documentation
VEHICLE VISUAL OBSTRUCTION
NOTE: (1) Category 13 applies to data from 2004 onwards. (2) Variable added in 1994.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AGE | OCCUPANT AGE | INJ. OCCUPANTS | NUM | 72 |
| CASENO | ACCIDENT CASE NUMBER | INJ. OCCUPANTS | CHA(11) | 72 |
| EJCT | OCCUPANT EJECTION | INJ. OCCUPANTS | CHA(1) | 72 |
| INJ | DRV/OCC INJURY | INJ. OCCUPANTS | CHA(8) | 72 |
| OCC_AIR | OCCUPANT AIR BAG | INJ. OCCUPANTS | CHA(1) | 73 |
| OCC_IMAG | IMAGE NUMBER | INJ. OCCUPANTS | NUM | 73 |
| OCC_REEL | REEL NUMBER | INJ. OCCUPANTS | NUM | 73 |
| REST1 | SAFETY EQUIPMENT | INJ. OCCUPANTS | NUM | 73 |
| SEATPOS | SEATING POSITION | INJ. OCCUPANTS | NUM | 74 |
| SEX | OCCUPANT SEX | INJ. OCCUPANTS | NUM | 74 |
| VEHNO | VEHICLE NUMBER | INJ. OCCUPANTS | NUM | 74 |
NOTE: (1) This file only contains data on injured occupants in the vehicle for Years 1985-1992. From 1992 onwards, the file contains injured as well as uninjured occupants.
(2) The 1985 data contains significantly more "no injury" codes than do the 1986 or 1987 files, probably due to a temporary change in coding procedures. The analyst should consider eliminating all cases where "injury severity" (OCC_SEV) is coded as "no injury" in all analysis except those related specifically to children less than age 5.
(3) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
NOTE: SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
OCCUPANT AGE
ACCIDENT CASE NUMBER
NON-LABELED VARIABLE -- CASE NUMBER
OCCUPANT EJECTION
NOTE: Variable added in 1994.
DRV/OCC INJURY
NOTE: The 1985 data contains significantly more "none" codes than future years, probably due to a temporary change in coding procedures. The analyst should consider eliminating all cases where "injury severity" (OCC_SEV) is coded as "none" in all analysis except those related specifically to children less than age 5.
OCCUPANT AIR BAG
NOTE: (1) Categories 3-8 apply to data from 2004 onwards. (2) Variable added in 1996.
IMAGE NUMBER
NON-LABELED VARIABLE
NOTE: (1) This variable was added in 1988 to aid Illinois DOT in the location of accident report forms. (2) Variable added in 1990 and discontinued in 1995.
REEL NUMBER
NON-LABELED VARIABLE
NOTE: (1) This variable was added in 1989 to aid Illinois DOT in the location of accident report forms. (2) Variable added in 1990 and discontinued in 1995.
SAFETY EQUIPMENT
NOTE: (1) This variable has a very high number of "not stated" codes and is characterized in general by poor data for years 1985 – 1991. (2) Categories 10-12 and 99 apply to data before 2004.
SEATING POSITION
NOTE: Categories 9-12 apply to data from 2004 onwards.
OCCUPANT SEX
VEHICLE NUMBER
NON-LABELED VARIABLE
NOTE: This is the reference number of vehicle in which this occupant is seated. This variable is used in linkage with vehicle subfile.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AADT | ANNUAL ADT | ROADLOG | NUM | 79 |
| AADT_YR | YEAR OF ADT | ROADLOG | CHA(4) | 79 |
| ACCESS | ACCESS CONTROL | ROADLOG | NUM | 79 |
| ADMINHWY | ADMINISTRATIVE HIGHWAY SYSTEM | ROADLOG | CHA(1) | 79 |
| APPR_NBR | APPURTENANCE NUMBER | ROADLOG | NUM | 79 |
| AVAI_ROW | AVAILABLE RIGHT OF WAY | ROADLOG | CHA(1) | 80 |
| BEGMP | BEGIN MILEPOST | ROADLOG | NUM | 80 |
| BUILD_BY | BUILT BY | ROADLOG | CHA(1) | 80 |
| CNTY_RTE | COUNTY ROUTE NUMBER | ROADLOG | CHA(7) | 80 |
| COMM_VOL | COMMERCIAL VOLUME | ROADLOG | NUM | 80 |
| COMMDATE | DATE | ROADLOG | CHA(4) | 81 |
| COUNTY | COUNTY | ROADLOG | NUM | 81 |
| CURB1 | CURB TYPE | ROADLOG | NUM | 83 |
| CURV_CUT | CURVE CUT | ROADLOG | CHA(1) | 83 |
| CURV_RAD | CURVE RADIUS | ROADLOG | NUM | 83 |
| DEF_ANGL | DEFLECTION ANGLE | ROADLOG | CHA(7) | 83 |
| DIR_CURV | HORIZONTAL CURVE DIRECTION | ROADLOG | CHA(1) | 83 |
| DISTRICT | ILL DISTRICT | ROADLOG | NUM | 84 |
| END_RTE | END OF ROUTE | ROADLOG | CHA(1) | 84 |
| ENDMP | END MILEPOST | ROADLOG | NUM | 84 |
| EXST_ROW | EXISTING RIGHT OF WAY | ROADLOG | NUM | 84 |
| FAUL_HGHT | FAULT HEIGHT | ROADLOG | NUM | 84 |
| FED_AID | FEDERAL AID (IN LIEU) | ROADLOG | NUM | 84 |
| FUNC_CLS | FUNCTIONAL CLASS | ROADLOG | NUM | 85 |
| HOR_BEG | HORIZONTAL CURVE BEGINNING MILEPOST | ROADLOG | NUM | 85 |
| HOR_BEGMP | HORIZONTAL CURVE BEGIN MILEPOST | ROADLOG | CHA(5) | 85 |
| HOR_END | HORIZONTAL CURVE END MILEPOST | ROADLOG | NUM | 85 |
| HOR_ENDMP | HORIZONTAL CURVE END MILEPOST | ROADLOG | CHA(5) | 86 |
| HPMS_IND | HPMS INDICATOR | ROADLOG | CHA(1) | 86 |
| HPMS_SEC | HPMS SECTION | ROADLOG | NUM | 86 |
| HPMS_SEG | HPMS SECTION SEGMENT | ROADLOG | NUM | 86 |
| HPMS1 | HPMS SECTION ID | ROADLOG | NUM | 86 |
| INSHTP1 | INSIDE SHOULDER TYPE 1 | ROADLOG | CHA(1) | 86 |
| INSHTP2 | INSIDE SHOULDER TYPE 2 | ROADLOG | CHA(1) | 87 |
| INSHWD1 | INSIDE SHOULDER WIDTH 1 | ROADLOG | NUM | 87 |
| INSHWD2 | INSIDE SHOULDER WIDTH 2 | ROADLOG | NUM | 87 |
| INT_TYPE | INTERSECTION FEATURE | ROADLOG | CHA(1) | 88 |
| INV_DIR | INVENTORY DIRECTION | ROADLOG | CHA(1) | 88 |
| KEY_RTE_APPRTE | KEY ROUTE APPURTENANCE NUMBER | ROADLOG | NUM | 88 |
| KEY_RTE_APPURTCD | KEY ROUTE APPURTENANCE TYPE | ROADLOG | CHA(1) | 88 |
| KEY_RTE_SEQNBR | KEY ROUTE SEQUENCE NUMBER | ROADLOG | CHA(4) | 88 |
| KEY_RTE_STATION | KEY ROUTE STATION | ROADLOG | NUM | 89 |
| KEY_RTE_SUF_CDE | KEY ROUTE SUFFIX CODE | ROADLOG | CHA(1) | 89 |
| KEY_RTE_TYPCD | KEY ROUTE TYPE CODE | ROADLOG | CHA(1) | 89 |
| LANEWID | AVERAGE LANE WIDTH | ROADLOG | NUM | 89 |
| LPK_REST | PARKING RESTRICTIONS LEFT | ROADLOG | CHA(1) | 89 |
| LST_SECD | LATEST CONSTRUCTION SECTION D | ROADLOG | CHA(15) | 89 |
| LST_SECE | LATEST CONSTRUCTION SECTION E | ROADLOG | CHA(10) | 89 |
| LST_UPDT | DATE OF LAST UPDATE | ROADLOG | CHA(8) | 90 |
| MAIN_DIS | MAINTENANCE DISTRICT | ROADLOG | NUM | 90 |
| MAIN_SEC | MAINTENANCE SECTION | ROADLOG | CHA(6) | 90 |
| MAINTENC | MAINTENANCE | ROADLOG | NUM | 90 |
| MED_TYPE | MEDIAN TYPE | ROADLOG | NUM | 90 |
| MEDWID | MEDIAN WIDTH | ROADLOG | NUM | 90 |
| MRK_BEG | MARKED BEGINNING | ROADLOG | NUM | 91 |
| MRK_RTE1 | MARKED ROUTE1 | ROADLOG | CHA(6) | 91 |
| MRK_RTE2 | MARKED ROUTE2 | ROADLOG | CHA(6) | 91 |
| MRK_RTE3 | MARKED ROUTE3 | ROADLOG | CHA(5) | 91 |
| MRK_RTE4 | MARKED ROUTE4 | ROADLOG | CHA(5) | 91 |
| MRK_RTNBR | MARKED ROUTE NUMBER | ROADLOG | NUM | 91 |
| MRKD_RTE_BEGMP | MARKED ROUTE BEGINNING MILEPOST |
ROADLOG | NUM | 91 |
| MULTICNT | AVERAGE ANNUAL DAILY MULTI- UNIT VOLUME |
ROADLOG | NUM | 92 |
| MUNI_NAME | MUNICIPAL NAME | ROADLOG | CHA(20) | 92 |
| MVMT | MILLION VEHICLE MILES OF TRAVEL |
ROADLOG | NUM | 92 |
| NEW_ONEWAY | NEW ONEWAY INDICATOR | ROADLOG | CHA(1) | 92 |
| NHS_CDE | NATIONAL HIGHWAY SYSTEM | ROADLOG | CHA(1) | 92 |
| NO_LANES | TOTAL NUMBER OF LANES | ROADLOG | NUM | 92 |
| NO_SPLNS | NUMBER OF SPECIAL LANES | ROADLOG | NUM | 93 |
| NON_ATTN | NON-ATTAINMENT AREA | ROADLOG | NUM | 93 |
| ODM_MILE | ODOMETER MILE | ROADLOG | NUM | 93 |
| ODM_SIGN | ODOMETER SIGN | ROADLOG | CHA(1) | 93 |
| OLD_AADT | OLD AADT | ROADLOG | NUM | 93 |
| ONEWAY | ONEWAY INDICATOR | ROADLOG | NUM | 94 |
| OPCRSNBR | OPPOSITE ROAD CRS NUMBER | ROADLOG | NUM | 94 |
| OPP_FAULT | OPPOSITE ROAD FAULT | ROADLOG | CHA(3) | 94 |
| OPP_PAVDIS | OPPOSITE ROAD PAVEMENT DISTRESS |
ROADLOG | CHA(10) | 94 |
| OPP_RUTDEPT | OPPOSITE ROAD RUT DEPTH | ROADLOG | CHA(3) | 94 |
| ORG_SECB | ORIGINAL CONSTRUCTION SEC B | ROADLOG | CHA(15) | 94 |
| ORG_SECC | ORIGINAL CONSTRUCTION SEC C | ROADLOG | CHA(5) | 94 |
| OUTSHTP1 | OUTSIDE SHOULDER TYPE 1 | ROADLOG | CHA(1) | 94 |
| OUTSHTP2 | OUTSIDE SHOULDER TYPE 2 | ROADLOG | CHA(1) | 95 |
| OUTSHWD1 | OUTSIDE SHOULDER WIDTH 1 | ROADLOG | NUM | 95 |
| OUTSHWD2 | OUTSIDE SHOULDER WIDTH 2 | ROADLOG | NUM | 96 |
| OVHOBSNR | OVERHEAD OBSTRUCTION NUMBER | ROADLOG | CHA(7) | 96 |
| PAV_DIST | PAVEMENT DISTRESS | ROADLOG | CHA(10) | 96 |
| PAVECOND | PRESENT SERVICE RATING | ROADLOG | NUM | 96 |
| PCNT_TRK | PERCENTAGE TRUCKS | ROADLOG | CHA(2) | 96 |
| PLN_SEQ | PLANNING SEQUENCE | ROADLOG | NUM | 97 |
| POP_GRP | MUNICIPALITY POPULATION GROUP | ROADLOG | CHA(1) | 97 |
| PRKLN_WD | PARKING LANE WIDTH | ROADLOG | NUM | 97 |
| RATE_DTE | MONTH-YR OF CONDITION RATING | ROADLOG | NUM | 97 |
| RD_DIST | TOWNSHIP/ROAD DISTRICT | ROADLOG | NUM | 97 |
| RD_STRUC | STRUCTURE NUMBER | ROADLOG | CHA(7) | 98 |
| RD_YEAR | YEAR ROAD CONSTRUCTED | ROADLOG | NUM | 98 |
| REF_PNT | REFERENCE POINT | ROADLOG | CHA(15) | 98 |
| REF_PNT1 | REFERENCE POINT 1 | ROADLOG | CHA(20) | 98 |
| REF_PNT2 | REFERENCE POINT 2 | ROADLOG | CHA(20) | 98 |
| REF_PNT3 | REFERENCE POINT 3 | ROADLOG | CHA(20) | 98 |
| REF_PNTA | REFERENCE POINT A | ROADLOG | CHA(15) | 98 |
| REFPNT1A | REFERENCE POINT 1 TYPE | ROADLOG | CHA(2) | 98 |
| REFPNT2A | REFERENCE POINT 2 TYPE | ROADLOG | CHA(2) | 98 |
| REFPNT3A | REFERENCE POINT 3 TYPE | ROADLOG | CHA(2) | 98 |
| REFPT1IN | REFERENCE POINT 1 INTERSECTION |
ROADLOG | CHA(1) | 99 |
| REFPT2IN | REFERENCE POINT 2 INTERSECTION |
ROADLOG | CHA(1) | 99 |
| REFPT3IN | REFERENCE POINT 3 INTERSECTION |
ROADLOG | CHA(1) | 99 |
| RESEV_RD | RESERVATION ROAD | ROADLOG | CHA(1) | 99 |
| REV_CDE | FORWARD/REVERSE CODE | ROADLOG | CHA(1) | 99 |
| RODWYCLS | ROADWAY CLASSIFICATION | ROADLOG | CHA(2) | 99 |
| ROW | RIGHT OF WAY | ROADLOG | NUM | 99 |
| RPK_REST | PARKING RESTRICTION | ROADLOG | CHA(1) | 100 |
| RR_CRX | RAILROAD CROSS RIDEABILITY | ROADLOG | NUM | 100 |
| RRD_LNK | RAILROAD LINK NUMBER | ROADLOG | CHA(7) | 100 |
| RRX_DIRCD | RAILROAD DIRECTION CODE | ROADLOG | CHA(1) | 100 |
| RRX_RIDE | RAILROAD CROSSING RIDEABILITY | ROADLOG | CHA(1) | 100 |
| RTE_APPURT | ROUTE APPURTENANCE | ROADLOG | NUM | 101 |
| RTE_NBR | ROUTE NUMBER | ROADLOG | NUM | 101 |
| RTE_SEGCD | ROUTE SEQUENCE NUMBER | ROADLOG | CHA(2) | 101 |
| RTE_STAT | ROUTE STATION | ROADLOG | NUM | 101 |
| RTE_STAT_END | ROUTE STATION END | ROADLOG | NUM | 101 |
| RTE_SUFX | ROUTE SUFFIX | ROADLOG | CHA(1) | 101 |
| RTE_TYPE | ROUTE TYPE | ROADLOG | NUM | 101 |
| RURURB | RURAL / URBAN CODE | ROADLOG | NUM | 102 |
| RUT_DEPTIN | RUT DEPTH INDICATOR | ROADLOG | CHA(3) | 102 |
| S_RTENBR | SAF-MRK-ROUTE NUMBER | ROADLOG | NUM | 102 |
| S_RTETYP | SAF-MRK-ROUTE TYP | ROADLOG | NUM | 102 |
| SAF_CNTL | SAF-ACCESS-CNTL | ROADLOG | NUM | 102 |
| SAF_FASY | SAF-FASYS | ROADLOG | NUM | 103 |
| SAF_TWN | SAF-TWNSHP | ROADLOG | NUM | 103 |
| SEG_LNG | SEGMENT LENGTH | ROADLOG | NUM | 103 |
| SHLD_CON | SHOULDER CONDITION | ROADLOG | NUM | 103 |
| SPD_LIM2 | POSTED SPEED LIMIT (MINUS DIRECTION) |
ROADLOG | NUM | 103 |
| SPD_LIMT | ROADWAY SPEED LIMIT | ROADLOG | NUM | 103 |
| SPEC_SYSM | SPECIAL SYSTEMS | ROADLOG | CHA(1) | 104 |
| SPLN_TYP | LANES SPECIAL TYPE | ROADLOG | CHA(1) | 104 |
| SPLN_WID | LANES SPECIAL WIDTH | ROADLOG | NUM | 104 |
| STAT_DIR | PLAN STATION DIRECTION | ROADLOG | CHA(1) | 104 |
| STOU_IND | STRUCTURE OVER/UNDER IND | ROADLOG | CHA(1) | 105 |
| STR_ENDM | STRUCTURE END MILEPOST | ROADLOG | CHA(5) | 105 |
| STR_LNG | STRUCTURE LENGTH | ROADLOG | NUM | 105 |
| STRDIRCD | STRUCTURE DIRECTION CODE | ROADLOG | CHAR(1) | 105 |
| STRT_NAM | STREET-NAME | ROADLOG | CHA(15) | 105 |
| STRU_FAC | STRUCTURE FACILITY LOCATION | ROADLOG | CHA(20) | 105 |
| STRU_LNK | STRUCTURE LINK NUMBER | ROADLOG | NUM | 105 |
| SUF_CDE | SUFFIX CODE | ROADLOG | CHA(1) | 105 |
| SURF_RAT | SURFACE CONDITION RATING | ROADLOG | NUM | 106 |
| SURF_TYP | SURFACE TYPE – ROAD 1 | ROADLOG | NUM | 106 |
| SURF_WID | TOTAL SURFACE WIDTH | ROADLOG | NUM | 106 |
| SURF_YR | YEAR OF PRESENT SUF CONST | ROADLOG | CHA(2) | 107 |
| SURFDATE | YEAR OF PRESENT SUF CONST | ROADLOG | CHA(4) | 107 |
| TOTINSHL | TOTAL IN SHOULDER | ROADLOG | NUM | 107 |
| TOTOTSHL | TOTAL OUT SHOULDER | ROADLOG | NUM | 107 |
| TRF_CNTL | TRAFFIC CONTROL | ROADLOG | CHA(1) | 107 |
| TRK_RTE | DESIGNATED TRUCK ROUTE | ROADLOG | CHA(1) | 107 |
| URB_AREA | URBAN AREA | ROADLOG | NUM | 108 |
| VER_BEGMP | VERTICAL GRADE BEGINNING MILEPOST |
ROADLOG | CHA(5) | 108 |
| VER_ENDMP | VERTICAL END MILEPOST | ROADLOG | CHA(5) | 108 |
| VERT_APP | VERTICAL CURVE APPROACH GRADE | ROADLOG | NUM | 108 |
| VERT_BEG | VERTICAL CURVE BEGINNING MILEPOST |
ROADLOG | NUM | 108 |
| VERT_END | VERTICAL CURVE END MILEPOST | ROADLOG | NUM | 109 |
| VERT_LEV | VERTICAL CURVE LEAVE GRADE | ROADLOG | NUM | 109 |
| VERT_LGN | VERTICAL CURVE LENGTH | ROADLOG | NUM | 109 |
| VERTAPPS | VERTICAL APPROACH SIGN | ROADLOG | CHA(1) | 110 |
| VERTLEVS | VERTICAL LEAVE SIGN | ROADLOG | CHA(1) | 110 |
| VOL_YR | YEAR OF HEAVY COMMERCIAL VOL | ROADLOG | NUM | 110 |
| XAADT | CROSSROAD AADT | ROADLOG | NUM | 110 |
| XCOMADT | CROSSROAD COMMERCIAL ADT | ROADLOG | NUM | 110 |
| XFUNC_CL | CROSS FUNCTIONAL CLASS | ROADLOG | NUM | 110 |
NOTE: SAS variable names and explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
ANNUAL ADT
NOTE: Variable added in 1987.
YEAR OF AADT
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
ACCESS CONTROL
NOTE: Variable added in 1987.
ADMISNISTRATIVE HIGHWAY SYSTEM
NOTE: Variable added in 1997.
APPURTENANCE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
AVAILABLE R.O.W.
NOTE: Variable added in 1997.
BEGIN MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
BUILT BY
NOTE: Variable added in 2004.
CNTY RTETYP RTENBR
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
HEAVY COMMERCIAL VOLUME
NOTE: Variable added in 1987.
DATE
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
COUNTY
NOTE: Variable added in 1987.
CURB TYPE
NOTE: Variable added in 1987 and discontinued in 1995.
CURVE CUT
NOTE: Variable added in 1987 and discontinued in 1995.
CURVE RADIUS
NON LABELED VARIABLE -- Gives the curve radius in feet.
NOTE: (1) For years later to 1997, refer to the CURVE file, which has variables for sections with curves. Also see discussion section for roadlog and curve files. (2) Variable added in 1987.
DEFLECTION ANGLE
NOTE: Variable added in 1987 and discontinued in 1995.
HORIZONTAL CURVE DIRECTION
NOTE: (1) For years later to 1997, refer to the CURVE file, which has variables for sections with curves. (2) Variable added in 1987.
ILL-DISTRICT
NOTE: Variable added in 1987.
END OF ROUTE
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
END MILE POST
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
EXISTING RIGHT OF WAY
NOTE: (1) Similar to ROW variable available during previous years. (2) Variable added in 1997.
FAULT HEIGHT
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
FEDERAL AID (IN LIEU)
NOTE: Variable added in 1987 and discontinued in 1995.
FUNCTIONAL CLASS
NOTE: Variable added in 1987.
HORIZONTAL CURVE BEGINNING MILEPOST
NON-LABELED VARIABLE
NOTES: (1) This variable is present in data prior to 1997. For later years refer to the CURVE file, which has variables for sections with curves. Also refer the discussion section, Roadlog file for more information on horizontal curves. (2) Variable added in 1997.
HORIZONTAL CURVE BEGIN MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
HORIZONTAL CURVE ENDING MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
HORIZONTAL CURVE END MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
HPMS INDICATOR
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
HPMS SECTION
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
HMPS-SECTION SEGMENT
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
HMPS-SECTION ID
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
INSIDE SHOULDER TYPE
NOTE: (1) This variable is only coded for divided roadway, resulting in a high numbers of un-coded cases. (2) If a road section has different shoulder types on the two inside shoulders, then the shoulder type having the lower numbered code is used. (3) For sections having composite shoulders (e.g., part paved, part sod), this is the type that is adjacent to the travel lane. See INSHTP2 for the other (outer) shoulder type. (4) Variable added in 1987.
INSIDE SHOULDER TYPE 2
NOTE: (1) This variable is only coded for divided roadway, resulting in a high number of high numbers of un-coded cases. This is coded for composite shoulders, and defines the shoulder type not adjacent to the travel lane – the outer shoulder type. See INSHTP1 for inner shoulder type – adjacent to the travel lane. (2) Variable added in 1997.
SHOULDER WIDTH FOR INSIDE SHOULDER TYPE 1
NOTE: (1) This variable is only coded for divided roadway, resulting in a high number of un-coded cases. This is the full width for shoulders of non-composite (single type) shoulders, and the width of the inner shoulder type – adjacent to the travel lane - for composite shoulders. (2) Variable added in 1987.
SHOULDER WIDTH FOR INSIDE SHOULDER TYPE 2
NOTE: (1) This variable is only coded for divided roadway, resulting in a high number of un-coded cases. Refer to notes for INSHTP2 for more information. (2) Variable added in 1997.
INTERSECTION FEATURE
NOTE: (1) Variable added in 1989 and discontinued in 1995. (2) The INT_TYPE variable is required for all marked routes and for all unmarked states system routes. It is optional for all other routes.
INTERFACE INVENTORY DIRECTION CODE
NOTE: Variable added in 1997.
KEY ROUTE APPURTENANCE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
KEY ROUTE APPURTENANCE TYPE
NOTE: Variable added in 2004.
KEY ROUTE SEQUENCE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
KEY ROUTE STATION
NON-LABELED VARIABLE
NOTE: Variable available only for 2004.
KEY ROUTE SUFFIX CODE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
KEY ROUTE TYPE CODE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
AVERAGE LANE WIDTH
NOTE: Variable added in 1987.
PARKING RESTRICTIONS LEFT
NOTE: Variable added in 1997.
LATEST CONSTRUC SECTION D
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
LATEST CONSTRUC SECTION E
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
DATE OF LAST UPDATE [IN YYYY/MM/DD FORMAT]
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
MAINTENANCE DISTRICT
NOTE: Variable added in 1987.
MAINTENANCE SECTION
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
MAINTENANCE RESPONSIBILY
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
MEDIAN TYPE
NOTE: (1) Category 6 is discontinued from 1994 onwards and appears to be combined with categories 5 and 7. (2) Variable added in 1987.
MEDIAN WIDTH
NOTE: (1) Median width is measured as the width of the portion of the divided highway separating the opposing directions of traffic. It is measured from inside edge of the pavement to the inside edge of the pavement. (2) Variable added in 1987.
MARKED BEGINNING
NON-LABELED VARIABLE
NOTE: Variable available only for 2004.
MARKED ROUTE1
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
MARKED ROUTE1
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
MARKED ROUTE1
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
MARKED ROUTE1
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
MARKED ROUTE NUMBER
NON-LABELED VARIABLE
NOTE: Variable available only for 2004.
MARKED ROUTE BEGINNING MILEPOST
NON-LABELED VARIABLE
NOTE: Variable available only for 2004.
ANNUAL AVERAGE DAILY MULTIPLE UNIT VOLUME
NOTE: Variable added in 1997.
MUNICIPAL NAME
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
MILLION VEHICLE MILES OF TRAVEL
NON-LABELLED VARIABLE
NOTE: Variable added in 1987.
NEW ONEWAY
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
NATIONAL HIGHWAY SYSTEM
NOTE: Variable added in 1997.
TOTAL NUMBER OF LANES
NOTE: Variable added in 1987.
NUMBER OF SPECIAL LANES
NOTE: Variable added in 1997.
NON-ATTAINMENT AREA
NOTE: Variable added in 1997.
ODOMETER MILE
NON-LABELED VARIABLE
NOTE: Variable added in 2002.
ODOMETER SIGN
NON-LABELED VARIABLE
NOTE: Variable added in 2002.
OLD AADT
NOTE: Variable discontinued in 1995.
ONEWAY INDICATOR
NOTE: Variable discontinued in 1987.
OPPOSITE ROAD CRS NUMBER
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1997.
OPPOSITE ROAD FAULT
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
OPPOSITE ROAD PAVEMENT DISTRESS
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
OPPOSITE ROAD RUT DEPTH
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
ORIGINAL CONSTRUCTION SEC B
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1995.
ORIGINAL CONSTRUCTION SEC C
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1995.
OUTSIDE SHOULDER TYPE 1
NOTE: (1) If a road section has different shoulder types on the two outside shoulder, then the shoulder type having the lower numbered coded is used. (2) For sections having composite shoulders (e.g., part paved, part sod), this is the type that is adjacent to the travel lane. See OUTSHTP2 for other (outer) shoulder type. (3) Variable added in 1987.
OUTSIDE SHOULDER TYPE 2
NOTE: (1) This is coded for composite shoulders, and defines the shoulder type not adjacent to the travel lane – the outer shoulder type. See OUTSHTP1 for inner shoulder type. (2) Variable added in 1997.
OUTSIDE SHOULDER WIDTH 1
NOTE: (1) This is the full width for shoulders of non-composite (single type) shoulders, and the width of the inner shoulder type – adjacent to the travel lane - for composite shoulders. See the note under OUTSHTP1 for more information. (2) Variable added in 1987.
OUTSIDE SHOULDER WIDTH 2
NOTE: (1) Refer to the notes for OUTSHTP2 for more information. (2) Variable added in 1997.
OVERHEAD OBSTRUCTION NUMBER
NON-LABELLED VARIABLE
NOTE: Variable added in 1997.
PAVEMENT DISTRESS
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
PRESENT SERVICE RATING
NOTE: (1) Only categories 0 and 1 are coded. Use this variable with caution. (2) Variable added in 1987 and discontinued in 1995.
PERCENTAGE TRUCKS
NOTE: (1) Little useable data after 1990. See COMM_VOL.
(2) Variable added in 1987 and discontinued in 1995.
PLANNING SEQUENCE
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
MUNICIPALITY POPULATION GROUP
NOTE: Variable added in 1997.
PARKING LANE WIDTH
NOTE: Variable added in 1987 and discontinued in 1995.
MNTH-YR OF COND RATING
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
TOWNSHIP/ROAD DISTRICT
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
STRUCTURE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
YEAR ROAD CONSTRUCTED
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
REFERENCE POINT
NON-LABELLED VARIABLE
NOTE: (1) Variable added in 1987 and discontinued in 1995. (2) See discussion section for more details.
REFERENCE POINT 1
REFERENCE POINT 2
REFERENCE POINT 3
NON-LABELLED VARIABLE
NOTE: Variables added in 1997.
REFERENCE POINT A
NON-LABELLED VARIABLE
NOTE: (1) Variable added in 1987 and discontinued in 1995. (2) See discussion section for more details.
REFERENCE POINT 1 TYPE
REFERENCE POINT 2 TYPE
REFERENCE POINT 3 TYPE
NOTE: Variable added in 1997.
REFERENCE POINT 1 INTERSECTION
REFERENCE POINT 2 INTERSECTION
REFERENCE POINT 3 INTERSECTION
NOTE: Variable added in 1997.
RESERVATION ROAD
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
FORWARD/REVERSE CODE
NON-LABELED VARIABLE
NOTE: (1) Designates direction of original inventory. Accidents are located correctly to sections regardless of directions. However, for sections designated with an AR@, the point that normally designates the PC is the PT, and the point normally designating the beginning of a structure is the end. The ‘other end’ can be determined by subtracting the length. (2) Variable added in 1987 and discontinued in 1995.
ROADWAY CLASSIFICATION
RIGHT OF WAY
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
PARKING RESTRICTION
NOTE: Variable added in 1997.
RAILROAD CROSS RIDEABILITY
NOTE: Variable added in 1987 and discontinued in 1995.
RAILROAD LINK NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
RAILROAD DIRECTION CODE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
RAILROAD CROSSING RIDEABILITY
NOTE: Variable added in 2004.
ROUTE APPURTENANCE
NON-LABELED VARIABLE
NOTE: Variable available only for 2004.
ROUTE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
ROUTE SEQUENCE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
ROUTE STATION
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 2005. Data is missing for the years 1993, and 1995 to 2003.
ROUTE STATION END
NON-LABELED VARIABLE
NOTE: Variable available only for 2004.
ROUTE SUFFIX
NOTE: Data available for the years 1992 and 1995.
ROUTE TYPE
NOTE: Variable discontinued in 1995.
RURAL/URBAN CODE
NOTE: (1) The RUR_URB variable was created to supplement the functional class and urban area' variables already on the file. By using a combination of these two variables, a Rural/Urban code was created. (2) Variable added in 1987.
RUT DEPTH INDICATOR
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
SAF-MRK-ROUTE NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
SAF-MRK-ROUTE TYPE
NOTE: Variable added in 1987.
SAF-ACCESS-CNTL
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
SAF-FASYS
NON-LABELED VARIABLE
NOTE: Variable added in 1987 discontinued in 1995.
SAF-TWNSHP
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
CALCULATED SECTION LENGTH
NON-LABELED VARIABLE
NOTE: (1) This is a calculated variable based on BEGMP and ENDMP, which provides an accurate section length. (2) Variable added in 1987.
SHOULDER CONDITION
NOTE: Variable added in 1987 and discontinued in 1995.
POSTED SPEED LIMIT (MINUS DIRECTION)
ROADWAY SPEED LIMIT
NOTE: (1) Variables added in 1987. (2) SPD_LIM2 was discontinued in 1995.
SPECIAL SYSTEMS
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
LANES SPECIAL TYPE
NOTE: Variable added in 1997.
SPECIAL LANE WIDTH
NOTE: Variable added in 1997.
PLAN STATION DIRECTION
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
STRUCTURE OVER/UNDER INDICATOR
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
STRUCTURE END MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
STRUCTURE LENGTH
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
STRUCTURE DIRECTION CODE
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
STREET NAME
NON-LABELED VARIABLE
NOTE: Variable added in 1987.
STRUCTURE FACILITY LOCATION
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
STRUCTURE LINK NUMBER
NON-LABELED VARIABLE
NOTE: Variable added in 1997 and discontinued in 1995.
SUFFIX CODE
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
SURFACE CONDITION RATING
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
SURFACE TYPE – ROAD 1
NOTE: Variable added in 1987.
TOTAL SURFACE WIDTH
NOTE: Variable added in 1987.
YEAR PRESENT SUF CONST
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
YEAR OF SURFACE CONSTRUCTION
NON-LABELED VARIABLE
NOTE: (1) This variable provides information similar to that provided by SURF_YR in the earlier years. (2) Variable added in 1997.
TOTAL INSIDE SHOULDER WIDTH (1 + 2)
NON-LABELED VARIABLE
NOTE: (1) '0' = NO WIDTH, '1 - 19' = WIDTH TO NEAREST FOOT (2) Variable coded only for divided highways. (3) Variable added in 1997.
TOTAL OUTSIDE SHOULDER WIDTH (1 + 2)
NON-LABELED VARIABLE
NOTE: (1) Refer to notes for outside shoulder type/width 1 and 2. (2) Variable added in 1997.
TRAFFIC CONTROL
NOTE: (1) TRF_CNTL describes the type of traffic control device operating at the intersection. In the description of the codes for this variable, 'PHASE' is the part of the cycle for any combination(s) of traffic movements receiving the right-of-way simultaneously. (2) Variable added in 1989.
DESIGNATED TRUCK ROUTE
NOTE: Variable added in 1987.
URBAN AREA
NOTE: Variable added in 1987.
VERTICAL GRADE BEGINNING MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
VERTICAL END MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 2004.
VERTICAL CURVE APPROACH GRAD
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. Refer to roadlog file discussion section. Use all vertical curve variables with caution, as information on vertical curves is neither a full census nor a random sample. (2) Variable added in 1987.
VERTICAL CURVE BEGINNING MILEPOST
NON-LABELED VARIABLE
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. Refer to roadlog file discussion section. Use all vertical curve variables with caution, as information on vertical curves is neither a full census nor a random sample. (2) Variable added in 1997.
VERTICAL CURVE END MILEPOST
NON-LABELED VARIABLE
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. Refer to roadlog file discussion section. Use all vertical curve variables with caution, as information on vertical curves is neither a full census nor a random sample. (2) Variable added in 1997.
VERTICAL CURVE LEAVE GRADE
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. Refer to roadlog file discussion section. Use all vertical curve variables with caution, as information on vertical curves is neither a full census nor a random sample. (2) Variable added in 1987.
VERTICAL CURVE LENGTH
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. (2) Variable added in 1987 and discontinued in 1995.
VERTICAL APPROACH SIGN
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. Refer to roadlog file discussion section. Use all vertical curve variables with caution, as information on vertical curves is neither a full census nor a random sample. (2) Variable added in 1997.
VERTICAL LEAVE SIGN
NOTE: (1) Vertical grade data is only collected for "substandard" vertical curves. Refer to roadlog file discussion section. Use all vertical curve variables with caution, as information on vertical curves is neither a full census nor a random sample. (2) Variable added in 1997.
YEAR OF HEAVY COMER VOL
NON-LABELED VARIABLE
NOTE: Variable added in 1987 and discontinued in 1995.
CROSSROAD AADT
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
CROSSROAD COMMERCIAL ADT
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
CROSS FUNCTIONAL CLASS
NOTE: Variable added in 1997.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| BEGMP | BEGINNING MILE POST | DEFICIENT CURVE | NUM | 112 |
| CNTY_RTE | COUNTY ROUTE NUMBER | DEFICIENT CURVE | CHA(7) | 112 |
| CURV_LGT | CURVE LENGTH | DEFICIENT CURVE | NUM | 112 |
| CURV_RAD | CURVE RADIUS | DEFICIENT CURVE | NUM | 112 |
| DEG_CURV | DEGREE OF CURVATURE | DEFICIENT CURVE | NUM | 112 |
| DIR_CURV | DIRECTION OF CURVE | DEFICIENT CURVE | CHA(1) | 112 |
| ENDMP | END MILE POST | DEFICIENT CURVE | NUM | 113 |
| SEG_LNG | SEGMENT LENGTH | DEFICIENT CURVE | NUM | 113 |
NOTE: (1) This file only contains data on deficient curves from 1997 onwards.
(2) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
BEGIN MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
CNTY RTETYP RTENBR
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
CURVE LENGTH
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
CURVE RADIUS
NOTE: Variable added in 1997.
DEGREE OF CURVE
NOTE: Variable added in 1997.
HORIZONTAL CURVE DIRECTION
NOTE: Variable added in 1997.
END MILEPOST
NON-LABELED VARIABLE
NOTE: Variable added in 1997.
SEGMENT LENGTH
NON-LABELED VARIABLE
NOTE: Variable added in 1997.