Professional Documents
Culture Documents
Coding Manual
Drive on the right edition - August 2014
Document description
PRINT WARNING printed copies of this document or parts thereof should not
be relied upon as a current reference document.
Always refer to the electronic copy for the latest version at:
http://downloads.irap.org/docs/RAP-SR-2-2_Star_Rating_coding_manual.pdf
About iRAP
The International Road Assessment Programme (iRAP) is a registered charity dedicated to saving lives
through safer roads.
We provide tools and training to help countries make roads safe. Our activities include:
inspecting high-risk roads and developing Star Ratings and Safer Roads Investment Plans
providing training, technology and support that will build and sustain national, regional and local
capability
tracking road safety performance so that funding agencies can assess the benefits of their
investments.
The programme is the umbrella organisation for EuroRAP, AusRAP, usRAP, KiwiRAP and ChinaRAP. Road
Assessment Programmes (RAP) are now active in more than 70 countries throughout Europe, Asia Pacific,
North, Central and South America and Africa.
iRAP is financially supported by the FIA Foundation for the Automobile and Society and the Road Safety
Fund. Projects receive support from the Global Road Safety Facility, automobile associations, regional
development banks and donors.
National governments, automobile clubs and associations, charities, the motor industry and institutions such
as the European Commission also support RAPs in the developed world and encourage the transfer of
research and technology to iRAP. In addition, many individuals donate their time and expertise to support
iRAP.
Version history
Date
Version
Jan
2013
May
2013
June
2014
August
2014
Update
RAP-SR document series
Drive on right edition:
http://downloads.irap.org/docs/RAP-SR-2-2_Star_Rating_coding_manual.docx
Drive on left edition:
http://downloads.irap.org/docs/RAP-SR-2-2_Star_Rating_coding_manual-left.docx
Added new pedestrian crossing categories and School Zone attributes.
Attribute and category names updated and other minor amendments.
Added descriptions for intersecting road volumes and minor changes to descriptions
for roadside severity object.
Contents
1 Introduction ................................................................................................................................................ 6
1.1
4.2
4.3
4.4
4.5
4.6
Section.............................................................................................................................................. 9
4.7
Distance.......................................................................................................................................... 10
4.8
Length............................................................................................................................................. 10
4.9
4.10
Landmark ....................................................................................................................................... 10
4.11
Comments ...................................................................................................................................... 10
4.12
4.13
4.14
4.15
4.16
4.17
4.18
4.19
4.20
4.21
4.22
4.23
4.24
4.25
4.26
4.27
4.28
4.29
4.30
Roadside severity left distance & Roadside severity left object ............................................... 47
4.31
4.32
4.33
4.34
4.35
4.36
4.37
4.38
4.39
4.40
4.41
Curvature ........................................................................................................................................ 74
4.42
4.43
Grade.............................................................................................................................................. 78
4.44
4.45
4.46
Delineation ..................................................................................................................................... 84
4.47
4.48
4.49
4.50
4.51
4.52
4.53
4.54
4.55
4.56
4.57
4.58
4.59
4.60
4.61
4.62
5.2
5.3
5.4
Pedestrian peak hour flow along the road - right ......................................................................... 123
5.5
Pedestrian peak hour flow along the road - left ........................................................................... 124
5.6
5.7
5.8
5.9
5.10
5.11
1 Introduction
Deaths and injuries from road vehicle crashes are a major and growing public health epidemic. Each year
1.3 million people die and a further 50 million are injured or permanently disabled in road crashes. Road
crashes are now the leading cause of death for children and young people aged between 10 and 24. The
burden of road crashes is comparable with malaria and tuberculosis and costs 1-3% of the worlds GDP.
In low and middle income countries, road crashes represent a major health concern. More than 85% of the
global death toll and serious injuries occur in developing countries. Whereas road deaths are expected to
fall in high-income countries, they are likely to increase by more than 80 per cent in the rest of the world. 1
The International Road Assessment Programme (iRAP - www.irap.org) has drawn upon the extensive
knowledge base of the developed worlds Road Assessment Programmes (EuroRAP, AusRAP and usRAP),
with the generous support of the FIA Foundation, to develop a road survey methodology for low and middle
income countries. This Star Rating methodology does not require detailed crash data and works directly from
road surveys.
1.1
Star Ratings are an objective measure of the likelihood of a road crash occurring and its severity. The focus
is on identifying and recording the road attributes which influence the most common and severe types of
crash, based on scientific evidence-based research. In this way, the level of road user risk on a particular
network can be defined without the need for detailed crash data, which is often the case in low and middle
income countries where data quality is poor. Research shows that a persons risk of death and serious injury
is highest on a one-star road and lowest on a five-star road.
Star Ratings are also particularly useful in order to objectively quantify the level of risk associated with new
road designs (where crash data is not present) enabling evidence based decisions and also for use in highperforming countries where the relatively low frequency of crashes limits the ability of crash analysis to
influence performance monitoring and investment prioritisation. Further information on iRAP Star Rating
methodology and access to training courses can be found on RAPcapacity 2.
1
2
World Health Organisation, Global Status Report on Road Safety. Time for Action, 2009
RAPcapacity: http://capacity.irap.org
iRAP Star Rating and Investment Plan Coding Manual | 6
The median is the road feature that separates the opposing vehicle flows, in this example the
median type is centre line road marking.
The right side is used to record the distance to the nearest object to the right, measured from the
right edge of the carriageway to the object.
The left side is used to record the distance to the nearest object to the left, measured from the left
edge of the carriageway to the object.
Roadside left
Median
Roadside right
The median is the feature that separates the opposing vehicle flows. On a divided carriageway this
will typically be recorded as a physical median strip or median safety barrier.
The right side is used to record the distance to the nearest object to the right, measured from the
right edge of the carriageway being inspected to the object.
The left side is used to record the nearest object to the left. The distance to the object is measured
from the left edge of the carriageway being inspected to the object. Often the object will be located
within the median. If there is no object in the median, then the object is likely to be on the far side of
the opposing carriageway. In this case, the distance to the object is likely to be >=10m.
Roadside left
Median
Roadside right
3 Quality Control
To help attain a high level of accuracy in the data collected and subsequent coding, the following procedures
should be followed:
The name of the coder that coded the attributes should be recorded. This information is included to
help trace and correct any inconsistencies in the data.
One coder should be responsible for a length of road. This helps ensure consistency along the
length of the road.
Data should be backed up on a regular basis through the road coding process.
Following completion of the road coding process for each length of road the data should be reviewed
for accuracy by a separate coder and any errors or inconsistencies can then be corrected and noted.
Errors should be reviewed by the coding team to help build consistency in the coding.
A sample of the data should be reviewed by the iRAP, or by an iRAP nominated coding team to help
consistency across the programme.
Further guidance can be found in RAP-SR-2.4 Star Rating and Safer Roads Investment Plan Quality
Assurance Guide.3
RAP-SR-2.4: http://downloads.irap.org/docs/RAP-SR-2-4_QA_Guide.pdf
iRAP Star Rating and Investment Plan Coding Manual | 8
4 Coding Attributes
All of the attributes covered within this section are mandatory for iRAP Star Rating V3 calculations.
Where two coding options are present within a 100m segment the item that appears first in the list of options
for the attribute should be recorded.
Coder name
The coding team members name should be recorded for each 100m length. This will assist in the quality
assurance process and enable the data to be traced.
4.2
Coding date
4.3
4.4
Image reference
An image reference for each 100m length should be recorded. For example this may take the form of a
survey reference / file name in combination with a frame number, or a video file name in combination with a
time stamp.
4.5
Road name
The road name should be included within the input file to identify which road the data refers to.
In addition to this the road name will be contained within the route file name (if road specific files are
generated).
4.6
Section
A section name/number is used in the data to differentiate between sections of road. The section name
should be created to distinguish the section of road from other sections of the same road, or a road
authoritys own road section system should be used.
For example, section names should describe a from and to location (Petersfield to Williamsburg), it should
be noted that the sections should be relevant to direction in which the inspection was carried out.
Alternatively, if the road authority has divided their network up into management or maintenance sections it
may be beneficial to use these for the section numbers.
4.7
Distance
The distance will contain the distance in kilometres from the start of road or inspection section. The distance
is used in the score calculation stage to order the data. This data should be provided by the inspection
system.
The distance should not be less than 0.1km.
4.8
Length
The segment length will contain the length in kilometres that the coding applies to, this should be 0.1km. The
segment length is used in the score calculation stage to help with smoothing. This data will be provided by
the inspection system.
4.9
The latitude and longitude will contain the respective GPS coordinates in decimal degrees & WGS84
projection at the start of each 100m segment.
4.10
Landmark
For the purpose of iRAP reporting it is beneficial to record key landmarks where they occur. This will allow
locations on the road to be referenced relative to the landmarks.
Landmarks can be any of the following or other items of interest:
Major bridge
Toll booth
Reference point
Notes:
4.11
Landmarks can either be entered during the collection of the attribute data or can be added from
maps at a later stage.
Comments
For the purpose of iRAP reporting it is important to record key comments to highlight particular road safety
issues or special features encountered during the coding process. Comments may include issues not fully
covered by the coding itself or additional location information.
Notes:
Include any supporting information or notes on assumptions made during the coding of the section for
example:
4.12
Carriageway label
Each section of road requires a carriageway label. This is because undivided carriageways are surveyed in a
single direction, divided carriageways are surveyed in both directions and dedicated motorcycle facilities are
surveyed separately in both directions, the label is used to distinguish between these carriageways.
Notes:
For single carriageway roads, the carriageway is labelled as U (undivided).
For divided roads and dedicated motorcycle facilities, each carriageway needs to be labelled A for one
direction and B for the other direction.
Coding options
Undivided road
4.13
Upgrade cost
Upgrade cost records the influence that the surrounding land-use, environment and topography will have on
the cost of major works.
Notes:
Upgrade cost impact should be recorded based on a project that requires additional road space. That is if
additional road space is required will the costs be low, medium or high depending on the surrounding
environment.
The available space may be high cost for:
Urban areas where there are permanent structures such as buildings, bridges, tunnels etc. close to
the road.
Coding options
High
High example 2
Medium
Low
No fringe development
4.14
Motorcycle flow observed records the number of motorcycles in use within the 100m length.
Notes:
A motorcycle is a motorised two wheel vehicle. This includes mopeds, scooters and light three wheel
vehicles.
Motorcycles parked or not in use should not be recorded.
Coding options
8+ motorcycles
6 to 7 motorcycles
4 to 5 motorcycles
2 to 3 motorcycles
1 motorcycle
None
4.15
Bicycle flow observed records the number of bicyclists observed within the 100m length.
Notes:
It is acknowledged that this is a random sampling of bicycle flow, it is not intended to reflect an exact bicycle
volume.
The bicycle flow observed can be used in association with land-use data and local knowledge to estimate the
bicyclist peak hour flow during pre-processing.
Coding options
8+ bicycles
6 to 7 bicycles
4 to 5 bicycles
2 to 3 bicycles
1 bicycle
None
No bicycles observed
4.16
Pedestrian observed flow across the road records the number of pedestrians crossing or about to cross
the road within the 100m length.
Notes:
The coding process will record the number of pedestrians crossing the road each 100m.
It is acknowledged that this is a random sampling of pedestrian activity. This data can be used in association
with land-use data and local knowledge in pre-processing to estimate the pedestrian flow.
Coding options
8+
crossing
pedestrians
6 to 7
crossing
pedestrians
4 to 5
crossing
pedestrians
2 to 3
crossing
pedestrians
1 pedestrian crossing
None
4.17
Pedestrian observed flow along the road right records the number of pedestrians walking along the
right side of the road within the 100m length.
Notes:
The coding process will record the number of pedestrians walking along the right side of the road each
100m.
It is acknowledged that this is a random sampling of pedestrian activity. This data can be used in association
with land-use data and local knowledge in pre-processing to estimate the pedestrian flow.
Coding options
8+ pedestrians along
right side
6 to 7 pedestrians
along right side
4 to 5 pedestrians
along right side
2 to 3 pedestrians
along right side
1 pedestrian
right side
None
along
4.18
Pedestrian observed flow along the road left records the number of pedestrians walking along the left
side of the road within the 100m length.
Notes:
The coding process will record the number of pedestrians walking along the road each 100m.
It is acknowledged that this is a random sampling of pedestrian activity. This data can be used in association
with land-use data and local knowledge in pre-processing to estimate the pedestrian flow.
Coding options
8+ pedestrians along
left side
6 to 7 pedestrians
along left side
4 to 5 pedestrians
along left side
2 to 3 pedestrians
along left side
None
4.19
Land use right records the type of roadside development that is observed on the right side of the road.
The Land use attribute is used to provide an indication of the pedestrian activity likely to be generated at the
roadside. Information on whether there are land uses leading to pedestrian activity on only one side of the
road or on both sides can indicate whether pedestrian activity is likely only to occur alongside the road or
also generate crossing activity.
Notes:
Land use is to be recorded if there is likely to be an impact on the pedestrian flow for the road. Factors
influencing the likely impact on the use of the road would be proximity to road way and accessibility of road.
To be recorded as a separate land use, the land use type should generally continue for at least 400m, but
where there are clearly identifiable shorter lengths of high intensity activity (e.g. short lengths of village
environment, or localised market sites on rural roads) these short areas should also be recorded.
Any areas of obvious potential high intensity pedestrian activity should be recorded as commercial even if
commercial activity is not immediately obvious.
If in doubt between two land use categories, select the one that appears first in the list of coding options.
Coding options
Educational
Commercial
Residential
Undeveloped areas
4.20
Land use - left records the type of roadside development that is observed on the left side of the road.
Coding options
Same as Land use - right.
4.21
Area type
Area type records the level of roadside development through which the road is passing.
Notes:
Roadside development should be close to the road and not separated by a large fence or wall.
Isolated small settlements (e.g., extending for 100m to 200m along route) will be recorded as rural for area
type, but will be identified as local land use changes within this general environment.
Coding options
4.22
Speed limit
Coding options
150km/h
140km/h
130km/h
120km/h
110km/h
100km/h
90km/h
80km/h
70km/h
60km/h
50km/h
40km/h
30km/h
4.23
The actual posted numerical speed limit for motorcycles should be recorded.
Notes:
Do not attempt to record the speed of the traffic using the road.
If no speed limit is signed, the default speed limit set by law for that type of road should be used.
Do not record temporary speed limits at road works.
Do not record advisory speeds.
Coding options
150km/h
140km/h
130km/h
120km/h
110km/h
100km/h
90km/h
80km/h
70km/h
60km/h
50km/h
40km/h
30km/h
4.24
The actual posted numerical speed limit for trucks should be recorded.
Notes:
Do not attempt to record the speed of the traffic using the road.
If no speed limit is signed, the default speed limit set by law for that type of road should be used.
The default speed limits for the inspection should be:
Rural roads speed limit
150km/h
140km/h
130km/h
120km/h
110km/h
100km/h
90km/h
80km/h
70km/h
60km/h
50km/h
40km/h
30km/h
4.25
Differential speeds
Differential speeds records the difference in either operating speed or speed limit between cars and trucks
or cars and motorcycles where it exceeds 20km/h.
Notes:
If the speed limit, motorcycle speed limit and truck speed limit have been fully coded, then the differential
speeds can be calculated in pre-processing.
Coding options
Present
Not Present
4.26
Median type
Median type records the road infrastructure feature that separates the two opposing traffic flows.
The way in which opposing flows are separated affects the likelihood of severe crashes occurring. Physical
barriers restrict the movement of errant vehicles across the median and physical medians reduce the
potential for head-on impacts by making it less likely that they reach opposing traffic before they recover.
Notes:
Where an obviously defective safety barrier is present in the median such that a vehicle is likely break
through the barrier on impact, code the median as if no safety barrier exists. Examples of this are barrier very
low, sub-standard materials, broken / un-repaired / poorly maintained railings.
Where a safety barrier is present in the median it should be recorded in median type and in roadside severity
left object. However, if there is an aggressive object in front of the safety barrier, in this case median type
would be recorded as safety barrier, and roadside severity left object would be the aggressive object.
Coding options
Centre line
Ladder hatching
Stripes
Coloured paving
Flexipost
Divided road with safety barrier to international standards constructed from concrete.
If the barrier is obviously defective, code as though there is no barrier present.
Divided road with safety barrier to international standards constructed from metal.
If the barrier is obviously defective, code as though there is no barrier present.
Divided road with safety barrier to international standard that will also minimize impact to motorcyclists.
Motorcycle friendly barriers will have some form of protection for the supporting post or legs.
If the barrier is obviously defective, code as though there is no barrier present.
Divided road with safety barrier to international standard constructed from tensioned wires.
If the barrier is obviously defective, code as though there is no barrier present.
One way
One way streets only. Vehicles travel in a single direction with no opposing flow.
4.27
Centreline rumble strips record any textured markings running along the centre of a road whose function is
to warn drivers crossing the median. Also known as raised profile markings, this feature provides an audiovibratory warning to the driver.
Notes:
Shoulder rumble strips should not be recorded here.
Rumble strips may be constructed by cutting grooves into the pavement surface or by adding raised ribs to
the road marking.
Coding options
Not Present
Present
4.28
Roadside severity right distance records the distance to the nearest object to the edge line likely to be
reached which could result in serious or fatal injury to road users.
Notes:
Each side of the road will be coded separately.
Record from the edge line if present. Where no edge line is present record distance from pavement edge.
Where distance to an object is at or very close to a border between categories, code as closer distance
category.
Where a motorcycle facility is present the distance to the nearest object should be measured from edge of
the outermost driven lane.
When there is no object present on the roadside record the distance as >=10m.
Coding options
0 to <1m
1 to <5m
5 to <10m
>= 10m
4.29
Roadside severity right object records the nearest object likely to be reached which could result in
serious or fatal injury to road users.
Notes:
The object should be the same as noted in Roadside severity distance.
Each side of the road section will be rated separately. An aggressive object is any item that could result in
serious injury to a road user upon impact.
These include:
Rocks
Unprotected bridges
Do not record passively safe (crash friendly) roadside objects or minor vegetation such as small shrubs,
bushes and grass.
Coding options
Cliff
Examples are:
Aggressive ends to safety barriers for example: ramped ends, unprotected ends, sharp ends, fish-tail
terminals. This category should also be used to record damaged sections of safety barrier.
Grass banks
Downwards slope
Rule of thumb
A slope should be recorded if a vehicle is likely to roll on it.
Culvert headwalls
Communications cabinets
Grass banks
No object
4.30
Roadside severity left distance records the same as roadside severity right distance but for the left
side of the roadway.
Roadside severity left object records the same as roadside severity right object but for the left side
of the roadway.
Notes:
For divided highways, use the left side severity for the assessment of severe objects in the median.
For a divided carriageway if there is an object in the median it should be recorded in roadside severity left,
with the distance being recorded from the left edge of the carriageway in the direction of travel to the object.
For an undivided carriageway the left roadside is recorded.
When a roadside object is in front of a safety barrier the distance to the hazardous object is recorded.
For a divided carriageway if a safety barrier is the closest item it should be recorded.
For a divided carriageway if there is no object in the median:
Coding options
Same codes as Roadside severity right distance & Roadside severity right object.
Roadside left
Roadside right
4.31
Shoulder rumble strips record any textured markings running along a road whose function is to warn
drivers leaving the travelled way on the right side of the roadway. Also known as raised profile markings, this
feature provides an audio-vibratory warning to the driver.
Notes:
Centreline rumble strips should not be recorded here.
Shoulder rumble strips will only be found on paved shoulders.
Rumble strips may be constructed by cutting grooves into the pavement surface or by adding raised ribs to
the road marking.
Coding options
Not Present
Present
4.32
The paved shoulder width right refers to the safe and drivable section of road to the side of the edge line
on the right hand side of the carriageway. It is measured from the centre of the shoulder marking (the edge
line) to the edge of the paving.
Notes:
If paving begins to break up on a shoulder, the paved shoulder width should be measured up to where the
edge break occurs.
If a road has no markings for a shoulder (no edge line), then no paved shoulder should be recorded, since a
vehicle can be considered to be able to travel to the edge of the sealed surface.
Coding options
None
Wide ( 2.4m)
4.33
The paved shoulder width left refers to the safe and drivable section of road to the side of the edge line
on the left hand side of the carriageway. It is measured from the centre of the shoulder marking to the edge
of the paving.
Notes:
If paving begins to break up on a shoulder, the paved shoulder width should be measured up to where the
edge break occurs.
If a road has no markings for a shoulder, then no paved shoulder should be recorded, since a vehicle can be
considered to be able to travel to the edge of the sealed surface.
Coding options
None
Wide ( 2.4m)
4.34
Intersection type
Intersection type records the presence and type of intersections with gazetted/adopted roads.
Notes:
Intersections should only be recorded once even if they cover more than 100m.
Intersections should be recorded if the intersecting road is an adopted road (i.e. not commercial or
residential access).
Coding options
4-leg (unsignalised) with no protected turn lane
Mini roundabout
Roundabout
Merge Lane
None
No intersection present.
4.35
Intersection channelization
Intersection channelization records if there are raised or coloured islands present at an intersection that
designate intended vehicle paths.
Notes:
Intersection channelization should include both splitter islands and median islands.
Coding options
Not present
Present
Not applicable
No intersection present.
4.36
1 to 100 vehicles
None
No intersection present
4.37
Intersection quality
Intersection quality represents the quality of the intersection design, advance warning, signing, and
markings.
Notes:
Factors resulting in a poor coding may include:
Poor deflection angles at roundabouts (approach means roundabout can be entered at high speeds)
Lack of advance signing and marking on an intersection approach where the intersection is not
clearly visible to approaching drivers (i.e., where approach sight distance is limited.)
Adequate
Not applicable
No intersection present.
4.38
Property access points records the number of low-flow points where vehicles can enter or exit the
roadway. This includes commercial and residential driveways and minor access lanes.
Notes:
A property access point should be an intersection with a road that has not been adopted by the road
authority (i.e. is not managed by the road authority).
Coding options
Commercial Access 1+
Residential Access 3+
Residential Access 1 or 2
None
4.39
Number of lanes
Number of lanes records the total number of lanes in the direction of travel.
Notes:
The number of lanes recorded should reflect the predominant character of the road, and changes over short
lengths of road (less than 400m) should not be recorded.
Only lanes that serve through traffic should be considered; turning lanes or short auxiliary lanes should not
be considered. Dedicated bus lanes, guided bus ways and bus rapid transit systems should not be
considered.
Where a divided carriageway has two lanes in one direction and one in the other direction or three and two
lanes, only the number of lanes in the direction of travel should be recorded (the number of lanes for the
opposing carriageway will be recorded when coding the opposing carriageway).
Coding options
Four or more
Three
Undivided carriageway with three lanes in one direction and two in the other direction.
Two
Undivided carriageway with two lanes in one direction and one in the other direction.
One
4.40
Lane width
Lane width is the distance from the centre of the shoulder marking to the centre of the adjacent lane
marking or the centreline marking.
Notes:
If the road has no markings for a shoulder, a vehicle can be considered to be able to travel up to the edge of
the sealed surface or the closest hazard.
If no lane markings are present, the total road width should be divided by the number of traffic streams.
Coding options
Narrow ( 0m to < 2.75m)
Wide ( 3.25m)
4.41
Curvature
The road contains curves which can only be driven at less than
40km/h. Approximate radius of curve <200m.
Sharp
Moderate
The road has fairly tight curves which can be driven at less
than 100km/h but more than 70km/h. Approximate radius of
curve 500 to 900m.
4.42
Quality of curve
Quality of curve records how easy it is to judge how sharp a curve is and if it can be driven safety. The
quality of the curve will reflect the extent to which signs and markings help the driver to judge the correct
curvature, and the sight distance in advance of, and around, the curve.
Notes:
A practical indication of the quality of the curve might be whether the driver needs to adjust speed suddenly
or unexpectedly on the approach to, or within the curve. This may occur even though there has been an
attempt through signing to warn the driver of extra risk.
If the code poor should be assigned, then it must be selected from the point the curve starts to the end of
the curve.
Coding options
Poor
Adequate
Not applicable
4.43
Grade
A rise of more than 10m over a 100m length, or an angle of over 5.75 degrees
7.5 to <10%
A rise of 7.5m to 10m over a 100m length, or an angle of 4.3 to 5.75 degrees
0 to <7.5%
4.44
Road condition
Road condition records the ability of the road to provide a level, even running surface, free from major
surface defects that may adversely affect the vehicle path.
Notes:
The features of a poor or medium road condition need only to be present at some point on the 100m length,
not over its entire length. Typically a poor quality category will have serious defects for over 10 meters or
more.
Defects that should be considered include anything that would cause an impact on vehicle control or path,
some examples are:
Deformation any forms of rutting or uneven surface that can lead to an uncomfortable or unsafe
ride.
Pot-holes any holes in the road surface due to loss of material, sufficiently wide or deep enough to
cause a severe jolt or loss of control to the vehicle.
Edge defects any road shoulder seal problems which encroach on the driven lane.
Coding options
Poor
Medium
Good
4.45
Skid resistance / grip records the general characteristic of the road surface in terms of its properties
relating to skidding resistance and texture depth.
Notes:
Surface texture deficiencies should be recorded here. This includes surface friction issues such as loose
gravel, flushing or stripping which could reduce traction for vehicles in wet or dry conditions.
The attribute recorded should reflect the general condition of the road over the 100m length.
Coding options
Unsealed - poor
Unsealed - adequate
Sealed - poor
Sealed - medium
Sealed - adequate
4.46
Delineation
Delineation records the road attributes which inform drivers of road conditions to keep them within the
driven lane and aware of the road ahead.
Notes:
The delineation is based on a combination of the following factors:
Centrelines
Edge lines
Signage
Warning signs must be present to warn drivers of any sudden change in the road conditions e.g. lane
narrowing.
Quality of delineation of curves, intersections and crossings are recorded under other attributes, in this
situation delineation should be kept the same as the previous value.
This attribute involves coding the quality of delineation under daylight conditions only.
Coding options
Poor
Adequate
4.47
Street lighting
Street lighting records the presence of street lighting that is sufficient to illuminate pedestrians and
bicyclists.
Notes:
A street light or street lamp is a raised source of light often mounted on a lamp column or pole either on the
side of the road or within the median, or suspended on a wire above the road to provide illumination.
Coding options
Not Present
Present
4.48
Pedestrian crossing facilities inspected road records the presence of purpose built pedestrian crossing
facilities on the road being inspected.
Notes:
Pedestrian crossing facilities should be recorded regardless of whether they are at an intersection or not.
If located at intersections, the facility needs to be recorded at the same point so that they can be linked.
If two pedestrian crossings on the inspected road are present at an intersection, only one is recorded.
Pedestrian crossings on intersecting roads are not recorded in this attribute.
Where crossing is at a signalized intersection the pedestrian crossing should only be considered signalised if
the signals have a pedestrian phase.
Coding options
Refuge only
No facility
4.49
Pedestrian crossing quality records how well the crossing can be seen by drivers, or if there are warning
signs present.
Notes:
When a pedestrian crossing facility has been recorded the quality of the crossing must also be recorded.
An assessment should be made on whether some drivers may need to brake suddenly when they become
aware of the crossing too late, or fail to see it completely.
The three primary factors to be considered in coding quality of crossing are:
Signing
Coding options
Poor
Adequate
Not applicable
4.50
Pedestrian crossing facilities intersecting road records the presence of purpose built pedestrian
crossing facilities on an intersecting road.
Notes:
If two pedestrian crossings are present at an intersection, only one is recorded.
Where crossing is at a signalised intersection the pedestrian crossing should only be considered signalised if
the signals have a pedestrian phase.
Coding options
Refuge only
No facility
4.51
Pedestrian fencing
Pedestrian fencing records if there is a fence present that is sufficient to restrict pedestrian crossing flow.
Notes:
Pedestrian fencing should be present for the whole 100m unless there is a surface level pedestrian crossing
facility present.
If there is a surface level pedestrian crossing facility present then the pedestrian fencing should restrict
crossing flow and direct the pedestrians to the location of the crossing facility.
Pedestrian fencing need only be present on one side of the road to be recorded as present, it does not need
to be present on both sides.
Coding options
Not present
Present
4.52
School zone warning records the presence of a school zone. School zones are areas within the vicinity of
schools and other educational establishments where school children and young pedestrians are likely to be
present in high numbers. School zones are likely to have reduced speed limits for certain times of the day.
Notes:
School zones are likely to have appropriate road signs and markings to make motorists aware of the
presence of vulnerable road users such as young pedestrians and bicyclists. Parking restrictions may also
apply in school zones.
Coding options
4.53
School zone crossing supervisor records the presence of a crossing supervisor or warden. The crossing
supervisor will assist children in safely crossing roads on their way to and from school.
Notes:
School crossing supervisors often operate during the school community's peak demand period both in the
morning and in the afternoon. Actual operating times depend on a number of factors that include school start
times, pedestrian access and traffic volumes. Also referred to as a school crossing patrol.
Coding options
Not applicable
4.54
Speed management / traffic calming records the presence of road infrastructure features that will typically
reduce the operating speed by 5 to 10km/h below the speed limit.
Notes:
Speed management / traffic calming is typically found in urban areas.
Traffic calming is often applied to local streets with the aim of lowering traffic speeds and volumes, and
sometimes, preventing particular types of vehicle travelling through an area.
Traffic calming features include: roundabouts, kerbed build-outs, speed humps, raised tables, entry
treatments, speed cushions, chicanes and modified intersections.
Coding options
Not present
Present
Speed table
Speed hump
4.55
Vehicle parking
Vehicle parking records the extent to which there is vehicle parking along the side of the road.
Notes:
Vehicle parking includes where several buses or taxis stop to service roadside activities.
This attribute should include parked vehicles and on-street parking spaces, bus stops and general
encroachment on the highway.
Vehicle parking should be based on activities within 2m of the outside edge of the driveable lane.
Coding options
Two sides
Parking on both sides of the road spill out onto the road.
One side
Parking on one side of the road spill out onto the road.
None
4.56
Sidewalk provision right records the provision of a footpath or the presence of an informal path on the
right side of the roadway.
Notes:
A footpath is a purpose built facility for pedestrians that has an all-weather surface (sealed or unsealed) that
provides a reliable surface for pedestrians to walk on.
An informal path is a surface that, although not purpose built for pedestrians, provides a location that is
commonly used by pedestrians to walk on that is adjacent or away from the driven lane.
Sidewalk provision is based on the sidewalks distance from the outer-most driveable lane, and the presence
of a vertical barrier between vehicular traffic and pedestrians. This distance can be defined as the distance
from the edge-line of the closest trafficable lane to the edge of the pedestrian sidewalk.
Provision for pedestrian crossing movements is not considered as part of this attribute.
A physical barrier can effectively remove the risk of pedestrian and vehicle interaction but to do so, the
physical barrier must be sufficient to restrain a vehicle from entering the pedestrian facility at the posted
speed limit.
Kerbs, while discouraging traffic from passing over them, can be considered to do little to prevent road traffic
from entering the sidewalk, unless specifically designed to do so; thus, kerbs are not a physical barrier.
If the footpath is obstructed e.g. by roadside traders, shop front activities (so that pedestrians have to walk in
the roadway), then code as if footpath is not present.
If there is a parking lane present then the distance to the footpath should be measured from the edge of the
driven lane.
Non-physical separation many include grass verges.
Coding options
None
Sidewalk separated from roadway by no more than 1m, including paved shoulder and no barrier
provided.
Sidewalk separated from roadway by between 1m and 3m, and no barrier provided.
Physical barrier
Sidewalk separated from road by a physical barrier sufficient to restrain a vehicle from entering the
pedestrian facility at the posted speed limit.
Observation or evidence of pedestrian flow along the road using an informal path separated from
roadway by less than 1m.
Observation or evidence of pedestrian flow along the road using an informal path separated from
roadway by more than 1m.
4.57
Sidewalk provision left records the provision of a footpath or the presence of an informal path on the left
side of the roadway.
Notes:
A footpath is a purpose built facility for pedestrians that has an all-weather surface (sealed or unsealed) that
provides a reliable surface for pedestrians to walk on.
An informal path is a surface that, although not purpose built for pedestrians, provides a location that is
commonly used by pedestrians to walk on that is adjacent or away from the driven lane.
Sidewalk provision is based on the sidewalks distance from the outer-most driveable lane, and the presence
of a vertical barrier between vehicular traffic and pedestrians. This distance can be defined as the distance
from the edge-line of the closest trafficable lane to the edge of the pedestrian sidewalk.
A physical barrier can effectively remove the risk of pedestrian and vehicle interaction but to do so, the
physical barrier must be sufficient to restrain a vehicle from entering the pedestrian facility at the posted
speed limit.
Kerbs are not a physical barrier.
If the footpath is obstructed e.g. by roadside traders, shop front activities (so that pedestrians have to walk in
the roadway), then code as if footpath is not present.
If there is a parking lane present then the distance to the footpath should be measured from the edge of the
driven lane.
For divided roads code this attribute as None.
Coding options
Same as Sidewalk provision right.
4.58
Service road
Service road records the presence of a service road running parallel with the main carriageway.
Notes:
The purpose of a service road is to link the property accesses and minor intersections together and then join
them to the main carriageway at a single point.
Coding options
Not present
Present
4.59
Facilities for motorised two-wheelers records the presence of purpose built facilities for motorcycles and
other motorised two-wheelers.
Notes:
This includes segregated motorcycle paths completely separated by barriers, as well as dedicated lanes
within the roadway but to one side of the normal traffic.
For the facility to be coded exclusive motorcycle path with barrier, there must be a physical barrier sufficient
enough to fully restrict vehicles from entering the dedicated path.
Coding options
None
4.60
None
On-road lane
Off-road path
Standard road layout that has been identified by signing as preferred bike route.
4.61
Roadworks
Coding options
Major road works in progress
Minor road works are when all the attributes can be coded
accurately even though there are road works. Road works and
temporary traffic management may affect the speed of passing
traffic.
No road works
4.62
Sight distance
Sight distance records the ability of the driver to see the pedestrians or bicyclists either in the roadway, or
about to cross the road ahead, or vehicles at an intersection.4
Notes:
Horizontal / vertical alignment or physical obstructions such as roadside objects and vegetation may reduce
sight distance.
Coding options
Poor
Adequate
Sight distance requirements are typically defined in local design standards and relate to the speed at the
location and the specific sight distance requirements (e.g. stopping, overtaking and intersection related). For
all design applications local standards should be adhered to.
iRAP Star Rating and Investment Plan Coding Manual | 120
5 Post-coding Attributes
5.1
Vehicle flow for each section of road is recorded. This is used by the fatality estimation component of the
model to convert from individual risk to collective risk for cars and motorcycles.
Total vehicle flow recorded in AADT
This should be the total road AADT (i.e. flow on all carriageways)
5.2
Motorcycle %
Motorcycle percent records the percentage of the total vehicle flow that can be classed as a motorised two
wheel vehicle or light three wheel vehicle. This includes mopeds, scooters and auto-rickshaws.
Categories
2
0%
1% - 5%
6% - 10%
11% - 20%
21% - 40%
41% - 60%
61% - 80%
81% - 99%
10
100%
5.3
Pedestrian peak hour flow across the road records the average number of pedestrians crossing the road
for each 100m over a typical peak hour.
Categories
1
1 to 5
6 to 25
26 to 50
51 to 100
101 to 200
101 to 200 pedestrians cross the road on average within a peak hour
201 to 300
201 to 300 pedestrians cross the road on average within a peak hour
301 to 400
301 to 400 pedestrians cross the road on average within a peak hour
401 to 500
401 to 500 pedestrians cross the road on average within a peak hour
10
501 to 900
501 to 900 pedestrians cross the road on average within a peak hour
11
900+
5.4
Pedestrian peak hour flow along the road right records the average number of pedestrians walking
along the right side of the road (relative to the direction of inspection) for each 100m over a typical peak
hour.
Categories
1
0
No pedestrians walking along the right side of the road on a peak hourly
basis
1 to 5
1 to 5 pedestrians walking along the right side of the road on a peak hourly
basis
6 to 25
6 to 25 pedestrians walking along the right side of the road on a peak hourly
basis
26 to 50
51 to 100
51 to 100 pedestrians walking along the right side of the road on a peak
hourly basis
101 to 200
101 to 200 pedestrians walking along the right side of the road on a peak
hourly basis
201 to 300
201 to 300 pedestrians walking along the right side of the road on a peak
hourly basis
301 to 400
301 to 400 pedestrians walking along the right side of the road on a peak
hourly basis
401 to 500
401 to 500 pedestrians walking along the right side of the road on a peak
hourly basis
501 to 900
501 to 900 pedestrians walking along the right side of the road on a peak
hourly basis
900+
900+ pedestrians walking along the right side of the road on a peak hourly
basis
10
11
5.5
Pedestrian peak hour flow along the road left records the average number of pedestrians walking along
the left side of the road (relative to the direction of inspection) for each 100m over a typical peak hour.
Categories
1
No pedestrians walking along the left side of the road on a peak hourly basis
1 to 5
1 to 5 pedestrians walking along the left side of the road on a peak hourly
basis
6 to 25
6 to 25 pedestrians walking along the left side of the road on a peak hourly
basis
26 to 50
26 to 50 pedestrians walking along the left side of the road on a peak hourly
basis
51 to 100
51 to 100 pedestrians walking along the left side of the road on a peak hourly
basis
101 to 200
101 to 200 pedestrians walking along the left side of the road on a peak hourly
basis
201 to 300
201 to 300 pedestrians walking along the left side of the road on a peak hourly
basis
301 to 400
301 to 400 pedestrians walking along the left side of the road on a peak hourly
basis
401 to 500
401 to 500 pedestrians walking along the left side of the road on a peak hourly
basis
501 to 900
501 to 900 pedestrians walking along the left side of the road on a peak hourly
basis
900+
900+ pedestrians walking along the left side of the road on a peak hourly basis
10
11
5.6
Bicycle peak hour flow records the average number of bicycles using the road for each 100m over a typical
peak hour.
Categories
1
1 to 5
6 to 25
26 to 50
51 to 100
101 to 200
201 to 300
301 to 400
401 to 500
10
501 to 900
11
900+
5.7
The 85th percentile operating speed is the speed at which 85 percent of the vehicles are travelling at or
below.
Notes:
This attribute is typically collected after the coding phase.
Coding options km/h
150km/h
95 to 99 km/h
90 to 94 km/h
85 to 89 km/h
80 to 84 km/h
75 to 79 km/h
70 to 74 km/h
65 to 69 km/h
60 to 64 km/h
55 to 59 km/h
50 to 54 km/h
45 to 49 km/h
40 to 44 km/h
35 to 39 km/h
34 km/h
85 to 89 mph
80 to 84 mph
75 to 79 mph
70 to 74 mph
65 to 69 mph
60 to 64 mph
55 to 59 mph
50 to 54 mph
45 to 49 mph
40 to 44 mph
35 to 39 mph
30 to 34 mph
25 to 29 mph
24mph
5.8
The mean operating speed is the mean average operating speed of the vehicles for the 100m length.
Notes:
This attribute is typically collected after the coding phase.
Coding options - km/h
150km/h
95 to 99 km/h
90 to 94 km/h
85 to 89 km/h
80 to 84 km/h
75 to 79 km/h
70 to 74 km/h
65 to 69 km/h
60 to 64 km/h
55 to 59 km/h
50 to 54 km/h
45 to 49 km/h
40 to 44 km/h
35 to 39 km/h
34 km/h
85 to 89 mph
80 to 84 mph
75 to 79 mph
70 to 74 mph
65 to 69 mph
60 to 64 mph
55 to 59 mph
50 to 54 mph
45 to 49 mph
40 to 44 mph
35 to 39 mph
30 to 34 mph
25 to 29 mph
24mph
5.9
Road that cars can read records if the road fulfils the specification for vehicles to be able recognise the
delineation (markings and signs).
Notes:
This attribute is currently not recorded.
All roads should be recorded as not meeting the specification.
Coding options
The road does not meet the roads that cars can read
specification.
Meets specification
The road meets the roads that cars can read specification.
5.10
The Star Rating policy targets record the minimum policy Star Rating targets set for each of the user
groups (vehicle occupant, motorcyclists, pedestrians, and bicyclist).
Notes:
Road user targets will be set during pre-processing.
If a policy minimum Star Rating has been set for any for the user groups it should be recorded using this
attribute.
Targets should be specified for each user group separately.
Coding options for each user group
Not applicable
No Star Rating policy has been set for specific user group
1 Star
2 Star
3 Star
4 Star
5 Star
5.11
Example 1
0.3m
2.5m
0.5m
Attribute group
Roadside Right Distance
Roadside Right Object
Median Type
Roadside Left Distance
Roadside Left Object
Attribute
1 to 5m
Tree
0 to 1m
0 to 1m
Lamp column
Notes
Distance from edge of lane to tree on the right
Tree with diameter >10cm
Full width of the median
Distance from edge lane to lamp column in median
Sign, post or pole with diameter >10cm
Example 2
2.5m
0.5m
Attribute group
Roadside Right Distance
Median Type
Roadside Left Distance
Attribute
1 to 5m
0 to 1m
10m+
Notes
Distance from edge of lane to tree on the right
Full width of the median
No object in median so distance recorded as >10m
Example 3
6m
Attribute group
Roadside Right Distance
Median Type
Roadside Left Distance
3m
Attribute
1 to 5m
Centre line
5 to 10m
Notes
Distance from edge of lane to lamp column
Opposing traffic next each other
Distance from edge lane to the tree on the left
Example 4
6m
Attribute group
Roadside Right Object
Median Type
Roadside Left Object
Attribute
Upwards slope
Centre line
Tree
Notes
Upward slope, no rollover gradient
Opposing traffic next each other
Grass bank is not high enough to be considered a
hazard therefore record tree
Example 5
8m
15m
Attribute group
Roadside Right Distance
Median Type
Roadside Left Distance
Attribute
10m+
Centre line
5 to 10m
Tree
Notes
Distance from edge of lane to nearest object on right
Opposing traffic next each other
Ditch is not deep enough so distance from edge lane to
the tree on the left
Tree is hazardous object on the left
Example 6
15m
Attribute group
Roadside Right Distance
Median Type
Roadside Left Object
Attribute
10m+
Centre line
Ditch
Notes
Distance from edge of lane to nearest object on right
Opposing traffic next each other
Deep drainage ditch
Example 7
9m
3m
Attribute group
Roadside Right Distance
Median Type
Roadside Left Distance
Attribute
1 to 5m
Centre line
5 to 10m
Notes
Distance from edge of lane to lamp column on left
Opposing traffic next each other
Grass slope not steep enough to count as upward slope
with rollover gradient, so distance to tree is recorded.
Example 8
2m
Attribute group
Roadside Right Distance
Attribute
1 to 5m
Median Type
Roadside Left Object
Centre line
Safety barrier
Notes
Lamp column is in front of barrier, so distance to lamp
column is recorded
Opposing traffic next each other
Barrier would the first object to be hit so is recorded
Example 9
7.5m
6m
Gradient >1:3
Attribute group
Roadside Right Distance
Roadside Right Object
Median Type
Roadside Left Distance
Roadside Left Object
Attribute
5 to 10m
Lamp column
Centre line
0 to 1m
Downward slope
Notes
Slope is less than 1:3, so distance to lamp column is used
Non-frangible post
Opposing traffic next each other
Downward slope begins adjacent to carriageway edge
Slope is greater than 1:3 gradient
Example 10
Attribute group
Number of lanes
Median Type
Attribute
1
Centre line
Notes
Number of lanes in direction of travel
Opposing traffic next each other
Example 11
Attribute group
Number of lanes
Median Type
Carriageway type
Attribute
2
Centre line
Undivided
Notes
Number of lanes in direction of travel
Opposing traffic next each other
Because there is no physical separation of the opposing
traffic
Attribute
2+1
Centre line
Undivided
Notes
Number of lanes in direction of travel
Opposing traffic next each other
Because there is no physical separation of the opposing
traffic
Example 12
Attribute group
Number of lanes
Median Type
Carriageway type
Example 13
Attribute
Centre line
Good
1
Attribute group
Median Type
Delineation
Number of lanes
Attribute
Centre line
Poor
1
Notes
Both roads are recorded as median type = centre line because this is what is
supposed to be on the road, however, because the lines on the road on the right are
not present delineation is recorded as poor.
Example 14
Attribute
Merge Lane
1
Attribute group
Intersection type
Number of lanes
Attribute
None
1
Notes
In the right image the lane leaves the road so this is recorded as intersection
category None (diverge lanes are not recorded).
In the left image the lane joins the road so this is recorded as a Merge lane.