Search the CC3 Database
Test items are trafficked using a defined wander pattern, with the carriage located at discrete lateral positions, or tracks. The Track table supplies the exact value of the carriage position relative to the center line for each track number. Refer to the diagram under “Wander Pattern” to better visualize the track locations.
The Wander table lists the loading sequence making up a complete wander pattern. Each wander sequence number is associated with a track position from the Track table.
Returns the Gear table, which contains information about the configured wheel loads.
Returns the the TestItem table, which contains engineering data about the CC-3 pavement test items (layer materials and thicknesses).
Click on the Traffic link below to search Traffic data for a specific date.
The MUX table stores information about the static sensors, including sensor type and location. (MUX refers to the multiplexer units, which acquire the static sensor data.)
The FWD table stores information about flexible pavement section, loads and reading for specific locations. A falling weight deflectometer (FWD) is a testing device used used to estimate pavement structural capacity.
Static Sensor Data
Static sensors collect temperature and moisture data on an hourly basis. Click on the Static Sensor Data link below to search static sensor data for a specific date.
SPU (Signal Processing Units)
The SPU table stores information about the dynamic sensors, including sensor type and location.
Dynamic Sensor Data
Dynamic sensors are triggered by movements of the load vehicle. Therefore, dynamic sensor responses are collected only on days when the load vehicle is in operation. Dynamic sensor records are available for most passes of the load vehicle on the test items. However some gaps in the data are known to exist. Click on the Dynamic Sensor Data link below to search the data for a particular dynamic sensor.
Advanced users can query the CC3 database using Structured Query Language (SQL). Note that data are read-only. Only “select” queries will be recognized by the database. Refer to the table map and definitions when formulating queries.