Skip to main content

Feasibility of Using In-Vehicle Video Data to Explore How to Modify Driver Behavior That Causes Nonrecurring Congestion (2011) / Chapter Skim
Currently Skimming:


Pages 42-45

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 42...
... Once events of interest are identified (e.g., crashes and near crashes) , the data reduction process begins.
Read the entire page →
From page 43...
... Conflicts are occasions in which a crash, near crash, incident, or conflict happens. Nonconflicts are occasions in which the trigger values satisfy the thresholds but the driver makes a maneuver and is in complete control of the vehicle.
Read the entire page →
From page 44...
... 44Figure 5.1. Quality assurance and quality control flowchart at VTTI.
Read the entire page →
From page 45...
... Similarly, a higher trigger value will result in a higher percentage of valid events but will generate some omissions. A careful examination of threshold values by experts is highly recommended before data reduction starts.
Read the entire page →

Key Terms

  • trigger values
  • baseline epoch
  • baseline epochs
  • subject vehicle
  • near crashes

  • travel time
  • valid events
  • near crash
  • lane change
  • aggressive driving

  • driver comment
  • variables included
  • comment button
  • trigger value
  • invalid events

  • traffic density
  • data reduction
  • yaw rate
  • false alarm
  • time reliability


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.