Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Contents

1. INTRODUCTION 2
2. PURPOSE OF THE MANUAL 2
3. LEVEL OF DETAIL FOR DATA COLLECTION 2
4. FREQUECY OF DATA COLLECTION/UPDATION 2
5. LINEAR REFERENCING SYSTEM 3
6. POTENTIAL SYNERIES BETWEEN AGENCIES FOR OPTIMISATION 4
7. NETWORK IDENTIFICATION OF ASSETs 4
7.1 Classified road network 4
7.2 Unclassified road network 5
7.3 Bridge and other structures network 5
7.4 Traffic database network 5
8. PLANNING REQUIREMENTS FOR FIELD SURVEYS 5
8.1 Annual survey cycle 5
8.2 Logistical planning 5
8.3 Team distribution and coordination planning 5
9. FIELD TEAM COMPOSITION5
10. DEVICE FOR DATA COLLECTION 5
10.1 Device for GPS data log6
10.2 Device for Digital data collection (Road and structures Inventory and condition data) 7
10.3 Device for Roughness data collection on paved roads 10
10.4 Device for Roughness data collection on unpaved roads 11
10.5 Device for inaccessible structures 11
10.6 Device for Traffic data collection 11
11. SOFTWARE FOR DATA COLLECTION 11
11.1 SW maps for Road and Structure Inventory and condition data collection 11
11.2 AR traffic counter for traffic data collection 14
12. DATA COLLECTION PROCEDURE 14
12.1 Road Inventory data collection 14
12.2 Condition assessment of paved roads 14
12.3 Condition assessment of unpaved roads 14
12.4 Structure Inventory data collection 14
12.5 Visual condition assessment of bridges and other structures 14
12.6 Classified Traffic count procedure 14
13. DATA TRANSMSSION AND STORAGE 14
14. QUALITY ASSURANCE/QUALITY CONTROL (QA/QC) OF FIELD DATA 14

Page 1 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

14.1 Quality control checklist 14

14.2 Quality control procedures 14
14.3 Quality Assurance procedures 14
15. DATA CLEANING AND PROCESSING 14
15.1 Alignment data cleaning 14
15.2 Attribute data cleaning 14
15.3 Data processing 14
15.4 Creation of geo-spatial database 14

Appendix I – GAP analysis of existing data

collection system and procedures.
The Harmonised data collection manual is
prepared based on the experience gained by
the consultants during the primary data
collection for the newly built Relational
database management system (RDBMS) by
RFB for deriving data from RMMS and
DROAMS.

2. PURPOSE OF THE MANUAL

The purpose of the manual shall be to use as

practice guide for data collection and updating
the databases of respective agencies in updated
schema with proposed forms (see Appendix
1. INTRODUCTION XX) its proposed attribute information for
DROMAS and RMMS.
Harmonised data collection manual is prepared The data updated shall be drawn into the RFB-
based on the review outcomes of the existing MIS database for the regular reports on asset
data collection system, procedures and existing type and nature, asset condition and its trend in
data collection manual statements of deterioration, asset maintenance requirements
TANROADS and TARURA. etc as required by RFB for planning purpose of
The review was carried out with respect to: maintenance activities across assets of both the
agencies.
 Attributes being collected for
Inventory and Condition assessment of 3. LEVEL OF DETAIL FOR DATA
Roads (Paved and Unpaved)
 Data Collection procedures being COLLECTION
followed
 Data Storage and its use in existing Level of Detail (LOD) depends on the purpose
Asset management systems of the for which the data is being collected.
respective agencies (TANROADS- World Bank guidelines refer these LOD as
RMMS and TARURA-DROMAS) IQL (Information quality levels).
 Existing system analysed with respect
to Latest technology trends and General guidance on the IQL’s defined by
Industry Best Practices. World Bank guidelines are as given below:
Review outcomes and proposed measures to  IQL-1 represents fundamental,
overcome the gaps identified are presented in research, laboratory, theoretical, or

Page 2 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

electronic data types, where numerous This data shall be collected at different
attributes are measured. frequencies, depending on the road class.
 IQL-2 represents a typical level of Main roads and major highways shall have to
detail of engineering analyses for monitored at frequent intervals, preferably
project-level decisions. once every year, at the least at a frequency of
 IQL-3 represents typically two or not more than 2 years
