Forrest M. Council
University of North Carolina
Highway Safety Research Center
730 Airport Road
Chapel Hill, NC 27599-3430
Yusuf M. Mohamedshah
LENDIS Corporation
Turner Fairbank Highway Research Center
Federal Highway Administration
6300 Georgetown Pike
McLean, VA 22101-2296
Federal Highway Administration
Office of Safety and Traffic Operations Research &
Development
U.S. Department of Transportation
Washington, DC 20590
Revised, April 2009
(NOTE: Changes from the previous edition of the Guidebook are shown in bold and italic.)
The Washington database incorporated into the HSIS system is derived from the Washington TRIPS system. The system, maintained by the Transportation Data Office (TDO) of the Washington DOT, is a relational database system which, like Utah, is based on ADABAS computer software. The Washington TDO provides the data to HSIS in the form of nine different data files. These include:
As originally received, all files except the basic roadway inventory data are "point" files, describing information about specific points (rather than sections) on the roadway. As will be described below, some of these point-files have been modified to a section-related format for ease of use in the HSIS system.
Raw file data are provided to the Highway Safety Research Center where they are retained as backup information. The documentation (variable listings, definitions, etc.) for these raw files and for the SAS files that are developed from them are available at FHWA offices.
Beginning in 1994, the HSIS system is being converted to a relational database for internal use. This database, using a SYBASE system till 2004 and then converted to an ORACLE system, will store the data received from Washington and other states, and the data files for a given state will be linked and manipulated using SQL language. However, this conversion from the original SAS-based system to the newer relational system is somewhat transparent to the end-user of the data since the output files produced by ORACLE for modeling and analysis will be SAS formatted. As in the past, we have continued to produce SAS format libraries for each of the variables in each of the files. Because it is envisioned that the majority of analyses will utilize these SAS files and formats, this Guidebook will concern these SAS files — their formats, completeness, and quality.
As noted above, the SAS accident data 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 three vehicles in each accident, and the third containing information on up to seven occupants in each of the three possible vehicles. The vehicle and occupant data can be linked to the basic accident file for a specific case using the accident report number and vehicle number. The accident subfile can be linked to roadway inventory and traffic files using an 11 character route/milepost variable. Also a separate pedestrian file is available from 1999 onwards. This file has information on the pedestrians that were involved in a crash. Just as with the vehicle and occupant files, this file can be linked to the accident sub-file using the accident report number.
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 which is consistent in terms of certain characteristics, with anew section being defined each time any of the characteristics changes). Each record on the basic inventory file contains current characteristics of the roadway system and includes such variables as surface width, lane width and type, shoulder width and type, median information and other variables. As will be noted below, unlike other HSIS state inventories, this file also contains information on the specifics of turn lanes and acceleration lanes.
Data on horizontal curvature and grade have been extracted from an original point-based file and converted in two homogenous section files — the Curve File and the Grade File. Each contains information concerning the location (i.e., beginning and ending milepoints) of a specific curve or grade, and descriptive information such as degree of curvature, direction of curve, curve length, percent grade, and grade length.
The Ramp File, a supplemental roadlog file, contains information on the location and roadway characteristics of ramps. This file is available from 2002 onwards. As is the case with other supplemental files, this file is linkable to the accident data.
The Special-Use Lanes File , unique to Washington, contains additional information on special auxiliary lanes or on usage of the paved shoulder as special lanes. For example, this file contains information on the presence of bike lanes, the presence of two-way turn lanes in the median, and the presence of auxiliary climbing lanes.
The Features File is a supplemental roadway inventory file which contains limited information on bridges, tunnels, and underpasses. These are point data, with location and limited descriptive information given for each point on the file. The bridge data have been formatted such that they are linkable with the National Bridge Index (NBI) file available from FHWA.
The Left/Right File is another unique file to Washington which contains descriptive information on crossing roadways and milepost markers, and the locations of roadside facilities such as park and ride lots, rest areas, and truck weight stations.
While the Railroad Grade Crossing Index does not contain detailed information on the railroad crossing, it does contain information which will allow one to link this file with the federally-required railroad grade crossing file.
Accident data is collected statewide by all police departments in the state on a standard form. The prescribed accident reporting threshold is currently $750 or personal injury. Prior to 1 January 2000, this used to be $500 or personal injury. It is felt that this threshold is generally used for accidents that occur on state system roads in most of the rural areas. It is the feeling of the TDO staff that city police in Tacoma and Seattle, two of the larger cities, may have begun to report fewer non-injury crashes than the official threshold would require, using something like a tow-away criteria.
There are approximately 130,000 accidents in the entire state each year. For each crash that is investigated, an accident report form is sent to the Washington State Patrol (WSP) Accident Reports Division, which is the central repository of the data. The WSP then separates the forms into those occurring on state routes and those on non-state routes, and sends the state- route hard copies to the Transportation Data Office (TDO) for location coding. The location coding is done by coding staff using logs showing virtually every possible reference point beside the roadway, including bridges, businesses, intersections, and a number of other references. The crash location is coded based on location-related information provided by the investigating officer on the form and on his/her reference map/sketch. In addition to the standard coding done by other states, all accidents which occur on interchange ramps are located to the specific interchange ramp on which they occur.
Each unit of the Washington State Patrol has been given a copy of the accident locator log to provide them with listings of possible reference points. In addition, physical reference markers are installed on Interstates and other state routes in both urban and rural locations. While some may be missing in urban areas, the rural state systems seem to be intact. TDO staff estimate that there are problems in location provided by the officers in only one to two percent of the accidents that the staff codes. These are sent back to the police officers for correction.
Because of the above-noted locating and coding procedures, it is felt that the location coding for these state-route accidents is probably as accurate as would be found in any state in the U.S., with over 95% of the rural accidents being located to at least the nearest 1/10 of a mile, and over 95% of the urban accidents being located within 100 feet.
After location coding by the TDO staff, the hard copies are sent back to the Washington State Patrol for coding of all other variables. Once keypunched and entered into the computer by the State Patrol, the complete computer file is sent back to the TDO office for their use. Approximately 15 to 20 percent of the crashes in the location-coded file are reported by citizens using a "citizen reports." This is a higher proportion of citizen-reported crashes than in other states. Because of the size of this sample, these reports are location coded by Washington staff, and are used in calculation of rates and in identification of high-accident sites. The form used by citizens is designed to eliminate some of the possible self-reporting biases by deleting some of the items found on the normal police report. However, because of the possible remaining biases, and in order to be consistent with the other state databases, these citizen reports have been deleted from the Washington HSIS file. Deleting these reports results in an HSIS file of approximately 48,000 accidents. The corresponding number of accidents in HSIS in its first year — 1993 — was about 34,000.
Currently the HSIS system contains accident data for 1993 to 1996 and 1999 onwards. The 1997 and 1998 accident data were not included by WADOT in the TRIPS system due to budget restrictions and problem encountered in year 2000 conversion efforts. Thus, these data are also not present in HSIS.
The Accident Subfile contains over 75 variables and approximately 48,000 crash records, and includes all basic variables that would be expected on standard police forms. The file provides a “first harmful event” variable but does not provide a "most harmful event." However, since 1993, the accident file has contained information on the sequence of events. This information includes the movements prior to the impact for up to two vehicles (e.g., "moving straight," "turning right"), and the specific type of the impact (e.g., "strikes other vehicle head on," "strikes appurtenance"). In addition, the accident file contains a variable concerning whether or not one or more vehicles was towed from the scene, which will allow analysis based on “towaway” vehicles in addition to standard analysis which include all vehicles meeting the dollar damage threshold, whether towed or not.
Also, the accident file contains a variable indicating the presence of a work zone at the crash location from 1999 onwards.
The Vehicle Subfile, containing approximately 80,000 vehicles each year, contains information on up to three vehicles in the crash. It contains specific information on the driver (including ejection information) as well as information on vehicle make/model, movements related to crash, miscellaneous actions, crash circumstances and causes. VIN data is not found on the TRIPS file available to HSIS. Crash-involved pedestrian information on such items as pedestrian age, sex, injury status, actions prior to the crash, sobriety, and crash circumstances is also included in the Vehicle Subfile up to 1996. From 1999 onwards, a separate pedestrian file has been developed that included information on all pedestrian related items.
Due to budget restrictions and conversions to post-2000 formatting, Washington stopped collecting some vehicle and occupant variables during the 1999-2001 period. Hence, some of the variables in the vehicle and occupant files are either missing or have limited coding, and the coding varies by year. Relevant notes under specific variables in the format section of the guidebook identify these variables. For these variables, the end-user is advised to examine the frequency distributions across years to determine the extent of missing values and the consistency of coding before using them in any analysis.
The Occupant Subfile contains information on up to seven occupants (including the driver) for any of the three vehicles, resulting in a file of approximately 100,000 entries each year. It contains information on occupant's sex, age, seating position, injury class, restraint use, and ejection. For 1999 and later years, this file does not contain information on the driver and the total number of observations in the file are about 33,000. The driver information continues to be captured in the Vehicle Subfile for all years.
Finally, as noted above, some Occupant Subfile variables are missing or inconsistent for the 1999-2001 period. Pertinent notes are included in the format section.
The Pedestrian Subfile, available from 1999 onwards contains information on pedestrians involved in a crash — approximately 1,000 entries per year. It contains information on various pedestrian characteristics like age, clothing, sex, injury, contributing circumstances, etc. Previously, these variables were available in the vehicle sub-file.
In order to assess the accuracy of accident variables, we both questioned the TDO staff concerning their feelings of variables that were incompletely coded or might be inaccurate and examined a series of single variable tables for 80 key variables. The TDO staff indicated that the truck-type codes in "vehicle type" variable are in error in some cases. In addition, there is no information on the crash report form concerning whether or not hazardous materials were spilled. It is noted that Washington may move toward capturing better truck information through incorporation of NGA accident data elements in the future. Second, the staff feel that the “road character” variable in the accident file, which include information such as "straight and level," "curve and grade", etc. is a poor variable. Also, while information is provided on the report form (and in two variables) concerning whether an accident occurred in a construction zone, the staff feels that there are some problems in accuracy because of work zone definition and interpretation problems. (Based on 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.) Finally, as noted above some vehicle and occupant related variables are not coded or coded inconsistently from 1999 to 2001 and are identified by notes in the formats section. All other variables were felt to be accurate.
In addition to information received from the TDO staff, single variable tabulations were run to examine the questions of reporting completeness and data accuracy for accident, vehicle, and occupant variables. Here study of the percent of “unknown,” “not applicable,“ and “not stated” values for over 80 key variables found in these files indicate that, in general, the data is coded to a high degree of completeness. 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, they are noted under the specific variables.
As noted above, using the multiple files provided by Washington from their TRIPS system (Transportation Information and Planning Support System), a series of roadway inventory files which contain current characteristics of the state road system have been developed for the HSIS. There is a basic Roadlog File containing information on such things as lane and shoulder width and type; two supplemental files on horizontal and vertical alignment; a supplemental Roadway Features file containing information on bridges, tunnels, underpasses and other features; a Left/Right file containing information on crossing roadways, milepost markers, and roadside features such as rest areas and weigh stations; and a supplemental Special-Use Lanes File which contains information on bike lanes, climbing lanes, etc.
The Roadlog, Curve, Grade and Ramp Files are "section" files, with each homogeneous roadway section being defined by a beginning and ending milepost. The remaining files are "point data" files describing characteristics at a given milepost. However, some variables in these "point" files include information on the length of a given feature from that point (e.g., the length of a bike lane from the milepost provided). Each of these files is described in the following narrative.
The basic inventory file and supplemental files which are part of the TRIPS were developed in the past based on inventory information collected through a series of field surveys. Prior to 1986, a field survey covering half of the state was conducted each year to verify the information on the file. Due to lack of funds, this process ended after 1986. However, an update to the file is now done on a routine basis by the TDO inventory staff based on new construction drawings. In addition, whenever a major construction or reconstruction project is completed, a manual physical inventory is conducted as a check of the final “as built” construction plans. The only updates that would be missed by the TDO staff are maintenance operations done at the district level. Districts are allowed to do maintenance projects on the roadway for projects which cost up to $30,000. Even for these projects, when it becomes apparent to the central office staff that certain things have been done in the district but have not been reported to them, they request the information from the district. The fact that they do not get systematic reports of these maintenance activities from the district leads the TDO staff to believe that they are missing some data on approximately 10-15 percent of the roadways. However, they feel that the data on 85-90 percent of the inventory system is quite complete and quite accurate.
The HSIS files, developed from files in TRIPS, contain information on approximately 7,000 miles of mainline (non-ramp) roadway and approximately 1,000 additional miles of ramp, frontage road, and other non-mainline roadway. This includes all functional classes of roads within the state system — Interstate, U.S. and state routes. (Note that there are no county- or municipal-owned roads in the file.) Currently, inventory data is available for 1993 to 1996 and from 2002 onwards. Data for intermediate years is unavailable because Washington stopped creating electronic files for those years due to budget restrictions. However, HSIS has AADT files for 1998-2000. While the beginning and end-points of these AADT records differ from the segments in the 1996 and 2002 roadlog file, HSIS staff will work with users in matching these data to the roadlog sections for either or both of those years. Unlike other states, many of the variables in all of the roadway inventory files contain not only a description of the item, but also information concerning the date that the item was last modified. This should allow "before/after" analyses related to the specific roadway changes. Because a new record is generated each time any of the items on a file changes, the sections that are generated are fairly short, resulting in a large number of individual records on the file. For example, the 8,000 miles of basic inventory information is divided into 46,000 records, resulting in an average section length of two tenths of a mile.
Table 1 presents mileage breakdowns for all paved, two-way, mainline roadways (i.e., omitting all unpaved and one-way roadways). As expected since it is a state-controlled system, the file is predominantly rural in nature, with close to 85% of the roadways being in rural areas.
| Roadway Category | Mileage |
|---|---|
| Urban Freeways | 562.07 |
| Urban Freeways < 4 Lanes | 95.86 |
| Urban Multilane Divided Non-Freeways | 49.29 |
| Urban Multilane Undivided Non-Freeways | 238.91 |
| Urban 2 Lane Highways | 328.77 |
| Rural Freeways | 466.91 |
| Rural Freeways < 4 Ins | 1.06 |
| Rural Multilane Divided Non-Freeways | 208.24 |
| Rural Multilane Undivided Non-Freeways | 31.94 |
| Rural 2 Lane Highways | 4958.54 |
| Other | 251.80 |
| Total | 7192.76 |
The basic roadway inventory file for Washington in the HSIS is the Roadlog File. As noted above, this file contains information on a homogeneous section of roadway (i.e., a stretch of road which is consistent in terms of certain characteristics, with a new section being defined each time any of the characteristics changes). Each record on the basic inventory file contains current characteristics of the roadway system and includes over 100 different variables, plus date-of-change variables for many of them. Variables include information on surface width, lane width and type, shoulder width and type, median information, rural/urban codes, terrain codes, and various roadway type descriptors including functional class. Unlike other HSIS state inventories, this file also contains some information on the specifics of turn lanes and acceleration lanes, such as width and length. It should be noted that, like turn lanes, the "acceleration lanes" being described here are related to at-grade intersections which occur at the beginning of a segment, rather than to grade-separated interchanges. Even though included in this section-based file, this acceleration- and turn-lane information is of a "point" nature, in that it is attached to the milepost of the related intersection, which is at the beginning of the section. (Thus, the milepost for the beginning of the acceleration lane will not begin a new section.) The same is true for additional variables related to intersection lighting and traffic control (for the mainline). It is also noted that there may be other intersections within a section that are not noted on this file. Thus, while a new section will begin at some (but not all) intersections with acceleration and/or turn lanes, a new section will not necessarily begin at other intersections. To obtain information on the number of intersections within a given section, one would link this file with the "Left/Right File" described later.
Finally, to facilitate analyses, variables related to Average Annual Daily Traffic (AADT) and Legal Speed Limit (SPD_LIMT) were extracted from other files and merged into the Roadlog File.
As with the accident files, Washington TDO staff were questioned concerning the completeness and accuracy of the variables on the Roadlog File. As noted above, there feeling is that the data are very accurate for between 85-90 percent of the inventoried system. In addition, a series of single variable tabulations for 48 key variables were reviewed. These runs indicated that almost all of the variables have less than five percent of the data uncoded. Where variables should be somewhat consistent (e.g., miles of median type and median width), they are. In summary, the data appear to have a high overall degree of completeness and consistency.
Two new variables, RODWYCLS and MVMT, have been created by HSIS staff in the roadway segment file of each of the HSIS states. The RODWYCLS (Roadway Class) variable is based on the combination of rural/urban, access control, number of lanes and median type variables. This variable classifies each roadway segment into one of ten roadway types described in the later “Format” section. This variable is also included as an accident-file variable by matching each crash to its corresponding roadway segment. The MVMT variable (Million Vehicle Miles of Travel) is calculated for each segment in the roadway file by multiplying the segment length, AADT and 365 days in a year, and dividing by one million. Both these variables were created in response to inquire from data users, whose most frequent questions have concerned either crash frequencies or rates (per MVMT) for one or more of these roadway classes.
Initially, data on horizontal curvature and grade were captured in the roadway features inventory as point data, along with information on bridges, tunnels, underpasses and changes in speed limit. For ease of use and consistency with other HSIS states, two separate section-based files have now been developed — a Curve File and a Grade File. In each case, a new section begins whenever there is a horizontal curve (in the first file) or a change in grade (in the second file.) For use in specific analyses, these files can be merged with the Roadlog File, the Accident File, or with each other using the beginning and ending milepoint variables and the “Road Inventoried” variable.
The Curve File contains information on approximately 15,000 curves. It includes variables related to angle, direction, degree (and radius), length, maximum super-elevation (for a very limited number of curves), legal speed limit, the date of last change to the curve, and whether the curve overlaps with a preceding curve. The latter would occur due to slight errors in ending milepoints resulting from the use of curve length in the calculation of this milepoint. This occurs in less than one percent of the cases. Note that when the curve file is merged with the Roadlog File to put curvature variables on the roadway sections, 70 to 80 percent of the roadway sections will show missing degree of curve and other variables. These "missing sections" actually denote tangent sections where the degree of curve is zero. This should be anticipated and handled by the analyst.
The Grade File contains approximately 33,000 records. In addition to beginning and ending milepoint, the Grade File contains information on the percent grade, direction ("+" or "-"), and length. In addition, the file contains information concerning "Grade Type," which denotes whether the downstream end of the grade is an angle point (i.e., a minor change in grade without a vertical curve) or is connected to the succeeding grade with a vertical curve.
Both curvature and grade information was originally developed from construction drawings and straight-line diagrams. It is updated yearly through review of new construction plans. As with the basic roadway inventory information, Washington TDO staff feel that the data are accurate for approximately 85-90 percent of the inventoried mileage on the TRIPS.
Ramp file, describing the roadway characteristics on ramps is created from the basic roadlog file. There is information on about 13,000 ramps in the ramp file. This file is available from 1993 to 1996 and then again from 2002 onwards. Each ramp has a beginning and ending mile point, and accidents can be linked to the ramp. (Indeed, accidents occurring at the end of a diamond-interchange ramp are located to the end of the ramp rather than to the crossing roadway, giving a clearer picture of ramp-related crashes.) While there is no information on the degree of curve for the ramp, there is information on surface type and width, shoulder type and width, number of lanes and location descriptors (e.g., urban/rural). Also traffic volumes are available only on a limited number of ramps. While there is no variable which will allow one to group the ramps for a given interchange, schematic drawings of each interchange in the state are available at the HSIS offices at FHWA.
In contrast to other states, Washington also provided to HSIS a file containing additional information on approximately 4,000 special auxiliary lanes. The file contains information on the type of special-use lane (e.g., bike lanes, two-way turn lanes in the median, auxiliary climbing lanes), the side of the roadway where the lanes are located, and the length, width and surface-type associated with the lanes. Where data are provided, accuracy is expected to be similar to that in the other inventory files.
This file contains supplemental information on bridges, tunnels, and overpasses. (Speed limit data which was originally in this file have been merged into the Roadlog File.) A new record appears anytime one of these features occurs on the roadway, resulting in approximately 6,000 records. These are point data, with a location and limited descriptive information given for each point on the file. The original TRIPS file also contained the curvature and grade information which was used to build the preceding two HSIS files. While "unique" curve and grade records were eliminated from this Features File, all remaining records still contain all information on curvature and grade. Thus, it is possible to determine whether a bridge or tunnel are located on a curve (or grade), and if so, the specifics of that curve/grade. It is noted, however, that there will be multiple records for the same bridge, tunnel, or overpass, since there will be a record for both the beginning and ending milepoint, and possible additional records if any of the other variables change between these end points (such as a change in grade). As noted earlier, information on the speed limit changes has been merged into the Roadlog File.
In general, except for curve/grade and speed limit information, the file provides little or no additional descriptive information. There is information on whether a feature is lighted or not. However, it is noted that the bridge data have been formatted such that they are linkable with the
National Bridge Index (NBI) file available from FHWA, a file which contains a wealth of descriptive information.
This file contains information on crossings, milepost markers, and various types of facilities found on the left and right sides of the mainline. Of the 49,000 records in the file, the overwhelming majority are related to crossing routes and milepost markers. Milepost marker information is primarily related to the location of the marker. The 25,000 records related to crossing routes contains information on the location of the crossing on the main route, the type of crossing (e.g., intersection, ramp entry/exit), and a brief narrative descriptive of the crossing route (e.g., name or number of street or route). Unfortunately, the file does not contain the related milepost on the crossing route, and thus cannot be linked with inventory data related to that route. The remainder of records on the file are related to various types of facilities including transit ("flyer") stops, park and ride lots, rest areas, truck weight stations, toll booths, ferry terminals, and state border crossing facilities. A new record is created for each point (milepost) where one or more of these facilities exist. In addition to the milepost information, the file contains descriptive information, facility owner, and date of last change for each facility. The samples of these facilities are, as expected, limited. For example, there are approximately 100 rest area and weight station records, and approximately 50 records concerning transit stops. The accuracy of the data in the file is considered quite good.
This file contains information for each milepost where a railroad crosses a state route. The file contains only limited descriptive data (e.g., whether the crossing is at-grade or on a structure). However, it does contain detailed location data, linkage variables and information which will allow one to link this file with the federally-required railroad grade crossing file. The latter file is available at FHWA, and contains a large variety of information on each crossing.
As noted above, traffic count data captured on the TRIPS file contain a number of variables including AADT, single-trailer truck percentage, double-trailer truck percentage, and various peak-hour descriptive percentages. For WA data up to 2004, HSIS staff merged the variables related to AADT and truck percentages into the Roadlog file. The merging method used was based on information received from the WADOT traffic staff during the 1990's. The basic assumption followed at that time was that a new traffic record began when there was change in the AADT. At that point, it appeared that the traffic census staff was identifying “discontinuities” along the routes in terms of volumes — locations where the staff expected there to be significant changes in the AADT, such as intersection with a significant turning volume, or a location of a major traffic generator such as a shopping mall exit. This resulted in a file of what might be considered “homogeneous traffic sections.” Until 2004, the HSIS staff used this information to apply AADTs and truck percentages to each roadway segment in the Roadlog file. However, new information was received from WADOT staff in 2004 indicating that the AADTs on the traffic file sent to HSIS are simply coded to the nearest roadway feature to which the count was conducted. This means that “homogeneous AADT sections” are not actually being defined. Beginning in 2004, WADOT began assigning AADTs to roadway segments based on a more refined procedure that takes into consideration various roadway features such as presence of an interchange and intersection, presence of a couplet, presence of a jurisdiction boundary, and other factors to assign the AADT to the roadway segments. From 2004 onwards, the roadway segments in the WA HSIS roadway file contain this WADOT-assigned AADT data. Note that this will result in some discrepancies between AADT counts for 2004 and prior years for the same roadway segment. (WADOT staff did not correct historic AADTs.) HSIS staff is working to minimize these differences by revising the AADT-to-segment linkage algorithm for these pre-2004 data. However, it will not be possible to exactly match the new methodology, so differences will exist.
For both pre- and post-2004 years, the basis for the traffic information is a series of permanent and non-permanent count stations across the state. While the number has changed over the life of the HSIS files, there are 159 permanent Automatic Traffic Recorders (ATR 's) in the state as of May 2006. All 159 produced volume counts. Of these permanent count stations, 145 produced vehicle classifications counts, 36 produced truck weight plus classifications counts, 14 produced vehicle length counts, and 145 produced speed counts.
In addition to the permanent count stations, the traffic census staff conducts approximately 2,400 short-duration mechanical traffic counts each year. The intent of each is to capture 72 hours of midweek (Tuesday through Thursday) data, although less is sometimes collected due to equipment malfunction or other issues. Of these counts, approximately 740 per year capture vehicle classification information. The counts are not always taken at the exact same sights, but do cover all HPMS locations as well as certain project counts for projects that are conducted each year. In Washington, there are 3,200 HPMS sections. Counts are usually made at each of approximately 5000 locations every third year. Of the 2,400 or so short-duration mechanical traffic counts per year, approximately 730 are conducted on non-federally reportable state highway roadway (e.g., ramps).
With respect to accuracy and completeness, the TDO staff feels that they have very good data on approximately 90 to 95 percent of the roadway in the trips system. They feel that the least accurate information on the file is vehicle classification data (e.g., truck percentages). This is because classification information is often annualized in a much less accurate fashion than total vehicle volume. In addition, vehicle classification data is much less complete, since roadway characteristics often preclude setting short-duration mechanical traffic counters to classify.
As noted under specific variable descriptions in the later format section, certain other variables (such as "Peak Hour Percentage" and "Peak Hour Split") have significant numbers of uncoded ("zero") locations. These represent locations where counts were not made or where old, erroneous counts have been deleted from the file.
As noted above, the accident data are subdivided into three subfiles — accident, vehicle and occupant. These subfiles can be linked together using the "case number" variable which includes the accident year (i.e., CASENO) present in each of the three files. When linking the occupant subfile, the additional linking variable "vehicle number" (i.e., VEHNO) must match so that the occupants are associated with the vehicle in which they were traveling. To link the Vehicle subfile with the Accident alone, first sort both subfiles by case number. To link the Occupant file with the other two subfiles, first sort both the Vehicle subfile and Occupant subfile by case number and vehicle position 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 presorted and the output will not be in any particular sort order unless ORDER BY is specified.
The Accident subfile can then be linked with the Roadlog File using information related to county, route number, and milepost on the route. The actual linkage variables on the Accident file which are used in the merging operation are RD_INV and MILEPOST. The linkage variables on the Roadlog File are BEGMP, ENDMP and ROAD_INV. (Note that in merging the Accident or Roadlog file with other files, the merging variables are the same two milepost variables, and either RD_INV or some variation of the latter variable always ending in "_INV." For example, on the Facilities File, the latter variable is LR_INV.)
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 RD_INV and MILEPOST on the Accident file and by ROAD_INV 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 RD_INV with ROAD_INV, and a range match where MILEPOST occurs between BEGMP and ENDMP. (Programs to accomplish this merging and division are documented in the HSIS Programmer's Guidebook, available at FHWA.)
Finally, where appropriate and possible, a format which defines categories within a given variable has been developed for HSIS SAS variables. These categories are shown in the pages below. These formats have been saved in a format library which can be provided to the user. As a naming convention, the "format name" is the same as the variable name, with the only exception being for certain character variables (in contrast with numeric variables). More specifically, a SAS format name has to be preceded by a "$" if the variable is character in nature.
State Liaison and Accident Data Information — Dan Davis (360-570-2451) — Mr. Davis is the HSIS Liaison and our main contact within the State of Washington when questions arise concerning the Washington data files in general. He is also the expert on the accident data in the WA files. Mr. Davis is the Supervisor of the Collision Data Analysis Branch of the WA DOT.
Roadway Inventory Information — Mark Finch (360-570-2369) — Mr. Finch and his staff are in charge of collection and maintenance of the basic roadway inventory data. He is the Manager of the Roadway Systems Branch of the WA DOT.
Traffic Counts — Dave Bushnell (306-570-2416) — Mr. Bushnell is the Branch Manager of the Travel Analysis Branch of WA DOT. He can provide general information on travel data. Joe St. Charles (360-570-2381) is a Transportation Planner within the Highway Usage Branch of WSDOT, the agency responsible for the statewide traffic counts. Mr. St. Charles developed the algorithm for assigning AADT counts to roadway segments and can provide the details of the traffic data collection system.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AADT | AVER ANNUAL DAILY TRAFFIC | Ramp | NUM | 137 |
| AADT | AVER ANNUAL DAILY TRAFFIC | Roadlog | NUM | 100 |
| AC_MLMP | ACC MAINLINE MILEPOST | Accident | NUM | 43 |
| AC_SRMP | STATE ROUTE MILEPOST | Accident | CHA(1) | 43 |
| AC_SRMPI | SRMP AH/BK | Accident | CHA(1) | 43 |
| ACC_DATE | ACC DATE YYMMDD | Accident | CHA(8) | 43 |
| ACCES_DT | ACCESS CONTROL DATE | Roadlog | CHA(8) | 100 |
| ACCESS | ACCESS CONTROL TYPE | Roadlog | CHA(1) | 100 |
| ACCTYPE | ACC TYPE | Accident | CHA(2) | 43 |
| ACCYR | ACC YEAR | Accident | CHA(4) | 44 |
| ACLL_DT1 | LEFT ACCEL LANE DATE RD1 | Roadlog | CHA(8) | 101 |
| ACLL_DT2 | LEFT ACCEL LANE DATE RD2 | Roadlog | CHA(8) | 101 |
| ACLL_LG1 | LEFT ACCEL LANE LENGTH RD1 | Roadlog | NUM | 101 |
| ACLL_LG2 | LEFT ACCEL LANE LENGTH RD2 | Roadlog | NUM | 101 |
| ACLL_WD1 | LEFT ACCEL LANE WIDTH RD1 | Roadlog | NUM | 101 |
| ACLL_WD2 | LEFT ACCEL LANE WIDTH RD2 | Roadlog | NUM | 102 |
| ACLR_DT1 | RIGHT ACCEL LANE DATE RD1 | Roadlog | CHA(8) | 102 |
| ACLR_DT2 | RIGHT ACCEL LANE DATE RD2 | Roadlog | CHA(8) | 102 |
| ACLR_LG1 | RIGHT ACCEL LANE LENGTH RD1 | Roadlog | NUM | 102 |
| ACLR_LG2 | RIGHT ACCEL LANE LENGTH RD2 | Roadlog | NUM | 102 |
| ACLR_WD1 | RIGHT ACCEL LANE WIDTH RD1 | Roadlog | NUM | 102 |
| ACLR_WD2 | RIGHT ACCEL LANE WIDTH RD2 | Roadlog | NUM | 103 |
| ACSEQ_NB | ACC SEQ NUM | Roadlog | NUM | 103 |
| ADD_INFO | ACC VEH ADDITIONAL INFO | Vehicle | CHA(2) | 69 |
| ADMCLASS | ADMIN CLASS | Accident | CHA(1) | 44 |
| AGE | DRV/OCC AGE | Occupant | NUM | 88 |
| AGENCY | INVESTIGATING AGENCY | Accident | CHA(1) | 45 |
| AIRBAG | OCCUPANT AIRBAY | Occupant | CHA(1) | 88 |
| ALCFLAG | DRV ALCOHOL FLAG | Accident | CHA(1) | 45 |
| BEGMP | BEGMP | Ramp | NUM | 137 |
| BEGMP | BEGMP | Roadlog | NUM | 103 |
| BEGMP | GRADE BEGIN MILEPOST | Grade | NUM | 132 |
| BEGMP | HORIZ CURVE BEGIN MLPOST | Curve | NUM | 128 |
| BODYTYPE | VEH MODEL | Vehicle | CHA(3) | 69 |
| BRDG_DT | BRIDGE DATE | Feature | CHA(8) | 156 |
| BRDG_LGT | BRIDGE LIGHTING | Feature | CHA(1) | 156 |
| BRDG_NBR | BRIDGE NUMBER | Feature | CHA(9) | 156 |
| BRDG_OWN | BRIDGE XROAD OWNER CD | Feature | CHA(2) | 156 |
| BRDG_XRD | BRIDGE XROAD DESC | Feature | CHA(24) | 156 |
| CASENO | ACC REPORT NUMBER | Vehicle | CHA(10) | 69 |
| CASENO | ACC RPT NUMBER | Occupant | CHA(6) | 88 |
| CASENO | ACCIDENT CASE NUMBER | Pedestrian | CHA(10) | 92 |
| CASENO | CASE NUMBER | Accident | CHA(10) | 45 |
| CDHAZNM | COMM CARRIER HAZMAT | Vehicle | CHA(17) | 69 |
| CDPLACCD | COMM CARRIER PLACARD | Vehicle | CHA(1) | 70 |
| CDPLACNO | COMM CARRIER PLACARD NUM | Vehicle | CHA(4) | 70 |
| CDPLACSU | COMM CARRIER PLACARD SUFFIX | Vehicle | CHA(1) | 70 |
| CENTURY | ACC CENTURY | Accident | CHA(2) | 45 |
| CITY | CITY NUMBER | Ramp | CHA(4) | 137 |
| CITY | CITY NUMBER | Roadlog | CHA(4) | 103 |
| CITY | CITY NUMBER | Accident | CHA(4) | 45 |
| CITY_DT | CITY DATE | Ramp | CHA(8) | 140 |
| CITY_DT | CITY DATE | Roadlog | CHA(8) | 106 |
| CLOTHING | PED CLOTHING | Pedestrian | CHA(1) | 92 |
| CMAXLES | COMM CARRIER NUM OF AXLES | Vehicle | CHA(2) | 70 |
| CMCONFIG | COMM CARRIER CONFIG | Vehicle | CHA(1) | 70 |
| CNTL_SEC | CNTL SECTION | Ramp | CHA(8) | 140 |
| CNTL_SEC | CNTL SECTION | Roadlog | CHA(8) | 106 |
| CNTY_DT | COUNTY DATE | Ramp | CHA(8) | 140 |
| CNTY_DT | COUNTY DATE | Roadlog | CHA(8) | 106 |
| COLTYPE1 | ACC 1 TYPE | Accident | CHA(2) | 48 |
| COLTYPE2 | ACC 2 TYPE | Accident | CHA(2) | 48 |
| COM_BODY | COMM CARRIER CARGO BODY | Vehicle | CHA(1) | 70 |
| COM_GWR | COMMERCIAL CARRIER WEIGHT | Vehicle | CHA(6) | 71 |
| COMP_DIR | COMPASS DIRECTION | Roadlog | CHA(2) | 106 |
| CONTRIB1 | DRV CONTRIB CIRCUMS 1 | Vehicle | CHA(2) | 71 |
| CONTRIB1 | PED/CYC CIRCUMSTANCES 1 | Pedestrian | CHA(2) | 92 |
| CONTRIB2 | DRV CONTRIB CIRCUMS 2 | Vehicle | CHA(2) | 71 |
| CONTRIB2 | PED/CYC CIRCUMSTANCES 2 | Pedestrian | CHA(2) | 92 |
| COUNTY | COUNTY NUMBER | Accident | CHA(2) | 49 |
| COUNTY | COUNTY NUMBER | Ramp | CHA(2) | 140 |
| COUNTY | COUNTY NUMBER | Roadlog | CHA(2) | 106 |
| CTY_ZONE | CITY ZONE TYPE | Ramp | CHA(1) | 141 |
| CTY_ZONE | CITY ZONE TYPE | Roadlog | CHA(1) | 107 |
| CURV_ANG | HORIZ CURVE CEN ANGLE | Curve | NUM | 128 |
| CURV_ANG | HORIZ CURVE CEN ANGLE | Feature | NUM | 156 |
| CURV_DT | HORIZ CURVE DATE | Curve | CHA(8) | 128 |
| CURV_DT | HORIZ CURVE DATE | Feature | CHA(8) | 157 |
| CURV_INV | STATE RTE TYPE ID | Curve | CHA(11) | 128 |
| CURV_LGT | HORIZ CURVE LENGTH (FT) | Feature | NUM | 157 |
| CURV_LGT | HORIZ CURVE LGT (FT) | Curve | NUM | 128 |
| CURV_MAX | HORIZ CURVE MAX SUPER | Curve | NUM | 128 |
| CURV_MAX | HORIZ CURVE MAX SUPER | Feature | NUM | 157 |
| CURV_NUM | HORIZ CURVE CONTROL NUM | Feature | CHA(6) | 157 |
| CURV_NUM | HORIZ CURVE NUM | Curve | CHA(6) | 128 |
| CURV_RAD | HORIZ CURVE RAD | Curve | NUM | 128 |
| CURV_RAD | HORIZ CURVE RADIUS | Feature | NUM | 157 |
| CURV_TYP | HORIZ CURVE TYPE | Feature | CHA(1) | 157 |
| CYC_INJ | PEDALCYCLIST INJURY CLASS | Vehicle | CHA(1) | 72 |
| DAMSEV | VEH DAMAGE SEVERITY | Vehicle | CHA(1) | 72 |
| DAYMTH | ACC DAY OF MONTH | Accident | CHA(2) | 50 |
| DEG_CURV | DEGREE OF CURVATURE | Curve | NUM | 129 |
| DETCH_NB | WSP DETACHEMENT NUM | Roadlog | CHA(2) | 107 |
| DEVCD | LEVEL OF DEVLMPT | Ramp | CHA(2) | 141 |
| DEVCD | LEVEL OF DEVLMPT | Roadlog | CHA(2) | 107 |
| DEVCD_DT | LEVEL OF DEVELMT DATE | Ramp | CHA(8) | 141 |
| DEVCD_DT | LEVEL OF DEVELMT DATE | Roadlog | CHA(8) | 107 |
| DIR_CURV | HORIZ CURVE DIRN | Curve | CHA(1) | 129 |
| DIR_CURV | HORIZ CURVE DIRN | Feature | CHA(1) | 157 |
| DIR_DT | COMPASS DIRECTION DATE | Roadlog | CHA(8) | 107 |
| DIR_GRAD | DIRECTION OF GRADE | Grade | CHA(1) | 132 |
| DIR_INV | RDWY DIR OF INVENTORY | Railroad | CHA(1) | 170 |
| DIR_TRVL | VEH MOVEMENT DIRECTION | Vehicle | CHA(2) | 72 |
| DISCN_DT | DISCONTY DATE | Roadlog | CHA(8) | 107 |
| DISCNTY | DISCONTINUITY INDICATOR | LR | CHA(1) | 162 |
| DISCONTY | DISCONTY IND | Roadlog | CHA(2) | 107 |
| DIST_DT | DISTRICT DATE | Feature | CHA(8) | 157 |
| DISTNUM | DISTRICT NUMBER | Feature | CHA(1) | 157 |
| DISTR_DT | DISTRICT DATE | Ramp | CHA(8) | 141 |
| DISTR_DT | DISTRICT DATE | Roadlog | CHA(8) | 108 |
| DISTRICT | DISTRICT NUMBER | Accident | CHA(1) | 50 |
| DISTRICT | DISTRICT NUMBER | Ramp | CHA(1) | 141 |
| DISTRICT | DISTRICT NUMBER | Roadlog | CHA(1) | 108 |
| DOMAIN | DOMAIN TYPE | Roadlog | CHA(2) | 108 |
| DOMN_DT | DOMAIN DATE | Roadlog | CHA(8) | 108 |
| DRAIRBAG | DRV AIRBAG STATUS | Vehicle | CHA(1) | 72 |
| DRASSESS | DRUG RECOG EXPERT ASSESS | Vehicle | CHA(1) | 72 |
| DRV_ACTN | DRV ACTION | Vehicle | CHA(2) | 73 |
| DRV_AGE | DRV AGE | Vehicle | CHA(2) | 73 |
| DRV_EJCT | DRV EJECTION | Vehicle | CHA(1) | 74 |
| DRV_INJ | DRV INJURY CLASS | Vehicle | CHA(1) | 74 |
| DRV_REST | DRV RESTRAINT USAGE | Vehicle | CHA(1) | 74 |
| DRV_SEX | DRV SEX | Vehicle | CHA(1) | 75 |
| EJECT | DRV/OCC EJECTION | Occupant | CHA(1) | 89 |
| ENDMP | CALCULATED ENDING MILEPOST | Ramp | NUM | 142 |
| ENDMP | CALCULATED ENDING MILEPOST | Roadlog | NUM | 109 |
| ENDMP | GRADE END MILEPOST | Grade | NUM | 132 |
| ENDMP | HORIZ CURVE END MLPOST | Curve | NUM | 129 |
| EVENT1 | SEQUENCE OF EVENTS 1 | Vehicle | CHA(2) | 75 |
| EVENT2 | SEQUENCE OF EVENTS 2 | Vehicle | CHA(2) | 75 |
| EVENT3 | SEQUENCE OF EVENTS 3 | Vehicle | CHA(2) | 75 |
| EVENT4 | SEQUENCE OF EVENTS 4 | Vehicle | CHA(2) | 75 |
| EW_DTE | EAST/WEST INDICATOR DATE | Ramp | CHA(8) | 142 |
| EW_DTE | EAST/WEST INDICATOR DATE | Roadlog | CHA(8) | 109 |
| EW_IND | EAST WEST IND | Ramp | CHA(1) | 142 |
| EW_IND | EAST WEST IND | Roadlog | CHA(1) | 109 |
| FACT_DES | FACILITY DESC | LR | CHA(24) | 162 |
| FACT_DT | FACILITY DATE | LR | CHA(8) | 162 |
| FACT_OWN | FACILITY OWNER | LR | CHA(3) | 162 |
| FACT_TYP | FACILITY TYPE | LR | CHA(1) | 162 |
| FED_AID | FED AID CLASS | Ramp | CHA(1) | 142 |
| FED_AID | FED AID CLASS | Roadlog | CHA(1) | 109 |
| FED_CD | FED AID TYPE | Ramp | CHA(4) | 142 |
| FED_CD | FED AID TYPE | Roadlog | CHA(4) | 109 |
| FEDAD_DT | FED-AID DATE | Ramp | CHA(8) | 142 |
| FEDAD_DT | FED-AID DATE | Roadlog | CHA(8) | 109 |
| FIRE | FIRE | Accident | CHA(1) | 50 |
| FLY_DT | FLYER STOP DATE | LR | CHA(8) | 163 |
| FLY_NUM | FLYER STOP NUMBER | LR | CHA(2) | 163 |
| FLY_OWN | FLYER STOP OWNER | LR | CHA(2) | 163 |
| FUNC_CLS | FEDERAL FUNC CLASS | Ramp | CHA(2) | 142 |
| FUNC_CLS | FEDERAL FUNC CLASS | Roadlog | CHA(2) | 109 |
| FUNC_CLS | FUNCTIONAL CLASS | Accident | CHA(2) | 50 |
| FUNC_DT | FUNCTIONAL CLASS DATE | Ramp | CHA(8) | 143 |
| FUNC_DT | FUNCTIONAL CLASS DATE | Roadlog | CHA(8) | 110 |
| GPS_LATX | GPS X | Accident | NUM | 51 |
| GPS_LATY | GPS Y | Accident | NUM | 51 |
| GPS_LATZ | GPS Z | Accident | NUM | 51 |
| GRAD_AHD | VERT ALIGN GRADE AHEAD | Feature | NUM | 158 |
| GRAD_BAK | VERT ALIGN GRADE BACK | Feature | NUM | 158 |
| GRAD_DT | VERT ALIGN DATE OF CHNG | Grade | CHA(8) | 132 |
| GRAD_DT | VERT ALIGN DATE | Feature | CHA(8) | 158 |
| GRAD_INV | STATE RTE TYPE ID | Grade | CHA(11) | 132 |
| GRAD_LGT | VERT CURVE LENGTH (FT) | Feature | NUM | 158 |
| GRAD_NUM | VERT ALIGN CONTR | Grade | CHA(6) | 132 |
| GRAD_NUM | VERT ALIGN CONTR NUM | Feature | CHA(6) | 158 |
| GRAD_TYP | VERT CURVE TYPE | Feature | CHA(1) | 158 |
| GRAD_TYP | VERT CURVE TYPE | Grade | CHA(1) | 132 |
| HAZMAT | HAZARDOUS MATERIAL | Accident | CHA(1) | 51 |
| HELMET | PED/CYC HELMET | Vehicle | CHA(1) | 75 |
| HELMET | PED/CYC HELMET | Occupant | CHA(1) | 89 |
| HELMET | PED/CYC HELMET | Pedestrian | CHA(1) | 93 |
| HIT_RUN | HIT AND RUN | Accident | CHA(1) | 51 |
| HPMS | HPMS SECTION NUMBER | Roadlog | CHA(13) | 110 |
| HPMS_DTE | HPMS DATE | Roadlog | CHA(8) | 110 |
| IMPACT | IMPACT LOCATION | Accident | CHA(2) | 51 |
| IN_DIR | DIRECTION OF INVENTORY | Feature | CHA(1) | 158 |
| IN_INV | STATE RTE TYPE ID | Feature | CHA(11) | 158 |
| IN_MLPT | ACCUM ROUTE MILEPOST | Feature | NUM | 159 |
| IN_RTNBR | ROUTE NUMBER | Feature | CHA(3) | 159 |
| IN_TYPE | RELATED ROAD TYPE | Feature | CHA(2) | 159 |
| INJ | DRV/OCC INJURY | Occupant | CHA(1) | 89 |
| INTENT | INTENTIONAL ACTION | Accident | CHA(1) | 55 |
| INTER_A | INTERSECTION INDICATOR | Vehicle | CHA(1) | 76 |
| INTOX | DRV SOBRIETY | Vehicle | CHA(1) | 76 |
| INTOX | PEDALCYCLIST SOBERITY | Pedestrian | CHA(1) | 93 |
| LANEWID | CALCULATED LANE WIDTH | Ramp | NUM | 143 |
| LANEWID | CALCULATED LANE WIDTH | Roadlog | NUM | 110 |
| LEGAL_SP | LEGAL SPEED LIMIT | Curve | NUM | 129 |
| LEGAL_SP | LEGAL SPEED LIMIT | Grade | NUM | 133 |
| LENGTH | LENGTH OF SLN IN FEET | Spl-ln | NUM | 152 |
| LIGHT | LIGHT CONDITION | Accident | CHA(1) | 55 |
| LOC_CHAR | LOCATION CHARACTERISTICS | Accident | CHA(1) | 55 |
| LOC_TYPE | ACC LOCATION TYPE | Accident | CHA(1) | 56 |
| LOT_DT | PARK RIDE LOT DATE | LR | CHA(8) | 163 |
| LOT_NUM | PARK RIDE LOT NUMBER | LR | CHA(2) | 163 |
| LOT_OWN | PARK RIDE LOT OWNER CD | LR | CHA(2) | 163 |
| LR_ABIND | LR AHEAD/BACK IND | LR | CHA(1) | 164 |
| LR_DESC | MISC FEATURE DESC | LR | CHA(24) | 164 |
| LR_DISTR | DISTRICT NUMBER | LR | CHA(1) | 164 |
| LR_INV | LEFT RIGHT ROAD INVENTORED | LR | CHA(11) | 164 |
| LR_MLPT | LR ACCUM ROUTE MILEPOST | LR | NUM | 164 |
| LR_MTDTE | LEFT RIGHT MAINTENACE DATE | LR | CHA(8) | 164 |
| LR_QUAL | RELATED ROAD QUAL | LR | CHA(6) | 164 |
| LR_RARM | LEFT RIGHT REVERSE ARM | LR | NUM | 165 |
| LR_RDTY | RELATED ROAD TYPE | LR | CHA(2) | 165 |
| LR_RTNBR | ROUTE NUMBER | LR | CHA(3) | 165 |
| LR_SEC | CONTROL SECTION | LR | CHA(6) | 165 |
| LR_SIDE | LEFT/RIGHT SIDE IND | LR | CHA(2) | 165 |
| LR_SRMP | LEFT RIGHT SRMP | LR | NUM | 165 |
| LRDIS_DT | DISTRICT DATE | LR | CHA(8) | 164 |
| LRMIS_DT | MISC FEATURE DATE | LR | CHA(8) | 164 |
| LSHL_DT2 | LEFT SHOULDER DATE RD2 | Roadlog | CHA(8) | 110 |
| LSHL_DTE | LEFT SHOULDER DATE RD1 | Ramp | CHA(8) | 143 |
| LSHL_DTE | LEFT SHOULDER DATE RD1 | Roadlog | CHA(8) | 110 |
| LSHL_TY2 | LEFT SHOULDER TYPE RD2 | Roadlog | CHA(1) | 110 |
| LSHL_TYP | LEFT SHOULDER TYPE RD1 | Ramp | CHA(1) | 143 |
| LSHL_TYP | LEFT SHOULDER TYPE RD1 | Roadlog | CHA(1) | 111 |
| LSHL_WD2 | LEFT SHOULDER WIDTH RD1 | Roadlog | NUM | 111 |
| LSHLDWID | LEFT SHOULDER WIDTH RD1 | Ramp | NUM | 143 |
| LSHLDWID | LEFT SHOULDER WIDTH RD1 | Roadlog | NUM | 111 |
| LST_UPDT | CNTL SEC LST UPD | Ramp | CHA(8) | 144 |
| LST_UPDT | CNTL SEC LST UPD | Roadlog | CHA(8) | 112 |
| LST_UPDT | LAST UPDATE DATE | LR | CHA(8) | 165 |
| MAINTDT | LAST MAINTENANCE DATE | Accident | CHA(8) | 56 |
| MAKE | VEHICLE MAKE | Vehicle | CHA(4) | 76 |
| MARK_DT | MILEPOST MARKER DATE | LR | CHA(8) | 165 |
| MARK_IND | MILEPOST MARKER AB IND | LR | CHA(1) | 165 |
| MARK_NUM | MILEPOST MARKER NUMBER | LR | CHA(3) | 166 |
| MDXN_DTE | MEDIAN CROSSING DATE | Roadlog | CHA(8) | 112 |
| MED_TYPE | MEDIAN TYPE | Roadlog | CHA(1) | 112 |
| MEDBARTY | MEDIAN BARRIER TYPE | Roadlog | CHA(2) | 112 |
| MEDCAUSE | MEDICALLY CAUSED | Accident | CHA(1) | 56 |
| MEDN_DTE | MEDIAN DATE | Roadlog | CHA(8) | 112 |
| MEDWID | MEDIAN WIDTH | Roadlog | NUM | 112 |
| MEDXNGTY | MEDIAN CROSSING TYPE | Roadlog | CHA(1) | 113 |
| MILEPOST | ACCUM ROUTE MILEPOST (ARM) | Accident | NUM | 56 |
| MISCACT1 | DRV MISC ACTION 1 | Vehicle | CHA(2) | 76 |
| MISCACT2 | DRV MISC ACTION 2 | Vehicle | CHA(2) | 76 |
| MLMP_IND | MAINLINE ARM INDICATOR | Accident | CHA(1) | 56 |
| MNT_AREA | MAINTENANCE AREA NBR | Ramp | CHA(1) | 144 |
| MNT_AREA | MAINTENANCE AREA NBR | Roadlog | CHA(1) | 113 |
| MNT_DTE | MAINTENANCE DATE | Ramp | CHA(8) | 144 |
| MNT_DTE | MAINTENANCE DATE | Roadlog | CHA(8) | 113 |
| MNTSC_DT | MAINTENANCE SECTION DATE | Ramp | CHA(8) | 144 |
| MNTSC_DT | MAINTENANCE SECTION DATE | Roadlog | CHA(8) | 113 |
| MNTSEC | MAINTENANCE SECT NBR | Ramp | CHA(2) | 144 |
| MNTSEC | MAINTENANCE SECT NBR | Roadlog | CHA(2) | 113 |
| MONTH | ACC MONTH | Accident | CHA(2) | 56 |
| MT_DTE | LAST MAINT DATE | Ramp | CHA(8) | 144 |
| MT_DTE | LAST MAINT DATE | Roadlog | CHA(8) | 113 |
| MT_PASID | MTN PASS ID | Roadlog | CHA(4) | 113 |
| MTC_INJ | PEDALCYCLIST INJURY CLASS | Vehicle | CHA(1) | 79 |
| MTC_INJ_TYPE | PECALCYCLIST INJURY TYPE | Vehicle | CHA(1) | 79 |
| MTPAS_DT | MOUNTAIN PASS DATE | Roadlog | CHA(8) | 114 |
| MVMT | MILLION VEH MILES TRAVELLED | Accident | NUM | 57 |
| MVMT | MILLION VEH MILES TRAVELLED | Roadlog | NUM | 114 |
| NHS_DT | NHS DATE | Roadlog | CHA(8) | 114 |
| NHS_IND | NHS IND | Roadlog | CHA(1) | 114 |
| NO_LANE1 | NUMBER LANES INC | Ramp | NUM | 144 |
| NO_LANE1 | NUMBER LANES INC | Roadlog | NUM | 114 |
| NO_LANE2 | NUMBER LANES DEC | Ramp | NUM | 144 |
| NO_LANE2 | NUMBER LANES DEC | Roadlog | NUM | 114 |
| NO_LANES | TOTAL NUMBER OF LANES | Ramp | NUM | 144 |
| NO_LANES | TOTAL NUMBER OF LANES | Roadlog | NUM | 114 |
| NO_LNDT1 | NUMBER OF LANES DATE RD1 | Ramp | CHA(8) | 145 |
| NO_LNDT1 | NUMBER OF LANES DATE RD1 | Roadlog | CHA(8) | 115 |
| NO_LNDT2 | NUMBER OF LANES DATE RD2 | Ramp | CHA(8) | 145 |
| NO_LNDT2 | NUMBER OF LANES DATE RD2 | Roadlog | CHA(8) | 115 |
| NO_OCCS | NUMBER OF OCCUPANTS | Occupant | NUM | 89 |
| NO_PEDS | NUMBER OF PEDESTRAINS | Accident | NUM | 57 |
| NONMVIND | NON-TRAFFIC INDICATOR | Accident | CHA(1) | 57 |
| NUMVEHS | NUMBER OF VEH | Accident | NUM | 57 |
| OBJECT1 | OBJECT STRUCK 1 | Accident | CHA(2) | 57 |
| OBJECT2 | OBJECT STRUCK 2 | Accident | CHA(2) | 57 |
| OCCUPAC | DRV OCCUPATION | Vehicle | CHA(2) | 79 |
| OFF_ACTN | OFFICER ACTION | Vehicle | CHA(1) | 80 |
| ON_DUTY | ON DUTY STATUS | Vehicle | CHA(1) | 80 |
| OUTSTATE | VEH STATE OF REGISTRATION | Vehicle | CHA(2) | 80 |
| OVERLAP | CURVE OVERLAP IND | Curve | CHA(3) | 129 |
| PCT_GRAD | PERCENT GRADE | Grade | NUM | 133 |
| PED_AGE | PED/CYC AGE | Pedestrian | CHA(2) | 93 |
| PED_CLT | PED/CYC CLOTHING | Vehicle | CHA(1) | 80 |
| PED_CUM1 | PED/CYC CIRCUMS 1 | Vehicle | CHA(1) | 80 |
| PED_CUM2 | PED/CYC CIRCUMS 2 | Vehicle | CHA(1) | 80 |
| PED_INJ | PED/CYC INJURY | Pedestrian | CHA(1) | 93 |
| PED_LOC | PED/CYC LOCATION | Vehicle | CHA(2) | 81 |
| PED_SEX | PED/CYC SEX | Pedestrian | CHA(1) | 94 |
| PED_STUS | PED/CYC STATUS | Pedestrian | CHA(1) | 94 |
| PED_STUS | PED/CYC STATUS | Vehicle | CHA(1) | 81 |
| PED_WALK | PED WALKING LOCATION | Pedestrian | CHA(1) | 94 |
| PED_WLK | PED WALK | Vehicle | CHA(1) | 81 |
| PEDACT | PED/CYC ACTIONS | Vehicle | CHA(2) | 82 |
| PEDACT | PED/CYCLIST ACTION | Pedestrian | CHA(2) | 94 |
| PGRP_DT | POPULATION GROUP DATE | Ramp | CHA(8) | 145 |
| PGRP_DT | POPULATION GROUP DATE | Roadlog | CHA(8) | 115 |
| PKZNE_DT | PARKING ZONE DATE | LR | CHA(8) | 166 |
| PKZNE_TY | PARKING ZONE TYPE | LR | CHA(1) | 166 |
| POP_GRP | CITY POPULATION | Roadlog | CHA(2) | 115 |
| POP_GRP | CITY POPULATION | Ramp | CHA(2) | 145 |
| PREFX_CD | PREFIX 1 | Accident | CHA(1) | 58 |
| PRK_ZNE | PARKING ZONE TYPE | Roadlog | CHA(1) | 115 |
| PRKZN_DT | PARKING ZONE TYPE DATE | Roadlog | CHA(8) | 115 |
| PROPDAM | PROPERTY DAMAGE AMOUNT | Accident | NUM | 59 |
| RAMP_IND | RAMP INDICATOR | Accident | CHA(1) | 59 |
| RD_ABIND | RDWY AHEAD/BACK IND | Roadlog | CHA(1) | 116 |
| RD_CHAR1 | ROADWAY CHARACTERISTICS | Accident | CHA(1) | 59 |
| RD_EQDTE | EQUATION DATE | Roadlog | CHA(8) | 116 |
| RD_EQUAT | EQUATION | Ramp | CHA(17) | 145 |
| RD_EQUAT | EQUATION | Roadlog | CHA(17) | 116 |
| RD_INV | ROADWAY INVENTORY | Accident | CHA(11) | 59 |
| RD_LIGHT | INTERSECTION ILLUM-ND | Ramp | CHA(1) | 146 |
| RD_LIGHT | INTERSECTION ILLUM-ND | Roadlog | CHA(1) | 116 |
| RD_OPEN | ROAD OPEN DATE | Ramp | CHA(8) | 146 |
| RD_OPEN | ROAD OPEN DATE | Roadlog | CHA(8) | 116 |
| RD_OWNER | ROADWAY OWNER CODE | Ramp | CHA(2) | 146 |
| RD_OWNER | ROADWAY OWNER CODE | Roadlog | CHA(2) | 116 |
| RD_QUAL | RELATED RD QUAL | Ramp | CHA(8) | 146 |
| RD_QUAL | RELATED RD QUAL | Roadlog | CHA(8) | 116 |
| RD_QUAL | ROADWAY QUALIFIER | Accident | CHA(6) | 60 |
| RD_RARM | REVERSE ARM | Ramp | NUM | 146 |
| RD_RARM | REVERSE ARM | Roadlog | NUM | 116 |
| RD_REL | ON/OFF ROAD | Accident | CHA(1) | 60 |
| RD_SEP | VEH ROAD SEPARATE | Vehicle | CHA(1) | 82 |
| RD_SRMP | RDWY SRMP | Ramp | NUM | 146 |
| RD_SRMP | RDWY SRMP | Roadlog | NUM | 116 |
| RD_TYPE | RELATED RD TYPE | Ramp | CHA(2) | 146 |
| RD_TYPE | RELATED RD TYPE | Roadlog | CHA(2) | 117 |
| RD_TYPE | RELATED ROADWAY TYPE | Accident | CHA(2) | 60 |
| RDAC_MGC | ACCESS MANAGEMENT CLASS | Roadlog | CHA(1) | 117 |
| RDAC_MGS | ACCESS MANAGEMENT SUBCLASS | Roadlog | CHA(1) | 117 |
| RDQUAL | RELATED ROADWAY QUALIFIER | Accident | CHA(6) | 60 |
| RDSURF | ROADWAY SURFACE | Accident | CHA(1) | 60 |
| RDWY_WD1 | ROADWAY WIDTH RD 1 | Ramp | NUM | 147 |
| RDWY_WD1 | ROADWAY WIDTH RD 1 | Roadlog | NUM | 117 |
| RDWY_WD2 | ROADYWAY WIDTH RD 2 | Roadlog | NUM | 117 |
| RDWY_WID | TOTAL ROADWAY WIDTH | Ramp | NUM | 147 |
| RDWY_WID | TOTAL ROADWAY WIDTH | Roadlog | NUM | 118 |
| RDWYWDD1 | ROADWAY WIDTH DATE RD 1 | Ramp | CHA(8) | 147 |
| RDWYWDD1 | ROADWAY WIDTH DATE RD 1 | Roadlog | CHA(8) | 118 |
| RDWYWDD2 | ROADWAY WIDTH DATE RD 2 | Roadlog | CHA(8) | 118 |
| REC_TYPE | RECORD TYPE | Accident | NUM | 61 |
| REC_TYPE | RECORD TYPE | Feature | NUM | 159 |
| REC_TYPE | RECORD TYPE | LR | NUM | 166 |
| REC_TYPE | RECORD TYPE | Railroad | NUM | 170 |
| REC_TYPE | RECORD TYPE | Ramp | NUM | 147 |
| REC_TYPE | RECORD TYPE | Roadlog | NUM | 118 |
| REPORT | ACC SEVERITY | Accident | CHA(1) | 61 |
| RESIDLOC | DRV RESIDENCE PROXIMITY | Vehicle | CHA(1) | 82 |
| REST_DT | REST AREA DATE | LR | CHA(8) | 166 |
| REST_NAM | REST AREA NAME | LR | CHA(24) | 166 |
| REST_NUM | REST AREA NUMER | LR | CHA(4) | 166 |
| REST_TYP | REST AREA TYPE | LR | CHA(2) | 166 |
| REST1 | DRV/OCC RESTRAINT | Occupant | CHA(1) | 89 |
| REV_MP | REVERSE ARM | Accident | NUM | 61 |
| ROAD_INV | ROUTE TYPE ID | Ramp | CHA(11) | 147 |
| ROAD_INV | ROUTE TYPE ID | Roadlog | CHA(11) | 118 |
| RODWYCLS | ROADWAY CLASS | Accident | CHA(2) | 61 |
| RODWYCLS | ROADWAY CLASSIFICATION | Roadlog | CHA(2) | 118 |
| RR_ABIND | RR CROSSING AB IND | Railroad | CHA(1) | 170 |
| RR_DISTR | DISTRICT NUMBER | Railroad | CHA(1) | 170 |
| RR_INV | RR CROSSING ROAD INV | Railroad | CHA(11) | 171 |
| RR_MLPT | RR XING ACCUM ROUTE MLPST | Railroad | NUM | 171 |
| RR_MTDTE | RR CROSSING MAINT DTE | Railroad | CHA(8) | 171 |
| RR_QUAL | RELATED ROAD QUAL | Railroad | CHA(6) | 171 |
| RR_RARM | RR CROSSING REVERSE ARM | Railroad | NUM | 171 |
| RR_RDTY | RELATED ROAD TYPE | Railroad | NUM | 171 |
| RR_RTNBR | ROUTE NUMBER | Railroad | CHA(3) | 171 |
| RR_SRMP | RR CROSSING SRMP | Railroad | NUM | 171 |
| RRDIS_DT | DISTRICT DATE | Railroad | CHA(8) | 170 |
| RRX_DTE | RR XING DATE | Railroad | CHA(8) | 170 |
| RRX_NUM | RR XING AAR NUM | Railroad | CHA(7) | 170 |
| RRX_TYPE | RR XING TYPE | Railroad | CHA(1) | 170 |
| RSHL_DT2 | RIGHT SHOULDER DATE RD2 | Roadlog | CHA(8) | 118 |
| RSHL_DTE | RIGHT SHOULDER DATE RD1 | Ramp | CHA(8) | 148 |
| RSHL_DTE | RIGHT SHOULDER DATE RD1 | Roadlog | CHA(8) | 119 |
| RSHL_TY2 | RIGHT SHOULDER TYPE RD2 | Roadlog | CHA(1) | 119 |
| RSHL_TYP | RIGHT SHOULDER TYPE RD1 | Ramp | CHA(1) | 148 |
| RSHL_TYP | RIGHT SHOULDER TYPE RD1 | Roadlog | CHA(1) | 119 |
| RSHL_WD2 | RIGHT SHOULDER WIDTH RD2 | Roadlog | NUM | 119 |
| RSHLDWID | RIGHT SHOULDER WIDTH RD1 | Ramp | NUM | 148 |
| RSHLDWID | RIGHT SHOULDER WIDTH RD1 | Roadlog | NUM | 119 |
| RTE_NBR | ROUTE NUMBER | Grade | CHA(3) | 133 |
| RTE_NBR | ROUTE NUMBER | Curve | CHA(3) | 129 |
| RTE_NBR | ROUTE NUMBER | Ramp | CHA(3) | 148 |
| RTE_NBR | ROUTE NUMBER | Roadlog | CHA(3) | 120 |
| RTE_NBR | STATE ROUTE NUMBER | Accident | CHA(3) | 61 |
| RUR_URB | RURAL URBAN | Accident | CHA(1) | 61 |
| RURURB | RURAL URBAN | Ramp | CHA(1) | 148 |
| RURURB | RURAL URBAN | Roadlog | CHA(1) | 120 |
| SEATPOS | DRV/OCC SEAT POSITION | Occupant | CHA(1) | 90 |
| SEG_LNG | GRADE LENGTH (MI) | Grade | NUM | 133 |
| SEG_LNG | HORIZ CURVE LGT (MI) | Curve | NUM | 130 |
| SEG_LNG | RD CALCULATED SECT LNGTH | Ramp | NUM | 148 |
| SEG_LNG | RD CALCULATED SECT LNGTH | Roadlog | NUM | 120 |
| SEQNO | SEQUENCE NUMBER | Accident | NUM | 61 |
| SEVERITY | MOST SEVERE INJURY | Accident | CHA(1) | 61 |
| SEX | DRV/OCC SEX | Occupant | CHA(1) | 90 |
| SLN_ABID | SPEC USE LANES AB IND | Spl-ln | CHA(1) | 152 |
| SLN_DATE | SPECIAL LANE DATE | Spl-ln | CHA(8) | 152 |
| SLN_DIST | SLN DISTRICT NUMBER | Spl-ln | CHA(1) | 152 |
| SLN_DSDT | SLN DISTRICT DATE | Spl-ln | CHA(8) | 152 |
| SLN_INV | SLN ROAD INV-SR TYPE ID | Spl-ln | CHA(11) | 152 |
| SLN_MLPT | SPEC USE LANES ARM | Spl-ln | NUM | 152 |
| SLN_MTDT | SPEC USE LANES MAINT DTE | Spl-ln | CHA(8) | 152 |
| SLN_QUAL | RELATED ROAD QUAL | Spl-ln | CHA(6) | 152 |
| SLN_RARM | SPEC USE LANES RV ARM | Spl-ln | NUM | 153 |
| SLN_RDTY | RELATED ROAD TYPE | Spl-ln | CHA(2) | 153 |
| SLN_RTNO | ROUTE NUMBER | Spl-ln | CHA(3) | 153 |
| SLN_SFTY | SPECIAL LANE SURFACE TYPE | Spl-ln | CHA(1) | 153 |
| SLN_SIDE | SLN LEFT/RIGHT SIDE IND | Spl-ln | CHA(2) | 153 |
| SLN_SRMP | SPEC USE LANES SRMP | Spl-ln | NUM | 153 |
| SLN_TYPE | SPECIAL LANE TYPE | Spl-ln | CHA(2) | 153 |
| SLN_WID | SPECIAL LANE WIDTH | Spl-ln | CHA(2) | 154 |
| SOB_TEST | DRV SOBRIETY | Vehicle | CHA(1) | 83 |
| SPD_DTE | SPEED DATE | Feature | CHA(8) | 159 |
| SPD_LIMT | LEGAL SPEED LIMIT | Feature | NUM | 159 |
| SPD_LIMT | LEGAL SPEED LIMIT | Roadlog | NUM | 120 |
| SPDLIMIT | VEH POSTED SPEED | Vehicle | CHA(2) | 83 |
| SPILLAGE | FUEL SPILLAGE | Accident | CHA(1) | 62 |
| SR_ADID | STATE ROUTE ADDITIONAL ID | Accident | CHA(3) | 62 |
| ST_FUNC | STATE FUNC CLASS | Ramp | CHA(2) | 149 |
| ST_FUNC | STATE FUNC CLASS | Roadlog | CHA(2) | 121 |
| ST_FUNC | STATE FUNCTIONAL CLASS | Accident | CHA(2) | 62 |
| STOLEN | VEH STOLEN | Vehicle | CHA(1) | 83 |
| STR_ALIS | STREET NAME ALIAS | Feature | CHA(24) | 159 |
| STR_DTE | STRUCTURE DATE | Feature | CHA(8) | 159 |
| STREPORT | STATE REPORT | Accident | CHA(1) | 63 |
| STYLE | VEH STYLE | Vehicle | CHA(2) | 83 |
| SURF_TY2 | SURFACE TYPE RD2 | Roadlog | CHA(1) | 121 |
| SURF_TYP | ROADWAY SURFACE TYPE | Vehicle | CHA(1) | 84 |
| SURF_TYP | SURFACE TYPE RD1 | Ramp | CHA(1) | 149 |
| SURF_TYP | SURFACE TYPE RD1 | Roadlog | CHA(1) | 121 |
| SWS_DT | STATEWIDE SYSTEM DATE | Roadlog | CHA(8) | 121 |
| SWS_IND | STATEWIDE SYSTEM IND | Roadlog | CHA(1) | 121 |
| TERRAIN | TERRAIN TYPE | Roadlog | CHA(1) | 121 |
| TERRN_DT | TERRAIN DATE | Roadlog | CHA(8) | 122 |
| TIME | ACC TIME | Accident | CHA(4) | 63 |
| TIMEARR | POLICE ARRIVED TIME | Accident | CHA(4) | 63 |
| TIMENOTE | POLICE DISPATCHED TIME | Accident | CHA(4) | 63 |
| TOT_INJ | NUMBER OF PERSONS INJURED | Accident | NUM | 63 |
| TOT_KILL | NUMBER OF PERSONS KILLED | Accident | NUM | 64 |
| TOT_PED | NUMBER OF PED/CYC | Accident | NUM | 64 |
| TRAILER | TRAILER INFO | Vehicle | CHA(1) | 84 |
| TRF_CNTL | INTERSECTION CONTROL TYPE | Ramp | CHA(2) | 149 |
| TRF_CNTL | INTERSECTION CONTROL TYPE | Roadlog | CHA(2) | 122 |
| TRF_CNTL | VEH TRAFFIC CONTROL | Vehicle | CHA(1) | 84 |
| TRFCN_DT | TRAFFIC CONTROL DATE | Ramp | CHA(8) | 149 |
| TRFCN_DT | TRAFFIC CONTROL DATE | Roadlog | CHA(8) | 122 |
| TRKPCTS | TRUCK PERCENTAGE | Ramp | NUM | 150 |
| TRKPCTS | TRUCK PERCENTAGE | Roadlog | NUM | 122 |
| TRLL_DT1 | LEFT TURN LANE DATE RD1 | Roadlog | CHA(8) | 122 |
| TRLL_DT2 | LEFT TURN LANE DATE RD2 | Roadlog | CHA(8) | 122 |
| TRLL_LG1 | LEFT TURN LANE LENGTH RD1 | Roadlog | NUM | 123 |
| TRLL_LG2 | LEFT TURN LANE LENGTH RD2 | Roadlog | NUM | 123 |
| TRLL_WD1 | LEFT TURN LANE WIDTH RD1 | Roadlog | NUM | 123 |
| TRLL_WD2 | LEFT TURN LANE WIDTH RD2 | Roadlog | NUM | 123 |
| TRLR_DT1 | RIGHT TURN LANE DATE RD1 | Roadlog | CHA(8) | 123 |
| TRLR_DT2 | RIGHT TURN LANE DATE RD2 | Roadlog | CHA(8) | 123 |
| TRLR_LG1 | RIGHT TURN LANE LENGTH RD1 | Roadlog | NUM | 124 |
| TRLR_LG2 | RIGHT TURN LANE LENGTH RD2 | Roadlog | NUM | 124 |
| TRLR_WD1 | RIGHT TURN LANE WIDTH RD1 | Roadlog | NUM | 124 |
| TRLR_WD2 | RIGHT TURN LANE WIDTH RD2 | Roadlog | NUM | 124 |
| TUN_NAME | TUNNEL NAME | Feature | CHA(24) | 160 |
| TUN_NUM | TUNNEL NUMBER | Feature | CHA(9) | 160 |
| TUNL_DT | TUNNEL DATE | Feature | CHA(8) | 160 |
| UBREG_DT | URBAN NUMBER DATE | Ramp | CHA(8) | 150 |
| UBREG_DT | URBAN NUMBER DATE | Roadlog | CHA(8) | 124 |
| UNX_DT | UNXING DATE | Feature | CHA(8) | 160 |
| UNX_LGT | UNXING LIGHTING | Feature | CHA(1) | 160 |
| UNX_OVHD | OVHD BRIDGE NUM | Feature | CHA(9) | 160 |
| UNX_XRD | UNXROAD DESC | Feature | CHA(24) | 160 |
| UNX_XRDO | UNXROAD OWNER CD | Feature | CHA(2) | 160 |
| URB_DT | URBAN REGION DATE | Ramp | CHA(8) | 150 |
| URB_DT | URBAN REGION DATE | Roadlog | CHA(8) | 124 |
| URB_NBR | URBAN AREA NUMBER | Ramp | CHA(2) | 150 |
| URB_NBR | URBAN AREA NUMBER | Roadlog | CHA(2) | 125 |
| URB_REG | URBAN REGION NUMBER | Ramp | CHA(1) | 150 |
| URB_REG | URBAN REGION NUMBER | Roadlog | CHA(1) | 125 |
| V_STATE | STATE OF VEH REGISTRATION | Vehicle | CHA(2) | 84 |
| V1CMPDIR | V1 COMPASS DIRECTION | Accident | CHA(1) | 64 |
| V1DIRCDE | V1 DIRECTION | Accident | CHA(1) | 64 |
| V1EVENT1 | V1 MOVEMENT | Accident | CHA(1) | 65 |
| V2CMPDIR | V2 COMPASS DIRECTION | Accident | CHA(1) | 64 |
| V2DIRCDE | V2 DIRECTION | Accident | CHA(1) | 64 |
| V2EVENT1 | V2 MOVEMENT | Accident | CHA(1) | 65 |
| VCUR_LGT | VERTICAL CURVE LENGTH | Grade | NUM | 133 |
| VEH_SEV | DRV INJURY SEVERITY | Vehicle | CHA(1) | 84 |
| VEH_USE | VEH USAGE | Vehicle | CHA(2) | 85 |
| VEHCOND1 | VEH DEFECT 1 | Vehicle | CHA(2) | 85 |
| VEHCOND2 | VEH DEFECT 2 | Vehicle | CHA(2) | 85 |
| VEHCOND3 | VEH DEFECT 3 | Vehicle | CHA(2) | 85 |
| VEHNO | VEH NUMBER | Vehicle | NUM | 86 |
| VEHNO | VEHICLE NUMBER | Occupant | NUM | 90 |
| VEHNO | VEHICLE NUMBER | Pedestrian | NUM | 95 |
| VEHTYPE | VEH TYPE | Vehicle | CHA(2) | 86 |
| VEHYR | VEH YEAR | Vehicle | CHA(2) | 86 |
| VRD_TYPE | ROADWAY TYPE | Vehicle | CHA(1) | 86 |
| WEATHER | WEATHER CONDITION | Accident | CHA(1) | 65 |
| WEEKDAY | DAY OF WEEK | Accident | CHA(1) | 65 |
| WGHT_DT | WEIGHT STATION DATE | LR | CHA(8) | 166 |
| WGHT_NUM | WEIGHT STATION NUMBER | LR | CHA(2) | 167 |
| WGHT_TYP | WEIGHT STATION TYPE | LR | CHA(2) | 167 |
| WKZONE | WORK ZONE STATUS | Accident | CHA(1) | 66 |
| WSP_DIST | WSP DISTRICT NUMBER | Ramp | CHA(1) | 150 |
| WSP_DIST | WSP DISTRICT NUMBER | Roadlog | CHA(1) | 125 |
| WSP_DT | WSP DATE | Ramp | CHA(8) | 150 |
| WSP_DT | WSP DATE | Roadlog | CHA(8) | 125 |
| WSP_UPDT | WSP UPDATE DATE | Accident | NUM | 66 |
| XRD_DESC | CROSSROAD ID DESC | LR | CHA(24) | 167 |
| XRD_DT | CROSSROAD DATE | LR | CHA(8) | 167 |
| XRD_OWN | CROSSROAD OWNER CD | LR | CHA(3) | 167 |
| XRD_TYP | CROSSROAD CONFIG TYPE | LR | CHA(1) | 167 |
| XRDCLASS | CROSS ROAD CLASS TYPE | Accident | CHA(1) | 66 |
| ZONE_DT | ZONE DATE | Roadlog | CHA(8) | 125 |
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AC_MLMP | ACC MAINLINE MILEPOST | Accident | NUM | 43 |
| AC_SRMP | STATE ROUTE MILEPOST | Accident | CHA(1) | 43 |
| AC_SRMPI | SRMP AH/BK | Accident | CHA(1) | 43 |
| ACC_DATE | ACC DATE YYMMDD | Accident | CHA(8) | 43 |
| ACCTYPE | ACC TYPE | Accident | CHA(2) | 43 |
| ACCYR | ACC YEAR | Accident | CHA(4) | 44 |
| ADMCLASS | ADMIN CLASS | Accident | CHA(1) | 44 |
| AGENCY | INVESTIGATING AGENCY | Accident | CHA(1) | 45 |
| ALCFLAG | DRV ALCOHOL FLAG | Accident | CHA(1) | 45 |
| CASENO | CASE NUMBER | Accident | CHA(10) | 45 |
| CENTURY | ACC CENTURY | Accident | CHA(2) | 45 |
| CITY | CITY NUMBER | Accident | CHA(4) | 45 |
| COLTYPE1 | ACC 1 TYPE | Accident | CHA(2) | 48 |
| COLTYPE2 | ACC 2 TYPE | Accident | CHA(2) | 48 |
| COUNTY | COUNTY NUMBER | Accident | CHA(2) | 49 |
| DAYMTH | ACC DAY OF MONTH | Accident | CHA(2) | 50 |
| DISTRICT | DISTRICT NUMBER | Accident | CHA(1) | 50 |
| FIRE | FIRE | Accident | CHA(1) | 50 |
| FUNC_CLS | FUNCTIONAL CLASS | Accident | CHA(2) | 50 |
| GPS_LATX | GPS X | Accident | NUM | 51 |
| GPS_LATY | GPS Y | Accident | NUM | 51 |
| GPS_LATZ | GPS Z | Accident | NUM | 51 |
| HAZMAT | HAZARDOUS MATERIAL | Accident | CHA(1) | 51 |
| HIT_RUN | HIT AND RUN | Accident | CHA(1) | 51 |
| IMPACT | IMPACT LOCATION | Accident | CHA(2) | 51 |
| INTENT | INTENTIONAL ACTION | Accident | CHA(1) | 55 |
| LIGHT | LIGHT CONDITION | Accident | CHA(1) | 55 |
| LOC_CHAR | LOCATION CHARACTERISTICS | Accident | CHA(1) | 55 |
| LOC_TYPE | ACC LOCATION TYPE | Accident | CHA(1) | 56 |
| MAINTDT | LAST MAINTENANCE DATE | Accident | CHA(8) | 56 |
| MEDCAUSE | MEDICALLY CAUSED | Accident | CHA(1) | 56 |
| MILEPOST | ACCUM ROUTE MILEPOST (ARM) | Accident | NUM | 56 |
| MLMP_IND | MAINLINE ARM INDICATOR | Accident | CHA(1) | 56 |
| MONTH | ACC MONTH | Accident | CHA(2) | 56 |
| MVMT | MILLION VEH MILES TRAVELLED | Accident | NUM | 57 |
| NO_PEDS | NUMBER OF PEDESTRAINS | Accident | NUM | 57 |
| NONMVIND | NON-TRAFFIC INDICATOR | Accident | CHA(1) | 57 |
| NUMVEHS | NUMBER OF VEH | Accident | NUM | 57 |
| OBJECT1 | OBJECT STRUCK 1 | Accident | CHA(2) | 57 |
| OBJECT2 | OBJECT STRUCK 2 | Accident | CHA(2) | 57 |
| PREFX_CD | PREFIX 1 | Accident | CHA(1) | 58 |
| PROPDAM | PROPERTY DAMAGE AMOUNT | Accident | NUM | 59 |
| RAMP_IND | RAMP INDICATOR | Accident | CHA(1) | 59 |
| RD_CHAR1 | ROADWAY CHARACTERISTICS | Accident | CHA(1) | 59 |
| RD_INV | ROADWAY INVENTORY | Accident | CHA(11) | 59 |
| RD_QUAL | ROADWAY QUALIFIER | Accident | CHA(6) | 60 |
| RD_REL | ON/OFF ROAD | Accident | CHA(1) | 60 |
| RD_TYPE | RELATED ROADWAY TYPE | Accident | CHA(2) | 60 |
| RDQUAL | RELATED ROADWAY QUALIFIER | Accident | CHA(6) | 60 |
| RDSURF | ROADWAY SURFACE | Accident | CHA(1) | 60 |
| REC_TYPE | RECORD TYPE | Accident | NUM | 61 |
| REPORT | ACC SEVERITY | Accident | CHA(1) | 61 |
| REV_MP | REVERSE ARM | Accident | NUM | 61 |
| RODWYCLS | ROADWAY CLASS | Accident | CHA(2) | 61 |
| RTE_NBR | STATE ROUTE NUMBER | Accident | CHA(3) | 61 |
| RUR_URB | RURAL URBAN | Accident | CHA(1) | 61 |
| SEQNO | SEQUENCE NUMBER | Accident | NUM | 61 |
| SEVERITY | MOST SEVERE INJURY | Accident | CHA(1) | 61 |
| SPILLAGE | FUEL SPILLAGE | Accident | CHA(1) | 62 |
| SR_ADID | STATE ROUTE ADDITIONAL ID | Accident | CHA(3) | 62 |
| ST_FUNC | STATE FUNCTIONAL CLASS | Accident | CHA(2) | 62 |
| STREPORT | STATE REPORT | Accident | CHA(1) | 63 |
| TIME | ACC TIME | Accident | CHA(4) | 63 |
| TIMEARR | POLICE ARRIVED TIME | Accident | CHA(4) | 63 |
| TIMENOTE | POLICE DISPATCHED TIME | Accident | CHA(4) | 63 |
| TOT_INJ | NUMBER OF PERSONS INJURED | Accident | NUM | 63 |
| TOT_KILL | NUMBER OF PERSONS KILLED | Accident | NUM | 64 |
| TOT_PED | NUMBER OF PED/CYC | Accident | NUM | 64 |
| V1CMPDIR | V1 COMPASS DIRECTION | Accident | CHA(1) | 64 |
| V2CMPDIR | V2 COMPASS DIRECTION | Accident | CHA(1) | 64 |
| V1DIRCDE | V1 DIRECTION | Accident | CHA(1) | 64 |
| V2DIRCDE | V2 DIRECTION | Accident | CHA(1) | 64 |
| V1EVENT1 | V1 MOVEMENT | Accident | CHA(1) | 65 |
| V2EVENT1 | V2 MOVEMENT | Accident | CHA(1) | 65 |
| WEATHER | WEATHER CONDITION | Accident | CHA(1) | 65 |
| WEEKDAY | DAY OF WEEK | Accident | CHA(1) | 65 |
| WKZONE | WORK ZONE STATUS | Accident | CHA(1) | 66 |
| WSP_UPDT | WSP UPDATE DATE | Accident | NUM | 66 |
| XRDCLASS | CROSS ROAD CLASS TYPE | Accident | CHA(1) | 66 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
ACC MAINLINE MILEPOST
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
STATE ROUTE MILEPOST
NON-LABELED VARIABLE
NOTE: Link with the Roadlog and other files with the MILEPOST variable rather than this variable.
SRMP AH/BK
NON-LABELED VARIABLE
ACC DATE YYMMDD
NON-LABELED VARIABLE
NOTE: (1) Date of last change in related variable (yyyymmdd). (2) Variable discontinued in 1999.
ACC TYPE
NOTE: Because this variable was developed by WA DOT staff using vehicle maneuvers, each basic crash type (e.g., head-on, rear-end) has both a “strikes other vehicle” and a “struck by other vehicle” component. See code pairs 01 and 11, 02 and 12, etc. The user must combine both components to define the total number of a given crash type. Frequencies for categories 02, 03, 04, 05, 14, 15 look different between pre-1999 and post-1999 periods. However, these categories are similar in definition and we believe that the inconsistencies are because of this similarity and not due to any data quality issues.
ACC YEAR
NON-LABELED VARIABLE
NOTE: The format used is yyyy.
ADMIN CLASS
INVESTIGATING AGENCY
DRV ALCOHOL FLAG
NOTE: (1) This variable is not coded in approximately six percent of the cases. (2) Variable discontinued in 1999.
CASE NUMBER
NON-LABELED VARIABLE
NOTE: The format used is a 4-digit year plus a 6-digit number.
ACC CENTURY
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
CITY NUMBER
ACC 1 TYPE
ACC 2 TYPE
NOTE: These variables provide information on the first collision and second collision of an accident.
COUNTY NUMBER
ACC DAY OF MONTH
NON-LABELED VARIABLE
DISTRICT NUMBER
FIRE
FUNCTIONAL CLASS
GPS X
GPS Y
GPS Z
NON-LABELED VARIABLE
NOTE: Variables added in 1999.
HAZARDOUS MATERIAL
NOTE: This variable is "not stated" in virtually all cases.
HIT AND RUN
NOTE: Variable added in 1999.
IMPACT LOCATION
NOTE: Information on "sequence of events" is found in V1EVENT1, V2EVENT1, and IMPACT variables.
INTENTIONAL ACTION
NOTE: Variable added in 1999.
LIGHT CONDITION
* Category added in 1999.
LOCATION CHARACTERISTIC
ACC LOCATION TYPE
* Category added in 1999.
LAST MAINTENANCE DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MEDICALLY CAUSED
NOTE: Variable added in 1999.
ACCUM ROUTE MILEPOST (ARM)
NON-LABELED VARIABLE
NOTE: This is the variable used to link to the roadway inventory and other files.
MAINLINE ARM INDICATOR
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
ACC MONTH
MILLION VEHICLE MILES TRAVELLED
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
NUMBER OF PEDESTRIANS
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
NON-TRAFFIC INDICATOR
NOTE: Variable added in 1999.
NUMBER OF VEH
NON-LABELED VARIABLE
OBJECT STRUCK 1
OBJECT STRUCK 2
NOTE: These variables provide information on the first object and the second object struck in a collision.
PREFIX 1
NOTE: A numeric code used for further identification of the state route. Washington staff indicates that the construction area information (code "5") may be somewhat inaccurate. Also see WKZONE, available for 1999 and later years. Washington staff recommends the use of WKZONE variable for any work zone related analysis.
PROPERTY DAMAGE AMOUNT
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
RAMP INDICATOR
NOTE: (1) This variable does not include a code for accidents occurring in the middle of a ramp (unless at an intersection or Y-connector). These crashes will be left uncoded along with non-ramp accidents. (See RD_TYPE.) (2) Variable discontinued in 1999.
ROADWAY CHARACTERISTICS
NOTE: This variable is "not stated" in approximately 60 percent of the cases. Washington staffs feel that it is a poor variable for analysis purposes.
ROADWAY INVENTORY
NON-LABELED VARIABLE
ROADWAY QUALIFIER
NON-LABELED VARIABLE
ON/OFF ROAD
RELATED ROADWAY TYPE
RELATED ROADWAY QUALIFIER
NON-LABELED VARIABLE
ROADWAY SURFACE
* Categories added in 1999.
RECORD TYPE
NON-LABELED VARIABLE
ACC SEVERITY
REVERSE ARM
NON-LABELED VARIABLE
ROADWAY CLASS
STATE ROUTE NUMBER
NON-LABELED VARIABLE
RURAL URBAN CD
SEQUENCE NUMBER
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
MOST SEVERE INJURY
* Categories added in 1999.
FUEL SPILLAGE
NOTE: Variable discontinued in 1999.
STATE ROUTE ADDITIONAL ID
STATE FUNCTIONAL CLASS
NOTE: This code represents the State assigned functional class for a section of roadway. Information obtained is similar to what is obtained from FUNC_CLS variable.
STATE REPORT
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
ACC TIME
POLICE ARRIVED TIME
NON-LABELED VARIABLE
POLICE DISPATCHED TIME
NON-LABELED VARIABLE
NUMBER OF PERSONS INJURED
NUMBER OF PERSONS KILLED
NUMBER OF PED/CYC
V1 COMPASS DIRECTION
V2 COMPASS DIRECTION
V1 DIRECTION
V2 DIRECTION
* Category added in 1999.
V1 MOVEMENT
V2 MOVEMENT
NOTE: Information on "sequence of events" is found in V1EVENT1, V2EVENT1, and IMPACT variables.
WEATHER CONDITION
DAY OF WEEK
WORK ZONE STATUS
NOTE: (1) Variable added in 1999. (2) Washington staff indicates that officers might be making an error in coding a crash as '2' (workers not present), for a crash that is unrelated work zone (should have been coded as missing) for some years.
WSP UPDATE DATE
NON-LABELED VARIABLE
NOTE: (1) Date of last change in related variable (yyyymmdd). (2) Variable discontinued in 1999.
CROSS ROAD CLASS TYPE
NOTE: Variable added in 1999.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| ADD_INFO | ACC VEH ADDITIONAL INFO | Vehicle | CHA(2) | 69 |
| BODYTYPE | VEH MODEL | Vehicle | CHA(3) | 69 |
| CASENO | ACC REPORT NUMBER | Vehicle | CHA(10) | 69 |
| CDHAZNM | COMM CARRIER HAZMAT | Vehicle | CHA(17) | 69 |
| CDPLACCD | COMM CARRIER PLACARD | Vehicle | CHA(1) | 70 |
| CDPLACNO | COMM CARRIER PLACARD NUM | Vehicle | CHA(4) | 70 |
| CDPLACSU | COMM CARRIER PLACARD SUFFIX | Vehicle | CHA(1) | 70 |
| CMAXLES | COMM CARRIER NUM OF AXLES | Vehicle | CHA(2) | 70 |
| CMCONFIG | COMM CARRIER CONFIG | Vehicle | CHA(1) | 70 |
| COM_BODY | COMM CARRIER CARGO BODY | Vehicle | CHA(1) | 70 |
| COM_GWR | COMMERCIAL CARRIER WEIGHT | Vehicle | CHA(6) | 71 |
| CONTRIB1 | DRV CONTRIB CIRCUMS 1 | Vehicle | CHA(2) | 71 |
| CONTRIB2 | DRV CONTRIB CIRCUMS 2 | Vehicle | CHA(2) | 71 |
| CYC_INJ | PEDALCYCLIST INJURY CLASS | Vehicle | CHA(1) | 72 |
| DAMSEV | VEH DAMAGE SEVERITY | Vehicle | CHA(1) | 72 |
| DIR_TRVL | VEH MOVEMENT DIRECTION | Vehicle | CHA(2) | 72 |
| DRAIRBAG | DRV AIRBAG STATUS | Vehicle | CHA(1) | 72 |
| DRASSESS | DRUG RECOG EXPERT ASSESS | Vehicle | CHA(1) | 72 |
| DRV_ACTN | DRV ACTION | Vehicle | CHA(2) | 73 |
| DRV_AGE | DRV AGE | Vehicle | CHA(2) | 73 |
| DRV_EJCT | DRV EJECTION | Vehicle | CHA(1) | 74 |
| DRV_INJ | DRV INJURY CLASS | Vehicle | CHA(1) | 74 |
| DRV_REST | DRV RESTRAINT USAGE | Vehicle | CHA(1) | 74 |
| DRV_SEX | DRV SEX | Vehicle | CHA(1) | 75 |
| EVENT1 | SEQUENCE OF EVENTS 1 | Vehicle | CHA(2) | 75 |
| EVENT2 | SEQUENCE OF EVENTS 2 | Vehicle | CHA(2) | 75 |
| EVENT3 | SEQUENCE OF EVENTS 3 | Vehicle | CHA(2) | 75 |
| EVENT4 | SEQUENCE OF EVENTS 4 | Vehicle | CHA(2) | 75 |
| HELMET | PED/CYC HELMET | Vehicle | CHA(1) | 75 |
| INTER_A | INTERSECTION INDICATOR | Vehicle | CHA(1) | 76 |
| INTOX | DRV SOBRIETY | Vehicle | CHA(1) | 76 |
| MAKE | VEHICLE MAKE | Vehicle | CHA(4) | 76 |
| MISCACT1 | DRV MISC ACTION 1 | Vehicle | CHA(2) | 76 |
| MISCACT2 | DRV MISC ACTION 2 | Vehicle | CHA(2) | 76 |
| MTC_INJ | PEDALCYCLIST INJURY CLASS | Vehicle | CHA(1) | 79 |
| MTC_INJ_TYPE | PECALCYCLIST INJURY TYPE | Vehicle | CHA(1) | 79 |
| OCCUPAC | DRV OCCUPATION | Vehicle | CHA(2) | 79 |
| OFF_ACTN | OFFICER ACTION | Vehicle | CHA(1) | 80 |
| ON_DUTY | ON DUTY STATUS | Vehicle | CHA(1) | 80 |
| OUTSTATE | VEH STATE OF REGISTRATION | Vehicle | CHA(2) | 80 |
| PED_CLT | PED/CYC CLOTHING | Vehicle | CHA(1) | 80 |
| PED_CUM1 | PED/CYC CIRCUMS 1 | Vehicle | CHA(1) | 80 |
| PED_CUM2 | PED/CYC CIRCUMS 2 | Vehicle | CHA(1) | 80 |
| PED_LOC | PED/CYC LOCATION | Vehicle | CHA(2) | 81 |
| PED_STUS | PED/CYC STATUS | Vehicle | CHA(1) | 81 |
| PED_WLK | PED WALK | Vehicle | CHA(1) | 81 |
| PEDACT | PED/CYC ACTIONS | Vehicle | CHA(2) | 82 |
| RD_SEP | VEH ROAD SEPARATE | Vehicle | CHA(1) | 82 |
| RESIDLOC | DRV RESIDENCE PROXIMITY | Vehicle | CHA(1) | 82 |
| SOB_TEST | DRV SOBRIETY | Vehicle | CHA(1) | 83 |
| SPDLIMIT | VEH POSTED SPEED | Vehicle | CHA(2) | 83 |
| STOLEN | VEH STOLEN | Vehicle | CHA(1) | 83 |
| STYLE | VEH STYLE | Vehicle | CHA(2) | 83 |
| SURF_TYP | ROADWAY SURFACE TYPE | Vehicle | CHA(1) | 84 |
| TRAILER | TRAILER INFO | Vehicle | CHA(1) | 84 |
| TRF_CNTL | VEH TRAFFIC CONTROL | Vehicle | CHA(1) | 84 |
| V_STATE | STATE OF VEH REGISTRATION | Vehicle | CHA(2) | 84 |
| VEH_SEV | DRV INJURY SEVERITY | Vehicle | CHA(1) | 84 |
| VEH_USE | VEH USAGE | Vehicle | CHA(2) | 85 |
| VEHCOND1 | VEH DEFECT 1 | Vehicle | CHA(2) | 85 |
| VEHCOND2 | VEH DEFECT 2 | Vehicle | CHA(2) | 85 |
| VEHCOND3 | VEH DEFECT 3 | Vehicle | CHA(2) | 85 |
| VEHNO | VEH NUMBER | Vehicle | NUM | 86 |
| VEHTYPE | VEH TYPE | Vehicle | CHA(2) | 86 |
| VEHYR | VEH YEAR | Vehicle | CHA(2) | 86 |
| VRD_TYPE | ROADWAY TYPE | Vehicle | CHA(1) | 86 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
ACC VEH ADDITIONAL INFO
NOTE: Variable discontinued in 1999.
VEH MODEL
NON-LABELED VARIABLE
NON-LABELED VARIABLE
NOTE: (1) Variable discontinued in 1999. (2) The format used is a 4-digit year plus a 6-digit number.
COMM CARRIER HAZMAT
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
COMM CARRIER PLACARD
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
COMM CARRIER PLACARD NUM
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
COMM CARRIER PLACARD SUFFIX
NOTE: Variable added in 1999.
COMM CARRIER NUM OF AXLES
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
COMM CARRIER CONFIG
NOTE: Variable added in 1999.
COMM CARRIER CARGO BODY
NOTE: Variable added in 1999.
COMMERCIAL CARRIER WEIGHT
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
DRV CONTRIB CIRCUMS 1
DRV CONTRIB CIRCUMS 2
* Categories added in 1999.
PEDALCYCLIST INJURY CLASS
NOTE: Data available only for year 1996.
VEH DAMAGE SEVERITY
NOTE: Variable discontinued in 1999.
VEH MOVEMENT DIRECTION
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
DRAIRBAG DRV AIRBAG STATUS
NOTE: (1) Variable added in 1999. (2) This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
DRUG RECOG EXPERT ASSESS
NOTE: (1) Variable added in 1999. (2) This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
DRV ACTION
DRV AGE
NOTE: Approximately six percent of cases is uncoded.
DRV EJECTION
NOTE: This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
DRV INJURY CLASS
* Categories added in 1999.
DRV RESTRAINT USAGE
* Categories discontinued from 1999 onwards.
NOTE: Approximately 12 percent of the cases are uncoded. As with all states with mandatory usage laws, this variable should be used with some caution.
DRV SEX
NOTE: This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
SEQUENCE OF EVENTS 1
SEQUENCE OF EVENTS 2
SEQUENCE OF EVENTS 3
SEQUENCE OF EVENTS 4
NOTE: (1) Variable added in 1999. (2) This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
PED/CYC HELMET
NOTE: This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
INTERSTATE INDICATOR
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
DRV SOBRIETY
NOTE: (1) HBD refers to “had been drinking”. (2) Variable added in 1996.
VEHICLE MAKE
NON-LABELED VARIABLE
DRV MISC ACTION 1
DRV MISC ACTION 2
SKIDDING INVOLVED
AVOIDING MANEUVERS
SUDDEN SLOWING MANEUVERS
STOPPED VEHICLE
PARKING MANEUVERS
SPECIAL MAMEUVERS
VEHICLE LOAD OR EQUIPMENT
TRAILER INVOLVED
BICYCLE OR OTHER MOTOR VEHICLE INVOLVED
PEDESTRIAN INVOLVED
PASSENGER INVOLVED
ATMOSPHERIC CONDITIONS
ROAD IRREGULARITY
OTHER ACTION
VOLCANO CAUSED ROADWAY CONDITIONS
VOLCANO CAUSED VEHICLE CONDITIONS
VOLCANO CAUSED DRIVING CONDITIONS
NOTE: (1) Washington staff indicates that the construction area information (code "87") may be somewhat inaccurate. (2) Variable added in 1999. This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
PEDALCYCLIST INJURY CLASS
NOTE: Variable discontinued in 1999.
PEDALCYCLIST INJURY TYPE
NOTE: Variable discontinued in 1999.
DRV OCCUPATION
NOTE: Variable discontinued in 1999.
OFFICER ACTION
NOTE: Variable discontinued in 1999.
ON DUTY STATUS FOR OFFICERS
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
VEH STATE OF REGISTRATION
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
PED/CYC CLOTHING
NON-LABELED VARIABLE
NOTE: (1) Variable discontinued in 1999. (2) See pedestrian file variable and discussion section.
PED/CYC CIRCUMS 1
PED/CYC CIRCUMS 2
NOTE: Variable discontinued in 1999. See pedestrian file
PED/CYC LOCATION
NOTE: (1) Variable discontinued in 1999. (2) See pedestrian file and discussion section.
PED/CYC STATUS
NOTE: (1) Variable discontinued in 1999. (2) See pedestrian file and discussion section.
PED WALK
NON-LABELED VARIABLE
NOTE: (1) Variable discontinued in 1999. (2) See pedestrian file and discussion section.
PED/CYC ACTIONS
PEDESTRIAN'S ACTIONS
PEDALCYCLIST'S ACTIONS
NOTE: (1) Variable discontinued in 1999. (2) See pedestrian file and discussion section.
VEH ROAD SEPARATE
NOTE: Variable discontinued in 1999.
DRV RESIDENCE PROXIMITY
NOTE: Variable discontinued in 1999.
DRV SOBRIETY
NOTE: (1) Approximately 13 percent of the cases are uncoded. (2) Variable discontinued in 1999.
VEH POSTED SPEED
VEH STOLEN
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
VEH STYLE
NON-LABELED VARIABLE
NOTE: Variable discontinued in 1999.
ROADWAY SURFACE TYPE
NOTE: Variable discontinued in 1999.
VEH TRAFFIC CONTROL
STATE OF VEHICLE REGISTRATION
NON-LABELED VARIABLE
NOTE: Variable added in 1999.
VEH_SEV DRV INJURY SEVERITY
* Categories added in 1999.
NOTE: This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
VEH USAGE
NOTE: (1) Variable added in 1999. (2) This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
VEH DEFECT 1
VEH DEFECT 2
VEH DEFECT 3
NOTE: VEHCOND3 was added in 1999.
VEH NUMBER
VEH TYPE
NOTE: (1) Washington staffs feel that the accuracy of the truck-type codes in this variable is somewhat questionable. (2) This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
VEH YEAR
NON-LABELED VARIABLE
TYPE OF ROADWAY
NON-LABELED VARIABLE
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AGE | DRV/OCC AGE | Occupant | NUM | 88 |
| AIRBAG | OCCUPANT AIRBAY | Occupant | CHA(1) | 88 |
| CASENO | ACC RPT NUMBER | Occupant | CHA(6) | 88 |
| EJECT | DRV/OCC EJECTION | Occupant | CHA(1) | 89 |
| HELMET | PED/CYC HELMET | Occupant | CHA(1) | 89 |
| INJ | DRV/OCC INJURY | Occupant | CHA(1) | 89 |
| NO_OCCS | NUMBER OF OCCUPANTS | Occupant | NUM | 89 |
| REST1 | DRV/OCC RESTRAINT | Occupant | CHA(1) | 89 |
| SEATPOS | DRV/OCC SEAT POSITION | Occupant | CHA(1) | 90 |
| SEX | DRV/OCC SEX | Occupant | CHA(1) | 90 |
| VEHNO | VEHICLE NUMBER | Occupant | NUM | 90 |
NOTE: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
DRV/OCC AGE
NOTE: Approximately six percent of the cases are uncoded.
OCCUPANT AIRBAG
NOTE: (1) Variable added in 1999. (2) This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded reasonably.
ACC RPT NUMBER
NON-LABELED VARIABLE
NOTE: The format used is a 4-digit year plus a 6-digit number.
DRV/OCC EJECTION
* Category added in 1999.
PED/CYC HELMET
NOTE: Variable added in 2006.
DRV/OCC INJURY
* Category added in 1999.
NUMBER OF OCCUPANTS
NON-LABELED VARIABLE
NOTE: Variable added in 1999 and discontinued in 2006.
DRV/OCC RESTRAINT
* Categories correspond to data from 1993 to 1996.
NOTE: Approximately 12 percent of the cases are un-coded / unknown. As with all states with mandatory usage laws, this variable should be used with some caution.
DRV/OCC SEAT POSITION
NOTE: This variable is almost 100 percent missing from 1999 to 2001. See discussion. From 2002 onwards, this variable is again coded, but no seat position information beyond 2 recorded.
DRV/OCC SEX
VEH NUMBER
NON-LABELED VARIABLE
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| CASENO | ACCIDENT CASE NUMBER | Pedestrian | CHA(10) | 92 |
| CLOTHING | PED CLOTHING | Pedestrian | CHA(1) | 92 |
| CONTRIB1 | PED/CYC CIRCUMSTANCES 1 | Pedestrian | CHA(2) | 92 |
| CONTRIB2 | PED/CYC CIRCUMSTANCES 2 | Pedestrian | CHA(2) | 92 |
| HELMET | PED/CYC HELMET | Pedestrian | CHA(1) | 93 |
| INTOX | PEDALCYCLIST SOBERITY | Pedestrian | CHA(1) | 93 |
| PED_AGE | PED/CYC AGE | Pedestrian | CHA(2) | 93 |
| PED_INJ | PED/CYC INJURY | Pedestrian | CHA(1) | 93 |
| PED_SEX | PED/CYC SEX | Pedestrian | CHA(1) | 94 |
| PED_STUS | PED/CYC STATUS | Pedestrian | CHA(1) | 94 |
| PED_WALK | PED WALKING LOCATION | Pedestrian | CHA(1) | 94 |
| PEDACT | PED/CYCLIST ACTION | Pedestrian | CHA(2) | 94 |
| VEHNO | VEHICLE NUMBER | Pedestrian | NUM | 95 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Pedestrian sub file is available for 1999-2002.
ACCIDENT CASE NUMBER
NON-LABELED VARIABLE
NOTE: (1) Data available only for year 2002. (2) The format used is a 4-digit year plus a 6-digit number.
PED/CYC CLOTHING
NON-LABELED VARIABLE
NOTE: Data available only for year 2002.
PED/CYC CIRCUMS 1
PED/CYC CIRCUMS 2
NOTE: Data available only for year 2002.
PED/CYC HELMET
NOTE: Data available only for year 2002.
PED SOBRIETY
NOTE: (1) “HBD” refers to “had been drinking”. (2) Data available only for year 2002.
PEDESTRIAN AGE
NON-LABELED VARIABLE
NOTE: Data available only for year 2002.
PEDESTRIAN INJ
NOTE: Data available only for year 2002.
PEDESTRIAN SEX
NON-LABELED VARIABLE
NOTE: Data available only for year 2002.
PED/CYC STATUS
NOTE: (1) See pedestrian file and discussion section. (2) Data available only for year 2002.
PED WALKING LOCATION
NOTE: Data available only for year 2002.
PED/CYC ACTIONS
PEDESTRIAN'S ACTIONS
PEDALCYCLIST'S ACTIONS
NOTE: Data available only for year 2002.
VEHICLE NUMBER
NON-LABELED VARIABLE
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AADT | AVER ANNUAL DAILY TRAFFIC | Roadlog | NUM | 100 |
| ACCES_DT | ACCESS CONTROL DATE | Roadlog | CHA(8) | 100 |
| ACCESS | ACCESS CONTROL TYPE | Roadlog | CHA(1) | 100 |
| ACLL_DT1 | LEFT ACCEL LANE DATE RD1 | Roadlog | CHA(8) | 101 |
| ACLL_DT2 | LEFT ACCEL LANE DATE RD2 | Roadlog | CHA(8) | 101 |
| ACLL_LG1 | LEFT ACCEL LANE LENGTH RD1 | Roadlog | NUM | 101 |
| ACLL_LG2 | LEFT ACCEL LANE LENGTH RD2 | Roadlog | NUM | 101 |
| ACLL_WD1 | LEFT ACCEL LANE WIDTH RD1 | Roadlog | NUM | 101 |
| ACLL_WD2 | LEFT ACCEL LANE WIDTH RD2 | Roadlog | NUM | 102 |
| ACLR_DT1 | RIGHT ACCEL LANE DATE RD1 | Roadlog | CHA(8) | 102 |
| ACLR_DT2 | RIGHT ACCEL LANE DATE RD2 | Roadlog | CHA(8) | 102 |
| ACLR_LG1 | RIGHT ACCEL LANE LENGTH RD1 | Roadlog | NUM | 102 |
| ACLR_LG2 | RIGHT ACCEL LANE LENGTH RD2 | Roadlog | NUM | 102 |
| ACLR_WD1 | RIGHT ACCEL LANE WIDTH RD1 | Roadlog | NUM | 102 |
| ACLR_WD2 | RIGHT ACCEL LANE WIDTH RD2 | Roadlog | NUM | 103 |
| ACSEQ_NB | ACC SEQ NUM | Roadlog | NUM | 103 |
| BEGMP | BEGMP | Roadlog | NUM | 103 |
| CITY | CITY NUMBER | Roadlog | CHA(4) | 103 |
| CITY_DT | CITY DATE | Roadlog | CHA(8) | 106 |
| CNTL_SEC | CNTL SECTION | Roadlog | CHA(8) | 106 |
| CNTY_DT | COUNTY DATE | Roadlog | CHA(8) | 106 |
| COMP_DIR | COMPASS DIRECTION | Roadlog | CHA(2) | 106 |
| COUNTY | COUNTY NUMBER | Roadlog | CHA(2) | 106 |
| CTY_ZONE | CITY ZONE TYPE | Roadlog | CHA(1) | 107 |
| DETCH_NB | WSP DETACHEMENT NUM | Roadlog | CHA(2) | 107 |
| DEVCD | LEVEL OF DEVLMPT | Roadlog | CHA(2) | 107 |
| DEVCD_DT | LEVEL OF DEVELMT DATE | Roadlog | CHA(8) | 107 |
| DIR_DT | COMPASS DIRECTION DATE | Roadlog | CHA(8) | 107 |
| DISCN_DT | DISCONTY DATE | Roadlog | CHA(8) | 107 |
| DISCONTY | DISCONTY IND | Roadlog | CHA(2) | 107 |
| DISTR_DT | DISTRICT DATE | Roadlog | CHA(8) | 108 |
| DISTRICT | DISTRICT NUMBER | Roadlog | CHA(1) | 108 |
| DOMAIN | DOMAIN TYPE | Roadlog | CHA(2) | 108 |
| DOMN_DT | DOMAIN DATE | Roadlog | CHA(8) | 108 |
| ENDMP | CALCULATED ENDING MILEPOST | Roadlog | NUM | 109 |
| EW_DTE | EAST/WEST INDICATOR DATE | Roadlog | CHA(8) | 109 |
| EW_IND | EAST WEST IND | Roadlog | CHA(1) | 109 |
| FED_AID | FED AID CLASS | Roadlog | CHA(1) | 109 |
| FED_CD | FED AID TYPE | Roadlog | CHA(4) | 109 |
| FEDAD_DT | FED-AID DATE | Roadlog | CHA(8) | 109 |
| FUNC_CLS | FEDERAL FUNC CLASS | Roadlog | CHA(2) | 109 |
| FUNC_DT | FUNCTIONAL CLASS DATE | Roadlog | CHA(8) | 110 |
| HPMS | HPMS SECTION NUMBER | Roadlog | CHA(13) | 110 |
| HPMS_DTE | HPMS DATE | Roadlog | CHA(8) | 110 |
| LANEWID | CALCULATED LANE WIDTH | Roadlog | NUM | 110 |
| LSHL_DT2 | LEFT SHOULDER DATE RD2 | Roadlog | CHA(8) | 110 |
| LSHL_DTE | LEFT SHOULDER DATE RD1 | Roadlog | CHA(8) | 110 |
| LSHL_TY2 | LEFT SHOULDER TYPE RD2 | Roadlog | CHA(1) | 110 |
| LSHL_TYP | LEFT SHOULDER TYPE RD1 | Roadlog | CHA(1) | 111 |
| LSHL_WD2 | LEFT SHOULDER WIDTH RD1 | Roadlog | NUM | 111 |
| LSHLDWID | LEFT SHOULDER WIDTH RD1 | Roadlog | NUM | 111 |
| LST_UPDT | CNTL SEC LST UPD | Roadlog | CHA(8) | 112 |
| MDXN_DTE | MEDIAN CROSSING DATE | Roadlog | CHA(8) | 112 |
| MED_TYPE | MEDIAN TYPE | Roadlog | CHA(1) | 112 |
| MEDBARTY | MEDIAN BARRIER TYPE | Roadlog | CHA(2) | 112 |
| MEDN_DTE | MEDIAN DATE | Roadlog | CHA(8) | 112 |
| MEDWID | MEDIAN WIDTH | Roadlog | NUM | 112 |
| MEDXNGTY | MEDIAN CROSSING TYPE | Roadlog | CHA(1) | 113 |
| MNT_AREA | MAINTENANCE AREA NBR | Roadlog | CHA(1) | 113 |
| MNT_DTE | MAINTENANCE DATE | Roadlog | CHA(8) | 113 |
| MNTSC_DT | MAINTENANCE SECTION DATE | Roadlog | CHA(8) | 113 |
| MNTSEC | MAINTENANCE SECT NBR | Roadlog | CHA(2) | 113 |
| MT_DTE | LAST MAINT DATE | Roadlog | CHA(8) | 113 |
| MT_PASID | MTN PASS ID | Roadlog | CHA(4) | 113 |
| MTPAS_DT | MOUNTAIN PASS DATE | Roadlog | CHA(8) | 114 |
| MVMT | MILLION VEH MILES TRAVELLED | Roadlog | NUM | 114 |
| NHS_DT | NHS DATE | Roadlog | CHA(8) | 114 |
| NHS_IND | NHS IND | Roadlog | CHA(1) | 114 |
| NO_LANE1 | NUMBER LANES INC | Roadlog | NUM | 114 |
| NO_LANE2 | NUMBER LANES DEC | Roadlog | NUM | 114 |
| NO_LANES | TOTAL NUMBER OF LANES | Roadlog | NUM | 114 |
| NO_LNDT1 | NUMBER OF LANES DATE RD1 | Roadlog | CHA(8) | 115 |
| NO_LNDT2 | NUMBER OF LANES DATE RD2 | Roadlog | CHA(8) | 115 |
| PGRP_DT | POPULATION GROUP DATE | Roadlog | CHA(8) | 115 |
| POP_GRP | CITY POPULATION | Roadlog | CHA(2) | 115 |
| PRK_ZNE | PARKING ZONE TYPE | Roadlog | CHA(1) | 115 |
| PRKZN_DT | PARKING ZONE TYPE DATE | Roadlog | CHA(8) | 115 |
| RD_ABIND | RDWY AHEAD/BACK IND | Roadlog | CHA(1) | 116 |
| RD_EQDTE | EQUATION DATE | Roadlog | CHA(8) | 116 |
| RD_EQUAT | EQUATION | Roadlog | CHA(17) | 116 |
| RD_LIGHT | INTERSECTION ILLUM-ND | Roadlog | CHA(1) | 116 |
| RD_OPEN | ROAD OPEN DATE | Roadlog | CHA(8) | 116 |
| RD_OWNER | ROADWAY OWNER CODE | Roadlog | CHA(2) | 116 |
| RD_QUAL | RELATED RD QUAL | Roadlog | CHA(8) | 116 |
| RD_RARM | REVERSE ARM | Roadlog | NUM | 116 |
| RD_SRMP | RDWY SRMP | Roadlog | NUM | 116 |
| RD_TYPE | RELATED RD TYPE | Roadlog | CHA(2) | 117 |
| RDAC_MGC | ACCESS MANAGEMENT CLASS | Roadlog | CHA(1) | 117 |
| RDAC_MGS | ACCESS MANAGEMENT SUBCLASS | Roadlog | CHA(1) | 117 |
| RDWY_WD1 | ROADWAY WIDTH RD 1 | Roadlog | NUM | 117 |
| RDWY_WD2 | ROADYWAY WIDTH RD 2 | Roadlog | NUM | 117 |
| RDWY_WID | TOTAL ROADWAY WIDTH | Roadlog | NUM | 118 |
| RDWYWDD1 | ROADWAY WIDTH DATE RD 1 | Roadlog | CHA(8) | 118 |
| RDWYWDD2 | ROADWAY WIDTH DATE RD 2 | Roadlog | CHA(8) | 118 |
| REC_TYPE | RECORD TYPE | Roadlog | NUM | 118 |
| ROAD_INV | ROUTE TYPE ID | Roadlog | CHA(11) | 118 |
| RODWYCLS | ROADWAY CLASSIFICATION | Roadlog | CHA(2) | 118 |
| RSHL_DT2 | RIGHT SHOULDER DATE RD2 | Roadlog | CHA(8) | 118 |
| RSHL_DTE | RIGHT SHOULDER DATE RD1 | Roadlog | CHA(8) | 119 |
| RSHL_TY2 | RIGHT SHOULDER TYPE RD2 | Roadlog | CHA(1) | 119 |
| RSHL_TYP | RIGHT SHOULDER TYPE RD1 | Roadlog | CHA(1) | 119 |
| RSHL_WD2 | RIGHT SHOULDER WIDTH RD2 | Roadlog | NUM | 119 |
| RSHLDWID | RIGHT SHOULDER WIDTH RD1 | Roadlog | NUM | 119 |
| RTE_NBR | ROUTE NUMBER | Roadlog | CHA(3) | 120 |
| RURURB | RURAL URBAN | Roadlog | CHA(1) | 120 |
| SEG_LNG | RD CALCULATED SECT LNGTH | Roadlog | NUM | 120 |
| SPD_LIMT | LEGAL SPEED LIMIT | Roadlog | NUM | 120 |
| ST_FUNC | STATE FUNC CLASS | Roadlog | CHA(2) | 121 |
| SURF_TY2 | SURFACE TYPE RD2 | Roadlog | CHA(1) | 121 |
| SURF_TYP | SURFACE TYPE RD1 | Roadlog | CHA(1) | 121 |
| SWS_DT | STATEWIDE SYSTEM DATE | Roadlog | CHA(8) | 121 |
| SWS_IND | STATEWIDE SYSTEM IND | Roadlog | CHA(1) | 121 |
| TERRAIN | TERRAIN TYPE | Roadlog | CHA(1) | 121 |
| TERRN_DT | TERRAIN DATE | Roadlog | CHA(8) | 122 |
| TRF_CNTL | INTERSECTION CONTROL TYPE | Roadlog | CHA(2) | 122 |
| TRFCN_DT | TRAFFIC CONTROL DATE | Roadlog | CHA(8) | 122 |
| TRKPCTS | TRUCK PERCENTAGE | Roadlog | NUM | 122 |
| TRLL_DT1 | LEFT TURN LANE DATE RD1 | Roadlog | CHA(8) | 122 |
| TRLL_DT2 | LEFT TURN LANE DATE RD2 | Roadlog | CHA(8) | 122 |
| TRLL_LG1 | LEFT TURN LANE LENGTH RD1 | Roadlog | NUM | 123 |
| TRLL_LG2 | LEFT TURN LANE LENGTH RD2 | Roadlog | NUM | 123 |
| TRLL_WD1 | LEFT TURN LANE WIDTH RD1 | Roadlog | NUM | 123 |
| TRLL_WD2 | LEFT TURN LANE WIDTH RD2 | Roadlog | NUM | 123 |
| TRLR_DT1 | RIGHT TURN LANE DATE RD1 | Roadlog | CHA(8) | 123 |
| TRLR_DT2 | RIGHT TURN LANE DATE RD2 | Roadlog | CHA(8) | 123 |
| TRLR_LG1 | RIGHT TURN LANE LENGTH RD1 | Roadlog | NUM | 124 |
| TRLR_LG2 | RIGHT TURN LANE LENGTH RD2 | Roadlog | NUM | 124 |
| TRLR_WD1 | RIGHT TURN LANE WIDTH RD1 | Roadlog | NUM | 124 |
| TRLR_WD2 | RIGHT TURN LANE WIDTH RD2 | Roadlog | NUM | 124 |
| UBREG_DT | URBAN NUMBER DATE | Roadlog | CHA(8) | 124 |
| URB_DT | URBAN REGION DATE | Roadlog | CHA(8) | 124 |
| URB_NBR | URBAN AREA NUMBER | Roadlog | CHA(2) | 125 |
| URB_REG | URBAN REGION NUMBER | Roadlog | CHA(1) | 125 |
| WSP_DIST | WSP DISTRICT NUMBER | Roadlog | CHA(1) | 125 |
| WSP_DT | WSP DATE | Roadlog | CHA(8) | 125 |
| ZONE_DT | ZONE DATE | Roadlog | CHA(8) | 125 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) No Roadlog files were received from Washington for 1997-2001. The formats described below pertain to 1993-1996 and 2002 onward years.
AVER ANNUAL DAILY TRAFFIC
NOTE: AADT in 2004 and later files were defined using a new methodology. This will result in some discrepancies between AADT counts for 2004 and prior years for the same roadway segment. See Discussion.
ACCESS CONTROL DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
ACCESS CONTROL TYPE
NOTE: Approximately 15% of the sections are uncoded. However, the majority of the uncoded sections are non-mainline roadway types (e.g., ramps) as shown under RD_TYPE. It is also noted that this variable is, to some extent, a "planning" variable. This results in approximately 900 miles of two-lane roads with full access control-sections, which will ultimately be upgraded to multilane freeway.
LEFT ACCEL LANE DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT ACCEL LANE DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT ACCEL LANE LENGTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
LEFT ACCEL LANE LENGTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
LEFT ACCEL LANE WIDTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
LEFT ACCEL LANE WIDTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT ACCEL LANE DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RIGHT ACCEL LANE DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RIGHT ACCEL LANE LENGTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT ACCEL LANE LENGTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT ACCEL LANE WIDTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT ACCEL LANE WIDTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
ACC SEQ NUM
NON-LABELED VARIABLE
BEGMP
NON-LABELED VARIABLE
CITY NUMBER
CITY DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
CNTL SECTION
NON-LABELED VARIABLE
COUNTY DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
COMPASS DIRECTION
NOTE: This is the compass direction of the (mainline) route at the beginning mile point. The 16% of sections, which are uncoded are predominantly non-mainline sections (e.g., ramps) as listed under RD_TYPE.
COUNTY NUMBER
CITY ZONE TYPE
NON-LABELED VARIABLE
WSP DETACHEMENT NUM
NON-LABELED VARIABLE
LEVEL OF DEVLMPT
NOTE: This variable indicates a classification assigned to sections of roadway, which relates to plans for maintenance and improvement of the sections.
LEVEL OF DEVELMT DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable(yyyymmdd).
COMPASS DIRECTION DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable(yyyymmdd).
DISCONTY DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
DISCONTY IND
'FZ' = 'FERRY ZONE'
'PG' = 'PHYSICAL GAP'
NOTE: Indicates a physical discontinuity in a state route in which no new attributes exist and mileposts continue to accumulate. An example of a physical discontinuity would be a ferry run where the state route continues on the other side of the ferry run. A short distance would be shown between the two docks to indicate that they are not the same point.
DISTRICT DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable(yyyymmdd).
DISTRICT NUMBER
DOMAIN TYPE
NOTE: Domain type identifies the federal, state, or local agency, if any, having control over the land through which the highway segment passes. Where the highway falls between two domains, a judgment must be made as to the most appropriate domain to be coded.
DOMAIN DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable(yyyymmdd).
CALCULATED ENDING MILEPOST
NON-LABELED VARIABLE
NOTE: Calculated ending milepost, which is defined as equal to beginning milepost (BEGMP) on the next segment of same route.
EAST/WEST DATE INDICATOR DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
EAST WEST IND
FED AID CLASS
FED AID TYPE
FED-AID DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable(yyyymmdd).
FEDERAL FUNC CLASS
FUNCTIONAL CLASS DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
HPMS SECTION NUMBER
NON-LABELED VARIABLE
HPMS DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
CALCULATED LANE WIDTH
NON-LABELED VARIABLE
NOTE: This variable is calculated by dividing the total roadway width by the total number of lanes. There will be some error on sections where the shoulder type is curb or wall. See "Note" under RDWY_WD1.
LEFT SHOULDER DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT SHOULDER DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT SHOULDER TYPE RD2
NOTE: The surface composition of the inside (left) shoulder in the decreasing direction of the roadway. This is only used for divided roadway.
LEFT SHOULDER TYPE RD1
NOTE: The surface composition of the inside (left) shoulder in the increasing direction of the roadway. This variable refers to both divided and undivided roadways.
LEFT SHOULDER WIDTH RD1
NOTE: The width of the inside (left) shoulder in feet in the decreasing direction of the roadway. This is only used for divided roadway.
LEFT SHOULDER WIDTH RD1
NOTE: The width of the inside (left) shoulder in feet in the increasing direction of the roadway. This variable refers to both divided and undivided roadways. The approximately 14% "no shoulder" category includes both curb sections and, unfortunately, some uncoded sections.
CNTL SEC LST UPD
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MEDIAN CROSSING DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MEDIAN TYPE
MEDIAN BARRIER TYPE
MEDIAN DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MEDIAN WIDTH
NOTE: The distance from inside shoulder edge to inside shoulder edge on a divided highway (median width includes inside shoulders). This is measured in feet.
MEDIAN CROSSING TYPE
NOTE: Indicates whether a median crossing is officially recognized by WSDOT.
MAINTENANCE AREA NBR
NON-LABELED VARIABLE
MAINTENANCE DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MAINTENANCE SECTION DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MAINTENANCE SECT NBR
NON-LABELED VARIABLE
LAST MAINT DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MTN PASS ID
NOTE: Identifies whether a SRMP location occurs in a specific mountain pass.
MOUNTAIN PASS DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MILLION VEHICLE MILES TRAVELLED
NON-LABELED VARIABLE
NHS DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable(yyyymmdd).
NHS IND
NUMBER LANES INC
NUMBER LANES DEC
TOTAL NUMBER OF LANES
NOTE: "Increasing" and "decreasing" number of lanes indicated the number of total thru lanes in those directions of travel regardless of whether a roadway is divided or not. Lane counts do not include acceleration lanes or turn lanes. "Total Number of Lanes" is a calculated variable, which sums the first two.
NUMBER OF LANES DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
NUMBER OF LANES DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
POPULATION GROUP DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
CITY POPULATION
NOTE: Approximately 85% of the sections are blank, indicating rural areas.
PARKING ZONE TYPE
PARKING ZONE TYPE DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RDWY AHEAD/BACK IND
EQUATION DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
EQUATION
INTERSECTION ILLUM-ND
NOTE: Defines intersection illumination for the intersection at the beginning of the section.
ROAD OPEN DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
ROADWAY OWNER CODE
RELATED RD QUAL
NON-LABELED VARIABLE
REVERSE ARM
NON-LABELED VARIABLE
RDWY SRMP
NON-LABELED VARIABLE
RELATED RD TYPE
ACCESS MANAGEMENT CLASS
NON-LABELED VARIABLE
ACCESS MANAGEMENT SUBCLASS
NON-LABELED VARIABLE
ROADWAY WIDTH RD 1
ROADWAY WIDTH RD 2
NOTE: The width of the driving surface, in feet, in the increasing (both divided and undivided) direction of the roadway, and in the decreasing (divided only) direction of the roadway. In sections with curbs, it is measured from curb to curb, and thus may include parking areas or other paved shoulder adjacent to the curb (as in curbs on interchange ramp islands).
TOTAL ROADWAY WIDTH
ROADWAY WIDTH DATE RD 1
ROADWAY WIDTH DATE RD 2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RECORD TYPE
NON-LABELED VARIABLE
ROUTE TYPE ID
NON-LABELED VARIABLE
ROADWAY CLASSIFICATION
RIGHT SHOULDER DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RIGHT SHOULDER DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RIGHT SHOULDER TYPE RD2
NOTE: The surface composition of the outside (right) shoulder in the decreasing direction of the roadway.
RIGHT SHOULDER TYPE RD1
NOTE: The surface composition of the outside (right) shoulder in the increasing direction of the roadway. This variable refers to both divided and undivided roadways.
RIGHT SHOULDER WIDTH RD2
NOTE: The width of the outside (right) shoulder surface in feet in the decreasing direction of the roadway.
RIGHT SHOULDER WIDTH RD1
NOTE: The width of the outside (right) shoulder in feet in the increasing direction of the roadway. This variable refers to both divided and undivided roadways. The approximately 10% "no shoulder" category includes both curb sections and, unfortunately, some uncoded sections.
ROUTE NUMBER
NON-LABELED VARIABLE
RURAL URBAN
RD CALCULATED SECT LNGTH
NON-LABELED VARIABLE
NOTE: Section length calculated as difference between beginning and ending mileposts.
LEGAL SPEED LIMIT
STATE FUNC CLASS
NOTE: This code represents the State assigned functional class for a section of roadway.
SURFACE TYPE RD2
SURFACE TYPE RD1
NOTE: The composition of the driving surface in the increasing (both divided and undivided) direction of the roadway, and in the decreasing (divided only) direction of the roadway.
STATEWIDE SYSTEM DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
STATEWIDE SYSTEM IND
NOTE: A National Highway System related indicator defining trunk and non-trunk roadways.
TERRAIN TYPE
NOTE: The configuration of the roadway as it relates to the frequency and steepness of hills and the effect on truck speed. This is only coded for mainline sections.
TERRAIN DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
INTERSECTION CONTROL TYPE
NOTE: This identifies the presence and type of any traffic control devices at an intersection at the beginning of a segment. Refers to only the traffic control on the state route, not the traffic control on the crossroad(s).
TRAFFIC CONTROL DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
TRUCK PERCENTAGE
NON-LABELED VARIABLE
LEFT TURN LANE DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT TURN LANE DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT TURN LANE LENGTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
LEFT TURN LANE LENGTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
LEFT TURN LANE WIDTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
LEFT TURN LANE WIDTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT TURN LANE DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RIGHT TURN LANE DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).Data is not available for 1999 to 2001.
RIGHT TURN LANE LENGTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT TURN LANE LENGTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT TURN LANE WIDTH RD1
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
RIGHT TURN LANE WIDTH RD2
NON-LABELED VARIABLE
NOTE: Acceleration lanes and Turn lanes are associated with at-grade intersections (at the beginning of the section) rather than interchanges. Interchange acceleration, deceleration, and merging areas are included as part of ramp lengths. (See Discussion and Raw File Documentation)
URBAN NUMBER DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
URBAN REGION DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
URBAN AREA NUMBER
URBAN REGION NUMBER
NON-LABELED VARIABLE
WSP DISTRICT NUMBER
NON-LABELED VARIABLE
WSP DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
ZONE DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| BEGMP | HORIZ CURVE BEGIN MLPOST | Curve | NUM | 128 |
| CURV_ANG | HORIZ CURVE CEN ANGLE | Curve | NUM | 128 |
| CURV_DT | HORIZ CURVE DATE | Curve | CHA(8) | 128 |
| CURV_INV | STATE RTE TYPE ID | Curve | CHA(11) | 128 |
| CURV_LGT | HORIZ CURVE LGT (FT) | Curve | NUM | 128 |
| CURV_MAX | HORIZ CURVE MAX SUPER | Curve | NUM | 128 |
| CURV_NUM | HORIZ CURVE NUM | Curve | CHA(6) | 128 |
| CURV_RAD | HORIZ CURVE RAD | Curve | NUM | 128 |
| DEG_CURV | DEGREE OF CURVATURE | Curve | NUM | 129 |
| DIR_CURV | HORIZ CURVE DIRN | Curve | CHA(1) | 129 |
| ENDMP | HORIZ CURVE END MLPOST | Curve | NUM | 129 |
| LEGAL_SP | LEGAL SPEED LIMIT | Curve | NUM | 129 |
| OVERLAP | CURVE OVERLAP IND | Curve | CHA(3) | 129 |
| RTE_NBR | ROUTE NUMBER | Curve | CHA(3) | 129 |
| SEG_LNG | HORIZ CURVE LGT (MI) | Curve | NUM | 130 |
NOTE: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Curve file is available for 1993-1996 and from 2002 onwards.
HORIZ CURVE BEGIN MILEPOST
NON-LABELED VARIABLE - Calculated beginning milepost for curve.
HORIZ CURVE CENTRAL ANGLE
NON-LABELED VARIABLE
HORIZ CURVE DATE
NOTE: Date of last change in related variable (yyyymmdd).
STATE RTE TYPE ID
NON-LABELED VARIABLE
HORIZ CURVE LENGTH (FT)
NON-LABELED VARIABLE - Length of curve in ft. (See SEG_LNG for length in miles)
HORIZ CURVE MAX SUPER
NON-LABELED VARIABLE
NOTE: Most of the cases are uncoded for this variable. The only data present is for recent reconstruction efforts.
HORIZ CURVE NUMBER
NON-LABELED VARIABLE
HORIZ CURVE RADIUS
NON-LABELED VARIABLE - Curve radius in feet.
DEGREE OF CURVATURE
NON-LABELED VARIABLE — Calculated (xxx.xx) from curve radius.
HORIZ CURVE DIRECTION
NOTE: Direction of a curve on a roadway in reference to the increasing direction of inventory.
HORIZ CURVE END MILEPOST
NON-LABELED VARIABLE - Calculated ending milepost for curve.
LEGAL SPEED LIMIT
CURVE OVERLAP INDICATOR
NOTE: A calculated variable indicating whether a curve overlaps with the preceding curve because of errors in mileposting due to conversion of curve length from miles to feet. This occurs in less than one percent of the cases.
ROUTE NUMBER
NON-LABELED VARIABLE
HORIZ CURVE LENGTH (MI)
NON-LABELED VARIABLE - Calculated length of curve in 1/100 mi.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| BEGMP | GRADE BEGIN MILEPOST | Grade | NUM | 132 |
| DIR_GRAD | DIRECTION OF GRADE | Grade | CHA(1) | 132 |
| ENDMP | GRADE END MILEPOST | Grade | NUM | 132 |
| GRAD_DT | VERT ALIGN DATE OF CHNG | Grade | CHA(8) | 132 |
| GRAD_INV | STATE RTE TYPE ID | Grade | CHA(11) | 132 |
| GRAD_NUM | VERT ALIGN CONTR | Grade | CHA(6) | 132 |
| GRAD_TYP | VERT CURVE TYPE | Grade | CHA(1) | 132 |
| LEGAL_SP | LEGAL SPEED LIMIT | Grade | NUM | 133 |
| PCT_GRAD | PERCENT GRADE | Grade | NUM | 133 |
| RTE_NBR | ROUTE NUMBER | Grade | CHA(3) | 133 |
| SEG_LNG | GRADE LENGTH (MI) | Grade | NUM | 133 |
| VCUR_LGT | VERTICAL CURVE LENGTH | Grade | NUM | 133 |
NOTE: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Grade file is available for 1993-1996 and from 2002 onwards.
HORIZ CURVE BEGIN MILEPOST
NON-LABELED VARIABLE - Calculated beginning milepost for curve.
DIRECTION OF GRADE
NOTE: Indication of positive (+) or negative (-) grade.
HORIZ CURVE END MILEPOST
NON-LABELED VARIABLE - Calculated ending milepost for curve.
VERT ALIGN DATE OF CHANGE
NOTE: Date of last change in related variable (yyyymmdd).STATE RTE TYPE ID
NON-LABELED VARIABLE - Linkage variable. See Raw File Documentation
VERT ALIGN CONTROL NUM
NON-LABELED VARIABLE
VERT ALIGN CURVE TYPE
NOTE: Indicates whether the end of the grade is connected to the succeeding grade with a vertical curve or an angle point,(i.e., instantaneous change in percent grade of the two intersecting tangent sections).
LEGAL SPEED LIMIT
PERCENT GRADE
NON-LABELED VARIABLE — Percent grade (x.xx%), preceeded by a "+" for an upgrade, a "-" for a downgrade and a blank where direction of grade is non stated.
ROUTE NUMBER
NON-LABELED VARIABLE
GRADE LENGTH (MI)
NON-LABELED VARIABLE
NOTE: Calculated length of grade in 1/100 miles.
VERTICAL CURVE LENGTH
NON_LABELED VARIABLE
NOTE: Length of vertical curve at end of grade in feet.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| AADT | AVER ANNUAL DAILY TRAFFIC | Ramp | NUM | 137 |
| BEGMP | BEGMP | Ramp | NUM | 137 |
| CITY | CITY NUMBER | Ramp | CHA(4) | 137 |
| CITY_DT | CITY DATE | Ramp | CHA(8) | 140 |
| CNTL_SEC | CNTL SECTION | Ramp | CHA(8) | 140 |
| CNTY_DT | COUNTY DATE | Ramp | CHA(8) | 140 |
| COUNTY | COUNTY NUMBER | Ramp | CHA(2) | 140 |
| CTY_ZONE | CITY ZONE TYPE | Ramp | CHA(1) | 141 |
| DEVCD | LEVEL OF DEVLMPT | Ramp | CHA(2) | 141 |
| DEVCD_DT | LEVEL OF DEVELMT DATE | Ramp | CHA(8) | 141 |
| DISTR_DT | DISTRICT DATE | Ramp | CHA(8) | 141 |
| DISTRICT | DISTRICT NUMBER | Ramp | CHA(1) | 141 |
| ENDMP | CALCULATED ENDING MILEPOST | Ramp | NUM | 142 |
| EW_DTE | EAST/WEST INDICATOR DATE | Ramp | CHA(8) | 142 |
| EW_IND | EAST WEST IND | Ramp | CHA(1) | 142 |
| FED_AID | FED AID CLASS | Ramp | CHA(1) | 142 |
| FED_CD | FED AID TYPE | Ramp | CHA(4) | 142 |
| FEDAD_DT | FED-AID DATE | Ramp | CHA(8) | 142 |
| FUNC_CLS | FEDERAL FUNC CLASS | Ramp | CHA(2) | 142 |
| FUNC_DT | FUNCTIONAL CLASS DATE | Ramp | CHA(8) | 143 |
| LANEWID | CALCULATED LANE WIDTH | Ramp | NUM | 143 |
| LSHL_DTE | LEFT SHOULDER DATE RD1 | Ramp | CHA(8) | 143 |
| LSHL_TYP | LEFT SHOULDER TYPE RD1 | Ramp | CHA(1) | 143 |
| LSHLDWID | LEFT SHOULDER WIDTH RD1 | Ramp | NUM | 143 |
| LST_UPDT | CNTL SEC LST UPD | Ramp | CHA(8) | 144 |
| MNT_AREA | MAINTENANCE AREA NBR | Ramp | CHA(1) | 144 |
| MNT_DTE | MAINTENANCE DATE | Ramp | CHA(8) | 144 |
| MNTSC_DT | MAINTENANCE SECTION DATE | Ramp | CHA(8) | 144 |
| MNTSEC | MAINTENANCE SECT NBR | Ramp | CHA(2) | 144 |
| MT_DTE | LAST MAINT DATE | Ramp | CHA(8) | 144 |
| NO_LANE1 | NUMBER LANES INC | Ramp | NUM | 144 |
| NO_LANE2 | NUMBER LANES DEC | Ramp | NUM | 144 |
| NO_LANES | TOTAL NUMBER OF LANES | Ramp | NUM | 144 |
| NO_LNDT1 | NUMBER OF LANES DATE RD1 | Ramp | CHA(8) | 145 |
| NO_LNDT2 | NUMBER OF LANES DATE RD2 | Ramp | CHA(8) | 145 |
| PGRP_DT | POPULATION GROUP DATE | Ramp | CHA(8) | 145 |
| POP_GRP | CITY POPULATION | Ramp | CHA(2) | 145 |
| RD_EQUAT | EQUATION | Ramp | CHA(17) | 145 |
| RD_LIGHT | INTERSECTION ILLUM-ND | Ramp | CHA(1) | 146 |
| RD_OPEN | ROAD OPEN DATE | Ramp | CHA(8) | 146 |
| RD_OWNER | ROADWAY OWNER CODE | Ramp | CHA(2) | 146 |
| RD_QUAL | RELATED RD QUAL | Ramp | CHA(8) | 146 |
| RD_RARM | REVERSE ARM | Ramp | NUM | 146 |
| RD_SRMP | RDWY SRMP | Ramp | NUM | 146 |
| RD_TYPE | RELATED RD TYPE | Ramp | CHA(2) | 146 |
| RDWY_WD1 | ROADWAY WIDTH RD 1 | Ramp | NUM | 147 |
| RDWY_WID | TOTAL ROADWAY WIDTH | Ramp | NUM | 147 |
| RDWYWDD1 | ROADWAY WIDTH DATE RD 1 | Ramp | CHA(8) | 147 |
| REC_TYPE | RECORD TYPE | Ramp | NUM | 147 |
| ROAD_INV | ROUTE TYPE ID | Ramp | CHA(11) | 147 |
| RSHL_DTE | RIGHT SHOULDER DATE RD1 | Ramp | CHA(8) | 148 |
| RSHL_TYP | RIGHT SHOULDER TYPE RD1 | Ramp | CHA(1) | 148 |
| RSHLDWID | RIGHT SHOULDER WIDTH RD1 | Ramp | NUM | 148 |
| RTE_NBR | ROUTE NUMBER | Ramp | CHA(3) | 148 |
| RURURB | RURAL URBAN | Ramp | CHA(1) | 148 |
| SEG_LNG | RD CALCULATED SECT LNGTH | Ramp | NUM | 148 |
| ST_FUNC | STATE FUNC CLASS | Ramp | CHA(2) | 149 |
| SURF_TYP | SURFACE TYPE RD1 | Ramp | CHA(1) | 149 |
| TRF_CNTL | INTERSECTION CONTROL TYPE | Ramp | CHA(2) | 149 |
| TRFCN_DT | TRAFFIC CONTROL DATE | Ramp | CHA(8) | 149 |
| TRKPCTS | TRUCK PERCENTAGE | Ramp | NUM | 150 |
| UBREG_DT | URBAN NUMBER DATE | Ramp | CHA(8) | 150 |
| URB_DT | URBAN REGION DATE | Ramp | CHA(8) | 150 |
| URB_NBR | URBAN AREA NUMBER | Ramp | CHA(2) | 150 |
| URB_REG | URBAN REGION NUMBER | Ramp | CHA(1) | 150 |
| WSP_DIST | WSP DISTRICT NUMBER | Ramp | CHA(1) | 150 |
| WSP_DT | WSP DATE | Ramp | CHA(8) | 150 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) No Ramp files were received from Washington for 1997-2001. The formats described below pertain to 1993-1996 and 2002 onward years.
AVER ANNUAL DAILY TRAFFIC
NOTE: (1) As in the roadlog file, AADT in 2004 and later files were defined using a new methodology. This will result in some discrepancies between AADT counts for 2004 and prior years for the same roadway segment. See Discussion. (2) This variable is not present for all ramps in the file. For ramps where traffic volume is not available, this variable is coded as missing.
BEGMP
NON-LABELED VARIABLE
CITY NUMBER
CITY DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
CNTL SECTION
NON-LABELED VARIABLE
COUNTY DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
COUNTY NUMBER
CITY ZONE TYPE
NON-LABELED VARIABLE
LEVEL OF DEVLMPT
NOTE: This variable indicates a classification assigned to sections of roadway, which relates to plans for maintenance and improvement of the sections.
LEVEL OF DEVELMT DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
DISTRICT DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
DISTRICT NUMBER
CALCULATED ENDING MILEPOST
NON-LABELED VARIABLE
NOTE: Calculated ending milepost, which is defined as equal to beginning milepost (BEGMP) on the next segment of same route.
EAST/WEST DATE INDICATOR DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
EAST WEST IND
FED AID CLASS
FED AID TYPE
FED-AID DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
FEDERAL FUNC CLASS
FUNCTIONAL CLASS DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
CALCULATED LANE WIDTH
NON-LABELED VARIABLE
NOTE: This variable is calculated by dividing the total roadway width by the total number of lanes. There will be some error on sections where the shoulder type is curb or wall. See "Note" under RDWY_WD1.
LEFT SHOULDER DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
LEFT SHOULDER TYPE RD1
NOTE: The surface composition of the inside (left) shoulder in the decreasing direction of the roadway. This is only used for divided roadway.
LEFT SHOULDER WIDTH RD1
NOTE: The width of the inside (left) shoulder in feet in the increasing direction of the roadway. This variable refers to both divided and undivided roadways. The approximately 14% "no shoulder" category includes both curb sections and, unfortunately, some uncoded sections.
CNTL SEC LST UPD
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MAINTENANCE AREA NBR
NON-LABELED VARIABLE
MAINTENANCE DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MAINTENANCE SECTION DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
MAINTENANCE SECT NBR
NON-LABELED VARIABLE
LAST MAINT DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
NUMBER LANES INC
NUMBER LANES DEC
TOTAL NUMBER OF LANES
NOTE: "Increasing" and "decreasing" number of lanes indicated the number of total thru lanes in those directions of travel regardless of whether a roadway is divided or not. Lane counts do not include acceleration lanes or turn lanes. "Total Number of Lanes" is a calculated variable, which sums the first two.
NUMBER OF LANES DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
NUMBER OF LANES DATE RD2
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
POPULATION GROUP DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
CITY POPULATION
NOTE: Approximately 85% of the sections are blank, indicating rural areas.
EQUATION
INTERSECTION ILLUM-ND
NOTE: Defines intersection illumination for the intersection at the beginning of the section.
ROAD OPEN DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
ROADWAY OWNER CODE
RELATED RD QUAL
NON-LABELED VARIABLE
REVERSE ARM
NON-LABELED VARIABLE
RDWY SRMP
NON-LABELED VARIABLE
RELATED RD TYPE
ROADWAY WIDTH RD 1
NOTE: The width of the driving surface, in feet, in the increasing (both divided and undivided) direction of the roadway, and in the decreasing (divided only) direction of the roadway. In sections with curbs, it is measured from curb to curb, and thus may include parking areas or other paved shoulder adjacent to the curb (as in curbs on interchange ramp islands).
TOTAL ROADWAY WIDTH
ROADWAY WIDTH DATE RD 1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RECORD TYPE
NON-LABELED VARIABLE
ROUTE TYPE ID
NON-LABELED VARIABLE
RIGHT SHOULDER DATE RD1
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RIGHT SHOULDER TYPE RD1
NOTE: The surface composition of the outside (right) shoulder in the increasing direction of the roadway. This variable refers to both divided and undivided roadways.
RIGHT SHOULDER WIDTH RD1
NOTE: The width of the outside (right) shoulder in feet in the increasing direction of the roadway. This variable refers to both divided and undivided roadways. The approximately 10% "no shoulder" category includes both curb sections and, unfortunately, some uncoded sections.
ROUTE NUMBER
NON-LABELED VARIABLE
RURAL URBAN
RD CALCULATED SECT LNGTH
NON-LABELED VARIABLE
NOTE: Section length calculated as difference between beginning and ending mileposts.
STATE FUNC CLASS
NOTE: This code represents the State assigned functional class for a section of roadway.
SURFACE TYPE RD1
NOTE: The composition of the driving surface in the increasing (both divided and undivided) direction of the roadway, and in the decreasing (divided only) direction of the roadway.
INTERSECTION CONTROL TYPE
NOTE: This identifies the presence and type of any traffic control devices at an intersection at the beginning of a segment. Refers to only the traffic control on the state route, not the traffic control on the crossroad(s).
TRAFFIC CONTROL DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
TRUCK PERCENTAGE
NON-LABELED VARIABLE
URBAN NUMBER DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
URBAN REGION DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
URBAN AREA NUMBER
URBAN REGION NUMBER
NON-LABELED VARIABLE
WSP DISTRICT NUMBER
NON-LABELED VARIABLE
WSP DATE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| LENGTH | LENGTH OF SLN IN FEET | Spl-ln | NUM | 152 |
| SLN_ABID | SPEC USE LANES AB IND | Spl-ln | CHA(1) | 152 |
| SLN_DATE | SPECIAL LANE DATE | Spl-ln | CHA(8) | 152 |
| SLN_DIST | SLN DISTRICT NUMBER | Spl-ln | CHA(1) | 152 |
| SLN_DSDT | SLN DISTRICT DATE | Spl-ln | CHA(8) | 152 |
| SLN_INV | SLN ROAD INV-SR TYPE ID | Spl-ln | CHA(11) | 152 |
| SLN_MLPT | SPEC USE LANES ARM | Spl-ln | NUM | 152 |
| SLN_MTDT | SPEC USE LANES MAINT DTE | Spl-ln | CHA(8) | 152 |
| SLN_QUAL | RELATED ROAD QUAL | Spl-ln | CHA(6) | 152 |
| SLN_RARM | SPEC USE LANES RV ARM | Spl-ln | NUM | 153 |
| SLN_RDTY | RELATED ROAD TYPE | Spl-ln | CHA(2) | 153 |
| SLN_RTNO | ROUTE NUMBER | Spl-ln | CHA(3) | 153 |
| SLN_SFTY | SPECIAL LANE SURFACE TYPE | Spl-ln | CHA(1) | 153 |
| SLN_SIDE | SLN LEFT/RIGHT SIDE IND | Spl-ln | CHA(2) | 153 |
| SLN_SRMP | SPEC USE LANES SRMP | Spl-ln | NUM | 153 |
| SLN_TYPE | SPECIAL LANE TYPE | Spl-ln | CHA(2) | 153 |
| SLN_WID | SPECIAL LANE WIDTH | Spl-ln | CHA(2) | 154 |
NOTE: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Special Lane Use file is available for 1993-1996 and from 2002 onwards.
LENGTH OF SPECIAL LANE IN FEET
NON-LABELED VARIABLE
SPEC USE LANES AHEAD/BACK IND
NON-LABELED VARIABLE
SPECIAL LANE DATE
NOTE: Date of last change in related variable (yyyymmdd).
DISTRICT NUMBER
NON-LABELED VARIABLE
DISTRICT DATE
NOTE: Date of last change in related variable (yyyymmdd).
ROAD INV - SR TYPE ID
NON-LABELED VARIABLE
SPEC LANES ACCUM ROUTE MILEPOST
NON-LABELED VARIABLE
SPEC USE LANES MAINT DTE
NOTE: Date of last change in related variable (yyyymmdd).
RELATED ROAD QUAL
NON-LABELED VARIABLE
SPEC USE LANES REVERSE ARM
NON-LABELED VARIABLE
SLN RELATED ROAD TYPE
NOTE: See codes under RD_TYPE in Roadlog File.
ROUTE NUMBER
NON-LABELED VARIABLE
SPECIAL LANE SURFACE TYPE
NOTE: This describes the composition of the surface for special use lanes. Approximately half of the special use lanes do not have a surface type value since they are already a part of the shoulders or medians.
SLN LEFT/RIGHT SIDE IND
NOTE: Describes the location of a feature which is off the through lanes in relation to the increasing direction of the roadway.
SPEC USE LANES SRMP
NON-LABELED VARIABLE
SPECIAL LANE TYPE
NOTE: Indicates a special use lane that occurs in conjunction with the main roadway. Some of the special use lane types are constructed separately from main roadway and some are part of shoulders or medians which are identified for special use (Example: A shoulder which is marked as a bicycle lane).
SPECIAL LANE WIDTH
NOTE: This describes the surface width, in feet, for special-use lanes. Approximately half of the special-use lanes will not have a surface type value since they are already a part of the shoulders or medians.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| BRDG_DT | BRIDGE DATE | Feature | CHA(8) | 156 |
| BRDG_LGT | BRIDGE LIGHTING | Feature | CHA(1) | 156 |
| BRDG_NBR | BRIDGE NUMBER | Feature | CHA(9) | 156 |
| BRDG_OWN | BRIDGE XROAD OWNER CD | Feature | CHA(2) | 156 |
| BRDG_XRD | BRIDGE XROAD DESC | Feature | CHA(24) | 156 |
| CURV_ANG | HORIZ CURVE CEN ANGLE | Feature | NUM | 156 |
| CURV_DT | HORIZ CURVE DATE | Feature | CHA(8) | 157 |
| CURV_LGT | HORIZ CURVE LENGTH (FT) | Feature | NUM | 157 |
| CURV_MAX | HORIZ CURVE MAX SUPER | Feature | NUM | 157 |
| CURV_NUM | HORIZ CURVE CONTROL NUM | Feature | CHA(6) | 157 |
| CURV_RAD | HORIZ CURVE RADIUS | Feature | NUM | 157 |
| CURV_TYP | HORIZ CURVE TYPE | Feature | CHA(1) | 157 |
| DIR_CURV | HORIZ CURVE DIRN | Feature | CHA(1) | 157 |
| DIST_DT | DISTRICT DATE | Feature | CHA(8) | 157 |
| DISTNUM | DISTRICT NUMBER | Feature | CHA(1) | 157 |
| GRAD_AHD | VERT ALIGN GRADE AHEAD | Feature | NUM | 158 |
| GRAD_BAK | VERT ALIGN GRADE BACK | Feature | NUM | 158 |
| GRAD_DT | VERT ALIGN DATE | Feature | CHA(8) | 158 |
| GRAD_LGT | VERT CURVE LENGTH (FT) | Feature | NUM | 158 |
| GRAD_NUM | VERT ALIGN CONTR NUM | Feature | CHA(6) | 158 |
| GRAD_TYP | VERT CURVE TYPE | Feature | CHA(1) | 158 |
| IN_DIR | DIRECTION OF INVENTORY | Feature | CHA(1) | 158 |
| IN_INV | STATE RTE TYPE ID | Feature | CHA(11) | 158 |
| IN_MLPT | ACCUM ROUTE MILEPOST | Feature | NUM | 159 |
| IN_RTNBR | ROUTE NUMBER | Feature | CHA(3) | 159 |
| IN_TYPE | RELATED ROAD TYPE | Feature | CHA(2) | 159 |
| REC_TYPE | RECORD TYPE | Feature | NUM | 159 |
| SPD_DTE | SPEED DATE | Feature | CHA(8) | 159 |
| SPD_LIMT | LEGAL SPEED LIMIT | Feature | NUM | 159 |
| STR_ALIS | STREET NAME ALIAS | Feature | CHA(24) | 159 |
| STR_DTE | STRUCTURE DATE | Feature | CHA(8) | 159 |
| TUN_NAME | TUNNEL NAME | Feature | CHA(24) | 160 |
| TUN_NUM | TUNNEL NUMBER | Feature | CHA(9) | 160 |
| TUNL_DT | TUNNEL DATE | Feature | CHA(8) | 160 |
| UNX_DT | UNXING DATE | Feature | CHA(8) | 160 |
| UNX_LGT | UNXING LIGHTING | Feature | CHA(1) | 160 |
| UNX_OVHD | OVHD BRIDGE NUM | Feature | CHA(9) | 160 |
| UNX_XRD | UNXROAD DESC | Feature | CHA(24) | 160 |
| UNX_XRDO | UNXROAD OWNER CD | Feature | CHA(2) | 160 |
NOTE: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Feature file is available for 1993-1996 and from 2002 onwards.
BRIDGE DATE
NOTE: Date of last change in related variable (yyyymmdd).
BRIDGE LIGHTING
BRIDGE NUMBER
NON-LABELED VARIABLE - Linkage to National Bridge Index.
BRIDGE XROAD OWNER CD
NOTE: Identification of ownership of the road or feature being crossed by the bridge.
BRIDGE XROAD DESC
NON-LABELED VARIABLE
HORIZ CURVE CEN ANGLE
NON-LABELED VARIABLE
HORIZ CURVE DATE
NOTE: Date of last change in related variable (yyyymmdd).
HORIZ CURVE LENGTH (FT)
NON-LABELED VARIABLE
HORIZ CURVE MAX SUPER
NON-LABELED VARIABLE
HORIZ CURVE CONTR NUM
NON-LABELED VARIABLE
HORIZ CURVE RADIUS (FT)
NON-LABELED VARIABLE
HORIZ CURVE TYPE
NOTE: Indicates whether the horizontal curve is a regular curve, an angle point, (i.e., an instantaneous change in direction between two intersecting tangent sections), or a gap where no information on the horizontal alignment is available. Code values are specific to the TRIPS system. The element is stored at the SRMP of the curve PC (beginning) with all other data relating to the curve.
HORIZ CURVE DIRN
NOTE: Direction of a curve on a roadway in reference to the increasing direction of inventory.
DISTRICT DATE
NOTE: Date of last change in related variable (yyyymmdd).
DISTRICT NUMBER
NON-LABELED VARIABLE
VERT ALIGN GRADE AHEAD
NON-LABELED VARIABLE — Percent grade (x.xx%).
VERT ALIGN GRADE BACK
NON-LABELED VARIABLE — Percent grade (x.xx%).
VERT ALIGN DATE OF CHANGE
NOTE: Date of last change in related variable (yyyymmdd).
VERT CURVE LENGTH (FT)
NON-LABELED VARIABLE
VERT ALIGN CONTROL NUM
NON-LABELED VARIABLE
VERT ALIGN CURVE TYPE
NOTE: Indicates whether the location is characterized by a vertical curve, an angle point,(i.e., instantaneous change in percent grade of the two intersecting tangent sections), or a gap where no information on the vertical alignment is available.
DIRECTION OF INVENTORY
NOTE: The inventory direction indicates the direction of mileposting on a state route. State routes are mileposted from a south to north or from west to east.
STATE RTE TYPE ID
NON-LABELED VARIABLE
ACCUM ROUTE MILEPOST
NON-LABELED VARIABLE
ROUTE NUMBER
NON-LABELED VARIABLE
RELATED ROAD TYPE
NON-LABELED VARIABLE
RECORD TYPE
NON-LABELED VARIABLE - File type identification
SPEED DATE
NOTE: Date of last change in related variable (yyyymmdd).
LEGAL SPEED LIMIT
STREET NAME ALIAS
NON-LABELED VARIABLE
STRUCTURE DATE
NON-LABELED VARIABLE
TUNNEL DATE
NOTE: Date of last change in related variable (yyyymmdd).
TUNNEL NAME
NON-LABELED VARIABLE
TUNNEL NUMBER
NON-LABELED VARIABLE
UNXING DATE
NOTE: Date of last change in related variable (yyyymmdd).
UNXING LIGHTING
NON-LABELED VARIABLE
OVHD BRIDGE NUM
NON-LABELED VARIABLE
UNXROAD DESC
NON-LABELED VARIABLE
UNXROAD OWNER CD
NOTE: Used to specify the owner of a road which crosses a state route.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| DISCNTY | DISCONTINUITY INDICATOR | LR | CHA(1) | 162 |
| FACT_DES | FACILITY DESC | LR | CHA(24) | 162 |
| FACT_DT | FACILITY DATE | LR | CHA(8) | 162 |
| FACT_OWN | FACILITY OWNER | LR | CHA(3) | 162 |
| FACT_TYP | FACILITY TYPE | LR | CHA(1) | 162 |
| FLY_DT | FLYER STOP DATE | LR | CHA(8) | 163 |
| FLY_NUM | FLYER STOP NUMBER | LR | CHA(2) | 163 |
| FLY_OWN | FLYER STOP OWNER | LR | CHA(2) | 163 |
| LOT_DT | PARK RIDE LOT DATE | LR | CHA(8) | 163 |
| LOT_NUM | PARK RIDE LOT NUMBER | LR | CHA(2) | 163 |
| LOT_OWN | PARK RIDE LOT OWNER CD | LR | CHA(2) | 163 |
| LRDIS_DT | DISTRICT DATE | LR | CHA(8) | 164 |
| LRMIS_DT | MISC FEATURE DATE | LR | CHA(8) | 164 |
| LR_ABIND | LR AHEAD/BACK IND | LR | CHA(1) | 164 |
| LR_DESC | MISC FEATURE DESC | LR | CHA(24) | 164 |
| LR_DISTR | DISTRICT NUMBER | LR | CHA(1) | 164 |
| LR_INV | LEFT RIGHT ROAD INVENTORED | LR | CHA(11) | 164 |
| LR_MLPT | LR ACCUM ROUTE MILEPOST | LR | NUM | 164 |
| LR_MTDTE | LEFT RIGHT MAINTENACE DATE | LR | CHA(8) | 164 |
| LR_QUAL | RELATED ROAD QUAL | LR | CHA(6) | 164 |
| LR_RARM | LEFT RIGHT REVERSE ARM | LR | NUM | 165 |
| LR_RDTY | RELATED ROAD TYPE | LR | CHA(2) | 165 |
| LR_RTNBR | ROUTE NUMBER | LR | CHA(3) | 165 |
| LR_SEC | CONTROL SECTION | LR | CHA(6) | 165 |
| LR_SIDE | LEFT/RIGHT SIDE IND | LR | CHA(2) | 165 |
| LR_SRMP | LEFT RIGHT SRMP | LR | NUM | 165 |
| LST_UPDT | LAST UPDATE DATE | LR | CHA(8) | 165 |
| MARK_DT | MILEPOST MARKER DATE | LR | CHA(8) | 165 |
| MARK_IND | MILEPOST MARKER AB IND | LR | CHA(1) | 165 |
| MARK_NUM | MILEPOST MARKER NUMBER | LR | CHA(3) | 166 |
| PKZNE_DT | PARKING ZONE DATE | LR | CHA(8) | 166 |
| PKZNE_TY | PARKING ZONE TYPE | LR | CHA(1) | 166 |
| REC_TYPE | RECORD TYPE | LR | NUM | 166 |
| REST_DT | REST AREA DATE | LR | CHA(8) | 166 |
| REST_NAM | REST AREA NAME | LR | CHA(24) | 166 |
| REST_NUM | REST AREA NUMER | LR | CHA(4) | 166 |
| REST_TYP | REST AREA TYPE | LR | CHA(2) | 166 |
| WGHT_DT | WEIGHT STATION DATE | LR | CHA(8) | 166 |
| WGHT_NUM | WEIGHT STATION NUMBER | LR | CHA(2) | 167 |
| WGHT_TYP | WEIGHT STATION TYPE | LR | CHA(2) | 167 |
| XRD_DESC | CROSSROAD ID DESC | LR | CHA(24) | 167 |
| XRD_DT | CROSSROAD DATE | LR | CHA(8) | 167 |
| XRD_OWN | CROSSROAD OWNER CD | LR | CHA(3) | 167 |
| XRD_TYP | CROSSROAD CONFIG TYPE | LR | CHA(1) | 167 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Left/Right file is available for 1993-1996 and from 2002 onwards.
DISCONTINUITY INDICATOR
NON-LABELED VARIABLESee Raw File Documentation
FACILITY DESC
NON-LABELED VARIABLE
FACILITY DATE
NOTE: Date of last change in related variable (yyyymmdd).
FACILITY OWNER
FACILITY TYPE
NOTE: Establishes whether the facility is a toll, ferry, or border facility. Facility generally refers to the building associated with the area. (e.g. Toll Booth, Ferry Ticket Building, Customs Building).
FLYER-STOP DATE
NOTE: Date of last change in related variable (yyyymmdd).
FLYER STOP NUMBER
NON-LABELED VARIABLE
FLYER-STOP OWNER
PARK-RIDE LOT DATE
NOTE: Date of last change in related variable (yyyymmdd).
PARK‑RIDE LOT NUMBER
NON-LABELED VARIABLE
PARK-RIDE LOT OWNER CD
DISTRICT DATE
NOTE: Date of last change in related variable (yyyymmdd).
MISC FEATURE DATE
NOTE: Date of last change in related variable (yyyymmdd).
LR AHEAD/BACK IND
NON-LABELED VARIABLE
MISC FEATURE DESC
NON-LABELED VARIABLE
DISTRICT NUMBER
NON-LABELED VARIABLE
LEFT RIGHT ROAD INVENTORED
NON-LABELED VARIABLE
LR ACCUMULATE ROUTE MILEPOST
NON-LABELED VARIABLE
LEFT RIGHT MAINTENACE DATE
NOTE: Date of last change in related variable (yyyymmdd).
RELATED ROAD QUAL
NON-LABELED VARIABLE
LEFT RIGHT REVERSE ARM
NON-LABELED VARIABLE
RELATED ROAD TYPE
NOTE: See codes under RD_TYPE in Roadlog File.
ROUTE NUMBER
NON-LABELED VARIABLE
CONTROL SECTION
NON-LABELED VARIABLE
RDWY LEFT/RIGHT SIDE IND
LEFT RIGHT SRMP
NON-LABELED VARIABLE
LAST UPDATE DATE
NOTE: Date of last change in related variable (yyyymmdd).
MILEPOST MARKER DATE
NOTE: Date of last change in related variable (yyyymmdd).
MILEPOST MARKER AB IND
NOTE: Uniquely identifies a milepost marker number when the same milepost marker number is used more than once for a route.
MILEPOST MARKER NUMBER
NON-LABELED VARIABLE
PARKING ZONE DATE
NOTE: Date of last change in related variable (yyyymmdd).
PARKING ZONE TYPE
NOTE: Describes the type of parking that is permitted along a state route as it passes through a city.
LEFT RIGHT RECORD TYPE
NON-LABELED VARIABLE - File type identification
REST AREA DATE
NOTE: Date of last change in related variable (yyyymmdd).
REST AREA NAME
NON-LABELED VARIABLE
REST AREA NUMER
NON-LABELED VARIABLE
REST AREA TYPE
NOTE: Indicates the relative size of a rest area.
WEIGHT STATION DATE
NOTE: Date of last change in related variable (yyyymmdd).
WEIGHT STATION NUMBER
NON-LABELED VARIABLE
WEIGHT STATION TYPE
NON-LABELED VARIABLE
CROSSROAD ID DESC
NON-LABELED VARIABLE
CROSSROAD DATE
NOTE: Date of last change in related variable (yyyymmdd).
CROSSROAD OWNER CD
NON-LABELED VARIABLE
CROSSROAD CONFIG TYPE
NOTE: Indicates how a cross road intersects with a state route.
| SAS VARIABLE NAME | DESCRIPTION | SAS VARIABLE FILE | FORMAT TYPE | PAGE NO. |
|---|---|---|---|---|
| DIR_INV | RDWY DIR OF INVENTORY | Railroad | CHA(1) | 170 |
| REC_TYPE | RECORD TYPE | Railroad | NUM | 170 |
| RRDIS_DT | DISTRICT DATE | Railroad | CHA(8) | 170 |
| RRX_DTE | RR XING DATE | Railroad | CHA(8) | 170 |
| RRX_NUM | RR XING AAR NUM | Railroad | CHA(7) | 170 |
| RRX_TYPE | RR XING TYPE | Railroad | CHA(1) | 170 |
| RR_ABIND | RR CROSSING AB IND | Railroad | CHA(1) | 170 |
| RR_DISTR | DISTRICT NUMBER | Railroad | CHA(1) | 170 |
| RR_INV | RR CROSSING ROAD INV | Railroad | CHA(11) | 171 |
| RR_MLPT | RR XING ACCUM ROUTE MLPST | Railroad | NUM | 171 |
| RR_MTDTE | RR CROSSING MAINT DTE | Railroad | CHA(8) | 171 |
| RR_QUAL | RELATED ROAD QUAL | Railroad | CHA(6) | 171 |
| RR_RARM | RR CROSSING REVERSE ARM | Railroad | NUM | 171 |
| RR_RDTY | RELATED ROAD TYPE | Railroad | NUM | 171 |
| RR_RTNBR | ROUTE NUMBER | Railroad | CHA(3) | 171 |
| RR_SRMP | RR CROSSING SRMP | Railroad | NUM | 171 |
NOTES: (1) SAS variable names and longer explanatory names are shown above each listing. (See Discussion for information on SAS formats.)
(2) For all SAS-formatted variables below, an extra category labeled as "ERROR CODES" consolidates all values not listed as legitimate codes. This category is printed when variables are listed in tables.
(3) Railroad crossing file is available for 1993-1996 and from 2002 onwards.
RDWY DIR OF INVENTORY
NON-LABELED VARIABLE
RECORD TYPE
NON-LABELED VARIABLE - File type identification
DISTRICT DATE
NOTE: Date of last change in related variable (yyyymmdd).
RR XING DATE
NOTE: Date of last change in related variable (yyyymmdd).
RR XING AAR NUM
NON-LABELED VARIABLE
RR XING TYPE
NOTE: Indicates how a railroad crossing physically crosses a state route.
RR CROSSING AB IND
NON-LABELED VARIABLE
DISTRICT NUMBER
NON-LABELED VARIABLE
RR CROSSING ROAD INV
NON-LABELED VARIABLE
RR CROSSING ACCUM ROUTE MILEPOST
NON-LABELED VARIABLE
RR CROSSING MAINT DTE
NON-LABELED VARIABLE
NOTE: Date of last change in related variable (yyyymmdd).
RELATED ROAD QUAL
NON-LABELED VARIABLE
RR CROSSING REVERSE ARM
NON-LABELED VARIABLE
RELATED ROAD TYPE
NOTE: See codes under RD_TYPE in Roadlog File.
ROUTE NUMBER
NON-LABELED VARIABLE
RR CROSSING RMP
NON-LABELED VARIABLE