Turner-Fairbank Highway Research Center

 
 
 

Highway Safety Information System Guidebook for the California State Data Files

SAS File Formats

Prepared by

Anusha patel Nujjetty
Soumya Sharma
LENDIS Corporation
Turner Fairbank Highway Research Center
Federal Highway Administration
6300 Georgetown Pike
McLean, VA 22101-2296

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

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

Revised, June 2015

TABLE OF CONTENTS

Introduction to the California HSIS Guidebook

The California database incorporated into the HSIS system is derived from the California TASAS (Traffic Accident Surveillance and Analysis System). The system, maintained by the Traffic Operations Office (TO) of CALTRANS, is a mainframe-based system based on COBOL programming. The TO Office provides the data to HSIS in the form of two different data files. These contain:

  • Accident data (including accident, vehicle, and occupant data)
  • Roadway inventory data (including intersection and interchange ramp data, and Average Daily Traffic counts)

Raw file data is provided to the Highway Safety Research Center (HSRC) where they are retained as backup information. When obtained from California, the documentation (variable listings, definitions, etc.) for these raw files and for the SAS files that are developed from them is available from HSIS staff.

Beginning in 2004, the HSIS system was converted from a SYBASE relational database to an ORACLE relational database for internal use. Data files for a given State are linked and manipulated by HSIS staff using SAS code and, as in the past, we have continued to produce SAS format libraries for each of the variables in each of the files. This Guidebook will concern these SAS files - their formats, completeness, and quality. However, researchers requesting data from HSIS can request the output in various formats such as SAS, Microsoft Excel® and Access®, dBase, ASCII, etc.

As noted above, the California SAS accident data are divided into three separate subfiles, the first containing the basic accident information on a case-by-case basis, the second containing information on up to nine vehicles in each accident (including driver information), and the third containing information on up to 70 occupants in each crash. (If more than nine vehicles are in a crash, the additional vehicles are captured in separate accident records that are exactly like the initial record, but 1 second later.)  The HSIS accident and vehicle data are extracted directly from the TASAS by the TO staff. The occupant data, including data on the driver, are not included in TASAS, but are in the California Highway Patrol's SWITRS  Statewide Integrated Traffic Records System) file. This latter file is acquired from California by the US DOT National Highway Traffic Safety Administration (NHTSA) each year, and HSRC staff obtains copies of this file from NHTSA and merges it with the TASAS data.

Unlike the accident file, which is referenced to a point on the roadway, each record in the Roadlog File contains information on a homogeneous section of roadway (i.e., a stretch of road that is consistent in terms of certain characteristics, with a new section being defined each time any of the characteristics changes). Each record contains current characteristics of the roadway system and includes such variables as traveled way width, number of lanes, paved and total shoulder width, median type, and other variables. Traffic information in the form of Average Annual Daily Traffic (AADT) and Daily Vehicle Miles of travel is included for each section. As will be noted below, unlike most other HSIS State inventories, this file also contains information on terrain, design speed, and special features such as auxiliary lanes. There is no horizontal or vertical alignment information in the files.

Although intersections were included as part of the basic TASAS roadway inventory record, a separate Intersection File has been created in the HSIS system. Each record in the file contains information on both the mainline route and the crossing route. The information includes such items as intersection type, traffic control type, lighting, channelization, and AADT for both the mainline and cross street.

In similar fashion, an Interchange Ramp File has been developed that contains information on approximately 14,500 individual ramps. Although there is no way to tie these ramps to one of the approximately 3,000 associated interchanges in the State, the file does contain information on ramp type (e.g., diamond, slip, direct left-turn connector, etc.), AADT, and whether the crossing road is a State route or not.

DETAILS OF MAJOR FILES

The Accident Files

The State agency responsible for statewide accident data collection is the California Highway Patrol (CHP). The CHP is responsible for investigating crashes on all freeways (urban and rural) and on other State routes and county roads outside municipal areas. It is also responsible for the collection and computerization of crash data from all investigating agencies in the State. The CHP investigates approximately two-thirds of all accidents occurring on State routes. The remainder is reported by municipal police. The general accident reporting threshold used by the CHP is currently $500 or personal injury. This threshold is believed to be fairly consistently used by all CHP personnel in terms of filing crash reports. Conversations with the CHP indicated that when minor (non-towaway) crashes are reported, they are reported on a "short form." In approximately 50 percent of these minor cases, the officer will not provide information on uninjured passengers.

However, neither the report form used nor the reporting threshold followed is consistent across the many local municipalities in the State. Unlike the other HSIS States, accident data are not collected statewide by all police departments on a standard form. While some municipalities use the standard CHP form, some have developed their own form. However, since 1995, both Los Angeles and San Diego have converted to the standard CHP form. Indeed, all major cities are now using this standard form, and CHP is continuing to “recruit” other cities to use the form. Even for cities that use non-CHP forms, their data are "converted" to CHP format by accident coders to the extent possible. They are ultimately key-punched into the CHP's data system, known as SWITRS (Statewide Integrated Traffic Records System).

In addition to differing forms, it also appears that different municipalities follow different reporting thresholds, with some reporting only towaway crashes, many reporting crashes with damage of greater than $1,000, and some not reporting property-damage-only (PDO) crashes at all.

Some information on the level of PDO reporting can be gleaned from CHP's "Annual Report of Fatal and Injury Motor Vehicle Traffic Accidents." This publication, available at the FHWA HSIS office, provides a city-by-city breakdown of fatal, injury, and PDO crashes reported.  In general, if reported to a moderately low threshold, 55 to 70 percent of the total crashes should be no-injury (PDO) crashes. Cities that don't show such a ratio are more than likely not fully reporting these non-injury crashes. Thus, in general, while injury and fatal data are felt to be accurate for both the CHP and most municipalities, PDO crashes (and thus total crashes) are most accurate for the Highway Patrol. Crashes investigated by the Patrol can be identified by using the variable CHP_IND. In terms of rate development, this means that rates developed for freeways (urban and rural) and for other rural roads (outside municipalities) where accidents are reported by the CHP would be accurate. Total accident rates developed for urban areas should be considered somewhat suspect, or the analyst must determine which cities should be included in the rate on the basis of reporting ratios or other information.

It is estimated that there are more than 400,000 accidents in the entire State each year. Approximately 150,000 of these are investigated by the CHP on State routes (where TASAS inventory information is available). As noted above, all forms (regardless of form type) are sent to the CHP for processing. The CHP then separates the forms into those occurring on State routes (including the urban areas using their own forms) and those on non-State routes, and sends the State route hard copies to the TO Office for location coding. Of the 400,000 total accidents that occur each year, approximately 150,000 occur on the State system and are location-coded by TO.

The location coding is done by coding staff using maps, straight line diagrams, reference marker location logs, and other aids. In addition to the standard coding done by other States, all accidents that occur on interchange ramps are located to the specific interchange ramp on which they occur. (See specifics under later discussion of "Interchange Ramps.")

The mile-posting of all accidents is based on the investigating officer's location-related information and on his/her narrative and sketch. Each officer is instructed to provide a distance to a reference point measured in 0.01 miles in rural areas or feet in urban areas. Unlike other States, the officer attempts to give distances to reference markers in both directions from the point of the crash. All routes on the State system (Interstate, U.S., and State numbered highways) have both regularly spaced reference markers as well as markers on many different objects along the roadway (e.g., bridges, culverts, boundary signs).

In summary, given the reference markers, locations procedures, and coding procedures used, it is believed that the location coding for the 150,000 State-route accidents per year is probably as accurate as would be found in any State in the United States, with more than 90 percent of the urban and rural accidents being located to within 0.01 miles. TO staff estimate that there are problems in location provided by the officers in less than 2 percent of the accidents that the staff codes. These are sent back to the police officers for correction.

In addition to the location coding, the TO staff also coded additional variables related to fixed objects struck (up to four in sequence), location of collision by lane, and movement and direction of travel prior to collision. These codes are then returned to the CHP along with the location codes and hard copies.

All codes are then keypunched by the CHP and entered into SWITRS. Once keypunched and entered, the complete computer file is sent back to the TO Office for its use.  The complete annual file is "closed out" around April of the following year.

The TASAS system retains up to 10 years of accident data. The HSIS system currently contains accident data for 1991-2011.

The Accident Subfile contains more than 40 variables and approximately 150,000 crash records per year. It contains basic variables describing the overall crash (i.e., time and location, weather, lighting, collision severity, accident type, etc.). The file does not include a “first harmful event” variable or a “most harmful event.” It also does not contain speed limit or vehicle damage or point of contact. More specific variables related to contributing factors, object struck, and vehicle movements are included in the Vehicle Subfile.

Although the Accident Subfile does not contain a “sequence of events” variable, the Vehicle Subfile does contain a type of sequence for fixed-object impacts. Here, the CHP coders enter up to four fixed-objects (and their locations) in the order they are struck. One of the fixed-object codes is "rollover," which will allow meaningful analysis of roadside hardware and fixed-object impacts.

The Vehicle Subfile contains more than 30 variables and approximately 301,000 vehicle records per year. It contains information on up to nine vehicles in the crash. (If more than nine vehicles are in a crash, the additional vehicles are captured in separate accident records that are exactly like the initial record, but 1 second later.)  In addition to the fixed-object sequence, the file contains specific information on vehicle type, an indication of “direction of travel,” contributing factors, vehicle maneuvers and pedestrian locations prior to the crash, and the number of injured and killed occupants. As noted above, specific driver information related to injury, restraint use, sex, and physical condition/drug use are extracted from a separate CHP file and attached to this file. (It is noted that approximately 2 percent of the vehicles in the HSIS vehicle file cannot be matched with the supplemental information. This occurs because the TO staff manually enters some city reports and some late CHP reports that are not included in the SWITRS file.) The truck information on the file contains some detail on the basic configuration - whether van or tanker and how many trailers are being pulled. The National Governor’s Association (NGA) truck-crash elements are not on the report form or the file, but are now collected by the CHP (not cities) on a supplementary form. These data are submitted to the U.S. DOT’s Federal Motor Carriers Safety Administration for its use. (While these data are not part of HSIS, it might be possible to link them with the standard accident report form, and thus to roadway inventory and traffic information, by matching time/date/location items of the supplemental forms.)

The HSIS Occupant Subfile contains information on up to 70 occupants per crash.  As noted above, it is not part of TASAS, but is extracted from the CHP file. It contains information on occupant type, sex, age, seating position, injury class, safety equipment use, and ejection for approximately 178,000 occupants per year. Of these, approximately 127,000 are injured and uninjured passengers. However, as noted above, information on uninjured passengers is not captured in approximately 50 percent of the minor (non-towaway) crashes. If one passenger is injured, data is captured on all other passengers whether injured or not. Thus, the file is biased to some extent toward more serious (injury-producing) crashes. The remaining 51,000 records concern injured (but not uninjured) drivers. Information on uninjured (and injured) drivers is found in the Vehicle Subfile.

To assess the accuracy of accident variables, we questioned the California DOT TO staff concerning their feelings of variables that were incompletely coded or might be inaccurate, and we examined a series of single-variable tables for key variables in each of the subfiles. The TO staff indicated that virtually all variables on the Accident and Vehicle Subfiles seem to be coded correctly, especially by the CHP. (They do not use the occupant data in the CHP files, and thus have no knowledge of its accuracy.)  They do feel that the information concerning whether an accident occurred in a construction zone (which is part of a "road condition" variable) is less than accurate. (On the basis of a recent HSIS staff analysis of work zone accident data in other HSIS and non-HSIS States, this problem is common across almost all States.)

In addition to information received from the TO staff, single-variable tabulations were run to examine the questions of reporting completeness and data accuracy for these accident subfiles. Here, study of percentage of "unknown," "not applicable," and "not stated" values for more than 50 key variables indicates that, in general, the data in the Accident and Vehicle Subfiles are coded to a high degree of completeness. With very few exceptions, these data also appear to be quite consistent across years, and similar variables appear to have similar values. The exceptions are noted under pertinent variables in the later format section.

As noted above, the major exception to this is in terms of completeness and accuracy of the Occupant Subfile data. First, the file contains data that are biased to some extent toward the more severe accidents, since some significant proportion of the uninjured occupants in non-towaway, PDO crashes do not get entered into the file. Second, there are some differences in the type/seating of occupants between the two variables related to OCC_TYP (Occupant Type) and SEATPOS (Seating Position). This is due to the fact that the Occupant Type variable combines all uninjured occupants into one code, and that while report forms used by California cities all contain some type of information on drivers, all do not contain a variable on seating position. It is again noted that the most complete information on drivers can be found in the Vehicle Subfile. Other data issues are noted with the specific variable in the later format section. Except for these Occupant Subfile problems, on the basis of both the interviews and the data comparisons conducted, the majority of the data appear quite accurate.

The Roadlog File