three attributes, used for network-level
surveys or where simpler data Minor paved roads may be monitored at 2 – 5
collection methods are appropriate. year intervals depending on the significance of
 IQL-4 is a key attribute used in the road class.
planning, senior management reports,  Unpaved road condition assessment
or in low technology data collection.
 IQL-5 represents top level data such as Condition of unpaved roads (Gravel and
key performance indicators, which Earthen) varies after every rainfall season due
combine key attributes from several to the fact of poor drainage and loss of surface
pieces of information. material by surface runoff. In such cases the
condition survey to be conducted twice every
IQL-4 is best suitable for network level data year (Dry Season and Rainy season) to update
collection and sufficient for national level the condition of the unpaved roads. Such
planning purposes. IQL-4 is being chosen for frequent updating shall give reliable condition
the data collection and database preparation, of the asset and help in timely attention for
updating and management of the proposed maintenance which shall aid to achieve
Road asset management system of RFB, optimised asset value of the varied assets of
TANROADS and TARURA. both agencies.
Data collection forms have been prepared in The frequency may vary depending on the
line with the requirement of IQL-4. The budgetary constraint and Institutional capacity
attribute information decided shows the for the data collection/updating by respective
snapshot of the current requirement of asset agencies.
information suggested by the both the road
agencies which needs to be validated/updated Frequency decided for updating needs to be
time to time to capture all the crucial sufficient to identify all major/significant
information required for appropriate decisions changes in asset condition which will
for maintenance of assets. influence road maintenance decisions.
 Bridge condition data
4. FREQUECY OF DATA  Condition assessment data is
COLLECTION/UPDATION recommended to be collected in two
cycles.
 Regular surveys are conducted at 1 – 2
The frequency of inventory and condition data
year intervals for collecting general
collection for monitoring road, bridge, or
data on bridge conditions. More
traffic conditions on the existing asset has an
intensive investigations are done at
important bearing on the cost of surveys and
longer intervals, typically on the order
the sustainability of data collection. Data
of five years.
should be collected only as frequently as is
 Classified Traffic Volume data
required to ensure proper management of the
road network. The frequency can vary  Sample one day classified traffic data
depending upon the data of interest: to be usually collected at the least
once every year.
 Road inventory data  However on major roads the data
This data shall be once-off exercise. They are needs to collected all through the year
then updated when changes are made to the through a set of permanent traffic
road. It is common to verify/update the data at count stations.
least every five years (5 yrs).
 Paved road condition data

Page 3 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

5. LINEAR REFERENCING system (LRS) and Sublink (1km length) acting

as smallest length of the road asset and a
SYSTEM
unique identifier.
Link number for TANROADS network shall
Linear referencing is the method of storing
be assigned by bringing forward the existing
geographic locations by using relative
allocated numbers in RMMS; however
positions along a measured linear feature.
TARURA network has no such Link number
Distance measures are used to locate events
information for the road assets the same shall
along the line as shown in Figure 5-1 below
be assigned as 4 digit number with number
Figure 5-1: Linear Referencing System prefix as per the functional classification of the
road network. List of prefix numbers as per
functional classification is provided in Table
5-1 below:
Table 5-1: Link number indicators
Sl Functional Prefix numbers to
No Classification denote
classification

1 Collector roads XX

While linear referencing is an important and 2 Feeder Roads XX

unique identification of records in database.
The features which are combined to make such 3 Community XX
uniqueness in generating unique data from the Roads
database are very significant. The format for
data used for unique identity of the highway The new link number allocation will follow
ordinance is road number and link number. region-wise commencing from farthest south-
The road number is 4 digits (10001 means west end of the Region and allocating broadly
T001) and it encamp the road class and the in clockwise direction towards the north-east.
link number. The link number is unique
throughout the entire network. In the same 6. POTENTIAL SYNERIES
lines the numbering system of DROMAS BETWEEN AGENCIES FOR
follows the NBS regional and district/council
code (27001) meaning Arusha, Meru, and road OPTIMISATION
number which is 0001.
The only difference is that the road is not Network level data collection for database
sectioned. For example, a road of 4.5km length management shall be a huge exercise and
will have only one way to be identified. IN potential synergies need to be established
RMMS each road is sectioned by link (Start between agencies to elude sunk cost of data
Node to End Node) and sub link (1km length). collection on logistics.

