1. Weigh-in-Motion Data

The Weigh-in-Motion (WIM) Systems can collect data from different kind of devices, like Automatic License Plate Recognition (ALPR), weigh sensors (piezoelectric quartz, piezoelectric ceramic, piezoelectric polymer, etc), temperature sensors, etc. Additionally, the WIM Systems can produce a variety kind of data, like weigh data, classification data, violation information, some analytic reports, etc.

In this paper, it will be treat some data structures and caution about these data, presented on the main WIM literatures.

The goal of this paper is to collect the main data structure and file structure to standardise the OpenWIM input and output data. The OpenWIM is a open science project for weigh-in-motion research. Its goal is to be a standard platform to be used for WIM researchers in their investigation and to be a collaborative repository about this subject.

In the final report of COST 323 (Jacob, OBrien and Jehaes, 2002), in the Section 12 and Appendix IV, some aspects about data storage, processing, transmission and standard format. This information will be the main guideline to this study.

Here will be presentated some recommendations about the data and specifications used to cleaning the data before analysis stage (Enright and OBrien, 2011).

The data that will be treated here is:

  • raw sensors data;
  • estimated data, like speed, gross vehicle weight, axles weight, axles group weight, distance between axles, vehicle classification, etc;
  • environment data, like temperature, humidity, traffic condition, etc;
  • statistic data, like relative errors, etc;

The general recommendations is treated in section 1.1, covering the general aspects of data and file formats.

The output data standard layout from WIM systems, tipically has some attributes, treated on the section 1.2.

The section 1.3 has some recommendations to cleaning outpu data.

And, finally, the section 1.4 has the conclusion of this study.

1.1 General Recommendations

To avoid any confusion while reading the output data files or using these data, it is important to consider some recommendations about the data and files, add some information to improve the completeness of the output data and apply some organization to this output (Jacob, OBrien and Jehaes, 2002).

Recommendations about the data:

  • the time should registered in hh:mm:ss:cc, up to hundreds of second;
  • temperature must be in $^{\circ}$C;
  • velocity must be in km/h;
  • all the weights and loads are given in kg, but with a scale division of 100 kg according to the sensitivity and accuracy of the system.

The division scales should be, according to the accuracy classes (Jacob, OBrien and Jehaes, 2002):

  • Class A: 20 kg;
  • Class B+: 50 kg;
  • Class B: 100 kg;
  • Class C: 200 kg;
  • Class D+(20): 200 to 500 kg;
  • Class D: 500 kg.

Recommendations about the file structure:

  • use explicit heading columns;
  • use units, and, as far as possible, S.I. (System International) must be used;
  • use a data file in a spreadsheet widly distributed format or a tabulated ASCII format, like CSV;

Some information should be present in the output data file to be more completed and offer some detail to future analysis:

  • environmental conditions during the measurement, like weather, traffic, etc;
  • calibration coefficient periodically computed by the system, in case of an automatic self-calibration;
  • reports about any eventual breakdown, failure or maintenace operation of WIM system.

The data package should have some identification information about the WIM site:

  • road identification;
  • accurate location of the WIM system,
  • type of sensor and of electronics used;
  • date of manufacture and of installation of the WIM system;
  • date of the last calibration;
  • period of measurement;
  • owner of the WIM system and contact person in charge of the data collection.

To apply some organization to the output data, the first columns should be data common to all vehicle and, the last ones, should be columns when can have variation in the number of axles per vehicle (like axles load, distance between axles, etc).

1.2 Raw Sensor Data

Basically, the first main input data is the raw data sensors. These data can be acquired using a data acquisition device (DAQ) through the analog channels (weigh sensor, temperature sensors, etc) and the digital channels (i.e., inductive loops).

The three more wideley piezo-eletric weigh sensors used are piezo-ceramic, piezo-polymer and piezo-electric (Jiang, 2009).

It is essencial to store the raw sensor data during the investigation about the input signal and to validate weigh methods. In COST 323 (Jacob, OBrien and Jehaes, 2002), was not found any description about the raw data layout file. By the way, this data can be represented by a matrix using as a first column a index with time instant, it represented by microseconds in floating point format, followed by other columns representing each sensor data (in table 1, a exemple of sensor data structure).

1.3 Estimated Data

The WIM data recorded per vehicle are typically (Enright and OBrien, 2011):

  • vehicle number (unique identifier);
  • ƒdate;
  • ƒtime (when leading axle passes sensor);
  • ƒspeed;
  • ƒlane;
  • ƒcategory (type of truck);
  • ƒtotal vehicle length (measured by inductive loop detectors);
  • ƒgross vehicle weight (GVW);
  • ƒindividual Axle loads, the sum of which is the GVW;
  • ƒwheelbase;
  • ƒaxle spacings, the sum of which is the wheelbase.

