Traffic Table
Contains information about the vehicle passes, including start and end times for each load event, gear configuration, applied loads (actual), and wander position. A summary of daily traffic applied to the CC5 test items is available in the Traffic Summary Table.
|
TrafficID
|
Unique number assigned to identify each vehicle passing event. The numbers from 1 to 12540 refer to the north side trafficking, and numbers ranging from 12541 to 54012 refer to south side trafficking. North side detail includes 1 to 12540 for LFC1NW, LFC1NE, LFC2NW, LFC2NE, LFC3N, and LFC4N. Further detail of the south side includes 12541 to 32430 for LFC3S and LFC4S; 32431 to 41076 for LFC2SW and LFC2SE; 41077 to 54012 for LFC1SW and LFC1SE. |
|
EventNo
|
A number assigned to a traffic event. An event is defined as a movement of the vehicle with loads.
|
|
SequenceNo
|
Position within the wander sequence corresponding to event EventNo. The wander pattern consists of wander sequences 1 through 66. (Note: The wander sequence number must agree with the track number as given in table Wander.)
|
|
WanderID
|
Number assigned to identify the north side and south side wander patterns. Numbers 1 to 66 indicate the north side test items and 67 to 132 are used for the south side test items respectively. |
|
EventStartTime
|
Date and time of the start of a traffic event. Dates are given in the format MM/DD/YYYY. Time is local time (New Jersey, USA).
|
|
EventEndTime
|
Date and time of the end of a traffic event. Dates are given in the format MM/DD/YYYY. Time is local time (New Jersey, USA).
|
|
Gearparameter
|
Gear configuration for event EventNo. Refer to table Gear. |
|
TestItem
|
Test item(s) loaded during event EventNo. |
|
AvgModuleLoads_LB
|
Average wheel loads corresponding to traffic event EventNo (lbs.). Values are given as a string of 10 comma-delineated values as follows: Carriage 1 Module 1, Carriage 1 Module2, …, Carriage 1 Module 5, Carriage 2 Module 1, Carriage 2 Module 2, …, Carriage 2 Module 5. For north side events, different sets of loads were applied to six different test items (see Test Item column). In such cases, six comma delineated strings may be given, separated by a semicolon. The first string applies to test item LFC1NW, the second string to test item LFC1NE, the third string to test item LFC2NW, the fourth string to test item LFC2NE, the fifth string to test item LFC3N, and the sixth string to test item LFC4N. For south side 7/12/2010 to 8/11/2010 events, different sets of loads were applied to two different test items (see Test Item column). In such cases, two comma delineated strings may be given, separated by a semicolon. The first string applies to test item LFC1SW and the second string to test item LFC1SE. . For south side 9/15/2010 to 10/26/2012 events, different sets of loads were applied to two different test items (see Test Item column). The first string applies to test item LFC3S and the second string to test item LFC4S. For south side 8/21/2012 to 10/26/2012 events, different sets of loads were applied to two different test items (see Test Item column). The first string applies to test item LFC2SW and the second string to test item LFC2SE.
|
|
Comment
|
Comments
|
Traffic Summary
Select Traffic Summary Link to view Traffic Summary Tables.
Test Strip
Processed Data-1 contains data on 114 passes from 3/6/2007
CL-Data contains data on 198 passes from 3/28/2007 and 4/3/2007
North and South contains data on 264 passes from 3/1, 3/2, 3/5, and 3/12/2007