RMMS uses multiple attribute elements (Road Below are the areas of potential synergies
number, Link number and Sublink number) for between TANROADS and TARURA.
Linear Referencing system (LRS) and is in  Roughness data and distress
line with the Best Industry practice; whereas, measurements on paved roads using
DROMAS uses only Road code/number as the Laser Crack Measurement System
only Linear Referencing Element. (LCMS).
Linear referencing system proposed for newly  Roughness data collection on unpaved
built open source relation database roads (Gravel roads in Good and fair
management system for RFB-MIS shall also condition) using 5th wheel Bump
be in line with the best industry practice and Integrator (BI).
shall use attribute elements like Road number
and Link number for Linear Referencing

Page 4 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

It is established that currently equipment Procedure for use of Navigation tools is as

availability is only with TANROADS, rather shown below:
than lending the equipment to TARURA both
Prepare procedural flowchart as shown above
agencies can collaborate during data collection
and Insert snapshots of the navigation tool
for network of roads handled by both agencies.
Further at later stages as stakeholder 7.2 Unclassified road network
influences expand for RFB this can be
A part of the network is not classified which
collaborated with roads being maintained by
could have happened due to one of the below
PO-RLG, TWS (Tanzania wildlife service),
reasons:
TFS (Tanzania forest service) etc.
 The target road is newly built and not
7. NETWORK IDENTIFICATION yet been gazetted/classified by GoT to
OF ASSETS be included as asset for any particular
agency.
 The target road might lack allocation
7.1 Classified road network of appropriate road number/other
Identification of classified road network shall linear referencing system as unique
be a two-step exercise: identifier for updating in road asset
management system
Step 1: Desktop study – through the updated  The target road might have been
shapefiles obtained by Regional offices and missed out during the database
District offices of TARURA and preparation.
TANROADS. Basic analysis on the condition  The target road might have been
of road can be done using basemap satellite upgraded to different functional
imageries through open source systems like classification.
open street maps (OSM), Google earth etc.  The target road might have been
Flowchart on the Desktop analysis is shown transferred from one agency to
below with an example: another.
 Any other unknown reason.
Such unclassified roads are difficult to be
identified since no particular spatial
information is available regarding such road.
The identification of such road can only be
Using QGIS Updated Use of done using:
as Desktop Shapefiles Satellite
analysis imageries as  Combination of Satellite imageries
Software base maps and local knowledge of District
engineers of respective agencies.
 Coordination with local community
people.
Insert an Image of Shapefile and GE image as
background showing broken or dismantled Once such network of roads are established the
road. location of such roads needs to be validated by
physical site inspection and collection of basic
Step 2: Field verification – Through the alignment data as identification details for
update shapefiles the locations of the identified further inventory and condition data collection
classified road network can be navigated for during detailed survey phase.
physical verification by engineer’s team for its
validation and further attribute data *In case of road networks awaiting to be
collection/update. gazetted; a temporary linear referencing
element to be provided to include the asset as a
The network identification to be done in part of Asset management system which can
consultation with concerned road agencies be amended at a later stage with appropriate
staff at regional and district level, local LRS assigned. Temporary referencing system
community people living around those areas, to include details as:
village heads etc.

Page 5 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Temporary LRS to be established as shown 8.2 Logistical planning

here
Allocating Road number for unclassified
road network: The proposed numbering 8.3 Team distribution and coordination
system shall be as “assigned Class of the Road planning
(alphabet) followed by county number (2 digit
number) followed by road number (4 digit
number) which shall be starting from 0001 and 9. FIELD TEAM COMPOSITION
moves on sequentially followed by underscore
and suffix “UNC” to represent unclassified
10. DEVICE FOR DATA
road network.
COLLECTION
Proposed Road numbering system format shall
be TXXYYYY_UNC whereby T represents
the class of the road, XX represents the unique Current practice in TANROADS and
Region reference number in accordance with TARURA of data collection is through manual
the provide reference document with region method using printed forms to fill all the
numbers assigned, YYYY represents the 4 attributes through site visit, further the data
digit unique number assigned to each new road collected will be verified and validated by
in the county in a series that starts from 0001 district/regional manager for further data entry
clockwise from South to East. UNC represents and updating into respective databases.
“Unclassified road network”,
Since the proposed database shall be in geo-
Illustration: If a new road has been identified spatial format along with geo-tagged attribute
as class T in Iringa region as per the information and relevant photographs. To
functionality and its traffic usage that achieve such database with manually collected
particular road shall be numbered as field data will require substantial efforts to:
T210001_UNC and immediate next road
 Create error free data entry from
