Coto Coto: Guidelines For Network Level Measurement of Road Roughness
Coto Coto: Guidelines For Network Level Measurement of Road Roughness
COTO
Committee of Transport
Officials
Version 1.0
April 2007
Roughness Measurement Guidelines
Acknowledgements
These guidelines were compiled under auspices of the COTO Road Network Management Systems
(RNMS) Committee. The authors wish to thank the members of the committee for their guidance and
management of the project. In particular, the authors would like to thank Mr Mervyn Henderson of the
Western Cape Provincial Administration (WCPA) for steering and guiding the project. Mr Louw
Kannemeyer of the South African National Roads Agency (SANRAL) provided excellent technical
guidance and valuable suggestions throughout. The following persons are also thanked for their
contributions :
Disclaimer
This document provides guidance for the planning and execution of road network roughness
measurement. The document is neither a specification nor a manual for network level surveillance in
general. The views and recommendations provided are based on opinions and methodologies
documented in available literature, and on the experience of the committee and the authors. The
guidelines do not necessarily cover the entire spectrum of knowledge and application related to road
roughness measurement. The information contained in this document is given in good faith. No
responsibility will be accepted by the Committee or the authors for any damage or adverse
consequences arising from the use of this document.
Roughness Measurement Guidelines
Table of Contents
7. REFERENCES ........................................................................................................................ 43
8. GLOSSARY............................................................................................................................. 45
List of Figures
List of Tables
Road roughness, or roughness, is the term used The road profile is measured along a fixed line in
to describe the relative degree of comfort or the direction of vehicle travel, as shown in
discomfort experienced by a road user when Figure 1.1. This figure also shows the difference
using a road. Roughness is one of the most between the lateral profile and the longitudinal
important aspects of a road network to monitor, profile.
since it directly relates to the experience of road
The transverse profile is measured in a direction
users. As such, roughness serves as a collective
perpendicular to the direction of vehicle
measure of several aspects of road condition,
movement, while the longitudinal profile is
including rutting, cracking, potholes, local failures
measured in the direction of movement.
and undulations.
Roughness is primarily concerned with the
The term riding quality is often used instead of longitudinal profile while transverse profiles are
roughness. The term roughness will be used in mainly used to assess rutting.
these guidelines, as it is used most often in the
Key concepts related to the measurement of a
international context.
road profile include the following (illustrated in 0
and Figure 1.2):
1.1. THE ROAD PROFILE
• Along any line on the road, there exists a
An uncomfortable ride, or high degree of “true profile” (top graph in Figure 1.2). The
roughness, is a result of variations in surface true profile is approximated by the measured
elevation along the wheelpaths of a road. Whilst profile, which is a profile measured at a
there are many approaches to measuring or predetermined sampling interval (middle
quantifying the degree of discomfort a road user graph in Figure 1.2).
will experience, the cause of such roughness will
always be variations in surface elevation. The • The sampling interval is the spacing between
most direct method of quantifying the variations measurement points along the line of
in surface elevations is by measuring the profile measurement. Most modern profiling devices
of the road surface. can sample elevations at intervals less than
250 mm when moving at speeds of up to
120 km/h.
Direction of movement
Transverse Profile
Elevation
Longitudinal Profile
Elevation
TRUE PROFILE nt
Alignme
Vertical
Elevation (mm)
SAMPLED PROFILE
Transducer
Suspension Stroke
PROFILOMETRIC METHODS
Processing Output
Measured Road Profile (“the Input”)
Mathematical Roughness
Processing/Filtering Indicator
system (typically
IRI)
Physical
Suspension Mathematical simulation of
System physical suspension system
Figure 1-4 Aspects of the IRI Calculation (after Sayers and Karamihas, 1988)
10 60 km/h
8
Rough Unpaved
6 80 km/h Roads
4 Maintained Unpaved
100 km/h Roads
Older or Damaged Paved Roads
2 New Paved Roads
> 100 km/h
Superhighways & Airport Runways
0
Figure 1-5 The IRI Interpretation Scale
Reference
Height elevation and
relative to longitudinal
instrument reference
height
Figure 2-5 Operation of the Precision Rod and Level (after Sayers and Karamihas, 1998)
• Survey procedures
• Contract quality plan
• Reporting and data reporting format
Component calibration should specify the System validation for profiling devices should be
requirements for calibration of system performed to ensure that the measurement
components, and should address the following methodology (which includes device operation,
issues: data acquisition, operation and output) will
provide roughness data in the correct format, and
• Where relevant, the specifications may to the specified quality and consistency. Aspects
require that the contractor produce to be covered in the specifications for system
calibration certificates that are current, and validation include the following:
that are preferably issued by an accredited
body. • Pre-validation report: before validation
procedures start, the contactor must provide
• If components are to be recalibrated during a report to ensure that calibration
the course of the contract, the rules or requirements are met and that the equipment
conditions of recalibration should be specifications are met.
specified.
• Aspects to be considered as part of the
• The components for which proof of validation should be clearly specified. These
calibration is required should be clearly should include roughness data, GPS
specified. equipment, distance measurement, etc.
System calibration for response type devices Details of these requirements are provided in
should be performed to ensure that the Sections 4 and 5.
measurement device as well as the data
• Personnel: for profiling surveys, the training
acquisition system are working properly, and to
and experience of the operator can have a
adjust the device output so that it is adequately
significant influence on the roughness
correlated to known values over a range of
results. Validations should ideally be
roughness values. Aspects to be covered in the
performed for each vehicle operator.
specifications for system calibration include the
following: • Multiple vehicles: the specifications should
specify validation procedures if the survey is
• The number and type of calibration sites
to use more than one vehicle.
should be specified. These sites should
preferably be located and measured (using a • Validation procedures should be specified in
Class 1 profiling device) by the network case of vehicle breakdown.
agency.
• Statistical methods for processing validation
• The length of the calibration sections should data should be clearly specified, and a
be specified (see Section 3.4 for details). processing algorithm or spreadsheet should
ideally be provided.
• The calibration methodology and criteria
should be specified (see Section 3.4 for • Acceptance criteria should be specified to
details). define the limits for a successful validation.
• Details of the calibration procedure, such as • The length of time over which a validation will
demarcation of sections, measurement be valid should be specified.
speeds, and data to be gathered should be
specified. • If the contractor is to compile a validation
report, then the reporting requirements
should be specified.
For each report type, the specifications should • Section lengths should be at least 200 m
state the submission deadlines, report formats, long, but should preferably be between 300
minimum requirements and general format. For and 500 m long. All sections should have the
calibration reports, it is important to ensure that same length.
vehicle configuration aspects (Section 6.1) be • The calibration sections should be selected
documented. Some of the aspects relating to the so that there is at least one section in each of
bulk roughness data and summary report are the roughness ranges shown in Table 3.4.
discussed in Section 6.3. The sites should also be selected so that
there are approximately an even proportion
Other Aspects of sections in each roughness range.
The data delivery time and deadlines for all other • Each calibration section should have a
deliverables should be specified. Where relatively uniform roughness over its length
applicable, bonus and penalty schemes can be as well as over the 50 m preceding the start
included. Most surveillance devices should be of the section.
able to provide the data in a processed format
immediately after, or within a short period after • The sections should preferably be on straight
measurement. It is recommended that delays (tangent) sections of road. The sections do
between the time of survey and data delivery be not need to be level, but there should be no
minimized to enable better monitoring of the significant change in grade within or before
measurement and processing tasks. the section.
The contract specifications should also address • The calibration sections should have different
other aspects which are part of the network surfacing types, representing the types of
agency’s directives and which may be affected by surfacing frequently found on the network.
the surveillance contract. These aspects include:
• Required standards for traffic management
and safety Important!
• Aspects related to occupational health and Since profiler components are calibrated in the
safety for operators and the public factory, these devices are never calibrated as
• Aspects related to environmental protection part of network survey operations, but only
validated (i.e. correct operation is validated in
For these aspects, it would often suffice to the field). Response type devices, on the other
specify a requirement for the contractor to adhere hand, are calibrated as part of the survey
to the relevant standards and codes of practice. process. For conciseness, however, the test
sections on which such validation and
calibration are performed will be referred to as
calibration sections in these guidelines.
3.4. CALIBRATION SECTION
REQUIREMENTS For practical reasons, it is also recommended
that the calibration sites be located relatively
The identification and survey of calibration close to the centre of operations, and that the
sections should be done before any surveying is sites selected sites are not subject to rapid
started on the network. Ideally, these sections deterioration. If a calibration site is rehabilitated,
should be selected and profiled by the network another site with a similar roughness range
agency, or by a contractor other than the one should be selected and profiled.
responsible for the actual survey.
Suggested
Check For Parameter Acceptance Scope of Calculations
Criterion
Absolute difference 80% of
Check for each 100 m segment
Error of IRI over between measured and values to be
at each speed and on each
100 m segments benchmark IRI over 100 less than
validation section.
m for each repeat run 8%
Bias and R2 of linear regression > 0,95 Check for the combined
Variability in Standard Error of Linear validation data set which
< 0,3
measured IRI Regression includes all repeat runs and all
over 100 m Slope of linear Between 0,9 measurement speeds. In this
segments regression and 1,1 data set, each data point
(all parameters Intercept of linear Between represents a pair of measured
are calculated regression -0,1 and 0,1 (X-axis) and benchmark (Y-axis)
from a linear 95% Confidence interval values over a 100 m segment of
regression Should each calibration section. There
of Slope of linear
between average bracket 1,0 should be a data point for each
regression
100 m IRI from 100 m segment of each
repeat runs and 95% Confidence interval calibration section and for each
Should
benchmark 100 of intercept of linear measurement speed and repeat
bracket 0,0
m IRI values) regression run.
Difference in mean 100
Bias in measured
m IRI value from repeat Check for each speed and on
IRI over 100 m <3%
runs measured on individual validation sections
segments
different days
• Height Sensor Accuracy Check: this check • GPS latitude, longitude and height;
involves the placement of a stepped block, of
which the height of each step is known • Km Position;
precisely, under the height measurement • Left and right wheelpath IRI, and
sensor. The height to the top of each step is
measured and the differences in height are • Measurement speed.
checked against the known heights. The contractor should also provide a definition
As with response type devices, the network sheet to define any codes or abbreviations used
manager cannot ensure that all of the checks are in the file and column naming. Details of the
rigorously performed each day. However, as a format in which the output will be provided should
minimum form of control over operating ideally be submitted with the contractor’s quality
procedures, spot checks should be performed control plan.
from time to time. These checks should be The specifications (see Section 3.3) should
performed randomly on a weekly or two-weekly stipulate the deadline for delivery of data files on
basis. During each check, the contractor should completion of the survey. It is important to
be asked to stop the vehicle and a control check minimize delays between the time of survey and
should be performed by the network manager. data analysis, in order for errors to be identified
Table 6.1 provides guidelines for items to monitor as soon as possible. Ideally, some data files
during random control checks on profilers. should be given to the network manager while
the survey is in progress, so that the data can be
6.3. DATA CAPTURE AND checked and any inconsistencies identified at an
early stage.
DOCUMENTING
The contractor should flag any data files or parts
The contract specifications should provide details thereof for which measurements are regarded as
on the format required for the captured unusual or in which excessive variations may
roughness data. As a minimum, the occur because of environmental effects.
specifications should state the format of the Operators should therefore be trained not only in
required files (e.g. Comma Delimited ASCII file, the vehicle operation aspects, but also in the
Spreadsheet format) and the required columns. interpretation of IRI and perceived roughness.
For roughness data, the required columns would Also, operators should be aware of the impact of
typically include at least the following: certain pavement and environmental parameters
• Operator name; on the precision of measurement, so that files
recorded under non-optimal conditions can be
• Section details (separate columns for Section clearly flagged for detailed analysis.
name, lane, direction, region, etc.);
6.4. DATA CHECKING AND Appendix D shows some examples of trends for
such comparative plots, and provides guidelines
TROUBLESHOOTING for interpreting each situation. The visual
When the roughness data has been received, the interpretation of data shown in Appendix D can
network manager should perform some control be enhanced by a quantified comparison of the
checks on a few data files. The objective of these IRI values measured over segments in different
checks should be to ensure the measured years. This comparison could, for example,
roughness corresponds with basic engineering consist of a correlation between IRI values
judgement, and that the data are consistent with measured over segments in different years. The
that of earlier surveys. coefficient of determination (R2) can be used as
an indicator of the strength of the correlation.
For these control checks, the network manager
should select a few sections for which the If a data check reveals an inconsistency between
manager is familiar with the roughness properties the measured roughness and the pavement
(e.g. sections with poor riding quality or newly condition, or between the measured roughness
reconstructed sections with good riding quality). and the roughness of the previous year, then the
data file should first be checked for comments
The control check should look at the detailed from the operator regarding the pavement
plotted profile (over 10 or 100 m intervals, condition and measurement environment. These
depending on the reporting frequency) as well as aspects are discussed in the following section.
the segment averages for IRI. If surveys were
undertaken in preceding years, then the
roughness data can be graphically compared to
the data collected in previous years.
Table 6-2 Checklist for Operational Control Checks on Profilers
Control or Decision Aspect
1. Check the vehicle and ensure it is the same as used in the validation exercise.
2. Ensure that the driver is the same as the one who conducted the validation exercise.
3. Request and inspect the daily checklist. Ensure it meets the Quality Control plan format.
4. Inspect the vehicle and ensure that the height sensors are free of excessive dirt, mud, etc.
Request the operator(s) to perform a height check using a height calibration block. Check to ensure that
5. the measured heights are within limits and ensure that the operator is capable of performing the test
consistently.
Request the operator(s) to perform the bounce check. Check the output to ensure the measured profile is
6.
flat, and ensure that the operator is capable of performing the check consistently.
7. Confirm the correct operation of the GPS.
2. Check to see that distance markers were not changed between surveys.
Check absolute difference error between the IRI of this and the previous survey. If the difference is
3.
less than 0,5 m/km, the cause may be inconsistent tracking or normal deterioration.
4. Check the pavement condition as reported in the previous survey year and in the current year.
Pavement condition: does the pavement have a coarse texture? This could cause accuracy
5.
problems, especially if the IRI is low.
6. Pavement condition: does the section have severe crocodile cracking?
7. REFERENCES
Relevant Standards:
FONG, S. et al. (1998). IRI Error Estimation by
Transfer Function Analysis. 9th REAAA ASTM Standard E 950-98 (Re-approved 2004).
Conference, Wellington, New Zealand, May, Standard Test Method for Measuring the
1998. Longitudinal Profile of Travelled Surfaces
with an Accelerometer Established Inertial
FONG, S. and Brown, D.N. (1997). Transfer Profiling Reference. ASTM International, 100
Function Based Performance Specifications Bar Harbor Drive, West Conshohocken, PA,
for Inertial Profilometer Systems. Opus USA.
International Consultants. Central Laboratories
Report 97-529351, December, 1997, Lower Hut, ASTM Standard E 1082-90 (Re-approved 2002).
New Zealand. Standard Test Method for Measurement of
Vehicular Response to Traveled Surface
NCHRP Research Results Digest (1999). Roughness. ASTM International, 100 Bar Harbor
National Cooperative Highway Research Drive, West Conshohocken, PA, USA.
Program. Transportation Research Board,
National Research Council, Washington, D.C. ASTM Standard E 1364-95 (Re-approved 2000).
(Research Results Digest Number 244, Standard Test Method for Measuring Road
November, 1999). Roughness by Static Level Method. ASTM
International, 100 Bar Harbor Drive, West
PREM, H. (1998) Development and Evaluation Conshohocken, PA, USA.
of a Method for Validation of Pavement
Roughness Measurements. Contract Report ASTM Standard E 1656-94 (Re-approved 2000).
RE7135, April, 1998. ARRB Transport Research Standard Guide for Classification of
Ltd., Vermont South, Vic. Automated Pavement Condition Survey
Equipment. ASTM International, 100 Bar Harbor
ROBERTSON, D.A. (1998). Towards a Drive, West Conshohocken, PA, USA.
Specification for Validating International
Roughness Index Measurements from Road ASTM Standard E 1926-98 (Re-approved 2003).
Profilers. 9th REAAA Conference, Wellington, Standard Practice for Computing International
New Zealand, May, 1998. Roughness Index of Roads from Longitudinal
Profile Measurements. ASTM International, 100
SAYERS, M.W et al. (1986) Guidelines for Bar Harbor Drive, West Conshohocken, PA,
Conducting and Calibrating Road Roughness USA.
Measurements. World Bank Technical Paper
Number 46. The World Bank, Washington, D.C.
SAYERS, M.W and Karamihas, S.M, (1998). The
Little Book of Profiling: Basic Information
About Measuring and Interpreting Road
Profiles. University of Michigan, Ann Arbor,
1998.
SAYERS, M.W. (1989). Two Quarter-Car
Models for Defining Road Roughness: IRI and
HRI. Transportation Research Board,
Washington, D.C. (Transportation Research
Record 1215).
WIKIPEDIA. The Free Encyclopaedia. 6 Feb,
2007. <http://en.wikipedia.org/wiki/>
References
- 43 -
Roughness Measurement: Version 1.0
8. GLOSSARY
Calibration: The process of determining the relationship between the output of a measuring
device (e.g. the ARS measured by a Response Type device) and the value of the
input quantity (e.g. the IRI). Calibration is often regarded as including the process
of adjusting the output of a measurement instrument to agree with the value of the
applied standard (definition after Wikepedia, 2007).
DGPS: Differential Global Positioning System. A system that uses a network of fixed
ground based reference stations to broadcast the difference between the
positions indicated by the GPS satellite systems and the known fixed positions
(definition after Wikepedia, 2007).
Dipstick: Commonly used term for the slow moving profiling device named the Face
DipstickTM (patented, manufactured and sold by the FACE Corporation).
Filter: A mathematical function used to process a measured profile, normally with the
objective of removing certain wavelengths from the profile. The moving average is
an example of a simple filter.
GPS: Global Positioning System.
HRI: Half Car Index. A roughness index calculated by means of the IRI transform, but
using the point-by-point average of the two profiles measured in both wheelpaths
(as opposed to the IRI, which uses the profile of only a single wheelpath). The
HRI is always lower than the IRI.
IRI: International Roughness Index. A roughness parameter determined from a
measured road profile in a single wheeltrack. In the IRI calculation, the measured
profile is processed using a mathematical transform which filters and cumulates
the wavelengths encountered in the profile.
LDI: Linear Displacement Integrator. A response type device manufactured and sold
by the CSIR in South Africa.
Profilometer: A mobile device used for measuring the longitudinal profile of a road. The
measured profile may or may not be the true road profile, depending on the
wavelengths that have been filtered out of the measured profile. High speed
profilometers are capable of measuring at normal road speeds. Static
profilometers operate at walking speeds or slower (definition after Sayers et al.,
1996).
Repeatability: The expected standard deviation of measures obtained in repeated tests, when
using the same instrument and measurement team on a single, randomly selected
test section (definition after Sayers et al., 1996).
Reproducibility: A measure of the ability to reproduce a measured result (such as the IRI
measured over a 100 m segment of road) by another measurement device or
measurement team working independently (definition after Wikepedia, 2007).
Resolution: The resolution of a device specifies the smallest measurement increment that the
device is capable of.
Riding Quality: Term used to describe the relative degree of comfort or discomfort a road user
experiences when using a road. The terms riding quality and roughness are often
used interchangeably. In these guidelines, the term roughness is preferred.
Roughness: Term used to describe the relative degree of comfort or discomfort a road user
experiences when using a road.
True Profile: The actual profile of the road, relative to a fixed reference point, without any
filtering out of certain wavelengths.
Validation: The process of determining if a measurement device, when operated according to
a established procedure and within established operating ranges, can operate
effectively and reproducibly (definition after Wikepedia, 2007).
Verification: The process of proving or disproving the correctness of a system or measurement
device with respect to a certain formal specification.
Glossary
- 45 -
Roughness Measurement Guidelines
Appendix A
Analysis of Road Profiles: Basic Concepts
0.60
0.50 λ = Wavelength
Elevation (m) X0 = Phase Shift
0.40
0.30 A = Amplitude
0.20
0.10
0.00
0 20 40 60 80 100 120
Distance from Origin (m)
Profile Analysis Using Power By contrast, the green line which has the
Spectral Density lowest wave number, has a much larger
amplitude (about 2 m) (For the X-axis scale
The example shown in Figure A1 is highly chosen in Figure A2, only part of this sinusoid
idealized and no road surface would have such is shown).
a profile. However, an interesting aspect of
road profiles (or any type of curve which varies If we now “sample”, at different locations along
with distance, time or angle), is that the profile the X-axis, the elevation (i.e. Y-value) of each
can be constructed by adding sinusoids like of the four sinusoids, and add up these four Y-
that shown in Figure A1, for which the values at each point, we get the profile shown
properties of each sinusoid varies in a specific in Figure A3. This profile is a more realistic
manner. representation of a road profile. It looks almost
“random” and any cyclic sinusoidal pattern is
Figure A2 shows four sinusoids, each with a hard to discern.
different wave number and amplitude. For this
example, the sinusoid with the highest wave
number (i.e. the blue line with the shortest
wave length) has the smallest amplitude.
2.50
1.50
1.00
0.50
0.00
0 2 4 6 8 10 12 14 16
Distance from Origin (m)
5.0
4.5
4.0
3.5
Elevation (m)
3.0
2.5
2.0
1.5
1.0 Profile resulting from a sum of four sinusoids, each
0.5 with different wavelength and amplitude.
0.0
0 2 4 6 8 10 12 14 16
Distance from Origin (m)
1.0E-04
1.0E-05
1.0E-06
1.0E-07
1.0E-08
0.01 0.1 1 10
Filtering of Road Profile Data Suppose now that, for a detailed analysis of
the roughness profile, we are not interested in
A filter is a transform that is applied to a the sinusoids with the shorter wave numbers
measured series of data to filter out or remove (e.g. the green curve in Figure A2). We can
some of the information. The filter, or then filter out the influence of this sinusoid
transform, can be a mathematical function (as (and others with similar wave numbers). There
in the IRI calculation) or it can be a physical are several filters that can be used to achieve
filter, such as the suspension of a road profile, this. One simple way to achieve such filtering
which filters the profile elevation into a series is by taking the moving average over a length
of counts. Engineers often think of a filter as a that is roughly equal to the wavelengths we are
way to hide some information in a negative trying to filter out. Figure A7 shows the original
way. However, in profile analysis, filtering is profile (as in Figure A6), with a filtered profile
rather used (or should be used) to remove consisting of the moving average over 6
unwanted information. metres. This moving average is called a
As an example, consider the simulated profile smoothing, or low-pass filter. It is denoted by
in Figure A6. The formulation of this profile is the smoothed red line in Figure A7.
identical to that shown in Figure A3, only the If we compare the moving average line in
data series was extended over a longer length Figure A7 to the original, we can see that the
of road. As shown before, this profile is smoothed profile mainly gives us an indication
actually constituted of the four sinusoids of slope changes (large elevation changes). It
shown in Figure A2. is thus not very useful for roughness purposes.
However, we can now apply a second filter in
which we subtract the original profile from the
moving average value at that point. This new
profile gives us an indication of the how much
Further Reading: SINUSOIDS and the profile deviates from the smoothed profile
FILTERS at each point. This filter is called a anti-
smoothing (or high-pass) filter, and is denoted
A comprehensive discussion of sinusoids by the blue line in Figure A7. As we can see,
and different filter types can be found in the the final filtered profile has removed much of
“Little Book of Profiling” [Sayers and the larger up-down movements in the profile,
Karamihas, 1998]. and now highlights the roughness with higher
For a more-in depth discussion of the use of wave numbers (i.e. shorter wavelengths).
PSD functions to validate profilers, see Prem
(1998) and Fong and Brown (1997).
1.0E-02
PSD of Elevation (m2.m/cycle) Curve B (high amplitude, low wave number)
1.0E-03
1.0E-04
1.0E-05
1.0E-06
1.0E-07
Curve A (low amplitude, high wave number)
1.0E-08
0.01 0.1 1 10
5.0
4.5 Profile resulting from a sum of four sinusoids, each
with different wavelength and amplitude (plotted over
4.0
longer distance compared to Figure A3)
3.5
Elevation (m)
3.0
2.5
2.0
1.5
1.0
0.5
0.0
0 10 20 30 40 50
Distance from Origin (m)
Figure A6: Profile as shown in Figure A3, Extended Over a Longer Length of Road
5
Original First filter, consisting of a moving average
4 Profile over 6 metres. This is a smoothing filter
2
Elevation (m)
0
0 10 20 30 40 50
-1
Appendix B
Calibration Report Details
(Response Type Devices Only)
Benchmark IRI
5.0
C Run 4 7.3 51 1.49
C Run 4 7.4 56 1.52 4.0
C Run 5 7.3 50 1.49
C Run 5 7.4 62 1.52 3.0
D Run 1 7.7 45 1.29
2.0
D Run 1 7.8 37 1.22
D Run 2 7.7 48 1.29 1.0
D Run 2 7.8 39 1.22
D Run 3 7.7 50 1.29 0.0
D Run 3 7.8 33 1.22 0 50 100 150 200 250 300 350
Measured Count
D Run 4 7.7 50 1.29
D Run 4 7.8 33 1.22
D Run 5 7.7 49 1.29 SUMMARY OUTPUT
Check graph for non-linear trends (there
D Run 5 7.8 36 1.22
Q Run 1 37.3 308 6.62 Regression Statistics
should be none). Also, ensure data
Q Run 1 37.2 297 6.91 Multiple R 0.977 covers expected IRI range.
Q Run 2 37.3 304 6.62 R Square 0.956
Q Run 2 37.2 296 6.91 Adjusted R Square 0.955
Q Run 3 37.3 298 6.62 Standard Error 0.44 Acceptance Criteria
Q Run 3 37.2 285 6.91 Observations 70
Q Run 4 37.3 309 6.62
Q Run 4 37.2 279 6.91 ANOVA
Q Run 5 37.3 309 6.62 df SS MS F Significance F
Q Run 5 37.2 279 6.91 Regression 1 278.3813858 278.3814 1460.212 1.08829E-47
R Run 1 19.1 230 5.35 Residual 68 12.9638248 0.190644
R Run 1 19 237 4.94 Total 69 291.3452106
R Run 2 19.1 230 5.35
R Run 2 19 237 4.94 Coefficients Standard Error t Stat P-value Lower 95% Upper 95%
R Run 3 19.1 205 5.35 Intercept 0.396533307 0.109552921 3.619559 0.000563 0.17792386 0.615143
R Run 3 19 232 4.94 X Variable 1 0.020445697 0.000535049 38.21272 1.09E-47 0.019378022 0.021513
R Run 4 19.1 212 5.35
Etc. Etc.
Appendix C
Validation Calculation Details
(Profilers Only)
• The calculated absolute percentage It will be noted from the data on the next page
difference between the measured and that, for this abbreviated example data set, the
benchmark IRI values, using the benchmark validation data pass all of the recommended
IRI as base value criteria shown in Table C1.
Measured IRI
5
1 D 3.3 3.39 60 5.75 5.43 6%
4.5
1 E 3.6 3.69 60 1.884 1.99 6%
4
1 E 3.7 3.79 60 1.673 1.75 5%
3.5
1 A 0.2 0.29 80 1.177 1.13 4%
3
1 A 0.3 0.39 80 1.076 1.16 8%
2.5
1 B 14.5 14.59 80 4.215 4.59 9%
2
1 B 14.4 14.49 80 3.493 3.49 0%
1.5
1 C 3 3.09 80 2.852 2.83 1% 1
1 C 3.1 3.19 80 3.985 3.83 4% 0.5
1 D 3.2 3.29 80 4.176 4.37 5% 0
1 D 3.3 3.39 80 5.75 5.43 6% 0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5 5.5 6 6.5 7 7.5 8
1 E 3.6 3.69 80 1.884 2.04 8% Benchmark IRI
1 E 3.7 3.79 80 1.673 1.54 8%
1 A 0.2 0.29 100 1.177 1.26 7%
1 A 0.3 0.39 100 1.076 1.14 6% SUMMARY OUTPUT
1 B 14.5 14.59 100 4.215 4.4 4%
1 B 14.4 14.49 100 3.493 3.22 8% Regression Statistics
1 C 3 3.09 100 2.852 2.89 1% Multiple R 0.992
1 C 3.1 3.19 100 3.985 3.96 1% R Square 0.984 Green Cells denote
1 D 3.2 3.29 100 4.176 4.46 7% Adjusted R Square 0.984 acceptance criteria
1 D 3.3 3.39 100 5.75 5.45 5% Standard Error 0.188
1 E 3.6 3.69 100 1.884 1.73 8% Observations 40
1 E 3.7 3.79 100 1.673 1.62 3%
2 A 0.2 0.29 60 1.177 1.16 1% ANOVA
2 A 0.3 0.39 60 1.076 1.08 0% df SS MS F Significance F
2 B 14.5 14.59 60 4.215 4.21 0% Regression 1 85.37438849 85.3743885 2407.58388 5.611E-36
2 B 14.4 14.49 60 3.493 3.19 9% Residual 38 1.347503107 0.03546061
2 C 3 3.09 60 2.852 3.1 9% Total 39 86.7218916
2 C 3.1 3.19 60 3.985 3.87 3%
2 D 3.2 3.29 60 4.176 3.83 8% Coefficients Standard Error t Stat P-value Lower 95% Upper 95%
2 D 3.3 3.39 60 5.75 6.06 5% Intercept 0.002 0.068 0.030 0.976 -0.137 0.141
2 E 3.6 3.69 60 1.884 1.83 3% X Variable 1 1.008 0.021 49.067 0.000 0.967 1.050
2 E 3.7 3.79 60 1.673 1.72 3%
Data Set Continues (abbreviated here because of space constraints)…
Percentage Absolute Errors Greater Than 8% = 18%
Appendix D
Guidelines for Checking of Data Consistency
Situation D1
6
Previous survey data
5
Latest survey data
Roughness (m/km)
0
0 2 4 6 8 10 12
Distance (Km)
Description: The new data follows the same trend as that of the previous survey. The
average IRI value for the section is roughly the same.
Interpretation: Roughness on the section deteriorated little or not at all. The data can be
accepted into the database.
Situation D2
6
Previous survey data
5
Latest survey data
Roughness (m/km)
0
0 2 4 6 8 10 12
Distance (Km)
Description: The new data follows the same trend as that of the previous survey, but the
average IRI value for the new survey is slightly higher.
Interpretation: Roughness deteriorated within acceptable limits. Data can be accepted into the
database.
6
Previous survey data
5
Latest survey data
Roughness (m/km)
0
0 2 4 6 8 10 12
Distance (Km)
Description: The new data follows the same trend as that of the previous survey, and the
average IRI is the same. However, the IRI at specific distance readings differs
significantly.
Interpretation: There is a phase difference in the trend of the data. This is most likely caused
by inaccurate distance measurement or triggering at the start of the section.
The cause of the phase change should be investigated and the problem should
be corrected before the data is accepted into the database.
Situation D4
6
Previous survey data
5
Latest survey data
Roughness (m/km)
0
0 2 4 6 8 10 12
Distance (Km)
Description: The average IRI for the section is visibly higher and the trend in the IRI data is
not the same for the two surveys.
Interpretation: First ensure that the correct section was measured. It may be possible that the
section name or starting distance is incorrect. If it is confirmed that the section
location and number is correct, perform a visual assessment to determine the
cause of the deviation in the data. Possible causes may include severe water
infiltration, severe cracking or extensive failures. If the visual condition or road
history does not suggest severe deterioration, faulty measurements should be
suspected.
Appendix D: Guidelines for Checking of Data Consistency
- D2 -
Roughness Measurement: Version 1.0
Situation D5
6
Previous survey data
5
Latest survey data
Roughness (m/km)
0
0 2 4 6 8 10 12
Distance (Km)
Description: The average IRI for the latest survey is lower than that of the previous survey,
but the data trend is the same.
Interpretation: If the data for the previous survey is assumed to be correct, then possible
explanations could be that the section received a surface seal or other light
maintenance treatment. It could also be that the device is not properly
calibrated, or an operational error occurred during measurement. The data can
be accepted into the database after a small adjustment is made, provided that
the cause of the inconsistency is determined with confidence.
Situation D6
6
Previous survey data
5
Latest survey data
Roughness (m/km)
0
0 2 4 6 8 10 12
Distance (Km)
Description: The average IRI for the two surveys is similar, but the data trend is significantly
different.
Interpretation: An adjustment to the distance measurement would not address this situation.
Since the average roughness for the latest survey is similar to that of the earlier
survey, likely causes may include: incorrect section name or starting position;
lateral wander; significant variations in measurement speed or a coarse
textured surface. Data should not be accepted into the database unless the
cause of the inconsistency can be determined with confidence.
Appendix D: Guidelines for Checking of Data Consistency
- D3 -