Roughness surveys should be done by driving
the vehicle at a constant speed. If it is necessary to operate at a range of speeds
different calibration equations should be established to cover this range. The ROMDAS
software will apply the appropriate equation given the survey speed.
It is useful to run a regular check of the data. This consists of
weekly running over a section of road measured previously and confirming that the results
are not markedly different. The vehicle should also be recalibrated at 5-10,000 km
intervals.
Roughness data are collected over what is called a sampling interval.
This is typically 100 m, although it can be anywhere from 50 to 5000 m. The roughness is
summed over the sampling interval and a single value is given, for example 120 counts/100
m. At the end of the interval the roughness is reset to 0 and summed for the next
interval. When the data are converted to IRI the units are adjusted to a per km basis.
Instead of using regular intervals such as 100 m the operator can optionally manually
define the end of the sampling interval. This is commonly done when there are km markers
and the roughness between markers is of interest, but it is not the recommended practice.
When measuring two-lane highways it is often necessary to measure both
lanes. When completing a survey the user is offered the option of doing the Other Side.
This tells the software that it is a two-lane highway and the sampling intervals are to be
correlated. This means that the first sampling interval in the opposite direction is a
shorter interval than usual, resulting in the same set of sampling intervals (see the (b)
below). If this was not done the top figure (a) would arise. This feature is used when
there are no LRP resets.

In executing a roughness survey one of the most difficult components is
the programming of the survey. It is often necessary to interrupt what should be a
continuous run to measure roads running off from the primary survey route. This can be
easily handled with ROMDAS, and an example of this is shown in the figure below.

The operators should terminate the main survey at an LRP or other
roadside feature which will be easy to return to (Run 1). It is generally recommended that
this be past the point where the other surveys are to commence. They may then execute the
other surveys (Run 2 and Run 3). Returning to where they ended the previous survey they
enter the same Road ID as was used previously. They will then be given the option to Continue
the previous run. The data collection will be started where they left off and, once
processed, both components of Run 1 will be integrated.
It is not always practical to run a separate LRP survey before the
roughness survey. If this is the case, you can create the LRPs during the roughness survey
by using the LRP Define option. At each LRP the operator presses the Insert key and
is then prompted to type in the name of the LRP. Optionally, the LRPs can be predefined
and a short form keycode (eg 100 for km 100) can be used. If defining LRPs the operator
can end the survey and define the final LRP at the same point by pressing the F9
key.
It is sometimes desirable not to measure the roughness over some
sections, for example if the survey comes across a pavement which is being reconstructed.
In this instance by pressing the F5 key the roughness meter measurements will be
turned off until the key is pressed again. The software will optionally calculate the Equivalent
Roughness which is simply the roughness over the interval which was measured, factored
up to cover the whole interval.
If it is likely that the vehicle will travel at low speeds, either due
to congestion or having to stop at LRPs for measurements/photos, then the option to use
equivalent roughnesses at low speeds should be used. This sees the roughness
measurements adjusted when the speed is below a user-specified minimum speed based on
measurements at higher speeds.
One of the greatest problems encountered when conducting annual surveys
is in reconciling the survey lengths. This is because in spite of the utmost care, the
measured lengths will never be identical in two successive surveys. In year 1 the road may
be 41.153 km long; in year 2 it will be 41.168 km while in year 3 it may be 40.952 km.
Since relational database systems expect all roads to have the same start and end points
it is necessary to "rubber band" the data so that they match. ROMDAS is
designed to do this "rubber banding" in real time. When the data are reset at
the LRP the measured distance is replaced with the distance in the LRP file and the data
adjusted accordingly. Thus, every year every survey will have the same start and end
points as the LRP survey thereby eliminating any post-processing of the data.