identified in the south west direction of same
physical forms to digital data.
category shall be numbered in same format
with next sequential number as  Configure digital data (created from
T210002_UNC and the same shall continue physical forms) with geolocation and
moving in clockwise direction towards north- alignment details to form geo-spatial
east. database.
 Configure all relevant photographs
7.3 Bridge and other structures network (taken using digital cameras) with
Prepare methodology for Network geolocation to form geo-spatial
identification of structures (desktop study and database.
field verification) It is recommended to adopt digital data
collection to save time on data entry, possible
7.4 Traffic database network
human errors in field and during data entry and
Prepare methodology for Network to minimise the efforts for data processing (for
identification of traffic count points (desktop more details see section 15).
study and field verification)
10.1 Device for GPS data log
8. PLANNING REQUIREMENTS It is essential to have appropriate location
FOR FIELD SURVEYS accuracy (<5m) for network level data
collection. In order to achieve the required
location accuracy High accuracy GNSS
receivers are to be used. The proposed device
8.1 Annual survey cycle along with its features and specifications is
provided below:
Proposed device: EOS Arrow 100plus

Page 6 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 10-2: High precision GNSS receiver  Number of Tracked satellites: 12

(EOS Arrow 100+) GPS (15 when no SBAS) 12
GLONASS, 15 Galileo, 22 BeiDou.
 Accuracy: Horizontal Accuracy: <
2.5m 95% confidence level1
 Communication: Ports available are
Bluetooth and USB 2.0.
Bluetooth transmission: Class 1, typical
range up to 1 km.
 Antenna: Frequency range: L1, G1,
E1, B1
 Field activated options: 10 Hz, 20 Hz
Output rate; Base station RCM output;
Single Frequency RTK for 1-3 cm
Salient Features of High precision Arrow accuracy; and Atlas satellite correction
100+ GNSS receiver: services.
 Works with any GPS applications:  Limits: Maximum Speed: 1850
Arrow 100+ GNSS receiver does not Kph/999 Knots; Maximum Altitude:
require any additional software or 18,288m (60,000 ft).
hardware in order to obtain submeter
positioning. The receiver streams its
submeter location data into any 10.2 Device for Digital data collection
mapping or data collection application (Road and structures Inventory and
on any smartphone mobile device. condition data)
 Real time submeter Accuracy Android based tablets have been chosen as the
worldwide: Arrow 100+ GNSS device for data collection.
receiver takes advantage of all the
GNSS constellations for processing Figure 10-3: Android based Tablet
like: GPS, GLONASS, Galileo,
BeiDou. With SBAS corrections
available in most regions of the world,
the receiver provides 30- 60 cm real
time accuracy. In case unavailability
of SBAS in remote areas it is proposed
to use Atlas satellite lifetime
subscription service to achieve 30-
50cm accuracy worldwide irrespective
of the remoteness.
 RTK capability: Arrow 100+ GNSS
receivers also feature the ability to be
used with single frequency RTK and
can achieve very high accuracy when
baseline station is less than 10km
radius or with the availability of
CORES network.
Android based tablets will be accompanied
Device technical specifications are: with SIM cards for internet connection for web
 Receiver type: L1/G1/E1/B11, GPS, based correctional services along with
GLONASS, Galileo, BeiDou with minimum of 64 GB internal storage space to
carrier smoothing save collected field data. However for satellite
 Channels: 158-channel, parallel 1
Depends on multipath environment, number
tracking of satellites in view, satellite geometry,
baseline length (for local service) and
ionospheric activities.

Page 7 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Positional data collection no internet Figure 10-4: Activating Developer Mode

connection is required.
In order to establish a connection between
GNSS receivers and tablets, it is necessary to
install Eos Tools Pro, a real-time GNSS
monitoring application developed by Eos
Positioning. The application provides the
following features within its user interface:
 Let’s you track the number of
satellites available and used, and
which differential correction status is
being used
 Compatible with Arrow Series GNSS
