Naturalistic Driving Study: Linking the Study Data to the Roadway Information Database (2015) / Chapter Skim
Currently Skimming:
Pages 12-17
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 12... ...
12 Findings and Applications As each file was processed, the results of the matching solution were written to a database. This database is referred to as the Linking Table.
|
From page 13... ...
13 different incident types. Attributes that can be joined include Highway Safety Information System (HSIS)
|
From page 14... ...
14 Figure 3.2. Raleigh/Durham, NC–area map indicating links and file count (green 5 low, red 5 high)
|
From page 15... ...
15 Figure 3.4. Seattle, WA–area map indicating links and file count (green 5 low, red 5 high)
|
From page 16... ...
16 Figure 3.6. State College, PA–area map indicating links and file count (green 5 low, red 5 high)
|
From page 17... ...
17 GPS data were never present or never reached the accuracy criteria, the file was too short for GPS to begin reporting, the vehicle was started but never moved, out-of-memory errors occurred for some very long trips, for some reason a succession of road links could not be established for the file, and so on. Percentage of Time Within Files Matched to Roads For the files that were processed, an analysis was conducted to determine what percentage of the driving time in each file was matched to roadways by the algorithm.
|
Key Terms
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.