The California roadway inventory system, taken directly from TASAS, contains current characteristics of the State road system. It is divided into three files within the HSIS system. The first is basic roadway characteristics file (i.e., the Roadlog") containing information on the roadway mainline cross section. The second is an Intersection File, which contains information on the characteristics of approximately 17,500 intersections and their approach roadways. The third is an Interchange Ramp File, describing the basic characteristics of more than 14,500 separate ramps of interchanges.

All three inventory files were developed from inventory information originally collected through a series of field surveys and from construction drawings. Updates to the file are now done on a routine basis by the TO inventory staff based on new construction drawings. The only updates that would be missed by the TO staff are new intersections built at the district level when new development (e.g., a shopping center) occurs. These are sometimes reported by the district office and sometimes not. Often, during accident plotting procedures, these come to the attention of the TO staff, who then request information from the district office.  In general however, the Operations staff feels that the inventory information is quite accurate.

As shown in Table 1 below, the basic Roadlog File contains information on approximately 15,500 miles of mainline (non-ramp) roadway. This includes all functional classes of roads within the State system - Interstate, U.S., and State routes. This file contains information on approximately 2,450 miles of Interstate, 11,000 miles of other primary highway, and 1,700 miles of secondary/county/township roads. California has a higher proportion of freeway mileage than do the other HSIS States, particularly urban freeway. Currently, there are 17 roadway inventory files in the HSIS system, 1993-2002 and 2005-2011. Because a new record is generated each time any of the items in the file changes, the sections that are generated are fairly short, resulting in a large number of individual records. The approximately 15,500 miles of basic inventory information is divided into approximately 50,000 records, resulting in an average section length of 0.3 miles.

The file contains information on route descriptors (including functional class) and general terrain, and cross-section information related to traveled way width, number of lanes, paved and total shoulder width, median type, and other variables. Unlike most State inventories, it also contains information on design speed, special features such as auxiliary lanes, and detailed information on median barriers. The original TASAS file does not contain specific information on the type of shoulder (e.g., earth, sod, gravel, paved). However, California staff note that two variables related to total shoulder width and treated shoulder width can be used to infer whether part or all of a shoulder is paved. 

Table 1. HSIS roadway mileage by roadway category (2011 data).

Roadway Category Mileage
Urban freeways 2376.05
Urban freeways < 4 Lanes 42.70
Urban multilane divided non-freeways 669.56
Urban multilane undivided non-freeways 104.35
Urban 2 lane highways 526.08
Rural freeways 1880.96
Rural freeways < 4 Ins 103.82
Rural multilane divided non-freeways 844.70
Rural multilane undivided non-freeways 292.11
Rural 2 lane highways 8336.10
Other 251.68
Total 15428.12

The original TASAS file contains groups of variables for "right roadbed" and "left roadbed." Since the definition of each type of roadbed can change depending on whether or not the roadway is divided, the data have been converted to more standard HSIS definitions. After conversion (and as in other HSIS States), "Road 1" is either the full roadway for undivided sections, or the right-hand roadway in the direction of inventory for divided sections. "Road 2" only exists for divided roadways, and is the left-hand roadway in the direction of inventory.

There are a few variables that were left in the original "roadbed" format (e.g., right and left roadbed "special features"). These are noted in the format section of this Guidebook.

Traffic information in the form of Average Daily Traffic is included for each section, along with Daily Vehicle Miles of travel. Truck percentages are not included in the basic inventory file. However, for 1996 and later, TO staff responsible for traffic counts have published truck counts and percentages on the web.  HSIS staff have extracted these data and added them to the Roadlog File for each roadway section where possible. A detailed description of the basis for these traffic variables is included below in “Traffic Information in the Roadway Inventory Files.”

Finally, unlike most States, the California Roadlog File contains some information concerning changes that occurred to the roadway elements. With some programming, this should allow "before/after" analysis for specific roadway changes. Unlike the Washington State HSIS file, this is not a "date of last change" for each variable. Instead, using a "history indicator" flag and an "effective date" variable, one can determine whether a change has occurred since the preceding year within a group of variables. These flag and date variables exist for groups of variables related to the access control, AADT, median, right roadbed, and left roadbed. To determine the specific variable that changed, and the change in that variable, one must compare the current group of variables with the same group in the preceding year's file. (As noted in the format section under these flag and date variables, this is somewhat difficult to do since the roadbed designations for most variables except for these "history" variables have now been converted to the more conventional “Road 1/Road 2” definitions.) It is also noted that both the history indicator and the effective-date variable must be used in identifying changes. The history indicator variable will remain “on” after the first change, and thus will not indicate whether a subsequent change has occurred.  However, the effective date will indicate when the current roadway characteristics became "open to traffic."

To assess the accuracy of roadway inventory variables in this Roadlog File and the related files concerning intersections and ramps, we again questioned the California DOT TO staff and examined a series of single-variable tables for key variables in each of the files. The TO staff feel that the overall quality of the variables in all three files is very high. As noted above, the information in the files is updated in an ongoing effort based on construction plans and maintenance effort reports.

In addition to information received from the TO staff, single-variable tabulations were run to examine the questions of reporting completeness and data accuracy. Here, study of percentage of “unknown,” “not applicable,” and “not stated” values for more than 40 key variables in the Roadlog File indicate that, in general, the data are coded to a high degree of completeness. For most variables, there was no missing data. The data also appear to be quite consistent across years, and similar variables appear to have similar values.

In general, from the interviews and the data comparisons conducted, the data appear quite accurate. In the limited number of cases where possible inaccuracies were found or where more detailed definitions might be critical in future analyses, they are noted in the later formats section under the specific variables.

Two new variables, RODWYCLS and MVMT, have been created by HSIS staff in the roadway segment file of each of the HSIS States. For California, both are included in the ROADLOG File, and RODWYCLS is also included in the Accident File. 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 10 roadway types described in the later “Format” section. The MVMT variable (Million Vehicle Miles of Travel) is calculated for each segment in the roadway file by multiplying the segment length, AADT and 365 days in a year, and dividing by one million. Both these variables were created in response to inquiries from data users, whose most frequent questions have concerned either crash frequencies or rates (per MVMT) for one or more of these roadway classes. Frequency distributions of selected crash variables by RODWYCLS for the latest year of the data are also included in Volume II of each State’s Guidebook.

The Intersection File

As noted earlier, intersection-related information for approximately 17,500 intersections. Prior to 2003, this information was extracted from the TASAS roadway inventory file by the HSIS staff and placed in a separate HSIS Intersection File.  Beginning in 2003, a separate intersection has been received from CADOT.This file contains more detail on intersections than do most State inventory files, describing both the mainline route and the intersecting route.  Unlike intersection files from other States, which contain "conventional" intersections where two major roads cross each other, California intersection data includes both these conventional intersections plus other non-standard "intersections" such as junctions at campgrounds, parks, forest service roads, etc. A new variable called JUNCTYPE has been created based on the intersection description and the traffic control device variables to more clearly define the different intersection types in the file (See "Intersection Format" section.)  JUNCTYPE equal to 1' would restrict the data to the more conventional intersections.

In the development of this file prior to 2003, the original TASAS roadway record was used to generate an intersection record each time a State route crosses either a State or non-State route. Thus, during the development process, two (duplicate) records would be generated each time two State routes crossed. (Only one record would be generated when a State route crossed a non- State route since the non- State route would not be inventoried in the roadway file.) A given State route would appear as "mainline" in one of these records, and as "intersecting street" in the second record. To reduce computer storage requirements, the original TASAS file only carries the full set of intersection variables on the record with the lower route number. For example, for an intersection of US 100 with California State Route 2, the data would be retained on the record in which CA 2 was the mainline. The higher number route record would only contain reference data pointing to the other record. For ease of use in the HSIS file, these higher-numbered route records have been deleted from the file.

The intersecting route can still be matched with other files since the location (milepost) information is retained on the intersection record, along with the mainline location information. For each intersection record, specific inventory variables for the mainline include variables related to intersection type, whether the mainline is divided or undivided, traffic control type (with information on whether the signals are semi-actuated or fixed time), intersection lighting, presence of signal mastarm, the presence of left-turn channelization, the presence of right-turn channelization, the type of traffic flow (e.g., two way versus one way with left turns permitted or not permitted), the number of through lanes, and the mainline AADT. It is noted that the channelization and traffic flow information is in the record only once for the mainline (and once for the intersecting street), meaning that the incoming and outgoing legs of each roadway are assumed identical with respect to these variables. In addition to the general information and the information on the mainline legs, cross-street variables include information on the traffic signal mastarms, left and right turn channelization, type of traffic flow, AADT and the number of through lanes.

Finally, as with inventory variables on the Roadlog File, there are a series of "history" and "effective date" variables that will help the analyst determine whether a change has occurred to the intersection in the past year. There are separate history variables for the entire intersection, traffic control, and lighting, and separate history variables for mainline and cross street AADT, and for the groups of variables describing the mainline and cross street (including channelization, mastarm, and traffic flow type).  Again, as discussed above, both variables must be used in determining when a change has occurred.

In terms of data accuracy and completeness, examination of tables for the 20 key variables in the file indicates very little missing data (i.e., less than 4 percent for any variable, and no missing data for most variables).  With the exception of the cross-street AADT variable (a very important variable), the values for all variables appear logical, and no problems were indicated by California TO staff.

Examinations of the data and conversations with California DOT staff indicate that most of the cross-street AADT values have not been updated for some time. Approximately two percent of the intersections (i.e., approximately 300 intersections) have cross streets which are state routes (see XSTSTRT). It appears that cross-street AADTs for this subset of intersections are updated annually.   However, the cross-street AADTs for roads which are not on state routes have not been updated for many years.  It is not possible to tell the AADT year after 2002 since the cross-street AADT date variable was discontinued in 2003.  Analysis of pre-2003 data shows that only approximately two percent of the intersections have cross-street AADTs that is the same as the file year.  (These are likely the state route intersections.) Examination of the cross-street AADT dates in 2002 indicates that the AADT years for the cross-streets are 1980 and earlier for over 66% of the intersections.  There is little indication that the cross-street AADTs were updated after 2002 except for the small number of intersections that have cross-streets that are on state routes.  In short, the user should consider carefully whether these AADTs are of suitable quality for the analysis being conducted.

The Interchange Ramp File

As with the intersection data, information on approximately 14,500 ramps is extracted from the TASAS roadway inventory file and placed in a separate HSIS Interchange Ramp File. It is noted there is no “unifying number” that would allow one to group ramps that would be in the same interchange. Thus, an analysis can be done on a ramp basis rather than interchange basis. It is estimated that these 14,500 ramps represent approximately 3,000 interchanges statewide.

Specific variables on the file include the general type of ramp (on or off ), the basic ramp design (e.g., diamond, direct, slip, loop, etc.), the AADT on the ramp, whether a median is present on the roadway where the ramp begins, and whether the crossroad on which the ramp terminates is a State or non-State ("area 4") route. Again, a separate pair of history variables is present for both the general descriptive information and for the AADT information.

For reference purposes, only one milepost is provided for each ramp (i.e., not “begin” and “end” mileposts as provided for non-ramp highway segments). This ramp milepost is the same as the mainline milepost at the “nose” of the ramp - the point where the ramp joins the mainline highway. Thus, for exit-ramps, it is the upstream end of the ramp (where the ramp leaves the freeway), and for entrance-ramps, it is the point where the ramp joins the freeway. Coding of crashes to ramps will be discussed in the later sections concerning “File Linkage.”

In terms of completeness and accuracy, examination of tables for the five key variables in the file indicates missing data in less than 1 percent of the records. Values appear logical, and no problems were indicated by California TO staff.

Traffic Information in the Roadway Inventory Files

AADT data: As indicated in the preceding three sections, all three inventory files contain AADT information. In addition, the Roadlog File contains information on Daily Vehicle Miles, which is computed as the product of the section length and section AADT estimate. As described at the end of this section, truck count data have been added to the files beginning with the 1996 data.

In California, the 12 district offices have the responsibility of collecting traffic data and developing the AADT estimates for each road section within their district. Traffic Operations (TO), in the CALTRANS central office, oversees the operation and attempts to maintain consistency in the methods and data across all districts as much as possible. If requested, TO personnel will assist a district in calculating the AADT estimates.  TO also maintains all count data on an on-line computer file for the districts' use.

There are approximately 4,000 permanent count stations on mainline highways operated by CALTRANS in California. Of these, approximately 800 are permanent, continuous counting control stations that operate continuously each day in a given year. Every major State-administered route is counted each year. The 800 permanent continuous count stations form a network that covers all major routes. The remaining control stations are permanent, quarterly counting control stations, i.e., in-pavement loops to which a counter/recorder device is attached for 7 to 14 days during each quarter. CALTRANS also collects count data at approximately 400 of these quarterly counting control stations once every 3 years. California has determined that the AADT estimates that are derived from the simple average of the four (unadjusted) quarterly counts do indeed account for seasonal fluctuations without further adjustment based on nearby permanent counters. Consequently, there are no additional adjustments or corrections applied to the AADTs estimated from the quarterly counts.

In addition to the permanent control stations, approximately 600 profile counts are collected annually. The intent is to collect profile counts on a 3-year cycle (for a total of approximately 1,800 coverage counts), although conditions may force longer intervals in certain districts at times. A coverage count is basically a 24-hour to 1-week count.

Profile counts are expanded to AADT estimates using factors derived from the combined continuous counts and quarterly count data. For road sections that are not counted in a given year, it is the responsibility of the districts to develop these AADT estimates. In some cases, the districts rely on overall traffic growth trends within the district. However, in most cases, the AADT assigned to the section is developed by studying the traffic growth in counts falling on each side of the section.

It is also noted that 24-hour to 1-week coverage counts are collected on approximately 3000 on- and off-ramps per year. These ramp counts are manipulated through ramp balancing to reflect continuity of flow on mainline freeways. A detailed description of the data can be found at the CALTRANS web site at http://www.dot.ca.gov/hq/traffops/saferesr/trafdata/index.htm.

Finally, “15-bin” vehicle classification data are collected at approximately 200 permanent stations and 120 weigh-in-motion stations across the State. Additional classification counts are collected on an as-requested basis, typically at locations where traffic count data are being collected. Since this is district-based, there is no reliable estimate on how many additional classification counts are collected across all 12 districts per year. Some of the 120weigh-in-motion stations also provide speed data.

Truck count data:  As noted above, CALTRANS TO staff responsible for traffic counts have published truck counts and percentages on the web. HSIS staff have extracted these data and added them to the Roadlog File for each roadway section where possible. A detailed description of the data can be found at the CALTRANS web site at
http://www.dot.ca.gov/hq/traffops/saferesr/trafdata/index.htm.

Truck counting is done throughout the State in a program of continuous truck count sampling. As noted above, these “15-bin” sample counts are conducted at 200 permanent stations and 120 weigh-in-motion stations. The sampling includes partial day, 24-hour, 7-day, and continuous vehicle classification counts. The partial day and 24-hour counts are usually made on high-volume, urban highways. The 7-day counts are made on low-volume, rural highways. The counts are usually taken only once in, and approximately one-sixth of the locations are counted annually. As indicated above, 120 locations were continuously monitored using weigh-in-motion equipment. The resulting counts are adjusted to an estimate of annual average daily truck traffic by compensating for seasonal influence, weekly variation, and other variables that may be present. It is noted that at many of the count locations, which are often intersections of major routes, two counts would be made - one on the upstream and one on the downstream side of the intersection (in the direction of roadway inventory).

For each count location, the data include a “Verification/Estimation Year” when there is either an actual count, or some other information that provides what TO staff consider to be an accurate estimate of truck counts.  In years between these actual counts or “estimates,” the truck data at a given station are adjusted based on changes in total AADT - i.e., the truck counts are changed proportional to changes in AADT for that location.

Because there are only limited locations where truck count data are actually collected, in order to provide truck information for each of the large number of highway segments in the HSIS California Roadlog File, these point counts had to be extrapolated to other roadway segments. Based on conversation with TO staff, the most logical manner of extrapolation was to “carry- forward” a set of truck counts on a route (from lower to higher mileposts) across all Roadlog sections until a section containing a new count station is reached. That new count is then carried forward to the Roadlog section on that route containing the next count station, etc. As noted above, since both a “before-intersection” and an “after-intersection” truck count is often made, the bias in this extrapolation is that the “after-intersection” counts will be applied to more Roadlog sections than the “before-intersection” counts. The latter may only be applied to one section, since the count may then be changed by the “after-intersection” count at the same location. While we know this is a bias, the TO staff indicated that they did not know of a more unbiased method for the extrapolation. In some limited cases, there are multiple counts within the same Roadlog section. These counts are averaged for that section, but the final (downstream) count is the one “carried forward.”

As expected, this limited number of count locations did not cover all routes or all sections on every route (e.g., sections prior to the initial count on a route contain no truck information). However, using the “carry forward” extrapolation method, truck data have now been attached to approximately 90 percent of the Roadlog mileage.

As is seen in the later “Format” section of this Guidebook, truck count variables attached to the Roadlog segments include total truck counts, counts for trucks with two axles (and dual rear tires), three axles, four axles, and trucks with five or more axles. In addition, a “flag” variable has been attached that defines the Roadlog sections where actual counts/verified estimates are made. For the researcher who wishes to work with the original web-based data, HSIS staff are retaining a separate file that can link each of the “flagged sections” with the original web-based information concerning the base-year in which a count (or verified estimate) was made, and whether the data in that year was a count or a verified estimate. Contact the HSIS staff for more details of this file and file linkage procedures.

In summary, as in other States, the truck count data in California are relatively limited, and significant extrapolation is necessary to provide estimates of data for a large sample of Roadlog sections. Truck volumes on “non-count” years are allowed to vary with changes in total AADT, which may or may not be a good assumption (but no other assumption appears more rational). However, unlike other States, the data provided are more than just a total “truck percentage” - they represent estimates of counts for various axle combinations.

Issues Related to Developing and Merging Files

As noted above, the accident data are subdivided into three subfiles - accident, vehicle, and occupant. The Accident and Vehicle Subfiles can be linked together using the accident report number (i.e., CASENO).  When linking the occupant subfile, the additional linking variable related to vehicle number (i.e., VEHNO) must match so that the occupants are associated with the vehicle in which they were traveling. To link vehicles with accidents, first sort both subfiles by CASENO. To link the Occupant file with the other two subfiles, first sort both the Vehicle subfile and Occupant subfile by case number and vehicle number. Next sort the Accident subfile by case number. Alternatively, the separate subfiles can be linked by specifying 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 pre-sorted and the output will not be in any particular sort order unless ORDER BY is specified.

The Accident Subfile can be linked to the Roadlog File using the CNTY_RTE and MILEPOST variables in the crash record, and the CNTYRTE, BEGMP, and ENDMP variables in the Roadlog File. Similarly, the Accident Subfiles can be linked to Intersection and Interchange Ramp Files using the two variables related to county/route (i.e., CNTY_RTE in the Accident Subfiles or CNTYRTE in the Interchange Ramp files) and MILEPOST. If the researcher is only interested in “mainline” crashes (i.e. non-ramp/non-intersection crashes), then INT_RMP variable should be screened for “Mainline Crashes” before matching with the roadway segment.

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 CNTY_RTE and MILEPOST on the Accident file and by CNTYRTE and BEGMP on the Roadlog File. Similar sorts would be done with other files to be merged. For the alternative SQL join, the analyst must specify an exact match on CNTYRTE and a range match where MILEPOST occurs between BEGMP and ENDMP. (Programs to accomplish this merging and division are available from HSIS staff at FHWA.)

The ramp accidents (INT_RMP = ‘1’, ‘2’, ‘3’, ‘4’) can be linked to the ramp file by CNTY_RTE and MILEPOST of the accidents and CNTYRTE and MILEPOST of the ramps. Each of the ramp accidents will have the same milepost as the ramp. (As described above, this milepost actually represents the nose of the ramp, but all accidents occurring on the ramp will be given that same milepost.) If an accident occurs in the speed change lane prior to the gore area, it is coded to the mainline rather than the ramp. If after the gore and prior to the ramp terminal, it is coded to the ramp. If the ramp terminal is an intersection (as in a diamond interchange), and the accident occurs in the crossroad/ramp intersection or is near enough to be judged as being affected by the ramp terminal (usually 46m [150 ft]), there are two different ways of locating the crash depending on the type of crossroad.  If the crossroad is a State route, then the crash is coded to the State route. If, on the other hand, the crossroad is non-State route, the accident is coded to the ramp, but is designated in the accident file under INT_RMP ("Intersection/Ramp accident location") to be a "ramp area, intersecting street" location. This is referred to as "area 4" by California staff. As noted above, there is also a code on the Interchange Ramp File defining whether an "area 4" exists for a given ramp (i.e., whether the crossroad is a non-State route.) For non-State routes, "area 4" would also include any crashes occurring between the two ramp terminals (i.e., on or near the overpass).

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

Composite List of Elements

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
AADT AADT Road NUM 94
ACC_DATE DATE OF ACCIDENT -YMD Accident CHA(8) 31
ACC_DTE ACCESS CONTROL DATE Road CHA(8) 94
ACC_HIST ACCESS CONTROL HISTORY Road CHA(1) 94
ACCESS ACCESS CONTROL Road CHA(1) 95
ACCTYPE TYPE-OF-COLLISION Accident CHA(1) 31
ACCYR COLLISION ACCYR Accident CHA(4) 31
ACCYR COLLISION ACCYR Occupant CHA(4) 85
ACCYR COLLISION ACCYR Vehicle CHA(4) 59
ADT_DTE ADT DATE Road CHA(8) 95
ADT_DVM DAILY VEHICLE MILES(DVM) Road NUM 95
ADT_HST ADT HISTORY Road CHA(1) 95
ADT_MSG ALPHA MESSAGE Road CHA(4) 95
ADT_STUS ADT STATUS PROFILE Road CHA(1) 96
AGE OCCUPANT AGE Occupant NUM 85
ALCH_FLG ALCOHOL INVOLVED Accident CHA(1) 31
AREA4 RAMP AREA 4 INDICATOR Ramp CHA(1) 139
BEGMP POSTMILE-BEGMP Road NUM 96
BELT1 BELT USAGE Vehicle CHA(1) 59
BIKE_FLG BICYCLE INVOLVED Accident CHA(1) 32
CASENO UNIQUE ACCIDENT CASEO Accident CHA(21) 32
CASENO UNIQUE ACCIDENT CASEO Occupant CHA(21) 85
CASENO UNIQUE ACCIDENT CASEO Vehicle CHA(21) 60
CAUSE CONTRIBUTION FACTOR Vehicle CHA(1) 60
CAUSE1 PRIMARY COLL FACTOR Accident CHA(1) 32
CAUSHPAL COLL FACTOR ALPHA (CHP) Accident CHA(1) 33
CAUSHPCD COLL FACTOR CODING (CHP) Accident CHA(5) 33
CAUSHPCT COLL FACTOR CATEGORY (CHP) Accident CHA(2) 34
CAUSHPLG COLL FACTOR LEGAL CODE(CHP) Accident CHA(1) 35
CAUSHPSB COLL FACTOR CODE SUBSECTION (CHP) Accident CHA(1) 35
CELPHONE CELL PHONE Vehicle CHA(1) 60
CITY CITY Road CHA(2) 96
CITY_CODE CITY CODE Intersection CHA(4) 122
CITY_CODE CITY CODE Ramp CHA(4) 139
CNTY_RTE COUNTY ROUTE Accident CHA(10) 35
CNTYRTE INTERSECTION COUNTY ROUTE Intersection CHA(9) 122
CNTYRTE ROAD COUNTY ROUTE Road CHA(10) 96
CONTRIB1 FIRST ASSOCIATED FACTOR Vehicle CHA(1) 61
CONTRIB2 SECOND ASSOCIATED FACTOR Vehicle CHA(1) 61
COUNTY COUNTY Accident CHA(2) 36
COUNTY COUNTY Intersection CHA(2) 122
COUNTY COUNTY Ramp CHA(2) 139
COUNTY COUNTY Road CHA(2) 96
CURB1 CURB AND LANDSCAPE Road CHA(1) 97
DEFECT VEHICLE DEFECT Vehicle CHA(1) 62
DES_NBR ROAD DESC NUMBER Road CHA(1) 97
DESG_SPD DESIGN SPEED Road CHA(1) 97
DIR_CODE DIRECTION Ramp CHA(1) 140
DIR_TRVL DIRECTION OF TRAVEL Vehicle CHA(1) 62
DISTANCE DISTANCE Accident CHA(5) 37
DISTRICT DISTRICT Accident CHA(2) 38
DISTRICT DISTRICT Intersection CHA(2) 122
DISTRICT DISTRICT Ramp CHA(2) 140
DISTRICT DISTRICT Road CHA(2) 98
DIVIDED DIVIDED HIGHWAY Road NUM 98
DRV_AGE DRIVER AGE Vehicle NUM 63
DRV_INJ DRIVER EXTENT OF INJURY Vehicle CHA(1) 63
DRV_RACE DRIVER RACE Vehicle CHA(1) 64
DRV_SEX DRIVER SEX Vehicle CHA(1) 64
DRVREST1 DRIVER SAFETY EQUIPMENT Vehicle CHA(1) 65
DRVREST2 DRIVER SAFETY EQUIPMENT Vehicle CHA(1) 65
EJECT EJECTED FROM VEHICLE Occupant CHA(1) 86
ENDMP POSTMILE + SEG_LNG Road NUM 98
FEAT_LF LEFT RDBD SPECIAL FEATURE Road CHA(1) 99
FEAT_RG RIGHT RDBD SPECIAL FEATURE Road CHA(1) 99
FED_AID FEDERAL AID (IN LIEU) Road CHA(1) 100
FED_PREF FEDERAL AID RTE PREFIX Road CHA(1) 100
FED_RTE FEDERAL AID RTE Road CHA(3) 100
FILETYP FILE TYPE Accident CHA(1) 38
FILETYP FILE TYPE Road CHA(1) 101
FIRE VEH FUEL LEAKS AND FIRES Vehicle CHA(1) 66
FUNC_CLS FUNCTIONAL CLASS Road CHA(1) 101
HAZ_CODE HAZARDOUS MATERIAL Vehicle CHA(1) 66
HAZMAT HAZARDOUS MATERIAL Vehicle CHA(1) 66
HIST_ADD HISTORY ELEMENTS RELATIVE ADDR Road NUM 101
HIT_RUN HIT AND RUN Accident CHA(1) 38
HOUR TIME OF ACCIDENT Accident CHA(4) 39
HWY_GRP HIGHWAY GROUP Accident CHA(1) 40
HWY_GRP HIGHWAY GROUP Intersection CHA(1) 123
HWY_GRP HIGHWAY GROUP Ramp CHA(1) 141
HWY_GRP HIGHWAY GROUP Road CHA(1) 102
INJ DRV/OCC INJURY Occupant CHA(1) 86
INS_OTS INSIDE OUTSIDE CITY Road CHA(1) 102
INSUR INSURANCE Vehicle CHA(1) 67
INT_ADDR HISTORY ELEMENTS RELATIVE Intersection NUM 123
INT_DESC INTERSECTION DESCRIPTION Intersection CHA(23) 123
INT_DTE INTERSECTION EFFECTIVE DATE Intersection CHA(6) 123
INT_HST INTERSECTION TYPE HISTORY Intersection CHA(1) 124
INT_PRF INTERSECTING RTE PREFIX Intersection CHA(1) 124
INT_POPGRP INTERSECTION POPULATION Intersection CHA(1) 124
INT_RMP INTS/RAMP ACC LOCATION Accident CHA(1) 40
INT_RSUF INTERSECTING RTE SUFFIX Intersection CHA(1) 124
INT_RTE INTERSECTING RTE NBR Intersection CHA(3) 124
INT_SEQ INTERSECTING RTE ORDER SEQ Intersection NUM 124
INTER INTERSECTION CRASH Accident CHA(1) 41
INTMP INTERSECTION MILEPOST Intersection NUM(8) 125
INTY_RTE CROSS STREET COUNTY ROUTE Intersection CHA(9) 125
JUNCTYPE JUNCTION TYPE Intersection CHA(1) 125
JUR_TYPE JURISDICTION TYPE Accident CHA(1) 41
LANEWID AVERAGE LANE WIDTH Road NUM 103
LGHT_DTE INTERSECTION LIGHT TYPE DATE Intersection CHA(6) 125
LGHT_HST INTERSECTION LIGHT TYPE HISTORY Intersection CHA(1) 125
LGHT_TYP INTERSECTION LIGHT TYPE Intersection CHA(1) 126
LIGHT LIGHT CONDITION Accident CHA(1) 41
LOC_TYP LOCATION TYPE Accident CHA(1) 42
LOC_TYP1 FIRST COLL LOCATION Vehicle CHA(1) 67
LOC_TYP2 SECOND COLL LOCATION Vehicle CHA(1) 67
LOC_TYP3 THIRD COLL LOCATION Vehicle CHA(1) 67
LOC_TYP4 FOURTH COLL LOCATION Vehicle CHA(1) 67
LOCATN COUNTY/CITY CODE WHERE CRASH OCCURRED Accident CHA(4) 42
LOG_ERR LOG ERROR INDICATOR Intersection CHA(1) 126
LSHL_WD2 LEFT SHOULDER WIDTH RD2 Road NUM 103
LSHLDWID LEFT SHOULDER WIDTH RD1 Road NUM 103
LST_SEG_CHG_DT DATE OF LAST CHANGE DATE Road NUM 103
LTRD_DTE LEFT ROADBED DATE Road CHA(8) 104
LTRD_HST LEFT ROADBED HISTORY Road CHA(1) 104
MAKE VEHICLE MAKE Vehicle CHA(2) 68
MAINT_LEVL MAINTENANCE LEVEL SERVICE Road CHA(1) 104
MED_DTE RAMP MEDIAN DATE Intersection CHA(6) 126
MED_DTE RAMP MEDIAN DATE Ramp CHA(8) 141
MED_DTE RAMP MEDIAN DATE Road CHA(8) 104
MED_HIST MEDIAN HISTORY Intersection CHA(1) 126
MED_HIST MEDIAN HISTORY Road CHA(1) 104
MED_HST RAMP MEDIAN HISTORY Ramp CHA(1) 141
MED_IND RAMP MEDIAN INDICATOR Intersection CHA(1) 127
MED_IND RAMP MEDIAN INDICATOR Ramp CHA(1) 142
MED_TYPE MEDIAN TYPE Road CHA(1) 105
MED_VAR MEDIAN VARIANCE Road CHA(1) 105
MEDBARTY MEDIAN BARRIER TYPE Road CHA(1) 106
MEDWID MEDIAN WIDTH Road NUM 107
MILEPOST RAMP MILEPOST Accident NUM 42
MILEPOST RAMP MILEPOST Intersection NUM 127
MILEPOST RAMP MILEPOST Ramp NUM 142
MISCACT1 MOVEMENT PRECEDING COLL Vehicle CHA(1) 69
ML_AADT MAINLINE AADT Intersection NUM 127
ML_ADTDT MAINLINE ADT DATE Intersection CHA(6) 128
ML_ADTHS MAINLINE ADT HISTORY Intersection CHA(1) 128
ML_DATE MAINLINE HISTORY DATE Intersection CHA(6) 128
ML_HIST MAINLINE HISTORY Intersection CHA(1) 128
ML_LANES MAINLINE NUMBER OF LANES Intersection CHA(1) 129
ML_LEFT MAINLINE LEFT TURN Intersection CHA(1) 129
ML_LNGT MAINLINE SECTION LENGTH Intersection CHA(3) 129
ML_MAST MAINLINE SIGNAL MASTARM Intersection CHA(1) 130
ML_RIGHT MAINLINE RIGHT TURN Intersection CHA(1) 130
ML_TRFLO MAINLINE TRAFFIC FLOW Intersection CHA(1) 130
MTCY_FLG MOTORCYCLE INVOLVED Accident CHA(1) 42
MVMT MILLION VEHICLE MILES Road NUM 107
NA_MILE NON-ADD MILEAGE Road CHA(1) 107
NAT_LND NATIONAL LANDS Road CHA(1) 108
NO_LANE1 NUMBER OF LANES RD1 Road NUM 108
NO_LANE2 NUMBER OF LANES RD2 Road NUM 108
NO_LANES TOTAL NUMBER OF LANES Road NUM 108
NUM_INJ TOTAL NUMBER INJURED Vehicle NUM 70
NUM_KILL TOTAL NUMBER KILLED Vehicle CHA(2) 70
NUM_OCCS OCCUPANTS Accident NUM 43
NUMVEHS TOT-NBR-VEHICLES Accident CHA(2) 43
OBJECT1 FIRST OBJECT STRUCK Vehicle CHA(2) 71
OBJECT2 SECOND OBJECT STRUCK Vehicle CHA(2) 71
OBJECT3 THIRD OBJECT STRUCK Vehicle CHA(2) 71
OBJECT4 FOURTH OBJECT STRUCK Vehicle CHA(2) 71
OCCNUM OCCUPANT NUMBER Occupant NUM 86
OCC_TYP OCCUPANT TYPE Occupant CHA(1) 87
ON_OFFRP ON/OFF RAMP INDICATOR Ramp CHA(1) 142
PART_TYP PARTY TYPE Vehicle CHA(1) 72
PAV_WDL LEFT PAVED SHLD WDTH RD1 Road NUM 109
PAV_WDL2 LEFT PAVED SHLD WIDTH RD2 Road NUM 109
PAV_WDR2 RIGHT PAVED SHLD WIDTH RD2 Road NUM 109
PAV_WIDR RIGHT PAVED SHLD WDTH RD1 Road NUM 109
PED_ACTN PEDESTRIAN ACTION Accident CHA(1) 44
PED_FLG PEDESTRIAN INVOLVED Accident CHA(1) 44
PHYSCOND DRIVER PHYSICAL CONDITION Vehicle CHA(1) 73
POP_GRP POPULATION GROUP = (CITY/RURAL GROUP) Accident CHA(1) 44
PSMILPRF POSTMILE PREFIX Accident CHA(1) 45
PSMILPRF POSTMILE PREFIX Intersection CHA(1) 131
PSMILPRF POSTMILE PREFIX Ramp CHA(1) 143
PSMILPRF POSTMILE PREFIX Road CHA(1) 110
PSMILSUF POSTMILE SUFFIX Accident CHA(1) 46
PSMILSUF POSTMILE SUFFIX Intersection CHA(1) 132
PSMILSUF POSTMILE SUFFIX Road CHA(1) 111
RAMP_TYP RAMP TYPE Ramp CHA(1) 144
RD_DATE ROAD DATE Road CHA(8) 111
RD_DEF1 ROADWAY CONDITION Accident CHA(1) 46
RD_DEF2 ROAD CONDITION 2 Accident CHA(1) 46
RD_DEF3 ROAD CONDITION 3 Accident CHA(1) 46
RD_DESC ROAD DESCRIPTION Road CHA(25) 111
RDSURF ROAD-SURFACE Accident CHA(1) 46
RECTYPE RECORD TYPE Intersection CHA(1) 132
RECTYPE RECORD TYPE Ramp CHA(1) 144
RECTYPE RECORD TYPE Road CHA(1) 111
REST1 SAFETY EQUIPMENT Occupant CHA(1) 88
REST2 SAFETY EQUIPMENT Occupant CHA(1) 88
RGRD_DTE RIGHT ROADBED DATE Road CHA(8) 111
RGRD_HSR RIGHT ROADBED HISTORY Road CHA(1) 112
RMADTDTE RAMP ADT DATE Ramp CHA(8) 144
RMADTHST RAMP ADT HISTORY Ramp CHA(1) 145
RMP_ADT RAMP AADT Ramp NUM 145
RMP_BEGMP RAMP BEGIN MILEPOST OFFSET Ramp NUM(8) 145
RMP_DTE RAMP TYPE DATE Ramp CHA(8) 145
RMP_HST RAMP HISTORY Ramp CHA(1) 146
RMP_POPGRP RAMP POPULATION CODE Ramp NUM 146
RMP_SEQ RAMP SEQUENCE NUMBER Ramp NUM 146
RMP_TYPE RAMP TYPE Ramp CHA(1) 147
RO_SEQ ROUTE ORDER SEQUENCE Intersection NUM 132
RO_SEQ ROUTE ORDER SEQUENCE Road NUM 112
RODWYCLS ROADWAY CLASSIFICATION Accident CHA(2) 47
RODWYCLS ROADWAY CLASSIFICATION Road CHA(2) 112
RPT_LEV ACCIDENT REPORT LEVEL Accident CHA(1) 47
RSHL_WD2 RIGHT SHOULDER WIDTH RD2 Road NUM 113
RSHLDWID RIGHT SHOULDER WIDTH RD1 Road NUM 113
RTE_NBR RDWAY ROUTE NUMBER Accident CHA(3) 47
RTE_NBR RDWAY ROUTE NUMBER Intersection CHA(3) 132
RTE_NBR RDWAY ROUTE NUMBER Ramp CHA(3) 147
RTE_NBR RDWAY ROUTE NUMBER Road CHA(3) 113
RTE_SUF RDWAY ROUTE SUFFIX Accident CHA(1) 48
RTE_SUF RDWAY ROUTE SUFFIX Intersection CHA(1) 132
RTE_SUF RDWAY ROUTE SUFFIX Ramp CHA(1) 148
RTE_SUF RDWAY ROUTE SUFFIX Road CHA(1) 113
RTE_TYPE HIGHWAY TYPE INDICATOR Vehicle CHA(1) 73
RU_IO RURAL/URBAN INSIDE OUTSIDE CITY Road CHA(1) 114
RURURB RURAL URBAN Road CHA(1) 115
SCHLBUS SCHOOL BUS Vehicle CHA(1) 73
SCN_FRWY SCENIC FREEWAY Road CHA(1) 115
SDE_HWY SIDE-OF-HIGHWAY Accident CHA(1) 48
SEATPOS SEATING POSTION Occupant CHA(1) 89
SEG_LNG SECTION LENGTH Road NUM 115
SEVERITY COLLISION SEVERITY Accident CHA(1) 48
SEX OCCUPANT SEX Occupant CHA(1) 89
SOBRIETY SOBRIETY Vehicle CHA(1) 74
SP_COND SPECIAL CONDITION Accident CHA(1) 49
SPEC_INF SPECIAL INFORMATION Vehicle CHA(1) 74
SUB_VIOL VIOLATION SUFFIX Vehicle CHA(1) 75
SURF_TY2 SURFACE TYPE RD2 Road CHA(1) 116
SURF_TYP SURFACE TYPE RD1 Road CHA(1) 116
SURF_WD2 TRAVELED-WAY WIDTH RD2 Road NUM 117
SURF_WID TRAVELED-WAY WIDTH RD1 Road NUM 117
TERRAIN TERRAIN Road CHA(1) 117
TOLL TOLL AND FOREST RDS Road CHA(1) 117
TOT_BIKEINJ TOTAL BICYCLISTS INJURED Accident NUM 49
TOT_BIKEKIL TOTAL BICYCLISTS KILLED Accident NUM 49
TOT_INJ OCCUPANTS INJURED Accident NUM 49
TOT_KILL OCCUPANTS KILLED Accident NUM 50
TOT_MTCYLINJ TOTAL MOTORCYCLISTS INJURED Accident NUM 50
TOT_MTCYLKIL TOTAL MOTORCYCLISTS KILLED Accident NUM 50
TOT_PEDINJ TOTAL PEDESTRIANS INJURED Accident NUM 50
TOT_PEDKILL TOTAL PEDESTRIANS KILLED Accident NUM 50
TOWAWAY INJURY, FATAL, OR TOWAWAY Accident CHA(1) 51
TRAIL_CODE TRAILER CODE Vehicle CHA(1) 76
TRF_CNTL TRAFFIC CONTROL TYPE Intersection CHA(1) 133
TRF_CNTL INTERSECTION TRAFFIC CONTROL TYPE Ramp CHA(1) 148
TRF_OPER TRAFFIC CONTROL OPERATING Accident CHA(1) 51
TRFCTLDT TRAFFIC CONTROL TYPE DATE Intersection CHA(6) 133
TRFCTLHS TRAFFIC CONTROL TYPE HISTORY Intersection CHA(1) 133
TRK_CODE TRUCK CODE Vehicle CHA(1) 76
TRK_FLG TRUCK INVOLVED Accident CHA(1) 51
TRK2AX 2-AXLE TRUCK AADT Road NUM 118
TRK3AX 3-AXLE TRUCK AADT Road NUM 118
TRK4AX 4-AXLE TRUCK AADT Road NUM 118
TRK5AX 5+-AXLE TRUCK AADT Road NUM 118
TRKCNTFL TRUCK COUNT FLAG Road CHA(1) 119
TRKTOT TOTAL TRUCK AADT Road NUM 119
TYPEDESC INTERSECTION TYPE Intersection CHA(1) 134
VEH_AT_FAULT VEHICLE AT FAULT Accident CHA(2) 51
VEH_AT_FAULT VEHICLE AT FAULT Vehicle CHA(1) 76
VEH_INVL MOTOR VEHICLES INVOLVED WITH Accident CHA(2) 52
VEHNO VEHICLE NUMBER Occupant NUM 90
VEHNO VEHICLE NUMBER Vehicle NUM 76
VEHTYPE VEHICLE TYPE Vehicle CHA(1) 78
VEHYR VEHICLE MODEL YEAR Vehicle CHA(4) 79
VIOL VIOLATION CATEGORY Vehicle CHA(2) 79
VIOLS CADMV VEHICLE VIOLATIONS CODES Vehicle CHA(5) 80
VTOWED VEHICLE TOWED Vehicle CHA(2) 81
VTOWING VEHICLE TOWING Vehicle CHA(2) 81
VTYPE_AT_FAULT_CHP CHP VEHICLE TYPE AT FAULT Accident CHA(2) 53
VTYPE_AT_FAULT_DOT VEHICLE TYPE AT FAULT Accident CHA(1) 55
WEATHER WEATHER Accident CHA(1) 56
WEATHER1 WEATHER Accident CHA(1) 56
WEATHER2 WEATHER Accident CHA(1) 56
WEEKDAY DAY-OF-WEEK Accident CHA(1) 56
XSTAADT X-STREET AADT Intersection NUM 134
XSTADTDT X-STREET ADT DATE Intersection CHA(6) 134
XSTADTHS X-STREET ADT HISTORY Intersection CHA(1) 135
XSTLANES X-STREET NUMBER OF LANES Intersection CHA(1) 135
XSTLNGT X-STREET SECTION LENGTH Intersection CHA(3) 135
XSTRTDTE X-STREET DATE Intersection CHA(6) 135
XSTRTHST X-STREET HISTORY Intersection CHA(1) 136
XSTRTLFT X-STREET LEFT TURN CHANNELIZATION Intersection CHA(1) 136
XSTRTMST X-STREET SIGNAL Intersection CHA(1) 136
XSTRTRGH X-STREET RIGHT TURN Intersection CHA(1) 136
XSTSTRT X-STREET STATE ROUTE INDICATOR Intersection NUM 137
XSTTRFLO X-STREET TRAFFIC FLOW Intersection CHA(1) 137
XST_RSUF X-STREET ROUTE SUFFIX Intersection CHA(1) 137

Crash File

Accident Subfile

List of Elements for the CA Accident Subfile

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
ACC_DATE DATE OF ACCIDENT -YMD Accident CHA(8) 31
ACCTYPE TYPE-OF-COLLISION Accident CHA(1) 31
ACCYR COLLISION ACCYR Accident CHA(4) 31
ALCH_FLG ALCOHOL INVOLVED Accident CHA(1) 31
BIKE_FLG BICYCLE INVOLVED Accident CHA(1) 32
CASENO UNIQUE ACCIDENT CASEO Accident CHA(21) 32
CAUSE1 PRIMARY COLL FACTOR Accident CHA(1) 32
CAUSHPAL COLL FACTOR ALPHA (CHP) Accident CHA(1) 33
CAUSHPCD COLL FACTOR CODING (CHP) Accident CHA(5) 33
CAUSHPCT COLL FACTOR CATEGORY (CHP) Accident CHA(2) 34
CAUSHPLG COLL FACTOR LEGAL CODE(CHP) Accident CHA(1) 35
CAUSHPSB COLL FACTOR CODE SUBSECTION (CHP) Accident CHA(1) 35
CNTY_RTE COUNTY ROUTE Accident CHA(10) 35
COUNTY COUNTY Accident CHA(2) 36
DISTANCE DISTANCE Accident CHA(5) 37
DISTRICT DISTRICT Accident CHA(2) 38
FILETYP FILE TYPE Accident CHA(1) 38
HIT_RUN HIT AND RUN Accident CHA(1) 38
HOUR TIME OF ACCIDENT Accident CHA(4) 39
HWY_GRP HIGHWAY GROUP Accident CHA(1) 40
INT_RMP INTS/RAMP ACC LOCATION Accident CHA(1) 40
INTER INTERSECTION CRASH Accident CHA(1) 41
JUR_TYPE JURISDICTION TYPE Accident CHA(1) 41
LIGHT LIGHT CONDITION Accident CHA(1) 41
LOC_TYP LOCATION TYPE Accident CHA(1) 42
LOCATN COUNTY/CITY CODE WHERE CRASH OCCURRED Accident CHA(4) 42
MILEPOST RAMP MILEPOST Accident NUM 42
MTCY_FLG MOTORCYCLE INVOLVED Accident CHA(1) 42
NUM_OCCS OCCUPANTS Accident NUM 43
NUMVEHS TOT-NBR-VEHICLES Accident CHA(2) 43
PED_ACTN PEDESTRIAN ACTION Accident CHA(1) 44
PED_FLG PEDESTRIAN INVOLVED Accident CHA(1) 44
POP_GRP POPULATION GROUP = (CITY/RURAL GROUP) Accident CHA(1) 44
PSMILPRF POSTMILE PREFIX Accident CHA(1) 45
PSMILSUF POSTMILE SUFFIX Accident CHA(1) 46
RD_DEF1 ROADWAY CONDITION Accident CHA(1) 46
RD_DEF2 ROAD CONDITION 2 Accident CHA(1) 46
RD_DEF3 ROAD CONDITION 3 Accident CHA(1) 46
RDSURF ROAD-SURFACE Accident CHA(1) 46
RODWYCLS ROADWAY CLASSIFICATION Accident CHA(2) 47
RPT_LEV ACCIDENT REPORT LEVEL Accident CHA(1) 47
RTE_NBR RDWAY ROUTE NUMBER Accident CHA(3) 47
RTE_SUF RDWAY ROUTE SUFFIX Accident CHA(1) 48
SDE_HWY SIDE-OF-HIGHWAY Accident CHA(1) 48
SEVERITY COLLISION SEVERITY Accident CHA(1) 48
SP_COND SPECIAL CONDITION Accident CHA(1) 49
TOT_BIKEINJ TOTAL BICYCLISTS INJURED Accident NUM 49
TOT_BIKEKIL TOTAL BICYCLISTS KILLED Accident NUM 49
TOT_INJ OCCUPANTS INJURED Accident NUM 49
TOT_KILL OCCUPANTS KILLED Accident NUM 50
TOT_MTCYLINJ TOTAL MOTORCYCLISTS INJURED Accident NUM 50
TOT_MTCYLKIL TOTAL MOTORCYCLISTS KILLED Accident NUM 50
TOT_PEDINJ TOTAL PEDESTRIANS INJURED Accident NUM 50
TOT_PEDKILL TOTAL PEDESTRIANS KILLED Accident NUM 50
TOWAWAY INJURY, FATAL, OR TOWAWAY Accident CHA(1) 51
TRF_OPER TRAFFIC CONTROL OPERATING Accident CHA(1) 51
TRK_FLG TRUCK INVOLVED Accident CHA(1) 51
VEH_AT_FAULT VEHICLE AT FAULT Accident CHA(2) 51
VEH_INVL MOTOR VEHICLES INVOLVED WITH Accident CHA(2) 52
VTYPE_AT_FAULT_CHP CHP VEHICLE TYPE AT FAULT Accident CHA(2) 53
VTYPE_AT_FAULT_DOT VEHICLE TYPE AT FAULT Accident CHA(1) 55
WEATHER WEATHER Accident CHA(1) 56
WEATHER1 WEATHER Accident CHA(1) 56
WEATHER2 WEATHER Accident CHA(1) 56
WEEKDAY DAY-OF-WEEK Accident CHA(1) 56

Date of Accident - YMD
SAS Name: ACC_DATE

Definition: Date when the accident occurred.

Additional Information: YYYMMDD = Year-Month-Day accident occurred.

 


Type of Collision
SAS Name: ACCTYPE

Definition: Type of accident that occurred.

  • A' - Head-On
  • 'B' - Sideswipe
  • 'C' - Rear End
  • 'D' - Broadside
  • 'E' - Hit Object
  • 'F' - Overturned
  • 'G' - Auto-Pedestrian
  • 'H' - Other
  • '<' - Not Stated
  • Other - Error/Other Codes

Collision ACCYR
SAS Name: ACCYR

Definition: Year accident occurred.

Additional Information: YYYY = Year accident occurred.

 


Alcohol Involved
SAS Name: ALCH_FLG

Definition: Alcohol involved in the crash  

Additional Information: Element added in 2001.

  • 'Y' - Yes

 


Bicycle Involved in the Accident
SAS Name: BIKE_FLG

Definition: Whether any bicycle was involved in the accident.

Additional Information: Element added in 2003.

  • 'Y' - Yes

 


Accident Case Number
SAS Name: CASENO

Definition: Case number of accident.

Additional Information: The first 4 digits show the accident year.

 


Primary Collision Factor (DOT)
SAS Name: CAUSE1

Definition: Primary collision factor of the crash.

Additional Information: This element concerning primary collision factor is based on coding provided by the California DOT TO Office. While sufficient for many analyses, these larger categories are developed by combining more detailed codes (e.g., "running red light" code is a subset of "Other Violations (hazardous)." More detailed coding for specific primary collision factors as coded by the California Highway Patrol can be found in combinations of the following elements: CAUSHPAL, AUSHPLG, CAUSHPCD, CAUSHPSB, and CAUSHPCT. See formats below.

  • '1' - Under Influence of Alcohol
  • '2' - Following Too Closely
  • '3' - Failure to Yield
  • '4' - Improper Turn
  • '5' - Speeding
  • '6' - Other Violations (Hazardous)
  • 'B' - Other Improper Driving
  • 'C' - Other Than Driving
  • 'D' - Unknown
  • 'E' - Fell Asleep
  • '<' - Not Stated
  • '-' - Invalid Code
  • Other - Errors/Other Codes

 


Collision Factor Alpha
SAS Name: CAUSHPAL

Definition: Collision factor alpha of the crash.

  • 'A'  - (Vehicle) Code Violation
  • 'B' - Other Improper Driving
  • 'C' - Other Than Driving
  • 'D' - Unknown
  • Other -   Error/Other Codes

 


Collision Factor Coding
SAS Name: CAUSHPCD

Definition: Collision factor coding of the crash .

Additional Information: This is a five-digit code related to violations/causes as defined in sections in the California legal codes. The extensive format for this element can be found on the California State Highway Patrol webpage at http://www.leginfo.ca.gov/calaw.html and then search on VEHICLE CODE.

 


Collision Factor Category
SAS Name: CAUSHPCT

Definition: Collision factor category of the crash.

  • '00' - Unknown
  • '01' - Driving or Bicycling Under Influence Of Alcohol Or Drug
  • '02' - Impeding Traffic
  • '03' - Unsafe Speed
  • '04' - Following Too Closely
  • '05' - Wrong Side of Road
  • '06' - Improper Passing
  • '07' - Unsafe Lane Change
  • '08' - Improper Turning
  • '09' - Automobile Right-Of-Way (Not 11)
  • '10' - Pedestrian Right-Of-Way
  • '11' - Pedestrian Violation
  • '12' - Traffic Signals and Signs
  • '13' - Hazardous Parking
  • '14' - Lights
  • '15' - Brakes
  • '16' - Other Equipment
  • '17' - Other Hazardous Violation (Not 22)
  • '18' - Other Than Driver (or Pedestrian)
  • '21' - Unsafe Starting or Backing
  • '22' - Other Improper Driving
  • '23' - Pedestrian Or Other Under Influence Of Alcohol Or Drug
  • '24' - Fell Asleep

 


Collision Factor Legal Code
SAS Name: CAUSHPLG

Definition: Part of legal code associated with Collision Factor.

  • 'B' - Business and Professions
  • 'C' - Vehicle
  • 'H' - City Health and Safety
  • 'I' - City Ordinance
  • 'O' - County Ordinance
  • 'P' - Penal
  • 'S' - Streets and Highways
  • 'W' - Welfare and Institutions
  • Other - Error/Other Codes

 


Collision Factor Code Subsection
SAS Name: CAUSHPSB

Definition: Collision factor legal code subsection

Additional Information: Subsection of the California legal code. See CAUSHPCD.

 


Country Route
SAS Name: CNTY_RTE

Definition: Crash location information used in linkage to other files.

Additional Information: Linkage element, consisting of DISTRICT+RTE_NBR+RTE_SUF+COUNTY+PS ILPRF+HWY_GRP.

 


County
SAS Name: COUNTY

Definition: County where the crash occurred

  • '01' - Alameda
  • '02' - Alpine
  • '03' - Amador
  • '04' - Butte
  • '05'  - Calaveras
  • '06' - Colusa
  • '07'  - Contra Costa
  • '08' - Del Norte
  • '09' - El Dorado
  • '10'  - Fresno
  • '11'  - Glenn
  • '12'  - Humboldt
  • '13' - Imperial
  • '14' - Inyo
  • '15' - Kern
  • '16' - Kings
  • '17'  - Lake
  • '18' - Lassen
  • '19' - Los Angeles
  • '20' - Madera
  • '21' - Marin
  • '22' - Mariposa
  • '23' - Mendocino
  • '24' - Merced
  • '25' - Modoc
  • '26' - Mono
  • '27' - Monterey
  • '28' - Napa
  • '29' - Nevada
  • '30' - Orange
  • '31' - Placer
  • '32' - Plumas
  • '33' - Riverside
  • '34' - Sacramento
  • '35' - San Benito
  • '36' - San Bernardino
  • '37' - San Diego
  • '38' - San Francisco
  • '39' - San Joaquin
  • '40' - San Luis Obispo
  • '41' - San Mateo
  • '42' - Santa Barbara
  • '43' - Santa Clara
  • '44' - Santa Cruz
  • '45' - Shasta
  • '46' - Sierra
  • '47' - Siskiyhou
  • '48' - Solano
  • '49' - Sonoma
  • '50' - Stanislaus
  • '51' - Sutter
  • '52' - Tehama
  • '53' - Trinity
  • '54' - Tulare
  • '55' - Tuolume
  • '56' - Ventura
  • '57' - Yolo
  • '58' - Yuba

 


Distance
SAS Name: DISTANCE

Definition: Distance from the center of the reference intersection to the point of collision.

Additional Information: Five-digit distance in feet from the center of the reference intersection to the point of collision.

 


District
SAS Name: DISTRICT

Definition: District where the crash occurred.

  • '01' - District One
  • '02' - District Two
  • '03' - District Three
  • '04' - District Four
  • '05' - District Five
  • '06' - District Six
  • '07' - District Seven
  • '08' - District Eight
  • '09' - District Nine
  • '10' - District Ten
  • '11' - District Eleven
  • '12' - District Twelve
  • '-' - Invalid Data
  • '+' - No Data

 


File Type
SAS Name: FILETYP

Definition: File type record of the crash.

  • 'H' - Highway Record
  • 'I' - Intersection
  • 'R' - Ramp
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Hit and Run
SAS Name: HIT_RUN

Definition: Whether or not the crash was a hit and run.

  • 'F' - Hit and Run Felony
  • 'M' - Hit and Run Misdemeanor
  • 'N' - Not Hit and Run
  • Other - Error/Other Codes

 


Time of Accident
SAS Name: HOUR

Definition: Hour at which the crash occurred.

  • '0000'-'0059' - 12 AM - 1259 AM
  • '0100'-'0159' - 1 AM - 159 AM
  • '0200'-'0259' - 2 AM - 259 AM
  • '0300'-'0359' - 3 AM - 359 AM
  • '0400'-'0459' - 4 AM - 459 AM
  • '0500'-'0559' - 5 AM - 559 AM
  • '0600'-'0659' - 6 AM - 659 AM
  • '0700'-'0759' - 7 AM - 759 AM
  • '0800'-'0859' - 8 AM - 859 AM
  • '0900'-'0959' - 9 AM - 959 AM
  • '1000'-'1059' - 10 AM - 1059 AM
  • '1100'-'1159' - 11 AM - 1159 AM
  • '1200'-'1259' - 12Noon- 1259 PM
  • '1300'-'1359' - 1 PM - 159 PM
  • '1400'-'1459' - 2 PM - 259 PM
  • '1500'-'1559' - 3 PM - 359 PM
  • '1600'-'1659' - 4 PM - 459 PM
  • '1700'-'1759' - 5 PM - 559 PM
  • '1800'-'1859' - 6 PM - 659 PM
  • '1900'-'1959' - 7 PM - 759 PM
  • '2000'-'2059' - 8 PM - 859 PM
  • '2100'-'2159' - 9 PM - 959 PM
  • '2200'-'2259' - 10 PM - 1059 PM
  • '2300'-'2359' - 11 PM - 1159 PM
  • '2500' - Unknown
  • '2600' - Not Stated

 


Highway Group
SAS Name: HWY_GRP

Definition: Highway group of the crash.

Additional Information: In the HSIS version of the Roadlog File, codes ‘D’, ‘U’, and ‘X’ do not appear. They are combined by CA DOT into ‘Z’. In other data files provided by California to other users, these codes may occur. To link with crash data, they must be recoded to ‘Z’.

  • 'R' - Right Independent Alignment
  • 'L' - Left Independent Alignment
  • 'D' - Divided Highway
  • 'U' - Undivided Highway
  • 'X' - Unconstructed
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


INTS/Ramp ACC Location
SAS Name: INT_RMP

Definition: Location of the crash in relation to a ramp on intersection.

Additional Information: Code "4" refers to locations on non-State intersecting routes (which are not mileposted) between 150 ft. "outside" the ramp-related intersection to 150 ft outside the opposing ramp- related intersection. Similarly, code "6" is for locations on non-State routes within + 150 ft. of the intersection. Thus, in both cases, the crashes are mileposted to the ramp or State route. In contrast, similar locations on intersecting State routes are mileposted to the intersecting State route. This element will allow for identification of such "area 4" crashes if desirable in the analysis. See AREA4 in the Ramp File.

  • '1' - Ramp Intersection (Exit), Last 50 Ft
  • '2' - Mid-Ramp
  • '3' - Ramp Entry, First 50 Ft
  • '4' - Ramp Area/Intersection Street, Within 100 Ft
  • '5' - In Intersection
  • '6' - Outside Intersection (Non-State Route), Within 250 Ft
  • '<' - Not Stated or Undetermined
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Intersection Crash
SAS Name: INTER

Definition: Indicates whether crash occurred on an intersection or not.

Additional Information: Element added in 2003.

  • 'Y' - Intersection
  • 'N' - Not Intersection
  • ' ' - Not Stated

 


Jurisdiction Type
SAS Name: JUR_TYPE

Definition: Jurisdiction type where crash occurred.

Additional Information: Element added in 1995 and discontinued in 2001.

  • '1' - CHP Jurisdiction
  • '2' - Other
  • Other - Unformatted

 


Light Condition
SAS Name: LIGHT

Definition: The type/level of light that existed at the time of the crash.

  • 'A' - Daylight
  • 'B' - Dusk - Dawn
  • 'C' - Dark - Street Lights
  • 'D' - Dark - No Street Lights
  • 'E' - Dark - Street Lights Not Functioning
  • 'F' - Dark - Not Stated
  • '<' - Not Stated
  • Other - Error/Other Codes

 


Location Type
SAS Name: LOC_TYP

Definition: Location type of the crash

Additional Information: Element added in 2003.

  • 'H' - Highway
  • 'I' - Intersection
  • 'R' - Ramp or Collector
  • '-', ' ' - Not State Highway

 

 


County/City Code Where Crash Occurred
SAS Name: LOCATN

Definition: County/city code where crash occurred

Additional Information: Refer COUNTY and CITY variables for codes.

 


Milepost
SAS Name: MILEPOST

Definition: Reference point where the crash occurred.

Additional Information: Milepost of crash in miles (XXX.XXX).

 


Motorcycle Involved
SAS Name: MTCY_FLG

Definition: Whether a motorcycle was involved in the crash.

Additional Information: Element added in 2001.

  • 'Y' - Yes

Total Number of Occupants
SAS Name: NUM_OCCS

Definition: Total number of occupants involved in the crash.

  • 0 - 0
  • 1 - 1
  • 2 - 2
  • 3 - 3
  • 4 - 4
  • 5 - 5
  • 6-99 - >5
  • Other - Error/Other Codes

 


Tot-NBR-Vehicles
SAS Name: NUMVEHS

Definition: Total number of vehicles involved in the crash

  • '0' - 0
  • '1' - 1
  • '2' - 2
  • '3' - 3
  • '4' - 4
  • '5' - 5
  • '6' - 6
  • '7' - 7
  • '8' - 8
  • '9' - 9
  • '10'-'15' - 10-15
  • Other - Error/Other Codes

 


Pedestrian Action
SAS Name: PED_ACTN

Definition: Pedestrian action in the crash.

Additional Information: Element added in 2003.

  • '-' - Not Stated
  • 'A' - No Pedestrian Involved
  • 'B' - Crossing in Crosswalk at Intersection
  • 'C' - Crossing in Crosswalk Not At Intersection
  • 'D' - Crossing Not in Crosswalk
  • 'E' - In Road, Including Shoulder
  • 'F' - Not in Road
  • 'G' - Approaching/Leaving School Bus

 


Pedestrian Involved
SAS Name: PED_FLG

Definition: Whether a pedestrian was involved in the crash

Additional Information: Element added in 2001.

  • 'Y' - Yes

 


Population Group
SAS Name: POP_GRP

Definition: Population group.

  • '1' - Incorporated (Less Than 2500)
  • '2' - Incorporated (2500 To 10000)
  • '3' - Incorporated (10000 To 25000)
  • '4' - Incorporated (25000 To 50000)
  • '5' - Incorporated (50000 To 100000)
  • '6' - Incorporated (100000 To 250000)
  • '7' - Incorporated (Greater Than 250000)
  • '9' - Unincorporated (Rural)
  • '0' - Unincorporated (Private Property)
  • '<' - Not Stated
  • Other - Error/Other Codes

 


Postmile Prefix
SAS Name: PSMILPRF

Definition: Postmile prefix of the crash location.

Additional Information: Roadways can be realigned in the middle of a year (see ‘R’ above).Thus, there may appear to be overlapping records in the same milepost range in a given year, except for this variable. Accidents are correctly mileposted to the correct record by California. RD_DATE can be used to determine when the new alignment was opened. However, if one is trying to match prior year’s crashes to such a section, the older crash records (not having the ‘R’) will not be computer matched to the new alignment (with the ‘R’) even though the roads are virtually the same piece of pavement. One can see how the Roadlog sections actually fall on the ground in a given year by sorting by RO_SEQ (Route Order Sequence). However, in multi-year before/after studies, the analyst may have to manually match the pertinent sections across years to conduct his/her analysis. Contact HSIS staff for assistance.

  • ' ' - No Prefix
  • 'A' - Reposted
  • 'B' - Bus Lane
  • 'C' - Commercial
  • 'D' - Duplicate (Meandering)
  • 'F' - Reposted - Commercial (C)
  • 'G' - Reposted - Duplicate (D)
  • 'H' - Realigned - Duplicate (D)
  • 'J' - Reposted, Realigned - Duplicate
  • 'K' - Reposted - Overlap (L)
  • 'L' - Overlapping Postmiles
  • 'M' - Realigned Realignment (R)
  • 'N' - Reposted, Realigned Realignment (M)
  • 'P' - Reposted Realignment (R)
  • 'Q' - Reposted - Spur (S)
  • 'R' - Realignment
  • 'S' - Spur
  • 'T' - Temporary Connection
  • 'U' - Reposted - Temporary Connection (T)
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Postmile Suffix
SAS Name: PSMILSUF

Definition: Postmile suffix where the crash occurred

  • ' ' - No Suffix
  • 'E' - Equation
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Roadway Condition
SAS Name: RD_DEF1
Roadway Condition 2
SAS Name: RD_DEF2
Roadway Condition 3
SAS Name: RD_DEF3

Definition: Roadway condition where the crash occurred.

Additional Information: Element RD_DEF3 discontinued in 2002.

  • 'A' - Holes, Deep Ruts
  • 'B' - Loose Material on Road
  • 'C' - Obstruction on Roadway
  • 'D' - Construction - Repair Zone
  • 'E' - Reduced Road Width
  • 'F' - Flooded
  • 'G' - Other
  • 'H' - No Unusual Conditions
  • '<' - Not Stated
  • Other - Error/Other Codes

 


Road Surface
SAS Name: RDSURF

Definition: The condition of the road surface where the crash occurred.

  • 'A' - Dry
  • 'B' - Wet
  • 'C' - Snowy, Icy
  • 'D' - Slippery/Muddy
  • '<' - Not Stated
  • Other - Error/Other Codes

 


Roadway Classification
SAS Name: RODWYCLS

Definition: The classification of the roadway where the crash occurred.

Additional Information: Created element added to HSIS accident and roadway inventory files in all States in 1999. See Discussion.

  • '01' - Urban Freeways
  • '02' - Urban Freeways < 4 Lanes
  • '03' - Urban Two Lane Roads
  • '04' - Urban Multilane Divided Non-Freeways
  • '05' - Urb Mul Undv Non-Free'urban Multilane Undivided Non- Freeways
  • '06' - Rural Freeways
  • '07' - Rural Freeways < 4 Lanes
  • '08' - Rural Two Lane Roads
  • '09' - Rural Multilane Divided Non-Freeways
  • '10' - Rural Multilane Undivided Non-Freeways
  • '99' - Others

 


Accident Report Level
SAS Name: RPT_LEV

Definition: Whether the crash was reportable based on the legal threshold.

Additional Information: This element is erroneous. All records on the file are considered reportable.

  • '1' - Below Reporting Level
  • '2' - Above Reporting Level
  • '<' - Not Stated or Undetermined
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Roadway Route Number
SAS Name: RTE_NBR

Definition: The number of the route where the crash occurred.

Additional Information: Mainline route number.

 


Route Suffix
SAS Name: RTE_SUF

Definition: Route suffix of the crash location.

  • 'P' - Alignment Prior
  • 'S' - Supplemental Alignment, Partial Opened For Use Before Alignment Is Complete
  • 'U' - Unrelinquished, Superseded By Realignment, but Not Yet Accepted For Non-State-Highway Maintenance
  • 'Z'  - Budgeted or Under Construction
  • ' ' - No Suffix
  • Other - Error/Other Codes

 


Side of Travel
SAS Name: SDE_HWY

Definition: Side of travel of the highway where crash occurred

Additional Information: For divided highways, roadway on which collision occurred based on nominal direction of route. For single vehicle crash, it is the same as nominal direction of travel, overruled by impact with second vehicle after crossing median.

  • 'N' - Northbound
  • 'S' - Southbound
  • 'E' - Eastbound
  • 'W' - Westbound
  • Other - Error/Other Codes

 


Collision Severity
SAS Name: SEVERITY

Definition: The most severe injury in the crash.

  • '1' - Fatal
  • '2' - Severe Injury
  • '3' - Other Visible Injury
  • '4' - Complaint of Pain
  • '0' - PDO - Property Damage Only
  • Other - Error/Other Codes

 


Special Condition
SAS Name: SP_COND

Definition: Special condition where the crash occurred.

Additional Information: Element added in 2003.

  • '1' - Schoolbus On Public Roadway
  • '2' - State University (Also Sfia)
  • '3' - Schoolbus Not On Public Roadway
  • '4' - Offroad (Unimproved)
  • '5' - Vista Point/Rest Area/Scales/Inspection Facility
  • '6' - Other Public Access (Improved)
  • '0' - Not Above
  • '-' - Not Stated

 


Total Bicyclist Injured
SAS Name: TOT_BIKEINJ

Definition: Total number of bicyclists injured in the crash.

Additional Information: Element added in 2003.

 


Total Bicyclist Killed
SAS Name: TOT_BIKEKIL

Definition: Total number of bicyclists killed in the crash.

Additional Information: Element added in 2003.

 


Occupants Injured
SAS Name: TOT_INJ

Definition: Total number of persons injured in the crash.     

  • 0 - 0
  • 1 - 1
  • 2 - 2
  • 3 - 3
  • 4 - 4
  • 5 - 5
  • 6-99 - > 5

 


Occupants Killed
SAS Name: TOT_KILL

Definition: Total number of persons killed in the crash.   

  • 0 - 0
  • 1 - 1
  • 2 - 2
  • 3 - 3
  • 4 - 4
  • 5 - 5
  • 6-99 - > 5

 


Total Motorcyclist Injury
SAS Name: TOT_MTCYLINJ

Definition: Total number of motorcyclists injured in the crash.

Additional Information: Element added in 2003.

 


Total Motorcyclist Killed
SAS Name: TOT_MTCYKIL

Definition: Total number of motorcyclists killed in the crash.

Additional Information: Element added in 2003.

  • 1

 


Total Pedestrian Injured
SAS Name: TOT_PEDINJ

Definition: Total number of pedestrians injured in the crash.

Additional Information: Element added in 2003.

 


Total Pedestrian Killed
SAS Name: TOT_PEDKILL

Definition: Total number of pedestrian killed in the crash.

Additional Information: Element added in 2003.

 


Injury, Fatal, or Tow-Away
SAS Name: TOWAWAY

Definition: Whether or not the vehicle involved in the crash was towed from the scene.

  • 'Y' - Yes
  • 'N' - No
  • Other - Error/Other Codes

 


Traffic Control Operating
SAS Name: TRF_OPER

Definition: Traffic control operation where the crash occurred.

  • 'A' - Controls Functioning
  • 'B' - Controls Not Functioning
  • 'C' - Controls Obscured
  • 'D' - No Controls Present
  • '<' - Not Stated/
  • Other - Error/Other Codes<

 


Truck Involvement
SAS Name: TRK_FLG

Definition: Whether a truck was involved in the crash.

Additional Information: Element added in 2001.

  • 'Y' - Yes

 


Vehicle at Fault
SAS Name: VEH_AT_FAULT

Definition: Whether a vehicle was at fault in the crash.

Additional Information: This element contains different data from the one that appears with the Vehicle File. This element is discontinued in 2001.

  • 'Y' - Yes
  • 'N' - No

 


Motor Vehicles Involved with
SAS Name: VEH_INVL

Definition: What vehicles or non-vehicles were involved in the crash.

  • 'A' - Non-Collision (E.G., Overturned Without Collision Or Occupant Jumped Out)
  • 'B' - Pedestrian
  • 'C' - Other Motor Vehicle
  • 'D' - Motor Vehicle On Other Roadway
  • 'E' - Parked Motor Vehicle
  • 'F' - Train
  • 'G' - Bicycle
  • 'H' - Animal (Not 10)
  • 'I' - Fixed-Object (Tree, Utility Pole, Light Standard, Guardrail, Boulder or Construction Machinery In Construction Area Not In Motion)
  • 'J' - Other Object (Animal-Drawn Conveyance, Ridden Animal, Street Car, Fallen Tree Or Stone, Construction Machinery In Motion In Construction Area, Or Object Dropped From Motor Vehicle But Not Still In Motion (If Still In Motion, Type Collision = 03))
  • '-' - Other (Obsolete, Combined With Not Stated)
  • Other - Error/Other Codes

 


CHP Vehicle Type at Fault
SAS Name: VTYPE_AT_FAULT_CHP

Definition: Vehicle type at fault in the crash as coded by the California Highway Patrol.

Additional Information: Element added in 2001.

  • '01' - Passenger Car, Station Wagon, or Jeep
  • '02' - Motorcycle
  • '03' - Motor-Driven Cycle (< 15 HP)
  • '04' - Bicycle
  • '05' - Motorized Bicycle
  • '06' - All-Terrain Vehicle (ATV)
  • '07' - Sport Utility Vehicle
  • '08' - Minivan
  • '09' - Paratransit Bus
  • '10' - Tour Bus
  • '11' - Other Commercial Bus
  • '12' - Non-Commercial Bus
  • '13' - Schoolbus Without Pupil Passengers
  • '14' - Schoolbus Public I
  • '15' - Schoolbus Public II
  • '16' - Schoolbus Private I
  • '17' - Schoolbus Private II
  • '18' - Schoolbus Contractual I
  • '19' - Schoolbus Contractual II
  • '20' - Public Transit Authority
  • '21' - Two-Axle Tank Truck
  • '22' - Pickup Or Panel Truck
  • '23' - Pickup Truck With Camper
  • '24' - Three-Axle Tank Truck
  • '25' - Truck Tractor
  • '26' - Two-Axle Truck
  • '27' - Three-Axle Truck
  • '41' - Ambulance
  • '42' - Dune Buggy
  • '43' - Fire Truck (Not Rescue)
  • '44' - Forklift
  • '45' - Highway Construction Equipment (Only While Not In Construction Area)
  • '46' - Implement Of Husbandry
  • '47' - Motor Home (40 Ft or Less)
  • '48' - CHP, Police, Or Sheriff Car (Emergency Service or Not)
  • '49' - CHP, Police, Or Sheriff Motorcycle (Emergency Service or Not)
  • '50' - Mobile Equipment51 - Farm Labor Vehicle (Certified)
  • '55' - Two-Axle Tow Truck
  • '56' - Three-Axle Tow Truck
  • '57' - Farm Labor Vehicle (Non-Certified)
  • '58' - Farm Labor Transporter
  • '59' - Motorhome (Over 40 Ft)
  • '60' - Pedestrian (Includes Motorized Wheelchair)
  • '61' - School Pupil Activity Bus I (Prior To 2002)
  • '62' - School Pupil Activity Bus Ii (Prior To 2002
  • '63' - Youth" Bus
  • '64' - School Pupil Activity Bus I (Eff. 2002)
  • '65' - School Pupil Activity Bus Ii (Eff. 2002)
  • '71' - Passenger Car - Hazardous Materials Only
  • '72' - Pickups and Panels - Hazardous Materials Only
  • '73' - Pickups and Campers - Hazardous Materials Only
  • '75' - Truck Tractor - Hazardous Materials Only
  • '76' - Two-Axle Truck - Hazardous Materials Only
  • '77' - Three or More Axle Truck - Hazardous Materials Only
  • '78' - Two-Axle Tank Truck - Hazardous Materials Only
  • '79' - Three-Axle Tank Truck - Hazardous Materials Only
  • '81' - Passenger Car - Hazardous Waste or Waste/Material Combo
  • '82' - Pickups and Panels - Hazardous Waste or Waste/Material Combo
  • '83' - Pickups and Campers - Hazardous Waste or Waste/Material Combo
  • '85' - Truck Tractor - Hazardous Waste or Waste/Material Combo
  • '86' - Two-Axle Truck - Hazardous Waste or Waste/Material Combo
  • '87' - Three or More Axle Truck - Hazardous Waste or Waste/Material Combo
  • '88' - Two-Axle Tank Truck - Hazardous Waste or Waste/Material Combo
  • '89' - Three-Axle Tank Truck - Hazardous Waste or Waste/Material Combo
  • '94' - Motorized Transportation Device
  • '95' - Miscellaneous Non-Motorized Vehicle (Ridden Animal, Animal-Drawn Conveyance, Train, or Building) With Victim
  • '96' - Miscellaneous Motorized Vehicle (Golf Cart)
  • '97' - Low Speed Vehicle
  • '99' '-' - Not Stated or Unknown (Hit And Run)

 


Type of Vehicle at Fault
SAS Name: VTYPE_AT_FAULT_DOT

Definition: Type of vehicle at fault in the crash as coded by the CA DOT.

Additional Information: Element added in 2001.

  • 'A' - Pass Car/Stat Wg
  • 'B' - Pass Car W/Trler
  • 'C' - Motorcycle
  • 'D' - Pkup/Panel Truck
  • 'E' - Pkup/Pnl Trk W/Tr
  • 'F' - Trk/Truck Tractor
  • 'G' - Trk Trac W/1 Trlr
  • '2' - Trk Trac W/2 Trlr
  • '3' - Trk Trac W/3 Trlr
  • '4' - Single Unit Tnkr
  • '5' - Trk/Trlr W/1 Tnk
  • '6' - Trk/Trlr W/2 Tnk
  • 'H' - School Bus
  • 'I' - Other Bus
  • 'J' - Emergency Veh
  • 'K' - Hwy Const Equip
  • 'L' - Bicycle
  • 'M' - Oth Mtr Vehicle
  • 'N' - Oth N/Mtr Veh
  • 'O' - Spilled Loads
  • 'P' - Disengaged Tow
  • 'Q' - Uninvolved Veh
  • 'R' - Moped
  • 'S' - Runaway Veh
  • 'T' - Train
  • 'U' - Pedestrian
  • 'V' - Dismounted Ped
  • 'W' - Animal - Livestk
  • 'X' - Animal - Deer
  • 'Z' - Animal - Other
  • '<' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Weather
SAS Name: WEATHER
Weather
SAS Name: WEATHER1
Weather
SAS Name: WEATHER2

Definition: Weather conditions when the crash occurred.

Additional Information: The element WEATHER was replaced in 2003 by WEATHER1 and
WEATHER2.

  • 'A' - Clear
  • 'B' - Cloudy
  • 'C' - Raining
  • 'D' - Snowing
  • 'E' - Fog
  • 'F' - Other
  • 'G' - Wind
  • '<' - Not Stated
  • Other - Error/Other Codes

 


Day of Week
SAS Name: WEEKDAY

Definition: Day of the week when the accident occurred.

  • '1' - Sunday
  • '2' - Monday
  • '3' - Tuesday
  • '4' - Wednesday
  • '5' - Thursday
  • '6' - Friday
  • '7' - Saturday
  • Other - Error/Other Codes

 

Vehicle Subfile

List of Elements for the CA Vehicle Subfile

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
ACCYR COLLISION ACCYR Vehicle CHA(4) 59
BELT1 BELT USAGE Vehicle CHA(1) 59
CASENO UNIQUE ACCIDENT CASEO Vehicle CHA(21) 60
CAUSE CONTRIBUTION FACTOR Vehicle CHA(1) 60
CELPHONE CELL PHONE Vehicle CHA(1) 60
CONTRIB1 FIRST ASSOCIATED FACTOR Vehicle CHA(1) 61
CONTRIB2 SECOND ASSOCIATED FACTOR Vehicle CHA(1) 61
DEFECT VEHICLE DEFECT Vehicle CHA(1) 62
DIR_TRVL DIRECTION OF TRAVEL Vehicle CHA(1) 62
DRV_AGE DRIVER AGE Vehicle NUM 63
DRV_INJ DRIVER EXTENT OF INJURY Vehicle CHA(1) 63
DRV_RACE DRIVER RACE Vehicle CHA(1) 64
DRV_SEX DRIVER SEX Vehicle CHA(1) 64
DRVREST1 DRIVER SAFETY EQUIPMENT Vehicle CHA(1) 65
DRVREST2 DRIVER SAFETY EQUIPMENT Vehicle CHA(1) 65
FIRE VEH FUEL LEAKS AND FIRES Vehicle CHA(1) 66
HAZ_CODE HAZARDOUS MATERIAL Vehicle CHA(1) 66
HAZMAT HAZARDOUS MATERIAL Vehicle CHA(1) 66
INSUR INSURANCE Vehicle CHA(1) 67
LOC_TYP1 FIRST COLL LOCATION Vehicle CHA(1) 67
LOC_TYP2 SECOND COLL LOCATION Vehicle CHA(1) 67
LOC_TYP3 THIRD COLL LOCATION Vehicle CHA(1) 67
LOC_TYP4 FOURTH COLL LOCATION Vehicle CHA(1) 67
MAKE VEHICLE MAKE Vehicle CHA(2) 68
MAINT_LEVL MAINTENANCE LEVEL SERVICE Vehicle CHA(1) 104
MISCACT1 MOVEMENT PRECEDING COLL Vehicle CHA(1) 69
NUM_INJ TOTAL NUMBER INJURED Vehicle NUM 70
NUM_KILL TOTAL NUMBER KILLED Vehicle CHA(2) 70
OBJECT1 FIRST OBJECT STRUCK Vehicle CHA(2) 71
OBJECT2 SECOND OBJECT STRUCK Vehicle CHA(2) 71
OBJECT3 THIRD OBJECT STRUCK Vehicle CHA(2) 71
OBJECT4 FOURTH OBJECT STRUCK Vehicle CHA(2) 71
PART_TYP PARTY TYPE Vehicle CHA(1) 72
PHYSCOND DRIVER PHYSICAL CONDITION Vehicle CHA(1) 73
RTE_TYPE HIGHWAY TYPE INDICATOR Vehicle CHA(1) 73
SCHLBUS SCHOOL BUS Vehicle CHA(1) 73
SOBRIETY SOBRIETY Vehicle CHA(1) 74
SPEC_INF SPECIAL INFORMATION Vehicle CHA(1) 74
SUB_VIOL VIOLATION SUFFIX Vehicle CHA(1) 75
TRAIL_CODE TRAILER CODE Vehicle CHA(1) 76
TRK_CODE TRUCK CODE Vehicle CHA(1) 76
VEH_AT_FAULT VEHICLE AT FAULT Vehicle CHA(1) 76
VEHNO VEHICLE NUMBER Vehicle NUM 76
VEHTYPE VEHICLE TYPE Vehicle CHA(1) 78
VEHYR VEHICLE MODEL YEAR Vehicle CHA(4) 79
VIOL VIOLATION CATEGORY Vehicle CHA(2) 79
VIOLS CADMV VEHICLE VIOLATIONS CODES Vehicle CHA(5) 80
VTOWED VEHICLE TOWED Vehicle CHA(2) 81
VTOWING VEHICLE TOWING Vehicle CHA(2) 81

Collision ACCYR
SAS Name: ACCYR

Definition: Year accident occurred.

Additional Information: Year of accident (YYYY).

 


Seatbelt Usage
SAS Name: BELT1

Definition: Occupant restraint use in this vehicle.

Additional Information: Data available only for the year 2001.

  • 'A' - None In Vehicle
  • 'B' - Unknown
  • 'C' - Lap Belt Used
  • 'D' - Lap Belt Not Used
  • 'E' - Shoulder Harness Used
  • 'F' - Shoulder Harness Not Used
  • 'G' - Lap/Shoulder Harness Used
  • 'H' - Lap/Shoulder Harness Not Used
  • 'J' - Passive Restraint Used
  • 'K' - Passive Restraint Not Used
  • 'L' - Air Bag Deployed
  • 'M' - Air Bag Not Deployed
  • 'N' - Other
  • 'P' - Not Required
  • 'Q' - Child Restraint In Vehicle Used
  • 'R' - Child Restraint In Vehicle Not Used
  • 'S' - Child Restraint In Vehicle, Use Unknown
  • 'T' - Child Restraint In Vehicle, Improper Use
  • 'U' - No Child Restraint In Vehicle
  • 'V' - Driver, Motorcycle Helmet Not Used
  • 'W' - Driver, Motorcycle Helmet Used
  • 'X' - Passenger, Motorcycle Helmet Not Used
  • 'Y' - Passenger, Motorcycle Helmet Used
  • '-',' ' - Not Stated

 


Case Number
SAS Name: CASENO

Definition: Case number of accident.

Additional Information: The first 4 digits show the accident year.

 


Cause of the Accident
SAS Name: CAUSE

Definition: Crash causal factor in this vehicle.

Additional Information: Element added in 2002.

  • >'A' - Cell Phone Handheld (7/1/03)
  • 'B' - Cell Phone Hands Free (7/1/03)
  • 'C' - Electronic Equip.(1/1/01)
  • 'D' - Radio/Cd (1/1/01)
  • 'E' - Smoking (1/1/01)
  • 'F' - Eating (1/1/01)
  • 'G' - Children (1/1/01)
  • 'H' - Animal (1/1/01)
  • 'I' - Personal Hygiene (1/1/01)
  • 'J' - Reading (1/1/01)
  • 'K' - Other (1/1/01)
  • 'P' - Cell Phone (1/1/01, Value Prior To 7/03 Form Revision)
  • '-' - Not Stated

 


Cellphone Usage
SAS Name: CELPHONE

Definition: Usage of cellphone in the vehicle

Additional Information: Element added in 2002.

  • 'B' - Cell Phone In Use (4/1/01)
  • 'C' - Cell Phone Not In Use (4/1/01)
  • 'D' - No Cell Phone/Unknown (4/1/01)
  • '-' - Not Stated (4/1/01)
  • '1' - Cell Phone Handheld In Use (7/1/03)
  • '2' - Cell Phone Hands Free In Use (7/1/03)
  • '3' - Cell Phone Not In Use (7/1/03)

 


First Associated Factor
SAS Name: CONTRIB1
Second Associated Factor
SAS Name: CONTRIB2

Definition: Violation or factor contributing to the crash.

  • '1' - Under Influence of Alcohol
  • '2' - Following Too Closely
  • '3' - Failure to Yield
  • '4' - Improper Turn
  • '5' - Speeding
  • '6' - Other Violations (Hazardous)
  • '7' - Vision Obscured
  • 'A' - Vehicle Code Violation
  • 'B' - Other Improper Driving
  • 'C' - Other Than Driving
  • 'D' - Unknown
  • 'E' - Vision Obscurement
  • 'F' - Inattention
  • 'G' - Stop and Go Traffic
  • 'H' - Enter/Leave Ramp
  • 'I' - Previous Collision
  • 'J' - Unfamiliar With Road
  • 'K' - Defect Vehicle Equipment
  • 'L' - Uninvolved Vehicle
  • 'M' - Other
  • 'N' - None Apparent
  • 'O','S' - Runaway Vehicle
  • 'P' - Wind'
  • 'R' - Ramp Accident
  • '<','Z' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Vehicle Defect
SAS Name: DEFECT

Definition: Defect in the vehicle

Additional Information: Element added in 2002.

  • 'C' - Tire Defect/Fail
  • '<' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Direction of Travel
SAS Name: DIR_TRVL

Definition: Direction of travel of the vehicle

  • 'N' - North, Northeast, or Northwest Bound
  • 'S' - South, Southeast, or Southwest Bound
  • 'E' - Eastbound
  • 'W' - Westbound
  • '<' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Driver Age
SAS Name: DRV_AGE

Definition: The age of the driver of the vehicle involved in the crash.

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

 


Driver Extent of Injury
SAS Name: DRV_INJ

Definition: Extent of injury to the driver of the vehicle involved in crash.

  • '1' - Killed
  • '2' - Severe Injury
  • '3' - Other Visible Injury
  • '4' - Complaint-Pain
  • '0' - No Injury
  • Other - Error/Other Codes

 


Driver Race
SAS Name: DRV_RACE

Definition: Race of the driver/pedestrian involved in the crash.

Additional Information: Element added in 2002.

  • ' ' - Not Stated
  • 'A' - Asian
  • 'B' - Black
  • 'W' - White
  • 'H' - Hispanic
  • 'O' - Other

 


Driver Sex
SAS Name: DRV_SEX

Definition: Sex of the driver of the vehicle involved in crash.

  • 'M' - Male
  • 'F' - Female
  • '-' - Not Stated
  • Other - Error/Other Codes

 


Driver Safety Equipment
SAS Name: DRVREST1
Driver Safety Equipment
SAS Name: DRVREST2

Definition: Safety equipment used by the driver of the vehicle.

Additional Information: Element added in 2002.

  • 'A' - None in Vehicle
  • 'B' - Unknown
  • 'C' - Lap Belt Used
  • 'D' - Lap Belt Not Used
  • 'E' - Shoulder Harness Used
  • 'F' - Shoulder Harness Not Used
  • 'G' - Lap/Shoulder Harness Used
  • 'H' - Lap/Shoulder Harness Not Used
  • 'J' - Passive Restraint Used
  • 'K' - Passive Restraint Not Used
  • 'L' - Air Bag Deployed
  • 'M' - Air Bag Not Deployed
  • 'N' - Other
  • 'P' - Not Required
  • 'Q' - Child Restraint in Vehicle Used
  • 'R' - Child Restraint in Vehicle Not Used
  • 'S' - Child Restraint in Vehicle, Use Unknown
  • 'T' - Child Restraint in Vehicle, Improper Use
  • 'U' - No Child Restraint in Vehicle
  • 'V' - Driver, Motorcycle Helmet Not Used
  • 'W' - Driver, Motorcycle Helmet Used
  • 'X' - Passenger, Motorcycle Helmet Not Used
  • 'Y' - Passenger, Motorcycle Helmet Used
  • '-',' ' - Not Stated

 


Fuel Leaks and Fires
SAS Name: FIRE

Definition: Whether or not the crash resulted in a fire in this vehicle.

Additional Information: Element added in 2002.

  • 'B' - Fire Involved
  • '<' - Not Stated
  • '-' - Does Not Apply
  • 'Other' - Error/Other Codes

 


Hazardous Material
SAS Name: HAZ_CODE

Definition: Whether there was hazardous material in the vehicle

Additional Information: Element added in 2002.

  • 'A' - Hazardous Materials
  • '-' - Not Stated

 


Hazardous Material
SAS Name: HAZMAT

Definition: Whether or not the vehicle was carrying hazardous material when the crash occurred.

  • 'A' - Hazardous Material
  • '<' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Insurance
SAS Name: INSUR

Definition: Whether the vehicle was insured.

Additional Information: Element added in 2001.

  • 'N' - No Proof of Insurance Obtained
  • 'Y' - Yes, Proof Of Insurance Obtained
  • 'O' - Not Applicable (Used For Parked Cars, Bicyclists, Pedestrians, and Party Type Others)
  • 'E' - Used If the Officer Is Called Away From the Scene Of The Collision Prior To Obtaining The Insurance Information
  • ' ' - Not Stated

 


First Collision Location
SAS Name: LOC_TYP1
Second Collision Location
SAS Name: LOC_TYP2
Third Collision Location
SAS Name: LOC_TYP3
Fourth Collision Location
SAS Name: LOC_TYP4

Definition: Location of each collision for the vehicle

  • 'A' - Beyond Median Or Barrier Stripe - Driver's Left
  • 'B' - Beyond Shoulder - Driver's Left
  • 'C' - Left Shoulder Area
  • 'D' - Left Lane
  • 'E' - Interior Lanes
  • 'F' - Right Lane
  • 'G' - Right Shoulder Area
  • 'H' - Beyond Shoulder - Driver's Right
  • 'I' - Gore Area
  • 'J' - Other
  • '<' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Vehicle Make
SAS Name: MAKE

Definition: Make of the vehicle involved in the crash.

  • '01' - American Motors
  • '02' - Buick
  • '03' - Cadillac
  • '04' - Chevrolet
  • '05' - Chrysler
  • '06' - Dodge
  • '08' - Ford
  • '09' - GMC
  • '10' - Imperial
  • '11' - Lincoln
  • '12' - Mercury
  • '14' - Oldsmobile
  • '16' - Plymouth
  • '17' - Pontiac
  • '18' - Studebaker
  • '30' - Other Domestic
  • '51' - Datsun
  • '52' - Fiat
  • '53' - Mercedes-Benz
  • '54' - MG
  • '55' - Opel
  • '56' - Renault
  • '57' - Triumph
  • '58' - Toyota
  • '59' - Volkswagen
  • '60' - Volvo
  • '61' - Honda
  • '62' - Mazda
  • '63' - Audi
  • '64' - BMW
  • '65' - Porsche
  • '66' - Subaru
  • '70' - Other Foreign
  • '98' - Ped, Bike, Other
  • '99' - Trk N/Pickup
  • Other - Error/Other Codes

 


Movement Preceding Accident
SAS Name: MISACT1

Definition: Movement of this vehicle preceding the crash

  • 'A' - Stopped
  • 'B' - Proceeding Straight
  • 'C' - Ran Off Road
  • 'D' - Making Right Turn
  • 'E' - Making Left Turn
  • 'F' - Making U Turn
  • 'G' - Backing
  • 'H' - Slowing, Stopping
  • 'I' - Passing Other Vehicle
  • 'J' - Changing Lanes
  • 'K' - Parking Maneuver
  • 'L' - Entering Traffic From Shoulder, Median, Parking Strip Or Private Drive
  • 'M' - Other Unsafe Turning
  • 'N' - Crossed Into Opposing Lane
  • 'O' - Parked
  • 'P' - Merging
  • 'Q' - Traveling Wrong Way
  • 'R' - Other
  • '<' - Not Stated

Pedestrians

  • '1' - No Pedestrian Involved
  • '2' - Crossing In Crosswalk at Intersection
  • '3' - Crossing In Crosswalk Not At Intersection
  • '4' - Crossing - Not In Crosswalk
  • '5' - In Roadway - Include Shoulder
  • '6' - Not In Roadway
  • '7' - Approaching/Leaving School Bus
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Total Number Injured
SAS Name: NUM_INJ

Definition: Total number of occupants injured in this vehicle (including fatal injuries).

  • 0 - 0
  • 1 - 1
  • 2 - 2
  • 3 - 3
  • 4 - 4
  • 5 - 5
  • 6-99 - > 5
  • Other - Error/Other Codes

 


Total Number Killed
SAS Name: NUM_KILL

Definition: Total number of persons killed in the vehicle

  • 0 - 0
  • 1 - 1
  • 2 - 2
  • 3 - 3
  • 4 - 4
  • 5 - 5
  • 6-99 - > 5
  • Other - Error/Other Codes

 


First Object Struck
SAS Name: OBJECT1
Second Object Struck
SAS Name: OBJECT2
Third Object Struck
SAS Name: OBJECT3
Fourth Object Struck
SAS Name: OBJECT4

Definition: Type of object struck by this vehicle.

Additional Information: Category 51 added in 1996. In 1996, "Crash Cushion" was separated into two codes (45) "Crash Cushion-Sand" and (46) "Crash Cushion-Other".

  • '01' - Side of Bridge Railing
  • '02' - End Of Bridge Railing
  • '03' - Pier, Column or Abutment of Bridge
  • '04' - Bottom of Bridge Structure
  • '05' - Bridge End Post in Gore
  • '06' - End Of Guardrail (New Code - 1992)
  • '07' - Bridge Approach Guardrail (New - 1992)
  • '10' - Light or Signal Pole
  • '11' - Utility Pole
  • '12' - Pole - Type Not Stated
  • '13' - Traffic Sign or Sign Post
  • '14' - Other Signs (Not Traffic)
  • '15' - Guardrail
  • '16' - Barrier
  • '17' - Wall (Concrete or Wood - Not Median Barrier)
  • '18' - Dike or Curb (Including Curb Of Median & A.C. Berm)
  • '19' - Traffic Island (Not Curbed Median Separation)
  • '20' - Raised Bars
  • '21' - Concrete Object (Hdwl, D.I., Etc.)
  • '22' - Guidepost, Culvert or Mile Post Marker
  • '23' - Cut Slope or Embankment, Struck From Below
  • '24' - Over Embankment
  • '25' - In Water (River, Lake, Canal)
  • '26' - Drainage Ditch (With or Without Water)
  • '27' - Fence
  • '28' - Trees
  • '29' - Plants (Miscellaneous)
  • '30' - Sound Walls
  • '40' - Rocks, Fallen Trees, Snowbank in Roadway, Tree Overhead, Falling Trees or Other Natural Material on Road
  • '41' - Temporary Barricades, Cones or Signs
  • '42' - Other Object On Road
  • '43' - Other Object Off Road
  • '44' - Overturned
  • '45' - Crash Cushion-Sand
  • '46' - Crash Cushion-Other
  • '51' - Call Box
  • '98' - Unknown Object Involved
  • '99' - No Object Involved
  • 'V1'-'V9' - Vehicle 1 to 9
  • '<<' - Not Stated
  • '--' - Does Not Apply
  • Other - Error/Other Codes

 


Party Type
SAS Name: PART_TYP

Definition: Type of party in the vehicle.

  • '1' - Driver
  • '2' - Passenger (Includes Non-Operator On Bicycle or Any Victim On/In Parked Vehicle, or Multiple Victims On/In Non-Motorized Vehicle)
  • '3' - Pedestrian
  • '4' - Bicyclist
  • '5' - Other (Single Victim On/In Non-Motor Vehicle, E.G., Ridden Animal, Horse-Drawn Carriage, Train, or Building)
  • Other - Error/Other Codes

 


Driver Physical Condition
SAS Name: PHYSCOND

Definition: Physical condition of the driver when the crash occurred.

  • 'E' - Under Drug Influence
  • 'F' - Other Physical Impairment
  • 'H' - Not Applicable
  • 'I'vSleepy or Fatigued
  • '-' - Not Stated

 


Highway Type Indicator
SAS Name: RTE_TYPE

Definition: Highway type indicator.

Additional Information: This element is not reliable for at least part of 1991-94. There were programming errors in the data coding/storage efforts.

  • '1' - On State Route
  • '2' - Not On State Route
  • '3' - Intersecting State Route
  • '-' - Does Not Apply
  • '<' - Not Stated
  • Other - Error/Other Codes

 


School Bus Involvement
SAS Name: SCHLBUS

Definition: Whether or not a school bus was involved in the accident.

Additional Information: Element added in 2002.

  • 'E' - School Bus Related (1/1/02)
  • '-' - Not Stated (1/1/02)

 


Sobriety
SAS Name: SOBRIETY

Definition: Sobriety of the driver of this vehicle

  • 'A' - Had Not Been Drinking
  • 'B' - Had Been Drinking, Under Influence
  • 'C' - Had Been Drinking, Not Under Influence
  • 'D' - Had Been Drinking, Impairment Unknown
  • 'E' - Under Drug Influence
  • 'F' - Other Physical Impairment
  • 'G' - Impairment Unknown
  • 'H' - Not Applicable
  • 'I' - Fatigue
  • '-','<' - Not Stated/Does Not Apply
  • Other - Error/Other Codes

 


Special Information
SAS Name: SPEC_INF

Definition: Special information of the vehicle

Additional Information: Element added in 2002.

  • 'A' - Hazardous Material
  • 'B' - Cell Phone in Use
  • 'C' - Cell Phone Not in Use
  • 'D' - Cell Phone None/Unknown
  • '<' - Not Stated'
  • '-' - Does Not Apply

 


Violation Suffix
SAS Name: SUB_VIOL

Definition: Violation suffix of the vehicle.

Additional Information: Element added in 2002.* Inattention Codes Eff. 01-01-01.

  • 1 - Influence of Alcohol
  • 2 - Following Too Close
  • 3 - Failure to Yield
  • 4 - Improper Turn
  • 5 - Speeding
  • 6 - Other Violations
  • A - Cell Phone* (Inattn)
  • B - Electronic Equip* (Inattn)
  • C - Radio/Cd/Headphn* (Inattn)
  • D - Smoking* (Inattn)
  • E - Vision Obscurement
  • F - Inattention - Other
  • G - Stop & Go Traffic
  • H - Enter/Leave Ramp
  • I - Previous Collision
  • J - Unfamiliar With Road
  • K - Defective Veh. Equipment
  • L - Uninvolved Vehicle
  • M - Other
  • N - None Apparent
  • P - Wind
  • R - Ramp Accident
  • S - Runaway Vehicle
  • T - Eating* (Inattn)
  • U - Children* (Inattn)
  • V - Animals* (Inattn)
  • W - Personal Hygiene* (Inattn)
  • X - Reading* (Inattn)
  • < - Not Stated
  • - - Does Not Apply

 


Trailer Code
SAS Name: TRAIL_CODE

Definition: Trailer code of the vehicle.

Additional Information: Element added in 2003.

  • 'G' - 32 Ft Trailer Combo (1/1/03)
  • '-' - Not Stated

 


Truck Code
SAS Name: TRK_CODE

Definition: Truck code of the vehicle.

Additional Information: Element added in 2003.

  • 'F' - 75 Ft Motortruck Combo (1/1/03)
  • '-' - Not Stated

 


Vehicle at Fault
SAS Name: VEH_AT_FAULT

Definition: Whether this vehicle was at fault

Additional Information: This element contains different data from the one that appears with the Accident File. This element was added in 2001.

  • 'Y' - Yes
  • 'N' - No

 


Vehicle Number
SAS Name: VEHNO

Definition: Relative vehicle number.

  • 0 - Not Stated
  • 1 - Vehicle One
  • 2 - Vehicle Two
  • 3 - Vehicle Three
  • 4 - Vehicle Four
  • 5 - Vehicle Five
  • 6 - Vehicle Six
  • 7 - Vehicle Seven
  • 8 - Vehicle Eight
  • 9 - Vehicle Nine

 


Vehicle Type
SAS Name: VEHTYPE

Definition: Type of vehicle involved in the crash.

  • 'A' - Passenger Car (Includes Station Wagon)
  • 'B' - Passenger Car With Trailer
  • 'C' - Motorcycle
  • 'D' - Pickup or Panel Truck
  • 'E' - Pickup or Panel Truck With Trailer
  • 'F' - Truck or Truck Tractor
  • 'G' - Truck or Truck Tractor With 1 Trailer
  • '2' - Truck or Truck Tractor With 2 Trailers
  • '3' - Truck or Truck Tractor With 3 Trailers
  • '4' - Single Unit Tanker
  • '5' - Truck/Trailer and 1 Tank Trailer
  • '6' - Truck/Trailer and 2 Tank Trailers
  • 'H' - School Bus
  • 'I' - Other Bus
  • 'J' - Emergency Vehicle
  • 'K' - Highway Construction Equipment
  • 'L' - Bicycle
  • 'M' - Other Motor Vehicle
  • 'N' - Other Non-Motor Vehicle
  • 'O' - Spilled Loads
  • 'P' - Disengaged Tow
  • 'Q' - Uninvolved Vehicle
  • 'R' - Moped
  • 'S' - Runaway Vehicle
  • 'T' - Train
  • 'U' - Pedestrian
  • 'V' - Dismounted Pedestrian
  • 'W' - Animal - Livestock
  • 'X' - Animal - Deer
  • 'Z' - Animal - Other
  • '<' - Not Stated
  • '-' - Does Not Apply
  • Other - Error/Other Codes

 


Vehicle Model Year
SAS Name: VEHYR

Definition: Model year of the vehicle involved in the crash.

Additional Information: There will be some invalid codes which appear valid (e.g., a “1999” vehicle in a 1997 crash – when “1999” should only be valid for 1998 and later crash years).

  • '1901'-'1979' - 1901 - 1979'
  • '1980'-'1989' - 1980 - 1989'
  • '1990'-'1999' - 1990 - 1999'
  • '2000'-'2099' - >= 2000'
  • 'Bike' - Ped, Bike/Ns'
  • Other - Error/Other Codes'

 


Violation Category
SAS Name: VIOL

Definition: Category of violation for the vehicle.

  • '00' - Not Stated
  • '01' - Under Influence in Public
  • '02' - County Ordinance
  • '03' - City Ordinance
  • '05' - Business/Professions Code
  • '06' - Felony (Not 15)
  • '08' - Controlled Substances
  • '09' - Health/Safety Code Not Otherwise Classified
  • '10' - Penal Code Not Otherwise Classified
  • '11' - Streets/Highways Code
  • '13' - Welfare/Institutions Code
  • '15' - Manslaughter
  • '16 - Other Code (Obsolete)
  • '19' - Hit and Run
  • '20' - Driving (Or Bicycling) Under Influence of Alcohol and/or Drug
  • '21' - Improper Lane
  • '22' - Impeding Traffic
  • '23' - Failure to Heed Stop Signal
  • '24' - Failure to Heed Stop Sign
  • '25' - Unsafe Speed
  • '26' - Reckless Driving
  • '27' - Wrong Side of Road
  • '28' - Unsafe Lane Change
  • '29' - Improper Passing
  • '30' - Following Too Closely
  • '31' - Improper Turning
  • '33' - Automobile Right-Of-Way
  • '34' - Pedestrian Right-Of-Way
  • '35' - Pedestrian Violation
  • '37' - Driving Under Influence of Drug
  • '38' - Hazardous Parking
  • '39' - Lights
  • '40' - Brakes
  • '43' - Other Equipment
  • '44' - Other Hazardous Movement
  • '46' - Improper Registration
  • '47' - Other Non-Moving Violation
  • '48' - Excessive Smoke
  • '49' - Excessive Noise
  • '50' - Overweight
  • '51' - Oversize
  • '52' - Over Maximum Speed
  • '53' - Unsafe Starting or Backing
  • '60' - Off-Highway Vehicle Violation
  • '61' - Child Restraint Violation
  • '62' - Seat Belt Violation (Non-Use)
  • '63' - Seat Belt Equipment Violation

 


CADMV Vehicle Violation Codes
SAS Name: VIOLS

Definition: California Department of Motor Vehicles violations codes for this vehicle.

Additional Information: Element added in 1998. Element values represent the CADMV vehicle violations codes. Refer to CADMV vehicle violations website for formats.

 


Vehicle Towed
SAS Name: VTOWED

Definition: Whether the vehicle was towed after the crash.

Additional Information: Element added in 2001.

  • '28' - Semi-Tank Trailer
  • '29' - Pull-Tank Trailer
  • '30' - Two-Tank Trailer
  • '31' - Semi-Trailer
  • '32' - Pull Trailer (Includes Dolly)
  • '33' - Two Trailers (Or 31 + 32)
  • '34' - Boat Trailer
  • '35' - Utility Trailer
  • '36' - Trailer Coach
  • '37' - Extralegal Permit Load
  • '38' - Pole, Pipe, Or Logging Dolly
  • '39' - Three Trailers (Or 31 + 33)
  • '40' - Federally Legal Semi-Trailer
  • '52' - Federally Legal Double Cargo Combo (Over 75 Ft)
  • '53' - Fifth Wheel Trailer
  • '54' - Container Chassis

 

Vehicle Towing
SAS Name: VTOWING

Definition: What was being towed by this vehicle.

Additional Information: Element added in 2001.

  • 01' - Passenger Car, Station Wagon, or Jeep
  • '02'  - Motorcycle
  • '03' - Motor-Driven Cycle (< 15 HP)
  • '04' - Bicycle
  • '05'  - Motorized Bicycle
  • '06' - All-Terrain Vehicle (ATV)
  • '07' - Sport Utility Vehicle
  • '08' - Minivan
  • '09' - Paratransit Bus
  • '10' - Tour Bus
  • '11' - Other Commercial Bus
  • '12' - Non-Commercial Bus
  • '13' - Schoolbus Without Pupil Passengers
  • '14' - Schoolbus Public I
  • '15' - Schoolbus Public II
  • '16' - Schoolbus Private I
  • '17' - Schoolbus Private II
  • '18' - Schoolbus Contractual I
  • '19' - Schoolbus Contractual II
  • '20' - Public Transit Authority
  • '21' - Two-Axle Tank Truck
  • '22' - Pickup or Panel Truck
  • '23' - Pickup Truck With Camper
  • '24' - Three-Axle Tank Truck
  • '25' - Truck Tractor
  • '26' - Two-Axle Truck
  • '27' - Three-Axle Truck
  • '41' - Ambulance
  • '42' - Dune Buggy
  • '43' - Fire Truck (Not Rescue)
  • '44' - Forklift
  • '45' - Highway Construction Equipment (Only While Not In Construction Area)
  • '46' - Implement Of Husbandry
  • '47' - Motor Home (40 Ft or Less)
  • '48' - CHP, Police, Or Sheriff Car (Emergency Service or Not)
  • '49' - CHP, Police, Or Sheriff Motorcycle (Emergency Service or Not)
  • '50' - Mobile Equipment51 - Farm Labor Vehicle (Certified)
  • '55' - Two-Axle Tow Truck
  • '56' - Three-Axle Tow Truck
  • '57' - Farm Labor Vehicle (Non-Certified)
  • '58' - Farm Labor Transporter
  • '59' - Motorhome (Over 40 Ft)
  • '60' - Pedestrian (Includes Motorized Wheelchair)
  • '61' - School Pupil Activity Bus I (Prior To 2002)
  • '62' - School Pupil Activity Bus Ii (Prior To 2002
  • '63' - Youth" Bus
  • '64' - School Pupil Activity Bus I (Eff. 2002)
  • '65' - School Pupil Activity Bus Ii (Eff. 2002)
  • '71' - Passenger Car - Hazardous Materials Only
  • '72' - Pickups and Panels - Hazardous Materials Only
  • '73' - Pickups and Campers - Hazardous Materials Only
  • '75' - Truck Tractor - Hazardous Materials Only
  • '76' - Two-Axle Truck - Hazardous Materials Only
  • '77' - Three or More Axle Truck - Hazardous Materials Only
  • '78' - Two-Axle Tank Truck - Hazardous Materials Only
  • '79' - Three-Axle Tank Truck - Hazardous Materials Only
  • '81' - Passenger Car - Hazardous Waste or Waste/Material Combo
  • '82' - Pickups and Panels - Hazardous Waste or Waste/Material Combo
  • '83' - Pickups and Campers - Hazardous Waste or Waste/Material Combo
  • '85' - Truck Tractor - Hazardous Waste or Waste/Material Combo
  • '86' - Two-Axle Truck - Hazardous Waste or Waste/Material Combo
  • '87' - Three or More Axle Truck - Hazardous Waste or Waste/Material Combo
  • '88' - Two-Axle Tank Truck - Hazardous Waste or Waste/Material Combo
  • '89' - Three-Axle Tank Truck - Hazardous Waste or Waste/Material Combo
  • '94' - Motorized Transportation Device
  • '95' - Miscellaneous Non-Motorized Vehicle (Ridden Animal, Animal-Drawn Conveyance, Train, or Building) With Victim
  • '96' - Miscellaneous Motorized Vehicle (Golf Cart)
  • '97' - Low Speed Vehicle
  • '99','-' - Not Stated or Unknown (Hit And Run)

 

Occupant Subfile

List of Elements for the CA Occupant Subfile

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
ACCYR COLLISION ACCYR Occupant CHA(4) 85
AGE OCCUPANT AGE Occupant NUM 85
CASENO UNIQUE ACCIDENT CASEO Occupant CHA(21) 85
EJECT EJECTED FROM VEHICLE Occupant CHA(1) 86
INJ DRV/OCC INJURY Occupant CHA(1) 86
OCCNUM OCCUPANT NUMBER Occupant NUM 86
OCC_TYP OCCUPANT TYPE Occupant CHA(1) 87
REST1 SAFETY EQUIPMENT Occupant CHA(1) 88
REST2 SAFETY EQUIPMENT Occupant CHA(1) 88
SEATPOS SEATING POSTION Occupant CHA(1) 89
SEX OCCUPANT SEX Occupant CHA(1) 89
VEHNO VEHICLE NUMBER Occupant NUM 90

Collision ACCYR
SAS Name: ACCYR

Definition: Year accident occurred.

Additional Information: Year of accident (YYYY). Element discontinued in 2000.

 


Occupant Age
SAS Name: AGE

Definition: Age of the injured/killed occupant.

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

 


Case Number
SAS Name: CASENO

Definition: Accident case number.

Additional Information: The first 4 digits show the accident year.

 


Eject From Vehicle
SAS Name: EJECT

Definition: Whether or not occupant was ejected when the crash occurred.

Additional Information: Approximately 10% of the cases are "unknown." This is not unusual given the nature of this variable and the fact that it may not appear on all police forms in California.

  • '0' - Not Ejected
  • '1' - Fully Ejected
  • '2' - Partially Ejected
  • '3' - Unknown
  • Other - Error/Other Codes

 


Driver/Occupant Injury
SAS Name: INJ

Definition: Severity of injuries sustained in the crash by occupant.

  • '1' - Killed (Died No Later Than 30 Days After Collision)
  • '2' - Severe Injury
  • '3' - Other Visible Injury
  • '
  • 4' - Complaint of Pain
  • '0' - Non-Injury (PDO) Crash

 


Occupant Number
SAS Name: OCCNUM

Definition: Number of this occupant

Additional Information: Element discontinued in 2000.

  • 0 - 0
  • 1 - 1
  • 2 - 2
  • 3 - 3
  • 4 - 4
  • 5 - 5
  • 6-99 - > 5
  • Other - Error/Other Codes

 


Occupant Type
SAS Name: OCC_TYP

Definition: Type of occupant.

Additional Information: Note that codes 1-5 are for injured occupants only. Code 6 includes all uninjured (non-driver) occupants and users.

  • '1' - Driver
  • '2' - Passenger (Includes Non-Operator on Bicycle or Any Victim On/In Arked Vehicle, or Multiple Victims On/In Non-Motorized Vehicle)
  • '3' - Pedestrian
  • '4' - Bicyclist
  • '5' - Other (Single Victim On/In Non-Motor Vehicle, E.G., Ridden Animal, Horse-Drawn Carriage, Train, or Building)

  • '6' - Non-Inj Party
  • Other - Error/Other Codes

 


Safety Equipment
SAS Name: REST1
Safety Equipment
SAS Name: REST2

Definition: Safety equipment used by occupant.  

Additional Information: Restraint information for drivers is for injured drivers only. As with all States, the data for restraint use is somewhat questionable given that it is not observed by the officer. REST2 is a new element that was added in 2001.

  • 'A' - None in Vehicle
  • 'B' - Unknown
  • 'C' - Lap Belt Used
  • 'D' - Lap Belt Not Used
  • 'E' - Shoulder Harness Used
  • 'F' - Lap/Shoulder Harness Not Used
  • 'G' - Lap/Shoulder Harness Used
  • 'H' - Lap/Shoulder Harness Not Used
  • 'J' - Passive Restraint Used
  • 'K' - Passive Restraint Not Used
  • 'L' - Air Bag Deployed
  • 'M' - Air Bag Not Deployed
  • 'N' - Other
  • 'P' - Not Required

Child Restraint

  • 'Q' - In Vehicle Used
  • 'R' - In Vehicle Not Used
  • 'S' - In Vehicle Use Unknown
  • 'T' - In Vehicle Improper Used
  • 'U' - None in Vehicle

M/C Helmet-Driver

  • 'V' - Driver - No Motorcycle Helmet
  • 'W' - Driver - Motorcycle Helmet In Use

M/C Helmet-Passenger

  • 'X' - Mc Passenger - No Motorcycle Helmet
  • 'Y' - Mc Passenger - Motorcycle Helmet In
  • '-',' ' - Not Stated

 


Seating Position
SAS Name: SEATPOS

Definition: Occupant position in vehicle when the crash occurred.

Additional Information: The data in this element is somewhat different from similar data in the OCC_TYP (Occupant Type) element. This is due to the fact that the Occupant Type element combines all uninjured occupants into one code, and that while report forms used by California cities all contain some type of information on drivers and the number of occupants, all do not contain a variable related to seating position.

  • '1' - Driver
  • '2'-'6' - Passengers
  • '7' - Stat Wagon Rear
  • '8' - Rear Occ Trr/Van
  • '9' - Position Unknown
  • '0' - Other Occupants
  • Other - Error/Other Codes

 


Occupant Sex
SAS Name: SEX

Definition: Sex of injured/killed occupant.

  • 'M' - Male
  • 'F' - Female
  • '-' - Not Stated
  • Other - Error/Other Codes

 


Vehicle Number
SAS Name: VEHNO

Definition: Vehicle number for occupant’s vehicle.

  • 0 - Not Stated
  • 1 - Vehicle One
  • 2 - Vehicle Two
  • 3 - Vehicle Three
  • 4 - Vehicle Four
  • 5 - Vehicle Five
  • 6 - Vehicle Six
  • 7 - Vehicle Seven
  • 8 - Vehicle Eight
  • 9 - Vehicle Nine

 

List of Elements for California Roadlog File

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
AADT AADT Road NUM 94
ACC_DTE ACCESS CONTROL DATE Road CHA(8) 94
ACC_HIST ACCESS CONTROL HISTORY Road CHA(1) 94
ACCESS ACCESS CONTROL Road CHA(1) 95
ADT_DTE ADT DATE Road CHA(8) 95
ADT_DVM DAILY VEHICLE MILES(DVM) Road NUM 95
ADT_HST ADT HISTORY Road CHA(1) 95
ADT_MSG ALPHA MESSAGE Road CHA(4) 95
ADT_STUS ADT STATUS PROFILE Road CHA(1) 96
BEGMP POSTMILE-BEGMP Road NUM 96
CITY CITY Road CHA(2) 96
CNTYRTE ROAD COUNTY ROUTE Road CHA(10) 96
COUNTY COUNTY Road CHA(2) 96
CURB1 CURB AND LANDSCAPE Road CHA(1) 97
DES_NBR ROAD DESC NUMBER Road CHA(1) 97
DESG_SPD DESIGN SPEED Road CHA(1) 97
DISTRICT DISTRICT Road CHA(2) 98
DIVIDED DIVIDED HIGHWAY Road NUM 98
ENDMP POSTMILE + SEG_LNG Road NUM 98
FEAT_LF LEFT RDBD SPECIAL FEATURE Road CHA(1) 99
FEAT_RG RIGHT RDBD SPECIAL FEATURE Road CHA(1) 99
FED_AID FEDERAL AID (IN LIEU) Road CHA(1) 100
FED_PREF FEDERAL AID RTE PREFIX Road CHA(1) 100
FED_RTE FEDERAL AID RTE Road CHA(3) 100
FILETYP FILE TYPE Road CHA(1) 101
FUNC_CLS FUNCTIONAL CLASS Road CHA(1) 101
HIST_ADD HISTORY ELEMENTS RELATIVE ADDR Road NUM 101
HWY_GRP HIGHWAY GROUP Road CHA(1) 102
INS_OTS INSIDE OUTSIDE CITY Road CHA(1) 102
LANEWID AVERAGE LANE WIDTH Road NUM 103
LSHL_WD2 LEFT SHOULDER WIDTH RD2 Road NUM 103
LSHLDWID LEFT SHOULDER WIDTH RD1 Road NUM 103
LST_SEG_CHG_DT DATE OF LAST CHANGE DATE Road NUM 103
LTRD_DTE LEFT ROADBED DATE Road CHA(8) 104
LTRD_HST LEFT ROADBED HISTORY Road CHA(1) 104
MAINT_LEVL MAINTENANCE LEVEL SERVICE CODE Road CHA(1) 104
MED_DTE RAMP MEDIAN DATE Road CHA(8) 104
MED_HIST MEDIAN HISTORY Road CHA(1) 104
MED_TYPE MEDIAN TYPE Road CHA(1) 105
MED_VAR MEDIAN VARIANCE Road CHA(1) 105
MEDBARTY MEDIAN BARRIER TYPE Road CHA(1) 106
MEDWID MEDIAN WIDTH Road NUM 107
MVMT MILLION VEHICLE MILES Road NUM 107
NA_MILE NON-ADD MILEAGE Road CHA(1) 107
NAT_LND NATIONAL LANDS Road CHA(1) 108
NO_LANE1 NUMBER OF LANES RD1 Road NUM 108
NO_LANE2 NUMBER OF LANES RD2 Road NUM 108
NO_LANES TOTAL NUMBER OF LANES Road NUM 108
PAV_WDL LEFT PAVED SHLD WDTH RD1 Road NUM 109
PAV_WDL2 LEFT PAVED SHLD WIDTH RD2 Road NUM 109
PAV_WDR2 RIGHT PAVED SHLD WIDTH RD2 Road NUM 109
PAV_WIDR RIGHT PAVED SHLD WDTH RD1 Road NUM 109
PSMILPRF POSTMILE PREFIX Road CHA(1) 110
PSMILSUF POSTMILE SUFFIX Road CHA(1) 111
RD_DATE ROAD DATE Road CHA(8) 111
RD_DESC ROAD DESCRIPTION Road CHA(25) 111
RECTYPE RECORD TYPE Road CHA(1) 111
RGRD_DTE RIGHT ROADBED DATE Road CHA(8) 111
RGRD_HSR RIGHT ROADBED HISTORY Road CHA(1) 112
RO_SEQ ROUTE ORDER SEQUENCE Road NUM 112
RODWYCLS ROADWAY CLASSIFICATION Road CHA(2) 112
RSHL_WD2 RIGHT SHOULDER WIDTH RD2 Road NUM 113
RSHLDWID RIGHT SHOULDER WIDTH RD1 Road NUM 113
RTE_NBR RDWAY ROUTE NUMBER Road CHA(3) 113
RTE_SUF RDWAY ROUTE SUFFIX Road CHA(1) 113
RU_IO RURAL/URBAN INSIDE OUTSIDE CITY Road CHA(1) 114
RURURB RURAL URBAN Road CHA(1) 115
SCN_FRWY SCENIC FREEWAY Road CHA(1) 115
SEG_LNG SECTION LENGTH Road NUM 115
SURF_TY2 SURFACE TYPE RD2 Road CHA(1) 116
SURF_TYP SURFACE TYPE RD1 Road CHA(1) 116
SURF_WD2 TRAVELED-WAY WIDTH RD2 Road NUM 117
SURF_WID TRAVELED-WAY WIDTH RD1 Road NUM 117
TERRAIN TERRAIN Road CHA(1) 117
TOLL TOLL AND FOREST RDS Road CHA(1) 117
TRK2AX 2-AXLE TRUCK AADT Road NUM 118
TRK3AX 3-AXLE TRUCK AADT Road NUM 118
TRK4AX 4-AXLE TRUCK AADT Road NUM 118
TRK5AX 5+-AXLE TRUCK AADT Road NUM 118
TRKCNTFL TRUCK COUNT FLAG Road CHA(1) 119
TRKTOT TOTAL TRUCK AADT Road NUM 119

AADT
SAS Name: AADT

Definition: Calculated average AADT

  • 0 - 0
  • 1-100 - 1-100
  • 101-500 - 101-500
  • 501-1000 - 501-1,000
  • 1001-2000 - 1,001-2,000
  • 2001-5000 - 2,001-5,000
  • 5001-10000 - 5,001-10,000
  • 10001-15000 - 10,001-15,000
  • 15001-20000 - 15,001-20,000
  • 20001-40000 - 20,001-40,000
  • 40001-999999 - >= 40,001
  • . - No Data

 


Access Control Date
SAS Name: ACC_DTE

Definition: Date when the accident occurred.

Additional Information: Date of last change in some element related to access control (YYYYMMDD). See discussion.

 


Access Control History
SAS Name: ACC_HIST

Definition: Change in access control information for the roadway segment

Additional Information: A “flag” indicating a change in some element related to access-control. See discussion.

 


Access Control
SAS Name: ACCESS

Definition: Control of access.

  • 'C' - Conventional - No Access Control
  • 'E' - Expressway - Partial Access Control
  • 'F' - Freeway - Full Access Control
  • 'S' - One-Way City Street - No Access Control
  • -' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 

ADT Date
SAS Name: ADT_DTE

Definition: ADT date of the roadway segment.

Additional Information: Date of last change in some element related to ADT (YYYYMMDD). See Discussion. Element discontinued in 2003.

 


Daily Vehicle Miles
SAS Name: ADT_DVM

Definition: Daily vehicle miles of travel for the roadway segment

Additional Information: Element discontinued in 2003.

 


ADT History
SAS Name: ADT_HIST

Definition: Change in ADT information for the roadway segment.

Additional Information: A “flag” indicating a change in some variable related to ADT. See Discussion. Element discontinued in 2003.

 


Alpha Message
SAS Name: ADT_MSG

Definition: Alpha message of the roadway segment.

Additional Information: All miles are blank. Element discontinued in 2003.

 


ADT Status Profile
SAS Name: ADT_STUS

Definition: ADT status profile

  • 'P' - ADT Provided
  • 'S' - ADT Calculated
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Postmile-BEGMP
SAS Name: BEGMP

Definition: Calculated begin milepost.

Additional Information: Beginning milepoint in miles (XXX.XXX)

 


City
SAS Name: CITY

Definition: City where the crash occurred.

Additional Information: Please contact HSIS for formats information.

 


Road County Route
SAS Name: CNTYRTE

Definition: County route of the roadway segment.

Additional Information: Linkage element, consisting of DISTRICT+RTE_NBR+RTE_SUF+COUNTY+PSMILPRF+HWY_GRP.

 


County
SAS Name: COUNTY

Definition: County where the crash occurred.

Additional Information: See listings under accident section of the guidebook.

 


Curb and Landscape
SAS Name: CURB1

Definition: Presence and location of curbs.

  • '1' - Curb Median
  • '2' - Curb Med W/Trees
  • '3' - Curb Med W/Shrub
  • '4' - Raised Traff Bar
  • '5' - Median W/Trees
  • '6' - Median W/Shrubs
  • '7' - N/Curbs/Shrubs
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Road DESC Number
SAS Name: DES_NBR

Definition: Description record number of the roadway segment.

Additional Information: Zero = no added description records, (1-9) = added description records. Element discontinued in 2003.

 


Design Speed
SAS Name: DESG_SPD

Definition: Design speed of the roadway segment.

  • 25 - < 30 MPH
  • 30 - 30 MPH
  • 35 - 35 MPH
  • 40 - 40 MPH
  • 45 - 45 MPH
  • 50 - 50 MPH
  • 55 - 55 MPH
  • 60 - 60 MPH
  • 65 - 65 MPH
  • 70 - > 70 MPH

 


District
SAS Name: DISTRICT

Definition: District of roadway segment.

  • '01' - District One
  • '02' - District Two
  • '03' - District Three
  • '04' - District Four
  • '05' - District Five
  • '06' - District Six
  • '07' - District Seven
  • '08' - District Eight
  • '09' - District Nine
  • '10' - District Ten
  • '11' - District Eleven
  • '12' - District Twelve
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Divided Highway
SAS Name: DIVIDED

Definition: Whether the highway is divided or not.

Additional Information: Based on MED_TYPE.

  • 1 - Divided
  • 0 - Not Divided
  • Other - Error/Other Codes

 


Postmile + SEG_LNG
SAS Name: ENDMP

Definition: Calculated ending milepost.

Additional Information: Ending milepost in miles, based on BEGMP + SEG_LNG (XXX.XXX).

 


Left Road Border Special Feature
SAS Name: FEAT_LF
Right Road Border Special Feature
SAS Name: FEAR_RG

Definition: Special feature of left/right roadbed.

Additional Information: Unlike most of the other surface and width descriptor elements, these elements are keyed to the "roadbed" rather than the roadway. For undivided roadways, the "right" element concerns the right "half" of the total roadway. The "left" element concerns the left "half." For undivided roads with auxiliary lanes, the lanes will be referenced to the right "half." For divided roadways, the "right" element concerns roadway 1, the right-hand roadway in the direction of inventory (usually north or east). The "left" element concerns roadway 2.

  • 'A' - One Lane Road With Turnouts For Passing
  • 'B' - Lane Transitions
  • 'C' - Passing or Truck Climbing Lane
  • 'D' - Bus Lane
  • 'E' - Auxiliary Lane (Included in No. Lanes Field)
  • 'F' - Auxiliary Lanes (Included in No. Lanes Field)
  • 'G' - Tunnel
  • 'H' - Toll Plaza and Approaches
  • 'J' - "Bug" Or Border Patrol Station
  • 'K' - Bottom Deck of Two-Deck Structure
  • 'L' - Top Deck of Two-Deck Structure
  • 'M' - Construction Zone Open To Traffic
  • 'N' - Median Lane Is HOV Lane
  • 'P' - Median Lanes Are HOV Lanes
  • 'Q' - Reversible Peak-Hour Lane(s)
  • 'Z' - No Special Feature
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Federal Aid
SAS Name: FED_AID

Definition: Presence and type of federal aid for this route segment.

  • '0' - None
  • '2' - In Lieu Interst
  • '3' - In Lieu Primary
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Federal Aid Route Prefix
SAS Name: FED_PREF

Definition: Federal aid route prefix.

  • '$' - No Federal Aid
  • 'I' - Interstate
  • 'P' - Primary
  • '5' - Fas or Fau – Final Alignment
  • '6' - Fas/Fau - Not Final Alignment
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Federal Aid Route
SAS Name: FED_RTE

Definition: Whether the segment is on a federal aid route.

  • '000' - Not Fed Aid
  • '-' - Invalid Data
  • '+' - No Data

 


File Type
SAS Name: FILETYPE

Definition: Type of file of the roadway segment.

Additional Information: Element discontinued in 2003.

  • 'H' - Highway Record
  • 'I' - Intersection
  • 'R' - Ramp
  • '-' - Invalid Data
  • '+' - No Data

 


Functional Class
SAS Name: FUNC_CLS

Definition: Functional class.

  • '1' - Rural Principal Arterial With Extension Into Urban Area Principal Arterial
  • '2' - Rural Principal Arterial With Extension Into Urban Area Minor Arterial
  • '3' - Principal Arterial Lying Entirely In Urban or Rural Area
  • '4' - Minor Arterial
  • '5' - Major Collector
  • '6' - Minor Collector
  • '7' - Local
  • '0' - None
  • Other - Error/Other Codes

 


History Elements
SAS Name: HIST_ADD

Definition: History elements of the roadway segment.

Additional Information: This provides the address in a separate “History Elements” file where the past configuration of this roadway section can be found. HSIS does not have this History Elements file, but California does.

 


Highway Group
SAS Name: HWY_GRP

Definition: Highway group of the roadway segment.

Additional Information: In the HSIS version of the Roadlog File, codes ‘D’, ‘U’, and ‘X’ do not appear. They are combined by CA DOT into ‘Z’. In other data files provided by California to other users, these codes may occur. To link with crash data, they must be recoded to ‘Z’.

  • 'R' - Right Independent Alignment
  • 'L' - Left Independent Alignment
  • 'D' - Divided Highway
  • 'U' - Undivided Highway
  • 'X' - Unconstructed
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Inside Outside City
SAS Name: INS_OTS

Definition: Whether the roadway segment is inside or outside a city.

Additional Information: See RU_IO for additional urban/rural codes. Element discontinued in 2003.

  • 'I' - Inside
  • 'O' - Outside
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Average Lane Width
SAS Name: LANEWID

Definition: Calculated average lane width of the roadway segment

Additional Information: Average lane width. Calculated by dividing total traveled way width by total number of lanes.

  • 0 - Zero
  • 1-7 - 1-7 Ft
  • 8 - 8 Ft
  • 9 - 9 Ft
  • 10 - 10 Ft
  • 11 - 11 Ft
  • 12 - 12 Ft
  • 13 - 13 Ft
  • 14 - 14 Ft
  • 15-999 - 15-999 Ft
  • . - Not Stated
  • Other - Error/Other Codes

 


Left Shoulder Width RD2
SAS Name: LSHL_WD2
Left Shoulder Width RD1
SAS Name: LSHLDWID

Definition: Width of left shoulder of the roadway segment.

  • 0 - Zero
  • 1-3 - 1-3 Ft
  • 4-6 - 4-6 Ft
  • 7-9 - 7-9 Ft
  • 10-13 - 10-13 Ft
  • 14-99 - 14-99 Ft
  • . - Not Stated

 


Date of Last Change
SAS Name: LST_SEG_CHG_DTE

Definition: Date of last significant change of the roadway segment.

Additional Information: Element added in 2005.

 


Left Roadbed Date
SAS Name: LTRD_DTE

Definition: Date of last change to the left roadbed of the roadway segment.

Additional Information: (YYYYMMDD).See Discussion. Element discontinued in 2003.

 


Left Roadbed History
SAS Name: LTRD_HST

Definition: Indicator of a change in the left roadbed of the roadway segment.

Additional Information: A “flag” indicating a change in some element related to Road 2 (left roadbed). See Discussion.

 


Maintenance Level of Service Code
SAS Name: MAINT_LEVL

Definition: Maintenance level of service code of the roadway segment.

Additional Information: Element added in 2005 and discontinued in 2007.

 


Ramp Median Date
SAS Name: MED_DTE

Definition: Date of last change to the ramp median.

Additional Information: Date of last change in some element related to the median (YYYYMMDD). See Discussion.

 


Median History
SAS Name: MED_HIST

Definition: Indicator of a change in the median of the roadway segment.

Additional Information: A “flag” indicating a change in some element related to the median. See Discussion.

 


Median Type
SAS Name: MED_TYPE

Definition: Type of median on the roadway segment.

  • 'A' - Undivided, Not Separated or Striped
  • 'B' - Undivided, Striped
  • 'C' - Undivided, Reversible Peak Hour Lane(S)
  • 'E' - Divided, Reversible Peak Hour Lane(S)
  • 'F' - Divided, Two-Way Left Turn Lane
  • 'G' - Divided, Continuous Left-Turn Lane
  • 'H' - Divided, Paved Median
  • 'J' - Divided, Unpaved Median
  • 'K' - Divided, Separate Grades
  • 'L' - Divided, Separate Grades With Retaining Wall
  • 'M' - Divided, Sawtooth (Unpaved)
  • 'N' - Divided, Sawtooth (Paved)
  • 'P' - Divided, Ditch
  • 'Q' - Divided, Separate Structure
  • 'R' - Divided, Railroad or Rapid Transit
  • 'S' - Divided, Bus Lanes
  • 'T' - Divided, Paved Area, Occasional Traffic Lane
  • 'U' - Divided, Railroad and Bus Lane
  • 'V' - Divided, Contains Reversible Peak-Hour Lane(S)
  • 'Z' - Divided, Other
  • '-' - Invalid Data
  • '+' - No Data

 


Median Variance
SAS Name: MED_VAR

Definition: Whether median width varies for the roadway segment.

  • 'V' - Variable Median Width
  • 'P' - Over 100' Median With No Variance
  • 'Z' - Median Constant Width - No Variance
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Median Barrier Type
SAS Name: MEDBARTY

Definition: Type of median barrier of the roadway segment.

  • 'A' - Cable Barrier
  • 'B' - Cable Barrier With Glare Screen
  • 'C' - Metal Beam Barr
  • 'D' - Metal Beam Barrier With Glare Screen
  • 'E' - Concrete Barrier
  • 'F' - Concrete Barrier With Glare Screen
  • 'G' - Bridge Barrier Railing
  • 'H' - Chain Link Fence
  • 'J' - Guardrail in Median, Both Roadways
  • 'K' - Guardrail in Median, Left Roadway
  • 'L' - Guardrail in Median, Right Roadway
  • 'M' - Two-Way, One-Lane Road as Median
  • 'N' - Thrie Beam Barr
  • 'P' - Thrie Beam Barrier With Glare Screen
  • 'Q' - Concrete Barrier, Both Ways Inside Both Shoulders
  • 'R' - Concrete Barrier on Inside Shoulder of Road 2 (Left Roadway)
  • 'S' - Concrete Barrier on Inside Shoulder of Road 1 (Right Roadway)
  • 'X' - External Barriers on Concrete Barrier
  • 'Y' - Other -No Listed
  • 'Z' - No Barrier
  • '-' - Invalid Data
  • '+' - No Data

 


Median Width
SAS Name: MEDWID

Definition: Median width (in feet).

Additional Information: Median width is measured from the edge of the traveled-way to the opposite edge of traveled-way. Thus, it includes inside shoulder widths. 00 to 04 feet medians are normally considered “undivided.” 04 to 99 feet are divided.

  • . - Unknown
  • 0 - Zero
  • 1-10 - 1-10 Ft
  • 11-20 - 11-20 Ft
  • 21-30 - 21-30 Ft
  • 31-40 - 31-40 Ft
  • 41-60 - 41-60 Ft
  • 61-90 - 61-90 Ft
  • 91-99 - 91-99 Ft

 


Million Vehicle Miles Traveled
SAS Name: MVMT

Definition: Millions vehicle miles traveled on road segment.

Additional Information: The Million Vehicle Miles Traveled on road segment. Created element added in 1999 for all HSIS roadway-inventory files. See Discussion.

 


Non-ADD Mileage
SAS Name: NA_MILE

Definition: Non-ADD mileage of the roadway segment.

  • 'A' - Normal
  • 'N' - Non-Add
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

National Lands
SAS Name: NAT_LND

Definition: Whether the roadway segment is within National lands.`

  • '0' - None
  • '1' - Natnl Monuments
  • '2' - Natnl Rec Areas
  • '3' - Natnl Forest
  • '4' - Natnl Milt Resv
  • '5' - Natnl Indn Resv
  • '6' - Bureu of Nat Lnd
  • '-' - Invalid Data
  • '+' - No Data

 


Number of Lanes RD1
SAS Name: NO_LANE1
Number of Lanes RD2
SAS Name: NO_LANE2
Total Number of Lanes
SAS Name: NO_LANES

Definition: Number through lanes towards increasing/decreasing milepoints.

Additional Information: Number of lanes includes through lanes plus HOV and other auxiliary lanes greater than 0.2 miles in length. See FEAT_LF and FEAT_RG for codes identifying special lanes/features. These special lanes only occur in less than four percent of the mileage, and are almost exclusively on sections with six or more total lanes.

  • 1 - One Lane
  • 2 - Two Lanes
  • 3 - Three Lanes
  • 4-6 - 4 to 6 Lanes
  • 7-8 - 7 to 8 Lanes
  • 9-99 - > 8 Lanes
  • . - Not Stated
  • Other - Error/Other Codes

 


Left Paved Shoulder Width RD1
SAS Name: PAV_WDL
Left Paved Shoulder Width RD2
SAS Name: PAV_WDL2
Right Paved Shoulder Width RD1
SAS Name: PAV_WDR2
Right Paved Shoulder Width RD2
SAS Name: PAV_WIDR

Definition: Width of left/right paved shoulder of the roadway segment.

  • 0 - Zero
  • 1-3 - 1-3 Ft
  • 4-6 - 4-6 Ft
  • 7-9 - 7-9 Ft
  • 10-13 - 10-13 Ft
  • 14-99 - 14-99 Ft
  • . - Not Stated

 


Postmile Prefix
SAS Name: PSMILPRF

Definition: Postmile prefix of the roadway segment.

Additional Information: Roadways can be realigned in the middle of a year (see ‘R’ above). Thus, there may appear to be overlapping records in the same milepost range in a given year, except for this variable. Accidents are correctly mileposted to the correct record by California. RD_DATE can be used to determine when the new alignment was opened. However, if one is trying to match prior year’s crashes to such a section, the older crash records (not having the ‘R’) will not be computer matched to the new alignment (with the ‘R’) even though the roads are virtually the same piece of pavement. One can see how the Roadlog sections actually fall on the ground in a given year by sorting by RO_SEQ (Route Order Sequence). However, in multi-year before/after studies, the analyst may have to manually match the pertinent sections across years to conduct his/her analysis. Contact HSIS staff for assistance.

  • ' ' - No Prefix
  • 'A' - Reposted
  • 'B' - Bus Lane
  • 'C' - Commercial
  • 'D' - Duplicate (Meandering)
  • 'F' - Reposted - Commercial (C)
  • 'G' - Reposted - Duplicate (D)
  • 'H' - Realigned - Duplicate (D)
  • 'J' - Reposted, Realigned - Duplicate
  • 'K' - Reposted - Overlap (L)
  • 'L' - Overlapping Postmiles
  • 'M' - Realigned Realignment (R)
  • 'N' - Reposted, Realigned Realignment (M)
  • 'P' - Reposted Realignment (R)
  • 'Q' - Reposted - Spur (S)
  • 'R' - Realignment
  • 'S' - Spur
  • 'T' - Temporary Connection
  • 'U' - Reposted - Temporary Connection (T)
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Postmile Suffix
SAS Name: PSMILSUF

Definition: Postmile suffix of the roadway segment.

  • ' ' - No Suffix
  • 'E' - Equation
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Road Date
SAS Name: RD_DATE

Definition: Date open to traffic for the roadway segment.

Additional Information: Date when a realigned roadway section was opened to traffic (YYYYMMDD). See further discussion under PSMILPRF. Element discontinued in 2003.

 


Road Description
SAS Name: RD_DESC

Definition: Description of the roadway segment.

Additional Information: 25 character verbal description of route name.

 


Record Type
SAS Name: RECTYPE

Definition: Type of record of the roadway segment.

Additional Information: Element is used to identify file type. Element discontinued in 2003.

 


Right Roadbed Date
SAS Name: RGRD_DTE

Definition: Date of last change to the right roadbed of the roadway segment.

Additional Information: Date of last change in some element related to Road 1 (right roadbed) (YYYYMMDD). See Discussion.

 


Right Roadbed History
SAS Name: RGRD_HSR

Definition: Indicator of a change in the right roadbed of the roadway segment.

Additional Information: A “flag” indicating a change in some element related to Road 1 (right roadbed). See Discussion. A “flag” indicating a change in some element related to Road 1 (right roadbed). See Discussion.

 


Route Order Sequence
SAS Name: RO_SEQ

Definition: Sequence of route order of the roadway segment.

Additional Information: This element can help one decide the order in which homogeneous sections are laid out. Routes can be sorted by this element to get adjacent segments in order.

 


Roadway Classification
SAS Name: RODWYCLS

Definition: The classification of the roadway where the crash occurred.

Additional Information: Created element added to HSIS accident and roadway inventory files in all States in 1999. See Discussion.

  • '01' - Urban Freeways/
  • '02' - Urban Freeways < 4 Lanes
  • '03' - Urban Two Lane Roads
  • '04' - Urban Multilane Divided Non-Freeways
  • '05' - Urban Multilane Undivided Non-Freeways
  • '06' - Rural Freeways
  • '07' - Rural Freeways < 4 Lanes
  • '08' - Rural Two Lane Roads
  • '09' - Rural Multilane Divided Non-Freeways
  • '10' - Rural Multilane Undivided Non-Freeways
  • '99' - Others

 


Right Shoulder Width RD2
SAS Name: RSHL_WD2
Right Shoulder Width RD1
SAS Name: RSHLDWID

Definition: Right shoulder width.

  • 0 - Zero
  • 1-3 - 1-3 Ft
  • 4-6 - 4-6 Ft
  • 7-9 - 7-9 Ft
  • 10-13 - 10-13 Ft
  • 14-99 - 14+ Ft
  • . - Not Stated

 


Roadway Route Number
SAS Name: RTE_NBR

Definition: Route number of the roadway segment.

 


Route Suffix
SAS Name: RTE_SUF

Definition: Route suffix of the roadway segment.

  • 'P' - Alignment Prior
  • 'S' - Supplemental Alignment, Partial Opened For Use Before Alignment Is Complete
  • 'U' - Unrelinquished, Superseded By Realignment, But Not Yet Accepted For Non-State-Highway Maintenance
  • 'Z' - Budgeted or Under Construction
  • ' ' - No Suffix
  • Other - Error/Other Codes

 


Rural/Urban-Inside/Outside City
SAS Name: RU_IO

Definition: Whether the roadway segment is rural or urban and inside or outside city

  • 'A' - Rural, Totally In One City
  • 'B' - Rural, 2 in And 2 Outside City
  • 'C' - Rural, 2 in One City, 2 in Another
  • 'D' - Rural, Inside City, 1/2 in One County, 2 in Another County
  • 'E' - Rural, Inside City, Independent Alignment in Other County
  • 'F' - Rural, Outside City, 2 in One County, 2 In Another County
  • 'G' - Rural, Totally Outside City
  • 'H' - Rural, Outside City, Independent Alignment in Other County
  • 'J' - Urban, Totally In One City
  • 'K' - Urban, Inside City, 2 in And 2 Outside City
  • 'L' - Urban, Inside City, 2 in One City, 2 In Another City
  • 'M' - Urban, Inside City, 2 in One County, 2 in Another County
  • 'N' - Urban, Inside City, Independent Alignment in Other County
  • 'P' - Urban, Outside City, 2 in One County, 2 in Another County
  • 'Q' - Urban, Totally Outside City
  • 'R' - Urban, Outside City, Independent Alignment in Other County
  • 'S' - Urbanized, Totally In One City
  • 'T' - Urbanized, Inside City, 2 in And 2 Outside City
  • 'U' - Urbanized, Inside City, 2 in One City, 2 in Another City
  • 'V' - Urbanized, Inside City, 2 in One County, 2 in Another County
  • 'W' - Urbanized, Inside City, Independent Alignment in Other County
  • 'X' - Urbanized, Outside City, 2 in One County, 2 in Another County
  • 'Y' - Urbanized, Totally Outside City
  • 'Z' - Urbanized, Outside City, Independent Alignment in Other County
  • '-' - Invalid Data
  • '+' - No Data

 


Rural/Urban
SAS Name: RURURB

Definition: Rural-Urban identification.

Additional Information: See RU_IO for additional rural-urban codes. Note that "URBAN" in this element also contains "Urbanized" in RU_IO.

  • 'R' - Rural
  • 'U' - Urban
  • '-' - Invalid Data
  • '+' - No Data

 

Scenic Freeway
SAS Name: SCN_FRWY

Definition: Whether the roadway segment is a Scenic freeway.

  • '0' - Non-Freeway, Non-Scenic, Non-Expressway
  • '1' - Scenic (Non-Freeway, Non-Expressway)
  • '2' - Freeway & Expwy System (Non-Scenic)
  • '3' - Freeway & Expwy System (Scenic)
  • '-' - Invalid Data
  • '+' - No Data

 


Section Length
SAS Name: SEG_LNG

Definition: Section length in miles.

Additional Information: Length of section in miles (XXX.XXX).

 


Surface Type RD2
SAS Name: SURF_TY2
Surface Type RD1
SAS Name: SURF_TYP

Definition: Surface type.

  • 'B' - PCC, Bridge Deck
  • 'C' - PCC, Concrete
  • 'H' - AC, Base & Surface 7" Thick
  • 'M' - AC, Base & Surface < 7" Thick
  • 'O' - AC, Oiled Earth-Gravel
  • 'P' - AC, Bridge Deck (2" Or Greater)
  • 'E' - Unpaved- Earth
  • 'F' - Unp- Undetermd
  • 'G' - Unpaved, Bridge Deck (All Not Codes – Or P)
  • '-' - Invalid Data
  • ' ','+' - No Data

 


Traveled Way Width RD2
SAS Name: SURF_WD2
Traveled Way Width RD1
SAS Name: SURF_WID

Definition: Width of traveled way of the roadway segment.

Additional Information: Traveled-way width includes widths of through lanes plus auxiliary lanes greater than 0.2 miles in length. On some bridges, the shoulder widths may be erroneously included in this measurement .California staff is correcting these errors as they find them. Sections which are bridges can be identified using SURF_TYP.

  • 0 - Zero
  • 1-9 - <10 Ft
  • 10 - 10 Ft
  • 11 - 11 Ft
  • 12 - 12 Ft
  • 13-14 - 13-14 Ft
  • 15-16 - 15-16 Ft
  • 17-999 - > Than 16 Ft
  • . - Not Stated

 


Terrain
SAS Name: TERRAIN

Definition: Terrain.

  • 'M' - Mountainous
  • 'R' - Rolling
  • 'F' - Flat
  • '-' - Invalid Data
  • '+' - No Data

 


Toll and Forest Roads
SAS Name: TOLL

Definition: Whether the roadway segment is a toll or Forest road.

  • '0' - None
  • '1' - Toll Rds & Brdg
  • '2' - Forest Highways
  • '-' - Invalid Data
  • '+' - No Data

 


2-Axle Truck AADT
SAS Name: TRK2AX

Definition: Two-axle truck AADT on the roadway segment.

Additional Information: AADT count for 2-axle trucks. This is one of seven variables extracted from the CA DOT web site beginning with the 1995 Roadlog File (see TRK3AX, TRK4AX, TRK5AX, TRKTOT, and TRKCNTFL). For each of these variables, truck count data are converted into AADTs at certain points along the roadway. Since the count points on the truck AADT file shown on the web page are only at a limited set of locations (when compared to the huge number of sections/records in the Roadlog File), a computer program was developed which averages counts if in the same roadlog section, attaches individual counts or averages to sections where they occur, and then “carries forward” the single count or the last (downstream)count from that section to all subsequent sections on a given route until a new count is reached. See section on “Truck Count Data” in Discussion for more details.

 


3-Axle Truck AADT
SAS Name: TRK3AX

Definition: Three-axle truck AADT on the roadway segment

Additional Information: AADT COUNT FOR 3-AXLE TRUCKS. See note under TRK2AX.

 


4-Axle Truck AADT
SAS Name: TRK4AX

Definition: Four-axle truck AADT on the roadway segment.

Additional Information: AADT COUNT FOR 4-AXLE TRUCKS. See note under TRK2AX.

 


5+ Axle Truck AADT
SAS Name: TRK5AX

Definition: Five+ axle truck AADT on the roadway segment.

Additional Information: AADT count for trucks with five or more axles. See note under TRK2AX.

 


Truck Count Flag
SAS Name: TRKCNTFL

Definition: Truck count flag at the roadway segment.

Additional Information: This indicates whether actual truck counts were made in this roadway section. Here, "1" indicates a count or verified estimate at that location, and a "0" indicates no count ("carry forward" data). A blank indicates both no count, and that it was not legitimate to carry-forward the data. See Discussion and "NOTE" under TRK2AX.

 


Total Truck AADT
SAS Name: TRKTOT

Definition: Total truck AADT on the roadway segment.

Additional Information: AADT count for total trucks, the sum of TRK2AX, TRK3AX, TRK4AX, and TRK5AX. See Note under TRK2AX. Element added in 1995.

 

List of Elements for California Intersection File

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
CITY_CODE CITY CODE Intersection CHA(4) 122
CNTYRTE INTERSECTION COUNTY ROUTE Intersection CHA(9) 122
COUNTY COUNTY Intersection CHA(2) 122
DISTRICT DISTRICT Intersection CHA(2) 122
HWY_GRP HIGHWAY GROUP Intersection CHA(1) 123
INT_ADDR HISTORY ELEMENTS RELATIVE Intersection NUM 123
INT_DESC INTERSECTION DESCRIPTION Intersection CHA(23) 123
INT_DTE INTERSECTION EFFECTIVE DATE Intersection CHA(6) 123
INT_HST INTERSECTION TYPE HISTORY Intersection CHA(1) 124
INT_PRF INTERSECTING RTE PREFIX Intersection CHA(1) 124
INT_POPGRP INTERSECTION POPULATION Intersection CHA(1) 124
INT_RSUF INTERSECTING RTE SUFFIX Intersection CHA(1) 124
INT_RTE INTERSECTING RTE NBR Intersection CHA(3) 124
INT_SEQ INTERSECTING RTE ORDER SEQ Intersection NUM 124
INTMP INTERSECTION MILEPOST Intersection NUM(8) 125
INTY_RTE CROSS STREET COUNTY ROUTE Intersection CHA(9) 125
JUNCTYPE JUNCTION TYPE Intersection CHA(1) 125
LGHT_DTE INTERSECTION LIGHT TYPE DATE Intersection CHA(6) 125
LGHT_HST INTERSECTION LIGHT TYPE HISTORY Intersection CHA(1) 125
LGHT_TYP INTERSECTION LIGHT TYPE Intersection CHA(1) 126
LOG_ERR LOG ERROR INDICATOR Intersection CHA(1) 126
MED_DTE RAMP MEDIAN DATE Intersection CHA(6) 126
MED_HIST MEDIAN HISTORY Intersection CHA(1) 126
MED_IND RAMP MEDIAN INDICATOR Intersection CHA(1) 127
MILEPOST RAMP MILEPOST Intersection NUM 127
ML_AADT MAINLINE AADT Intersection NUM 127
ML_ADTDT MAINLINE ADT DATE Intersection CHA(6) 128
ML_ADTHS MAINLINE ADT HISTORY Intersection CHA(1) 128
ML_DATE MAINLINE HISTORY DATE Intersection CHA(6) 128
ML_HIST MAINLINE HISTORY Intersection CHA(1) 128
ML_LANES MAINLINE NUMBER OF LANES Intersection CHA(1) 129
ML_LEFT MAINLINE LEFT TURN Intersection CHA(1) 129
ML_LNGT MAINLINE SECTION LENGTH Intersection CHA(3) 129
ML_MAST MAINLINE SIGNAL MASTARM Intersection CHA(1) 130
ML_RIGHT MAINLINE RIGHT TURN Intersection CHA(1) 130
ML_TRFLO MAINLINE TRAFFIC FLOW Intersection CHA(1) 130
PSMILPRF POSTMILE PREFIX Intersection CHA(1) 131
PSMILSUF POSTMILE SUFFIX Intersection CHA(1) 132
RECTYPE RECORD TYPE Intersection CHA(1) 132
RO_SEQ ROUTE ORDER SEQUENCE Intersection NUM 132
RTE_NBR RDWAY ROUTE NUMBER Intersection CHA(3) 132
RTE_SUF RDWAY ROUTE SUFFIX Intersection CHA(1) 132
TRF_CNTL TRAFFIC CONTROL TYPE Intersection CHA(1) 133
TRFCTLDT TRAFFIC CONTROL TYPE DATE Intersection CHA(6) 133
TRFCTLHS TRAFFIC CONTROL TYPE HISTORY Intersection CHA(1) 133
TYPEDESC INTERSECTION TYPE Intersection CHA(1) 134
XSTAADT X-STREET AADT Intersection NUM 134
XSTADTDT X-STREET ADT DATE Intersection CHA(6) 134
XSTADTHS X-STREET ADT HISTORY Intersection CHA(1) 135
XSTLANES X-STREET NUMBER OF LANES Intersection CHA(1) 135
XSTLNGT X-STREET SECTION LENGTH Intersection CHA(3) 135
XSTRTDTE X-STREET DATE Intersection CHA(6) 135
XSTRTHST X-STREET HISTORY Intersection CHA(1) 136
XSTRTLFT X-STREET LEFT TURN CHANNELIZATION Intersection CHA(1) 136
XSTRTMST X-STREET SIGNAL Intersection CHA(1) 136
XSTRTRGH X-STREET RIGHT TURN Intersection CHA(1) 136
XSTSTRT X-STREET STATE ROUTE INDICATOR Intersection NUM 137
XSTTRFLO X-STREET TRAFFIC FLOW Intersection CHA(1) 137
XST_RSUF X-STREET ROUTE SUFFIX Intersection CHA(1) 137

City Code
SAS Name: CITY_CODE

Definition: City code for intersection location.

Additional Information: Element added in 2003. Please contact HSIS for formats information.

 


Intersection County Route
SAS Name: CNTYRTE

Definition: Description of intersection mainline location used in linkage to other files.

Additional Information: Linkage element, consisting of
DISTRICT+RTE_NBR+RTE_SUF+COUNTY+PSMILPRF+HWY_GRP.

 


County
SAS Name: COUNTY

Definition: County of the intersection.

Additional Information: See listings under accident section of the guidebook.

 


District
SAS Name: DISTRICT

Definition: District of intersection.

  • '01' - District One
  • '02' - District Two
  • '03' - District Three
  • '04' - District Four
  • '05' - District Five
  • '06' - District Six
  • '07' - District Seven
  • '08' - District Eight
  • '09' - District Nine
  • '10' - District Ten
  • '11' - District Eleven
  • '12' - District Twelve
  • '- ' - Invalid Data
  • '+ ' - No Data
  • Other - Error/Other Codes

 


Highway Group
SAS Name: HWY_GRP

Definition: Highway group of mainline in the intersection.

Additional Information: In the HSIS version of the Roadlog File, codes ‘D’, ‘U’, and ‘X’ do not appear. They are combined by CA DOT into ‘Z’. In other data files provided by California to other users, these codes may occur. To link with crash data, they must be recoded to ‘Z’.

  • 'R' - Right Independent Alignment
  • 'L' - Left Independent Alignment
  • 'D' - Divided Highway
  • 'U' - Undivided Highway
  • 'X' - Unconstructed
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


History Elements Relative
SAS Name: INT_ADDR

Definition: History element address for the intersection.

Additional Information: This provides the address in a separate “History Elements” file where the past configuration of this intersection can be found.  HSIS does not have this History Elements file, but California does. Element discontinued in 2003.

 


Intersection Description
SAS Name: INT_DESC

Definition: Description of the intersection.

Additional Information: This provides Character description of intersection location.

 


Intersection Effective Date
SAS Name: INT_DTE

Definition: Date of last change in intersection type.

Additional Information: Date of last change in some element related to intersection type (YYYYMMDD). See Discussion.

 


Intersection History
SAS Name: INT_HST

Definition: Indication of a change in intersection type.

Additional Information: A “flag” indicating a change in some variable related to intersection type. See Discussion. Element discontinued in 2003.

 


Intersecting Route Prefix
SAS Name: INT_PRF

Definition: Route prefix for the intersecting (not mainline) route in the intersection.

 


Intersection Population Code
SAS Name: INT_POPGRP

Definition: Population code of the intersection.

Additional Information: Element added in 2003.

  • 'B' - Urban
  • 'R' - Rural
  • 'U' - Urbanized

 


Intersecting Route Suffix
SAS Name: INT_RSUF

Definition: Route suffix for the intersecting (not mainline) route in the intersection.

  • 'P' - Alignment Prior To Conversion
  • 'S' - Supplemental Mileage
  • 'U' - Unrelinquished
  • 'Z' - Budgeted or Under Construction
  • ' ' - No Suffix

 


Intersecting Route NBR
SAS Name: INT_RTE

Definition: Intersecting route number.

 


Intersecting Route Order SEQ
SAS Name: INT_SEQ

Definition: Intersecting route sequence order.

Additional Information: See RO_SEQ.

 


Intersection Milepost
SAS Name: INTMP

Definition: Milepost of the intersection on the cross street.

Additional Information: Only present when cross street is a State Route (See element XSTSTRT).

 


Cross Street County Route
SAS Name: INTY_RTE

Definition: Cross Street (intersecting route) description used in linkage to other files.

Additional Information: Linkage element, consisting of DISTRICT+INT_RTE+INT_RSUF+COUNTY+INT_PRF+HWY_GRP.

 


Junction Type
SAS Name: JUNCTYPE

Definition: Type of junction.

  • '1' - Intersections
  • '2' - Ramps
  • '3' - Dirt/Gravel/Access Roads
  • '4' - Camp/Campgrounds/Parks
  • '5' - Forest/Forest Service, Usfs Oads
  • '6' - Named Roads
  • '7' - Public/Private High Volume Roads
  • '8' - Public/Private Low Volume Roads

 


Intersection Light Date
SAS Name: LGHT_DTE

Definition: Date of last change to intersection lighting.  Additional Information:   Date of last change in some element related to intersection lighting (YYYYMMDD). See Discussion.

 


Intersection Light History
SAS Name: LGHT_HST

Definition: Indicator of change to intersection lighting. 

Additional Information: A “flag” indicating a change in some element related to intersection lighting. See Discussion. Element discontinued in 2003.

 


Intersection Light Type
SAS Name: LGHT_TYP

Definition: Light type of the intersection.

  • 'N' - No Lighting
  • 'Y' - Lighted
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Log Error Indicator
SAS Name: LOG_ERR

Definition: Log error indicator.

Additional Information: All level is blank from 1993-1997. Element discontinued in 2003.

 


Ramp Median Date
SAS Name: MED_DTE

Definition: Date of last change to median at intersection.

Additional Information: Date of last change in some element related to the median (YYYYMMDD). See Discussion. Element discontinued in 2003.

 


Median History
SAS Name: MED_HIST

Definition: Indicator of change to the median at the intersection.

Additional Information: A “flag” indicating a change in some element related to the median. See Discussion. Element discontinued in 2003.

 


Ramp Median Indicator
SAS Name: MED_IND

Definition: Whether the mainline was divided or undivided at the intersection.

Additional Information: Element discontinued in 2003.

  • 'U' - Undivided
  • 'D' - Divided
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Milepost
SAS Name: MILEPOST

Definition: Milepost of the intersection on the mainline.

Additional Information: Milepost of intersection in miles (XXX.XXX).

 


Mainline AADT
SAS Name: ML_AADT

Definition: Mainline AADT of the intersection.

  • 0 - 0
  • 1-100 - 1-100
  • 101-500 - 101-500
  • 501-1000 - 501-1,000
  • 1001-2000 - 1,001-2,000
  • 2001-5000 - 2,001-5,000
  • 5001-10000 - 5,001-10,000
  • 10001-15000 - 10,001-15,000
  • 15001-20000 - 15,001-20,000
  • 20001-40000 - 20,001-40,000
  • 40001-999999 - >= 40,001/
  • .  - No Data

 


Mainline ADT Date
SAS Name: ML_ADTDT

Definition: Date of Mainline ADT of the intersection

Additional Information: Date of last change in some element related to mainline ADT (YYYYMMDD). See Discussion. Element  discontinued in 2003.

 


Mainline ADT History
SAS Name: ML_ADTHS

Definition: Indication of change in mainline ADT of the intersection.

Additional Information: A “flag” indicating a change in some element related to mainline ADT. See Discussion. Element discontinued in 2003.

 


Mainline History Date
SAS Name: ML_DATE

Definition: Date of mainline history of the intersection.

Additional Information: Date of last change in some element related to the mainline (YYYYMMDD). See Discussion.


 


Mainline History
SAS Name: ML_HIST

Definition: Indicator of a change in the mainline of the intersection.

Additional Information: A “flag” indicating a change in some element related to the mainline. See Discussion. Element discontinued in 2003.

 

Mainline Number of Lanes
SAS Name: ML_LANES

Definition: Number of lanes on the mainline at the intersection.

Additional Information: This is the number of "thru" lanes on the mainline approaches. It includes all lanes with thru movements (including thru and left turn, or thru and right turn), but does not contain exclusive turn lanes.

  • '0' - Zero
  • '1' - One Lane
  • '2' - Two Lanes
  • '3' - Three Lanes
  • '4'-'6' - 4 To 6 Lanes
  • '7'-'9' - 7 To 9 Lanes
  • '-' - Invalid Data
  • '+' - No Data
  • Other   Error/Other Codes

 


Mainline Left Turn Channelization
SAS Name: ML_LEFT

Definition: Left turn channelization on mainline at the intersection.

  • 'C' - Curbed Median Left Turn Channelization
  • 'N' - No Left Turn Channelization
  • 'P' - Painted Left Turn Channelization
  • 'R' - Raised Bars Left Turn Channelization
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Mainline Section Length
SAS Name: ML_LNGT

Definition: Section length of mainline in the intersection.

Additional Information: 000-999 (feet) from centerline of intersection in each direction.

 


Mainline Signal Mastarm Channelization
SAS Name: ML_MAST

Definition: Presence of signal mastarm on the mainline of the intersection.

  • 'N' - No Mastarm
  • 'Y' - Yes, Mastarm
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Mainline Right Turn Channelization
SAS Name: ML_RIGHT

Definition: Right turn channelization on the mainline of the intersection.

  • 'N' - No Right Turn Channelization
  • 'Y' - Channelization Provided For Right Turns
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Mainline Traffic Flow
SAS Name: ML_TRFLO

Definition: Traffic flow on the mainline of the intersection.

  • 'N' - 2-Way Traffic, No Left Turns Permitted
  • 'P' - 2-Way Traffic, Left Turn Permitted
  • 'R' - 2-Way Traffic, Left Turn Restricted During Peak Hours
  • 'W' - One-Way Traffic
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Postmile Prefix
SAS Name: PSMILPRF

Definition: Postmile prefix of the mainline at the intersection.

Additional Information: :  Roadways can be realigned in the middle of a year (see ‘R’ above). Thus, there may appear to be overlapping records in the same milepost range in a given year, except for this element. Accidents are correctly mileposted to the correct record by California. RD_DATE can be used to determine when the new alignment was opened. However, if one is trying to match prior year’s crashes to such a section, the older crash records (not having the ‘R’) will not be computer matched to the new alignment (with the ‘R’) even though the roads are virtually the same piece of pavement. One can see how the Roadlog sections actually fall on the ground in a given year by sorting by RO_SEQ (Route Order Sequence). However, in multi-year before/after studies, the analyst may have to manually match the pertinent sections across years to conduct his/her analysis. Contact HSIS staff for assistance.

  • ' ' - No Prefix
  • 'A' - Reposted
  • 'B' - Bus Lane
  • 'C' - Commercial
  • 'D' - Duplicate (Meandering)
  • 'F' - Reposted - Commercial (C)
  • 'G' - Reposted - Duplicate (D)
  • 'H' - Realigned - Duplicate (D)
  • 'J' - Reposted, Realigned - Duplicate
  • 'K' - Reposted - Overlap (L)
  • 'L' - Overlapping Postmiles
  • 'M' - Realigned Realignment (R)
  • 'N' - Reposted, Realigned Realignment (M)
  • 'P' - Reposted Realignment (R)
  • 'Q' - Reposted - Spur (S)
  • 'R' - Realignment
  • 'S' - Spur
  • 'T' - Temporary Connection
  • 'U' - Reposted - Temporary Connection (T)
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Postmile Suffix
SAS Name:PSMILSUF

Definition: Postmile suffix of the mainline at the intersection.

Additional Information: Element discontinued in 2003.

  • ' ' - No Suffix
  • 'E' - Equation
  • '-' - Invalid Data
  • '+' - No Data

 


Record Type
SAS Name: RECTYPE

Definition: Type of record of the intersection.

Additional Information: This element is used to identify file type. Element discontinued in 2003.

 


Route Order Sequence
SAS Name: RO_SEQ

Definition: Order sequence of mainline route segment at the intersection.

Additional Information: See RO_SEQ in Roadlog File.

 


Roadway Route Number
SAS Name: RTE_NBR

Definition: Route number of the mainline at the intersection.

Additional Information: Mainline route number.

 


Roadway Route Suffix
SAS Name: RTE_SUF

Definition: Route suffix of the mainline at the intersection.

  • 'P' - Alignment Prior
  • 'S' - Supplemental Alignment, Partial Opened For Use Before Alignment Is Complete
  • 'U' - Unrelinquished, Superseded By Realignment, But Not Yet Accepted For Non-State Highway Maintenance
  • 'Z' - Budgeted Or Under Construction'
  • ' ' - No Suffix'
  • Other - Error/Other Codes'

 


Traffic Control Type
SAS Name: TRF_CNTL

Definition: Traffic control type at the intersection.

  • 'A' - No Control
  • 'B' - Stop Signs on Cross Street Only
  • 'C' - Stop Signs on Mainline Only
  • 'D' - Four-Way Stop Signs
  • 'E' - Four-Way Flasher (Red on Cross Street)
  • 'F' - Four-Way Flasher (Red on Mainline)
  • 'G' - Four-Way Flasher (Red on All)
  • 'H' - Yield Signs on Cross Street Only
  • 'I' - Yield Signs on Mainline Only
  • 'J' - Signals Pretimed (2 Phase)
  • 'K' - Signals Pretimed (Multi-Phase)
  • 'L' - Signals Semi-Traffic Actuated, 2 Phase
  • 'M' - Signals Semi-Traffic Actuated, Multi-Phase
  • 'N' - Signals Full Traffic Actuated, 2 Phase
  • 'P' - Signals Full Traffic Actuated, Multi-Phase
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data

 


Traffic Control Type Date
SAS Name: TRFCTLDT

Definition: Date of last change in traffic control type of the intersection.

Additional Information: Date of last change in some element related to traffic control type (YYYYMMDD). See Discussion. Element discontinued in 2003.

 


Traffic Control Type History
SAS Name: TRFCTLHS

Definition: Indicator or change in traffic control type of the intersection.

Additional Information: A “flag” indicating a change in some element related to the traffic control type. See Discussion. Element discontinued in 2003.

 


Intersection Type
SAS Name: TYPEDESC

Definition: Type of the intersection.

  • 'F' - 4 - Legged
  • 'M - > 4 Legs
  • 'S' - Offset
  • 'T' - Tee
  • 'Y' - Wye
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


X-Street AADT
SAS Name: XSTAADT

Definition: Cross (intersecting)-street AADT.

Additional Information: The AADTs for most of the cross-streets which are NOT on state routes have not been updated for many years.  The user should consider carefully whether these AADTs are of suitable quality for the analysis being conducted. See Discussion.

  • 0 - 0
  • 1-100 - 1-100
  • 101-500 - 101-500
  • 501-1000 - 501-1,000
  • 1001-2000 - 1,001-2,000
  • 2001-5000 - 2,001-5,000
  • 5001-10000 - 5,001-10,000
  • 10001-15000 - 10,001-15,000
  • 15001-20000 - 15,001-20,000
  • 20001-40000 - 20,001-40,000
  • 40001-999999 - >= 40,001
  • . = - No Data

 


X-Street ADT Date
SAS Name: XSTADTDT

Definition: Date of cross-street ADT.

Additional Information: Date of last change in some element related to cross-street ADT (YYYYMMDD). See Discussion. Element discontinued in 2003.

 


X-Street ADT History
SAS Name: XSTADTHS

Definition: Indicator of change in AADT information on the cross-street

Additional Information: A “flag” indicating a change in some element related to the cross-street ADT. See Discussion. Element discontinued in 2003.

 


X-Street Number of Lanes
SAS Name: XSTLANES

Definition: Number of lanes on the cross-street.

Additional Information: This is the number of "thru" lanes on the cross street approaches. It includes all lanes with thru movements (including thru and left turn, or thru and right turn), but does not contain exclusive turn lanes.

  • '0' - Zero
  • '1' - One Lane
  • '2' - Two Lanes
  • '3' - Three Lanes
  • '4'-'6' - 4 To 6 Lanes
  • '7'-'9' - 7 To 9 Lanes
  • '-' - Invalid Data
  • '+' - No Data

 


X-Street Section Length
SAS Name: XSTLNGT

Definition: Length of cross-street in the intersection .

 


X-Street Date
SAS Name: XSTRTDTE

Definition: Date of last change on the cross-street.

Additional Information: Date of last change in some element related to the cross- street (YYYYMMDD). See Discussion.

 


X-Street History
SAS Name: XSTRTHST

Definition: Indicator of change on the cross-street at the intersection.

Additional Information: A “flag” indicating a change in some element related to the cross-street. See Discussion. Element discontinued in 2003.

 


X-Street Left Turn Channelization
SAS Name: XSTRTLFT

Definition: Left turn channelization on the cross-street.

  • 'C' - Curbed Median Left Turn Channelization
  • 'N' - No Left Turn Channelization
  • 'P' - Painted Left Turn Channelization
  • 'R' - Raised Bars Left Turn Channelization
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


X-Street Signal
SAS Name: XSTRTMST

Definition: Presence of signal mastarm on the cross-street.

  • 'N' - No Mastarm
  • 'Y' - Yes, Mastarm
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


X-Street Right Turn
SAS Name: XSTRTRGH

Definition: Right turn channelization on the cross-street.

  • 'N' - No Right Turn Channelization
  • 'Y' - Channelization Provided For Right Turns
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


X-Street State Route Indicator
SAS Name: XSTSTRT

Definition: State route indicator for the cross-street

  • 1 - State Route
  • 0 - Not State Route

 


X-Street Traffic Flow
SAS Name: XSTTRFLO

Definition: Type of traffic flow on the cross-street.

  • 'N' - 2-Way Traffic, No Left Turns Permitted
  • 'P' - 2-Way Traffic, Left Turn Permitted
  • 'R' - 2-Way Traffic, Left Turn Restricted During Peak Hours
  • 'W' - One-Way Traffic
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


X-Street Route Suffix
SAS Name: XST_RSUF

Definition: Route suffix of cross-street.

 

List of Elements for California Interchange Ramp File

SAS VARIABLE NAME DESCRIPTION SAS VARIABLE FILE FORMAT TYPE PAGE NO.
AREA4 RAMP AREA 4 INDICATOR Ramp CHA(1) 139
CITY_CODE CITY CODE Ramp CHA(4) 139
COUNTY COUNTY Ramp CHA(2) 139
DIR_CODE DIRECTION Ramp CHA(1) 140
DISTRICT DISTRICT Ramp CHA(2) 140
HWY_GRP HIGHWAY GROUP Ramp CHA(1) 141
MED_DTE RAMP MEDIAN DATE Ramp CHA(8) 141
MED_HST RAMP MEDIAN HISTORY Ramp CHA(1) 141
MED_IND RAMP MEDIAN INDICATOR Ramp CHA(1) 142
MILEPOST RAMP MILEPOST Ramp NUM 142
ON_OFFRP ON/OFF RAMP INDICATOR Ramp CHA(1) 142
PSMILPRF POSTMILE PREFIX Ramp CHA(1) 143
RAMP_TYP RAMP TYPE Ramp CHA(1) 144
RECTYPE RECORD TYPE Ramp CHA(1) 144
RMADTDTE RAMP ADT DATE Ramp CHA(8) 144
RMADTHST RAMP ADT HISTORY Ramp CHA(1) 145
RMP_ADT RAMP AADT Ramp NUM 145
RMP_BEGMP RAMP BEGIN MILEPOST OFFSET Ramp NUM(8) 145
RMP_DTE RAMP TYPE DATE Ramp CHA(8) 145
RMP_HST RAMP HISTORY Ramp CHA(1) 146
RMP_POPGRP RAMP POPULATION CODE Ramp NUM 146
RMP_SEQ RAMP SEQUENCE NUMBER Ramp NUM 146
RMP_TYPE RAMP TYPE Ramp CHA(1) 147
RTE_NBR RDWAY ROUTE NUMBER Ramp CHA(3) 147
RTE_SUF RDWAY ROUTE SUFFIX Ramp CHA(1) 148
TRF_CNTL INTERSECTION TRAFFIC CONTROL TYPE Ramp CHA(1) 148

Ramp Area4 Indicator
SAS Name: AREA4

Definition: Ramp area4 indicator.

Additional Information: This variable indicates whether the ramp in question is associated with “area 4” for accident location purposes. This will occur when the intersecting (non-mainline) route is a (non- mileposted) county route.  In these cases, all crashes which occur on the intersecting route between 150 ft. "outside" the ramp- related intersection to the center of the bridge structure will be mileposted to this ramp. In contrast, when a ramp intersects a (mileposted) State route, the same crashes will be mileposted to the crossing route. This variable will allow for identification of such "area 4" locations if desirable in the analysis. See
INT_RMP in the Accident File.

  • 'Y' - Yes
  • 'N' - No
  • ' ' - Not Stated
  • Other - Error/Other Codes

 


City Code
SAS Name: CITY_CODE

Definition: City code of the ramp.

Additional Information: Element added in 2003. Please contact HSIS for formats information.

 


County Route
SAS Name: CNTYRTE

Definition: Ramp location information used in linkage to other files.

Additional Information: Linkage element, consisting of DISTRICT+RTE_NBR+RTE_SUF+COUNTY+PSMILPRF+HWY_GRP.

 


County
SAS Name: COUNTY

Definition: County of the ramp.

Additional Information: See listings under accident section of the guidebook. Element added in 2003.

 


Direction
SAS Name: DIR_CODE

Definition: Direction of the ramp.

Additional Information: Element added 2003.

  • 'N' - North
  • 'S' - South
  • 'E' - East
  • 'W' - West

 


District
SAS Name: DISTRICT

Definition: District of the ramp.

Additional Information: Element  added in 2003.

  • '01' - District One
  • '02' - District Two
  • '03' - District Three
  • '04' - District Four
  • '05' - District Five
  • '06' - District Six
  • '07' - District Seven
  • '08' - District Eight
  • '09' - District Nine
  • '10' - District Ten
  • '11' - District Eleven
  • '12' - District Twelve
  • '- ' - Invalid Data
  • '+ ' - No Data
  • Other - Error/Other Codes

 


Highway Group
SAS Name: HWY_GRP

Definition: Highway group of the ramp

Additional Information: In the HSIS version of the Roadlog File, codes ‘D’, ‘U’, and ‘X’ do not appear. They are combined by CA DOT into ‘Z’. In other data files provided by California to other users, these codes may occur. To link with crash data, they must be recoded to ‘Z’.

  • 'R' - Right Independent Alignment
  • 'L' - Left Independent Alignment
  • 'D' - Divided Highway
  • 'U' - Undivided Highwy
  • 'X' - Unconstructed
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Ramp Median Date
SAS Name: MED_DTE

Definition: Date of last change for median associated with the ramp.

Additional Information: Date of last change in some element related to the median and associated with the ramp (YYYYMMDD). See Discussion. Element discontinued in 2003.

 


Ramp Median History
SAS Name: MED_HST

Definition: Indicator of a change in the median associated with the ramp.

Additional Information: A “flag” indicating a change in some element related to the median and associated with the ramp. See Discussion. Element discontinued in 2003.

 


Ramp Median Indicator
SAS Name: MED_IND

Definition: Whether the mainline associated with the ramp is divided or not.

Additional Information: Element discontinued in 2003.

  • 'U' - Undivided
  • 'D' - Divided
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Ramp Milepost
SAS Name: MILEPOST

Definition: Reference point for the ramp.

Additional Information: Milepost of “nose” of ramp in miles (XXX.XXX). See discussion.

 


On/Off Ramp Indicator
SAS Name: ON_OFFRP

Definition: On/Off ramp indicator.

  • 'O' - On Ramp
  • 'F' - Off Ramp
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Postmile Prefix
SAS Name: PSMILPRF

Definition: Postmile prefix of the ramp.

Additional Information: Roadways can be realigned in the middle of a year (see ‘R’ above). Thus, there may appear to be overlapping records in the same milepost range in a given year, except for this element. Accidents are correctly mileposted to the correct record by California. RD_DATE can be used to determine when the new alignment was opened. However, if one is trying to match prior year’s crashes to such a section, the older crash records (not having the ‘R’) will not be computer matched to the new alignment (with the ‘R’) even though the roads are virtually the same piece of pavement. One can see how the Roadlog sections actually fall on the ground in a given year by sorting by RO_SEQ (Route Order Sequence). However, in multi-year before/after studies, the analyst may have to manually match the pertinent sections across years to conduct his/her analysis. Contact HSIS staff for assistance. This element is new and was added in 2003.

  • ' ' - No Prefix
  • 'A' - Reposted
  • 'B' - Bus Lane
  • 'C' - Commercial
  • 'D' - Duplicate (Meandering)
  • 'F' - Reposted - Commercial (C)
  • 'G' - Reposted - Duplicate (D)
  • 'H' - Realigned - Duplicate (D)
  • 'J' - Reposted, Realigned - Duplicate
  • 'K' - Reposted - Overlap (L)
  • 'L' - Overlapping Postmiles
  • 'M' - Realigned Realignment (R)
  • 'N' - Reposted, Realigned Realignment (M)
  • 'P' - Reposted Realignment (R)
  • 'Q' - Reposted - Spur (S)
  • 'R' - Realignment
  • 'S' - Spur
  • 'T' - Temporary Connection
  • 'U' - Reposted - Temporary Connection (T)
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Ramp Type
SAS Name: RAMP_TYP

Definition: Type of ramp.

Additional Information: Element added in 2003.

  • 'A' - Frontage Road
  • 'B' - Collector Road
  • 'C' - Dir/Semi Lft Rmp
  • 'D' - Diamond Interchg
  • 'E' - Slip Ramp
  • 'F' - Dir/Semi Rgt Rmp
  • 'G' - Loop W/Lft Trn
  • 'H' - Buttonhook Ramp
  • 'J' - Scissors Ramp
  • 'K' - Split Ramp
  • 'L' - Loop W/O Lff Trn
  • 'M' - Two-Way Ramp
  • 'P' - Dummy Paired Rmp
  • 'R' - Rest Area/Vista
  • 'V' - Dummy-Volume Onl
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Record Type
SAS Name: RECTYPE

Definition: Type of record.

Additional Information: Element used to identify file type. Element discontinued in 2003.

 


Ramp ADT Date
SAS Name: RMADTDTE

Definition: ADT date of the ramp.

Additional Information: Date of last change in some element related to ramp ADT (YYYYMMDD). See discussion. Element discontinued in 2003.

 


Ramp ADT History
SAS Name: RMADTHST

Definition: Indicator of a change in ramp ADT.

Additional Information: A “flag” indicating a change in some element related to the ramp ADT. See Discussion. Element discontinued in 2003.

 


Ramp AADT
SAS Name: RMP_ADT

Definition: AADT of the ramp.

  • 0 - 0
  • 1-100 - 1-100
  • 101-500 - 101-500
  • 501-1000 - 501-1,000
  • 1001-2000 - 1,001-2,000
  • 2001-5000 - 2,001-5,000
  • 5001-10000 - 5,001-10,000
  • 10001-15000 - 10,001-15,000
  • 15001-20000 - 15,001-20,000
  • 20001-40000 - 20,001-40,000
  • 40001-999999 - >= 40,001
  • .  - No Data

 


Ramp Begin Milepost Offset
SAS Name: RMP_BEGMPOFFSET

Definition: Offset of milepost for beginning of ramp.

Additional Information: Element  added in 2003.

 


Ramp Type Date
SAS Name: RMP_DTE

Definition: Date of last change in ramp type.

Additional Information: Date of last change in some element related to ramp type (YYYYMMDD). See Discussion. Element discontinued in 2003.

 


Ramp History
SAS Name: RMP_HST

Definition: Indicator or change in the ramp.

Additional Information: A “flag” indicating a change in some element related to the ramp. See Discussion. Element  added in 1995 and discontinued in 2003.

 


Ramp Population Group
SAS Name: RMP_POPGRP

Definition: Population group of the ramp.

Additional Information: Element added in 2003.

  • 'B' - Urban
  • 'R' - Rural
  • 'U' - Urbanized

 


Ramp Sequence Number
SAS Name: RMP_SEQ

Definition: Sequence number of the ramp.

Additional Information: See RO_SEQ in Roadlog File. Element added in 2003.

 


Ramp Type
SAS Name: RMP_TYPE

Definition: Type of the ramp.

Additional Information: Element discontinued in 2003..

  • 'A' - Frontage Road
  • 'B' - Collector Road
  • 'C' - Direct or Semi-Direct Connector (Left)
  • 'D' - Diamond Type Ramp
  • 'E' - Slip Ramp
  • 'F' - Direct or Semi-Direct Connector (Right)
  • 'G' - Loop With Left Turn
  • 'H' - Bottonhook Ramp
  • 'J' - Scissors Ramp
  • 'K' - Split Ramp
  • 'L' - Loop Without Left Turn
  • 'M' - Two-Way Ramp Segment
  • 'P' - Dummy-Paired
  • 'R' - Rest Area, Vista Point, Truck Scale
  • 'V' - Dummy-Volumes Only
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes

 


Route Number
SAS Name: RTE_NBR

Definition: The route number of the ramp.

Additional Information: Mainline route number. Element added in 2003.

 


Roadway Route Suffix
SAS Name: RTE_SUF

Definition: Route suffix of the ramp.

Additional Information: Element added in 2003.

  • 'P' - Alignment Prior
  • 'S' - Supplemental Alignment, Partial Opened For Use Before Alignment Is Complete'
  • 'U' - Unrelinquished, Superseded By Realignment, But Not Yet Accepted For Non-State-Highway Maintenance
  • 'Z' - Budgeted or Under Construction
  • ' ' - No Suffix
  • Other - Error/Other Codes

 


Traffic Control
SAS Name: TRF_CNTL

Definition: Traffic control devices at the ramp terminal.

Additional Information: Element added in 2003.

  • 'A' - No Control
  • 'B' - Stp Sgn X/Stret
  • 'C' - Stp Sgn Mainlne
  • 'D' - 4 Way Stop Sgns
  • 'E' - 4 Way Flsh Red-X
  • 'F' - 4 Way Flsh Red-M
  • 'G' - 4 Way Flsh Red-A
  • 'H' - Yield Sgn X-Strt
  • 'I' - Yield Sgn Mnline
  • 'J' - Sgnl Pretime -2p
  • 'K' - Sgnl Pretime -Mp
  • 'L' - Sgnl Semi-Act 2p
  • 'M' - Sgnl Semi-Act Mp
  • 'N' - Sgnl Full-Act 2p
  • 'P' - Sgnl Full-Act Mp
  • 'Z' - Other
  • '-' - Invalid Data
  • '+' - No Data
  • Other - Error/Other Codes