receivers
 Available for iOS, Android, and
Windows devices
 Can support any third-party apps
Furthermore, Android device shall be installed
with proposed field data collection software
“SW maps” loaded with digitised forms for
data collection (for more information see
section 11.1).
Steps to Connect GNSS Receiver with
GNSS Monitoring Application:
Step 1: Install EOS Tools Pro App
Download and install EOS Tools Pro on your
device from a digital distribution service (like
Google Play Store).
Step 2: Activate Developer Mode
Go to device's Settings > Select 'About Tablet'
> Tap 'Software Information' > Tap 'Build
Number' seven times to activate developer
mode

Step 3: Select Mock Location App

Go back to device's Settings > Scroll down
and select 'Developer Options' > Within
Developer Options, locate 'Select mock
location app' > Select 'EOS Tools Pro' as the
Mock Location App

Page 8 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 10-5: Selecting Mock Location App Figure 10-6: Connecting to GNSS Receiver

*With these settings configured, you are now Step 6: Configure EOS Tools Pro App
ready to connect your GNSS receiver to the Settings
EOS Tools Pro app*
Access the app's settings menu > Locate and
Step 4: Pair Your Device with GNSS toggle 'Replace Device Location' to 'ON'
Receiver
Figure 10-7: Configuring Device Location
Turn on your GNSS receiver > On your
device, go to 'Bluetooth Settings‘ > Scan for
available devices > Select your GNSS receiver
and pair it
Step 5: Connect to GNSS Receiver
Inside the EOS Tools Pro app, find and tap on
the 'GNSS Receiver' soft key

Again access the app's settings menu > Change

the 'Altitude Reference' setting to
'Receiver_MSL'

Page 9 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 10-8: Configuring Device Altitude Figure 10-9: ATLAS Differential Correction
Reference

Step 7: Wait for Connection to Complete

In the EOS Tools Pro app, monitor the
'Differential Source' status > Initially, it
displays 'None' > Wait patiently until the
source changes to 'Atlas'

*For the first connection, ensure the antenna

remains stable, and stand in a location free
from obstacles such as tall buildings or trees
until convergence is attained.*
Step 8: Accessing real-time information
Upon establishing a successful connection,
users can access information on the number of
satellites in view and those currently being
utilized in the 'Satellite' tab. Additionally, the

Page 10 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

application displays the GPS, Glonass, corresponding to the device location and Eos
Galileo, and BeiDou satellites currently in use. Receiver. It is essential for these values to
align accurately.
Figure 10-10: Satellite Tab
Figure 10-12: Map View Tab

In the 'RTK Status' tab, users have visibility

into the current differential correction source 10.3 Device for Roughness and distress
in use, as well as the horizontal accuracy (H measurements data collection on
RMS). paved roads
Figure 10-11: RTK Status Tab ROMDAS is an acronym for Road
Measurement Data Acquisition System which
is Survey equipment manufactured by Data
Collection Limited (DCL) from New Zealand.
The assessment of the condition of the
pavement will be conducted from a specially
prepared condition data collection vehicle
fitted with ROMDAS equipment.
This data collection vehicle will be operated
by a driver and three specially trained
Surveyors. The first Surveyor is responsible
for the automatic measurement of roughness
system as shown in Figure 10-13.
Figure 10-13 : Collection of Automated
Roughness measurement

In the 'Map View' tab, users can observe

latitude, longitude, and altitude information

Page 11 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

intuitive SW Maps Template Builder, allowing

you to create customized templates for data
collection. SW Maps Template Builder is a PC
based application.
SW Maps Template Builder
Key Features:
 A free utility for creating project
templates for SW Maps.
 A convenient PC based app for creating
templates for use with SW Maps.
 Can be used to create normal (swmt) or
The second Surveyor is also responsible for read-only (swmr) templates.
recording the visual assessment of the road
 Read-only templates do not allow the user
