Naturalistic Driving Study: Linking the Study Data to the Roadway Information Database (2015)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

20 SHRP 2 Manual Route Matching Protocol Software needed: Data/Video/Map viewer, spreadsheet (VTTI’s Hawkeye data viewer and Microsoft Excel were used for this work). Collections: NEW SHRP 2. The goal of this task is to review files in Hawkeye from the NEW SHRP 2 data collection to provide sequential names of roads traveled during a trip and also to categorize problems if any part of the trip is not clear on the Hawkeye map. This document provides guidance and definitions required for completing these analyses consistently. Please bring any questions to the data reduction coordinator as soon as possible so that consistency and accuracy can be maintained. Reduction Log 1. Locate SHRP 2 Linking QA reduction.xls. 2. In the first worksheet (named “1000 files”), find the first row that has not been marked by a reviewer. Enter your name in that row under Reviewer, and proceed to Hawkeye to open the file. Setting Up Hawkeye 1. Load Hawkeye. 2. Load the NEW SHRP 2 collection. 3. Copy and paste the File_ID from the Excel log for the file you have signed out into the Trip field in Hawkeye. Click on Enter or Load Trip. 4. Open the Map (found in the Dashboards tab). a. Enlarge the map if necessary. b. Zoom in and out by using the scroller on the mouse and move the map by dragging. 5. Open the Gyro_Z variable graph (found in the Variables menu, in the IMU module). A p p e n d i x A

21 Reduction Spreadsheet 1. Open the SHRP 2 Linking QA Reduction spreadsheet. 2. Create a new sheet for the current file by copying the worksheet named Template. Rename this worksheet with the File_ID. Begin Data File Route Assessment • When the play button is clicked and the trip data collection begins, a green dot will show up on the map, indicating what should be the vehicle location. There should also be a dotted path (usually blue or purple), showing the vehicle’s entire travel path. At times the green dot will not be on the actual (dotted) travel path when the file starts playing. The data reduction will begin when the green dot begins to move along the dotted path. • The goal of the assessment is to record each road that the vehicle travels on, as indicated by the map travel path (green dot moving along the dotted path), using approximate timestamps for time on each road. If the travel path is not actu- ally on a road, this should also be noted by timestamp duration, along with a categorization of the nature of path devia- tion (described below). To save time and advance the green vehicle indicator to the next road, double-click on the next location on the Gyro_Z graph where there is a substantial jump in value (this should indicate a notable change in direction). • Record the File_ID in each completed row. • Record the sequence order of each road in the Road Sequence column and the corresponding name of each road in the column Road Name. 44 Add more values or remove excess in the Road Sequence column as necessary. 44 Record road name exactly as it is written on the map. For special unnamed road configurations, code as applicable (e.g., On ramp, Off ramp, Cloverleaf, Parking lot, Driveway). Otherwise, if the road name is not indicated on the map, code as “No name.” 44 If there is no path or you cannot tell what road the path corresponds to, enter “none” for Road Name. 44 If there are questions about the path, videos may be opened for clarification. • To indicate whether there are cases in which the path is not on a road segment for any period, code each segment using the following categories (provided in a dropdown menu in the GPS Problems column): 44 None. There are no problems with correspondence between the indicated travel path and the roads presented on the map. Points indicated on dotted travel path might not be completely on the road segment, but are less than a road width from the actual roadway (Road Name will be entered). 44 Slightly displaced. Points indicated on dotted travel path are not on the road segment, and are generally between one and two road widths from the actual roadway (points follow the general travel direction of the road but are slightly shifted as

22 a unit) (Road Name will be entered if it is known; “None” if it is not). The following figure shows an example of a portion of a travel path that is slightly displaced. 44 Moderately displaced. Points indicated on dotted travel path are not on the road segment and are generally more than two but less than five road widths from the actual roadway (points follow the general travel direction of the road but are moderately shifted as a unit) (Road Name will be entered if it is known; “None” if it is not). The following figure shows an example of a portion of a travel path that is moderately displaced.

23 44 Extremely displaced. Points indicated on dotted travel path are not on the road segment and are generally five or more road widths from the actual roadway (points follow the general travel direction of the road but are extremely shifted as a unit) (Road Name will be entered if it is known; “None” if it is not). In the following figure, the portion between points 2089 and 2104 illustrates a travel path that is extremely displaced. 44 Missing. There are no points on the map indicating travel path; there is a gap in the actual travel path (“None” will be entered for Road Name). 44 Poor geometry. Either the travel path points are scattered (they do not follow a route and look haphazard or clustered), or they indicate a travel path not related to the actual roadway (e.g., a diagonal path cutting across horizontal streets), or the green dot indicating vehicle position has become stationary (but vehicle is actually still moving, seen in video) (“None” will be entered for Road Name). • If a particular road segment contains a travel path with poor points, but not all for the same reason, add another row to the spreadsheet with a duplicate Road Sequence number and Road Name to indicate each problem and the timestamps for which that problem occurs. Also enter duplicate rows if part of the segment has no problems and part does have problems. See the following example. Road Sequence Road Name Timestamp Start Timestamp End GPS Problems Comments 1 Main Street 10000 50000 None 2 Elm Avenue 50001 70000 Slightly displaced 2 Elm Avenue 70001 100000 Missing 2 Elm Avenue 100001 400000 None 3 Second Street 400001 500000 Poor geometry 3 Second Street 500001 700000 None 4 Third Street 700001 900000 None • If it appears that there is no path to record for a trip (no GPS points to indicate road segments), open the graphs for Latitude and Longitude (both in the Collected>Head_Unit module) to be sure that GPS points do not appear at a point later in the file. If there are any points at all from which road segments can be determined, record those road segments with applicable road names. • If there are any situations that make reduction difficult, provide explanation in the Comments column.