In (Qu, Lee and Huang, 1997) is showed a layout structure used in their research. Where, in the file name standard, these rules were used:

  • unique file name;
  • using the “Dsssmmdd.yy” format, where:
    • D: Raw data file designator;
    • sss: Site number, (i.e., 001 for site 1);
    • mm: Month;
    • dd: Day;
    • .: Extension separator;
    • yy: Year.

About the ASCII data file format, these rules were used:

  • After the data file is converted to ASCII code, the file name is changed from “Dssmdd.yy” to “Vsssmmdd.yy”;
  • An ASCII data file is composed of strings like: 2,3,24,0,0,26,63,28,12,1.2,1.2,12,0.8,0.7,9.4; where:
    • 2: Lane used by vehicle (i.e., 1 for right lane, 2 for left lane)
    • 3:Month
    • 24: Day
    • 0: Hour
    • 0: Minute
    • 26: Second
    • 63: Speed of first axle (mi/h)
    • 28: Time, used to calculate lateral position (ms)
    • 12: Infrared blocked time for the first axle (ms)
    • 1.2: Load of the left wheel of the first axle (kip)
    • 1.2: Load of the right wheel of the first axle (kip)
    • 12: Infrared blocked time for the second axle (ms)
    • 0.8: Load of the left wheel of the second axle (kip)
    • 0.3: Load of the right wheel of the second axle (kip)
    • 9.4: Axle spacing between the first and second axle (ft)

1.4 Environment Data

Piezo-ceramic and piezo-polymer sensors are sensible to temperature influence and, for this reason, a temperature sensors is needed to apply some correction method (Burnos, 2008).

1.5 Data Cleaning

Some data cleaning criteria can be used to eliminate some undesireble data in statistical analysis. For example, in (Elkins and Higgins, 2008) is used these criteria:

  • misplaced characters, such as a letter where a number should be or a number where aletter should be;
  • an individual axle weight greater than 50 kips;
  • a speed less than 10 mph;
  • a speed greater than 99 mph;
  • a length greater than 200 ft;
  • the sum of the axle spacings greater than the length of the truck;
  • the sum of the axle spacings less than 7 ft;
  • the first axle spacing less than 5 ft.

1.6 Statistical Data

1.7 Discussions

1.8 Conclusions

1.9 Appendix


In [28]:
from IPython.display import display, HTML
import pandas as pd
import numpy as np
import io

data = pd.DataFrame({
    'A1_v': np.random.random(10), 
    'A2_v': np.random.random(10),
    'D1_v': np.random.random(10)    
})
data.index /= 5000
data.index.name = 'TIME_ss'

buffer = io.StringIO()

data.to_csv(buffer, sep=';')
buffer.seek(0)

print(buffer.read())
print('20151231')


TIME_ss;A1_v;A2_v;D1_v
0.0;0.6532256560486067;0.7825516687745769;0.13909638756553477
0.0002;0.012080131007545125;0.25936644956461063;0.6130571599469344
0.0004;0.49806121790972024;0.04532767667405424;0.11353139841604765
0.0006;0.376994232179206;0.1334437849658927;0.4586038409839722
0.0008;0.9194422502608218;0.04829203659282266;0.2625550204900562
0.001;0.34844307878738023;0.7954767095508017;0.405740947371785
0.0012;0.6504015250336552;0.622537816694311;0.4118297153073377
0.0014;0.4335708469780257;0.6757066126848909;0.5561231772033712
0.0016;0.6029603198010272;0.969571027216345;0.37780169632813
0.0018;0.4743284965480635;0.5762469417927556;0.7139057143768299

References

[^](#ref-3) [^](#ref-5) [^](#ref-6) [^](#ref-8) Jacob, Bernard and OBrien, EJ and Jehaes, S. 2002. Weigh-in-Motion of Road Vehicles: Final Report of the COST 323 Action.

[^](#ref-4) [^](#ref-9) Enright, Bernard and OBrien, Eugene J. 2011. Cleaning weigh-in-motion data: Techniques and recommendations.

[^](#ref-7) Jiang, Xiaohua. 2009. Improvements in Piezoelectric Sensors and WIM Data Collection Technology.

[^](#ref-10) Qu, Tongbin and Lee, Clyde E and Huang, Liren. 1997. Traffic-load forecasting using weigh-in-motion data.

[^](#ref-11) Burnos, Piotr. 2008. Auto-calibration and temperature correction of WIM systems.

[^](#ref-12) Elkins, Lori and Higgins, Christopher. 2008. Development of truck axle Spectra from Oregon Weigh-in-motion Data for Use in Pavement Design and Analysis.