condition and the legible recording of this
to add or remove layers and attributes.
information on the forms provided as shown in
Appendix A1 – Form to paved Road Condition Installation:
Survey Step 1: Go to
The third Surveyor is responsible for overall http://softwel.com.np/download_software and
observations and judgements of pavement download the SW Maps Template Builder.
distress. The driver of the vehicle will be Step 2: Run the installer TemplateBuilder.msi
responsible for driving the vehicle at a fixed
speed of 40kph in the lane wheel-path. The Step 3: Click “Next”
driver is additionally and specifically Figure 11-14: First Screen of SW Maps
responsible for the safe conduct of the survey Template Builder Installation Wizard
and should be fully aware of prevailing traffic
conditions at all times. The vehicle will be
fitted with safety gears such as an amber
rotating beacon, red flags, signboard etc.
10.4 Device for Roughness data collection
on unpaved roads
10.5 Device for inaccessible structures
10.6 Device for Traffic data collection

11. SOFTWARE FOR DATA

COLLECTION

11.1 SW maps for Road and Structure Step 4: Change the install destination if
Inventory and condition data required and choose whether to install for all
collection users or the current user only. Click “Next”
SW Maps is a GIS app designed for collecting,
presenting, and sharing geographic
information on phones and tablets. It is a free,
open-source application that can be
customized for various purposes, including
Paved and Unpaved road assessments,
Structures Inventory, and condition surveys,
with the option of capturing geo-referenced
pictures.
Workflow can be enhanced by combining the
power of the SW Maps application with the

Page 12 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 11-15: Second Screen of SW Maps  Enter the layer name, select the feature
Template Builder Installation Wizard type and define the layer style (point
color, line width and point shape).
Figure 11-18: Adding a Layer

Step 5: Click “Next” and wait until the

installation is complete.
Figure 11-16: Third Screen of SW Maps Step 3: Adding Attributes to Layers
Template Builder Installation Wizard
 Select the layer to which the attribute is to
be added. Press the Add button under the
attribute list.
 Enter the attribute name and the data type.
If the data type is Options, enter the
choices for the attribute in the Options
grid. Press Save to add the attribute.
Figure 11-19: Adding Attributes to Layers

Using SW Maps Template Builder:

Step 1: Open SW Maps Template Builder
Double-click to open the application and start
creating templates.
Figure 11-17: SW Maps User Interface

Step 4: Editing Existing Layers and

Attributes
 To edit a layer, select the layer and press
Edit button under the layers list.
 To edit an attribute of a layer, first select
the layer. Then select the desired attribute
on the attributes list and press the Edit
button.
Step 2: Adding a Layer
Step 5: Deleting Layers and Attributes
 Press the Add button under Layers.

Page 13 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Layers and attributes can be removed from the  Import feature layers from templates or
template by selecting the layer or template in existing projects
the respective list, and pressing the  Share or export collected data as KMZ,
corresponding Delete button. Shapefiles or as CSV
Figure 11-20: Editing & Deleting Layers and  Share templates or projects with other
Attributes users
Requirements:
SW Maps is currently available for devices run
ning Android 4.0.3 and above. Google Play Se
rvices is required and will be updated if necess
ary.
Installation:
SW Maps is available from a digital
distribution service (like Google Play Store).
SW Maps User Interface:
The SW Maps user interface has the following
components as shown in the figure.
Figure 11-22: The SW Maps App Screen
Step 6: Saving and Opening Templates
 To save the template, click the File >
Save menu.
 To save as a new template, click File >
Save As.
 To open an existing template for editing,
click File > Open.
Figure 11-21: Saving and Opening
Templates

Installing Templates and Creating Project

in SW Maps:
SW Maps Application Step 1: Transfer Templates to Your Device
Key Features:  After Installing SW Maps app on your
mobile device, connect your phone or tablet
 Online Base maps: Google Maps or Open
to your PC.
Street Map
 Locate the SW_Maps/Templates folder on
 Support for multiple mbtiles (SQL lite
the device storage.
database files) and KML overlays
 Copy the saved .swmt or .swmr file from
 Define multiple feature layers with
your computer to this folder on your
unique attributes
device.
 Record GPS tracks, with distance
measurement

Page 14 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 11-23: Transferring Templates to Figure 11-24: Creating Project

Device

 Under the ‘Project Name’ subheading, type

in the desired name for your project.
 Within the ‘Layers’ subheading, select
‘Template’ as your layer type > Choose the
template you previously imported from
your PC > Finally, tap ‘Create’.
Figure 11-25: Creating Project (Cont’d)

Step 2: Create a New Project in SW Maps

SW Maps stores all recorded data and layer de
finitions in a project database.
 Open the SW Maps app on your mobile
