|
|
|
Potential Use of Archived Intelligent Transportation Systems Data for Government Reporting |
| Data Element | Description | Links to ITS Data Sources |
|---|---|---|
| WEATHER | Weather during crash | TMDD: Codes are: Sunny; Rain; Hurricane; Severe Rain; Flood; Sleet; Snow; Blizzard; Overcast Cloudy; Sun Glare; Earthquake Landslide; some FARS codes may be derived ATIS: Weather message includes information on: dayOfWeek Day-of-week temperature Weather-Temperature highTemperature Weather-HighTemperature lowTemperature Weather-LowTemperature skyConditions Weather-SkyConditions probability Weather-Probability -- level of faith in this information specialConditions Weather-SpecialConditions visibility Weather-Visibility windSpeed Weather-WindSpeed windDirection Weather-WindDirection humidity Weather-Humidity pressure Weather-Pressure sunriseTime ATIS-Time sunsetTime ATIS-Time ...but determining the specific weather at a crash location from this is problematic. |
| CITY | Crash City | |
| COUNTY | Crash County | |
| Crash County | ||
| C_M_ZONE | Crash Zone Type | TMDD: Work zones may be distinguished, but not all FARS codes can be obtained. |
| DAY | Day of crash | TMDD and P1512: date/time derivable from incident data elements |
| MONTH | Month of crash | |
| DAY_WEEK | Day of the week of crash | |
| YEAR | The year in which the crash took place. | |
| DRUNK_DR | The number of drunk drivers involved in the fatal crash | |
| FATALS | Number of fatalities that occurred in the crash. | TMDD: "Incident Human Fatalities Count" may be used P1512: "fatalityCnt" may be used |
| NHS | Is crash site part of the National Highway System? | |
| HARM_EV | First harmful event to the vehicle during crash | |
| HIT_RUN | Hit and Run type | |
| LGT_COND | Light conditions | |
| MAN_COLL | Collision type | TMDD: Direct correspondence with FARS |
| MILEPT | Milepost | TMDD: Should be derivable from linear referencing data |
| PEDS | No. of Non-Motorists i.e. any person(s) who is (are) not an occupant of a motor vehicle in transport | |
| NO_LANES | Crash site number of lanes | TMDD: "Number of Through Lanes" on a link can be used. P1512: "laneConfig" may be used. NA: "number_of_lanes" reserved for this information |
| .PERSONS | The number of persons involved in the crash, except for uninjured bus and train passengers. A form describing all other persons involved in a crash, will be filed, i.e. this variable is a count of the persons in the crash. | TMDD: May be derived from incident injury data if this data element is related to every person involved in the incident. (No such relation currently exists in the TMDD.) |
| RAIL | The FRA code for involved railroad | |
| CF1 or CF2 or CF3 | Collision Factors | |
| REL_JUNC | Junction type | TMDD: Direct correspondence to FARS codes |
| REL_ROAD | Crash site relative to the roadway | TMDD: Identifies whether lanes or shoulders are blocked, but these are not necessarily the "crash site". |
| ALIGNMNT | Roadway alignment | |
| ROAD_FNC | Roadway function type | TMDD: "Link Type" has inconsistent coding; allows: Freeway, Arterial, Collector, and Local only |
| ROUTE | Route type | TMDD: "Road Number" can be used directly, but must follow state coding rules. |
| PROFILE | Roadway grade/profile | |
| SUR_COND | Pavement surface condition | TMDD: Codes are mode detailed than FARS; FARS codes directly derivable. NTCIP DCM: "essPavementTemperature" Integer (-1000..1001) Near Match |
| PAVE_TYP | Pavement material | TMDD: Most FARS codes are derivable but not all |
| SCH_BUS | Crashes in which a vehicle functioning as a school bus was directly or indirectly involved. | |
| SP_JUR | Jurisdiction | |
| SP_LIMIT | Speed limit | TMDD: Direct correspondence with FARS. NA: "link_speed_limit" reserved for this information |
| STATE | The state in which the crash occurred, except for Puerto Rico. | |
| ST_CASE | This variable is stored as a numeric variable of six characters, the first two characters are the state code, the next four characters are case number, with leading zeros if necessary. | |
| HOUR | HOUR and Minute are the time of the crash, hours and minutes. | TMDD: "Timeline Start" for roadway event can be used directly (format is HHMMSS.ssss) P1512: Should be able to derive FARS data, depending on how data elements are related. |
| NOT_HOUR | NOT_HOUR and NOT_MIN are the times, hours and minutes, of the notification of the need for emergency medical service, i.e. the time of the 911 call. | TMDD: Includes free-form text for agencies notified, but does not include the time they were notified. P1512: Should be able to derive FARS data, depending on how data elements are related. |
| ARR_HOUR | ARR_ HOUR and ARR_MIN are the arrival times, hours and minutes, of the emergency medical service at the crash scene. | TMDD: Includes the time of the first responder only; may not be EMS. P1512: Should be able to derive FARS data, depending on how data elements are related. |
| HOSP_HR | HOSP_HR and HOSP_MIN are the arrival times, hours and minutes of the emergency medical service at the hospital. | |
| TRA_CONT | Traffic Controls | TMDD: Code are: Signalized; All-way stop sign control; 2-way stop sign control; Yield sign control; Uncontrolled. Some FARS codes are derivable. |
| T_CONT_F | Does the traffic controller function properly? | TMDD: "Faults" for signals are documented; some interpretation necessary for FARS. NA: "hri_closure_data" and "hri_state_data" reserved for this type of data for grade crossings; "intersection_state_data" for signalized intersections. |
| TRAF_FLO | Divided/non-divided roadway type | TMDD: "Median Type" may use to infer divided/undivided. |
| TWAY_ID | Actual Posted Number, Assigned Number, or Common Name (if no posted or assigned number) except: 9999999999 Unknown | TMDD: "Road Number" can be used directly, but must follow state coding rules. |
| VE_FORMS | This counts the number of vehicles in transport involved in the crash. Legally parked vehicles are not included. | TMDD: "Incident Vehicles Involved (count)" may be used, but definitions vary slightly. P1512: May be derived by summing all involved vehicles. |
| AXLES | Number of vehicle axles | P1512: Allows distinguishing trucks of this definition (DE_Axle_Count and DE_PowerUnitType) CVIEW: "NUMBER_OF_AXLES" Number (2,0) NTCIP DCM: "dcmNumAxles" Integer (0..255) |
| BODY_TYP | Vehicle Body Classification by NHTSA, precise definitions for several vehicle categories, such as passenger cars, pickups, buses etc. This information provided here. For some categories one will also need the variable TOW_VEH. BODY_TYP data by numerical order follows this listing. | P1512: Can be derived from DE_PowerUnitType and DE_CargoPackageType directly. NTCIP DCM: "dcmVehicleClass" Integer (0..255) Near Match |
| CARGO_BT | Cargo/heavy vehicle type | |
| L_ENDORS | Endorsements | |
| AVOID | Crash Avoidance Maneuver | |
| FIRST_MO | FIRST_MO and FIRST_YR are the month and year of the driver's first crash. | |
| LAST_MO | LAST_MO and LAST_YR are the month and year of the driver's last crash. | |
| FIRST_YR | FIRST_MO and FIRST_YR are the month and year of the driver's first crash. | |
| LAST_YR | LAST_MO and LAST_YR are the month and year of the driver's last crash. | |
| DR_DRINK | This is a derived variable. Data from the vehicle file are analyzed and if there is "sufficient information to conclude that a driver was drinking, i.e., positive BAC data or police reported alcohol involvement then a driver is classified as drinking. Note that alcohol data are often missing. | |
| L_COMPL | Vehicle License Status | |
| CDL_STAT | Commercial Driver's License Status | |
| L_STATUS | Driver's License Status | |
| DR_PRES | Driver Status | |
| DR_ZIP | Driver Residential ZIP Code | |
| EMER_USE | Emergency Use | |
| DEFORMED | Extent of Deformation | |
| DEATHS | The number of fatalities that occurred in the vehicle. | TMDD and P1512: Number of deaths in a specific vehicle not obtainable. |
| FIRE_EXP | Was there fire during crash? | TMDD: Codes for type of incident include both "vehicular accident" and "vehicular fire"; if only one is coded, obtaining FARS information is impossible. P1512: DE_UnitCondtion may be used directly |
| M_HARM | The most harmful event applied to the vehicle. | |
| HAZ_CARG | Any hazardous cargo? | TMDD: "Description Type Incident" may be used directly P1512: HazMat well covered in P1512.3 ATIS: DE_MAYDAY_Data_cargo_text may be used, but it is free text NA: cf_hazmat_vehicle_information data flow CVIEW: "HAZMAT_STATUS" CHAR(1) |
| IMPACT1 | Initial (or first) impact point | |
| IMPACT2 | Principal impact point | |
| UNDERRIDE | Override/Underride Status | |
| J_KNIFE | Jackknifed Vehicle Status | |
| TOWAWAY | Was the vehicle towed away? | |
| MOD_YEAR | Model Year | CVIEW: "Model_Year" VARCHAR2(4) |
| OCUPANTS | The actual number of occupants in the vehicle, except as listed below. | |
| PREV_ACC | Previously Recorded Accidents (Crashes) | CVIEW: "SNET_TOTAL_ACCIDENTS_LAST24" Number (4,0) Near Match: this field reports the total number of accidents for the past 2 years only |
| PREV_DWI | Previously Recorded DWI Convictions | CVIEW: "VIOLATIONS_DRUGS" Number (6,0) Near Match |
| PREV_OTH | Previously Recorded Other Moving Violations Convict | CVIEW: "VIOLATIONS_TRAFFIC" Number (6,0) Near Match |
| PREV_SPD | Previously Recorded Speeding Convictions | |
| PREV_SUS | Previously Recorded Suspensions and Revocations | |
| OWNER | Registered Owner Status | |
| DR_CF1 or DR_CF2 or DR_CF3 or DR_CF4 | Driver Collision Factor | |
| VEH_CF1 or VEH_CF2 | Vehicle Collision Factor | |
| ROLLOVER | Vehicle Rollover Status | |
| SPEC_USE | Was this a special use vehicle? | |
| REG_STAT | State in which the vehicle was registered | P1512: Optionally provided for in HazMat message sets |
| L_STATE | State in which the driver is licensed | |
| TOW_VEH | Did the vehicle have anything in tow? | TMDD: "Incident Vehicles Involved" has some trailering information, but not enough to allow proper FARS coding. P1512: Derivable from data on "cargo units" |
| TRAV_SP | Travel speed, in miles per hour (mph) | NTCIP DCM: "dcmVehicleSpeed" Integer (0..65535) |
| FLDCD_TR | This is RLPolk VINA decode data. | |
| V_CONFIG | Vehicle Configuration | TMDD: "Incident Vehicles Involved" has some configuration information, but not enough to allow proper FARS coding. P1512: Can be derived from DE_PowerUnitType and DE_CargoPackageType directly. |
| VINA_MOD | The Vin Model, for automobiles, is obtained from the VINA program for automobiles of model year 1966 and later that have verifiable VIN numbers | P1512: VIN for trucks optionally provided for in HazMat message sets ATIS: DE_VEHICLE_Identity_code is the VIN NTCIP DCM: "dcmVehicleID" Octet String, Near Match |
| VIN_1 | The first character of the VIN usually identifies the country or Nation of Origin, the most popular are: | |
| VIN_2 | The second and third characters of the VIN, more or less, identify the make of the vehicle. The most common are: | |
| VIN_10 | The model year of the vehicle is usually the tenth character. The values are: | |
| VIN_LNGT | This is the actual length of the vehicle identification number | |
| MAKE | Vehicle Make | .P1512: Vehicle make and model are free form text; usually only used in HazMat messages CVIEW: "MAKE" VARCHAR2(10) |
| VEH_MAN | Vehicle Maneuver | |
| VEH_NO | This variable is in each Vehicle and Person record. Together with the State Case, ST_CASE, it forms a unique identifier for the vehicle within the year. VEH_NO and ST_CASE ARE OFTEN used together as a key, when a Vehicle file and Person file, are merged, from the same year. This is done to insure that the correct occupants are placed in the proper vehicle. ST_CASE is used by itself in a merge when non-occupants must be counted, in this case there is no information about the vehicle. | |
| MAK_MOD | Vehicle Make and Model | P1512: Vehicle make and model are free form text; usually only used in HazMat messages for trucks only CVIEW: "MODEL" VARCHAR2(3); "MAKE" VARCHAR2(10) |
| IMPACTS | Impact Type | |
| VIN_BT | Vin Body Type: the VINA program that decodes these data, partitions vehicles into three classes, passenger vehicles, trucks and motorcycles. | |
| SER_TR | Vin Chassis-Truck: this is a code that identifies the type of truck, i.e. body style. This material comes from analysis of the Vehicle Identification Number (VIN). | CVIEW: "VIN" VARCHAR2(30) |
| VIOLATE1 or VIOLATE2 or VIOLATE3 | Violation Type | |
| WGTCD_TR | Truck Weight | CVIEW: "GVW" Number (8,0) Near Match NTCIP DCM: "dcmGrossVehicleWeight" Integer (0..16711425) Near Match |
| AGE | Driver Age | |
| ALC_DET | Alcohol detection test type | |
| ALC_RES | Actual result of alcohol (BAC) test. A value of 10 is a BAC of 0.10. The BAC is expressed as grams/100ml% or a clinical evaluation of the same. | |
| DRINKING | Drunk driving? | |
| DEATH_DA | Day of the month of the death | |
| DEATH_MO | Month of the death | |
| DEATH_YR | Last two digits of the year, e.g. 92 for 1992. Note that a person can die the year after the crash year. | |
| CERT_NO | Death Certificate Number | |
| CERT_NO_1 | First four digits is the GSA City code where the death occurred | |
| CERT_NO_5 | Digits 5 and 6 is the GSA State Code | |
| CERT_NO_7 | Last 6 digits is the sequence Number (as assigned by State Vital Statistics Department) | |
| DRUGRES1, or DRUGRES2, or DRUGRES3 | Drug Test Results | |
| DRUGTST1 or DRUGTST2 or DRUGTST3 | Drug Test Type | |
| DRUGS | Police Reported Drug Involvement | |
| DRUG_DET | Method of Other Drug Determination by Police | |
| EJECTION | Any persons ejected from the vehicle during crash | |
| EJ_PATH | Path of the ejected persons from the vehicle | |
| EXTRICAT | Any persons extricated from the vehicle during crash | |
| WORK_INJ | Injured from work? | |
| HOSPITAL | Hospitalized? | P1512: |
| INJ_SEV | Injury Severity | TMDD: "Incident Severity" indicates overall severity of the crash in terms of operational impacts, not injuries to humans P1512: Overall crash severity only |
| LOCATION | Crash location | TMDD: Location of incident is identified by coordinates and position relative to cross-streets. |
| MCYCL_DS | Motorcycle Displacement - This is the Cubic Centimeter piston bore. This is a numeric value (example, Honda 160 cc engine). | |
| N_MOT_NO | Non-Motorist Striking Vehicle Number, applies only to non-motorists and reflects the vehicle who made contact with the non-motorist | |
| PER_NO | Person Number: Each occupant of the vehicle is numbered. The numbers are consecutive, beginning with 01. | |
| PER_TYP | Person involved in crash type | |
| P_CF1 or P_CF2 or P_CF3 | Person collision factor | |
| REST_USE | Restraints or protective gears used | |
| AIR_BAG | Air Bag deployment | |
| SEAT_POS | Seating position | |
| SEX | Gender | |
| DEATH_HR | DEATH_HR and DEATH_MN are the times, hours and minutes, of the death. | |
| LAG_HRS | LAG_HRS and LAG_MINS are computed as the time, hours and minutes, between the time of the crash and the time of death. | |
| DEATH_MN | DEATH_HR and DEATH_MN are the times, hours and minutes, of the death. | |
| LAG_MINS | LAG_HRS and LAG_MINS are computed as the time, hours and minutes, between the time of the crash and the time of death. | |
| DEATH_TM | Four digits DEATH_HR followed by DEATH_MN, e.g. 0643 for 6:43 a.m. | |
| VIN_WGT | Auto Weight | CVIEW: "GVW" Number (8,0) Near Match NTCIP DCM: "dcmGrossVehicleWegiht" Integer (0..16711425) Near Match |
| WHLBS_LG | The longest wheelbase respectively for the manufactured model as determined by the VINA program for automobiles made since 1966. | NTCIP DCM: "dcmVehWheelBase" Integer (0..65535) Near Match |
| WHLBS_SH | The shortest wheelbase respectively for the manufactured model as determined by the VINA program for automobiles made since 1966. |