device > At the top right corner of the
screen, tap on the three vertical dots >
From the dropdown menu, select ‘Projects’.
 Inside the ‘Projects’ section, tap the ‘+’
icon.

*To delete a project, select the project in the li

st and then press the Bin icon beside the proje
ct’s name on the list.*
Recording Data in SW Maps:
Georeferenced points are used to record data
for both point features and line features. Each
line feature necessitates two points for one
entity, namely the start and end points.
 Recording RICS Data

Page 15 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

The initial step before commencing the Figure 11-27: Layers to Collect RICS
survey is to activate the record track Data
option. This feature allows the user to
capture and record the path they traverse.
To start recording the track, click Record
> Record Track > Enable it by clicking
the soft key at bottom right.
Figure 11-26: To Record Track

*Once the entire length has been covered,

deactivate this feature by following the
same steps.*
There are 18 layers designated for
gathering road inventory and condition
data. Initiate the data recording process
by selecting Record > Record Feature >
choose the layer from the dropdown menu
> begin entering the data.

Page 16 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 11-28: To Record Feature Figure 11-29: Measuring Carriageway

Width at Site

Figure 11-30: Soft Key at Bottom Right to

Save the Point Data

"A- Inv Basic" is a mandatory initial

collection for each section, encompassing
fundamental details like region, district,
council, road name, road class, road
number, date, from, to, start node, end
node, carriageway width, roadway width,
road reserve width, number of lanes,
carriageway type, cross section, adjacent
land use, climate, shoulder type, shoulder
width, and horizontal and vertical
geometry. The enumerator is required to *If any information requires editing after
position themselves at the starting point, saving the point, simply click on the saved
gather the relevant information, and input it point on the screen, and the saved data will
into the corresponding field of the digitized become accessible. The enumerator can
form. Once all information is entered, the then update the information and click the
enumerator should add the point by save soft key to retain the edited details.*
clicking the icon located at the bottom right "B- Inv Drainage" is employed to gather
of the screen. A new point must be drainage information (side, type, lining
collected as and when any of the feature material and condition). Although it is a
changes. line feature, as mentioned earlier, it must be
recorded as a combination of two points,
namely the start and end points. The user is
instructed to position themselves at the
starting point, gather the necessary
information, input it into the form, and save
the point. Subsequently, when the feature
concludes, the user should collect another

Page 17 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

point at the end. Additionally, it's important the visual inspection of the enumerator,
to note that in the digitized form, there is an who assesses that the entire section exhibits
attribute labelled "location". At the starting a consistent condition. The attributes are
point, it must be selected as "start", and at categorized into those common to both
the end, it must be designated as "end". paved and unpaved roads, exclusive to
unpaved roads, and exclusive to paved
Figure 11-31: Collecting Start & End for
roads. If the road is unpaved, the attributes
Line Features
related to paved roads can be marked as
N/A, and vice versa.
"P- Cond Unpaved Spot Improvement,"
"Q- Cond Unpaved Special Drainage," and
"R- Cond Paved Loss of Paved Surfacing"
are point features. The user must stand at
the feature location, collect the required
details, and save the point.
Each layer includes an additional attribute
for pictures. The user has the option to
click on this feature and capture images.
However, it's important to note that the
option to capture a picture will only be
accessible after the user has saved the
point. After the user saves the point, a
dialogue box will appear with the message
"Feature Recorded." The user can click
"Yes" to access the window for editing
values. Subsequently, pictures can be taken
by clicking on the camera icon.
Alternatively, if the user wishes to capture
a picture of a previously collected point,
they should select the desired point in the
"C- Inv Mitre Drains", "D- Inv Junctions", user interface and take the picture while in
"F- Inv Landmarks", "G- Inv Culvert", "J- edit mode.
Inv Other Road Elements" and "K- Inv
Road Crossing" are point features. The user
is required to stand at the feature location,
gather the necessary details, and save the
point.
"H- Inv Road Structures", "I- Inv
Vegetation", "L- Inv Footway", "M- Inv
Cycle Track" and "N- Inv Median" are line
features and should be recorded as a
combination of start and end points.
"E- Inv Safety Features" consists of
attributes, some of which are line features
(Safety Barrier, Pedestrian Barrier, Traffic
Island, Street Light, and Road Studs) and
must be captured as combination of two
points, while others are captured as point
features (Bollard, Traffic Light, Road Sign,
Hump, Rumble Strip, and Marker Post).
"O- Cond Road Surface" is collected as a
point feature at the conclusion of a section.
The endpoint should be determined through

Page 18 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

Figure 11-32: Option to Click Pictures Figure 11-33: Layers to Collect BMS Data

All layers are gathered as individual points.

Later, in the data processing stage, these
points will be consolidated into a single
point encompassing the entire dataset.
The enumerator will record the features as
mentioned in the respective layers, measure
or inspect them on-site, and input the
Please take note that "A- Inv Basic" and information into the digitized form. After
"O- Cond Road Surface" were initially entering the information, the user must save
collected as points for each section. These the point. To capture pictures, the point
will be converted to line features for their must be saved first, and later, pictures can
respective sections in the later stages of be taken, following the same process as
data processing. explained in the RICS section.
 Recording BMS Data Figure 11-34: Data Collection at Site
There are 7 layers designated for gathering
Bridge inventory and condition data. For
bridges, commence the data recording
process in a manner similar to RICS data
by selecting Record > Record Feature >
choose the layer from the dropdown menu
> begin entering the data.

"A-Inventory- Identification Data"

comprises essential details for identifying a
bridge, including information such as
region, district, council, bridge/river name,
bridge type, carriageway width, maximum
clear height, road code, bridge code,
number of spans, footway width, maximum
clear width, inventory date, overall width,
maximum gross vehicle weight limit,
construction year, road name, total length,
bridge crossing type, maximum axial load
limit, bridge status, statistical system, type
of modifications, and modification date.

Page 19 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

"B-Inventory- Superstructure" includes Figure 11-35: Uploading Data from SW

inventory details pertaining to the Maps
superstructure, such as span number, span
length, surfacing type, deck slab type,
beam/girder type, number of beams/girders,
beam/girder height, beam/girder width,
beam/girder diameter, pier capping width,
pier capping height, parapet wall type,
expansion joint type, bearing type, drainage
system type, and attached utilities type.
This layer needs to be replicated
repeatedly, matching the number of spans.
The span number should be input into the
"Span No." field corresponding to the span
under investigation.
"C-Inventory- Abutments and Piers"
encompasses inventory information,
including details such as span number,
abutment type, abutment height, abutment
width, abutment foundation type, abutment
protection type, wingwall type, pier type,
pier height, pier width, pier diameter, pier
foundation type, and pier protection type.
This layer needs to be replicated
repeatedly, matching the number of spans.
The span number should be input into the
"Span No." field corresponding to the span
under investigation.
"D-Inventory- Approaches" includes
inventory information concerning
embankment height, number of guideposts,
guardrail length, rumble strips, speed
bumps, and traffic signs.
"E-Condition- Superstructure," "F-
Condition- Abutment & Piers," and "G-
Condition- Approaches" encompasses
condition information related to the
features collected in the inventory. It is
important to note that Layer E and Layer F
need to be replicated repeatedly,
corresponding to the number of spans.
The same procedure will be applied for
other structures such as culverts and
retaining walls using their respective
digitized forms.
Uploading Data from SW Maps:
Once the data has been collected on-site, it can
be uploaded to cloud storage, shared, or
exported in various formats such as KML,
shapefile, CSV, and more as shown in the
figure below.

Page 20 of 22
Harmonised data collection and procedures manual – RFB-MIS, DROMAS and RMMS

11.2 AR traffic counter for traffic data

collection

12. DATA COLLECTION

PROCEDURE

12.1 Road Inventory data collection

12.2 Condition assessment of paved roads
12.3 Condition assessment of unpaved
roads
12.4 Structure Inventory data collection
12.5 Visual condition assessment of
bridges and other structures
12.6 Classified Traffic count procedure

13. DATA TRANSMSSION AND

STORAGE

14. QUALITY
ASSURANCE/QUALITY CONTROL
(QA/QC) OF FIELD DATA

14.1 Quality control checklist

14.2 Quality control procedures
14.3 Quality Assurance procedures

15. DATA CLEANING AND

PROCESSING

15.1 Alignment data cleaning

15.2 Attribute data cleaning
15.3 Data processing
15.4 Creation of geo-spatial database

Page 21 of 22