xyg

8/11/2019 Xyg

1/13

Asian Development Bank

Technical Assistance ProjectTA-7297 (MON): Road Database Development Using

Geographic Information System, Mongolia

ROMDAS and dTIMS CT

Data Processing User Guide

Prepared by:

Andy Kim(LEA International Ltd.)

August 2010

8/11/2019 Xyg

2/13

ROMDAS and dTIMS CT Data Processing User Guide

1TA-7297 (MON): Road Database DevelopmentUsing Geographic Information System

Table of ContentsPage

1 About 2

2 Data Collected by the ROMDAS 2

3 What Data to Process as a Priorit y 2

4 ROMDAS Survey Data File 2

5 ROMDAS Keycode Rating 3

6 Base Elements in dTIMS CT 3

7 Location Referencing 4

8 Roughness Data 5

9

Cracking Data 7

10 Pothole Data 8

11 dTIMS CT Data Transformations 10

Appendices

Appendix A: ROMDAS Keycodes

Appendix B: Data to be Transformed for LCC Analysis

8/11/2019 Xyg

3/13



1 About

This user guide describes the processing of the data collected by the ROMDAS for importing intodTIMS CT, and the data transformations necessary within dTIMS CT to allow for the Life CycleCost (LCC) analysis.

2 Data Collected by the ROMDAS

The types of data collected by the ROMDAS are as follows:

Road network definition data includes location reference points, road lengths, GPScoordinates, and video.

Road roughness data- collected at 100 metre intervals.

Road condition data measurement of pavement defects such as cracking, potholing,edge break, etc.

Road inventory items such as km posts, bridges, culverts, intersections, signs, busstops, etc.

The surveys are presently being carried out on some 2,300 km of paved roads

Details on the operation of the ROMDAS as well as a description of the data files that itgenerates are described in the ROMDAS Users Guide.

3 What Data to Process as a Priori ty

The ROMDAS has been configured to collect a large number of event types related to roadcondition and inventory. It would however be difficult to process and import them all during theimplementation period given limited time and resources available.

Therefore, the LCC analysis is given high priority and only the data items that are used in theanalysis will initially be processed and populated in dTIMS CT. Specifically, they are as follows:

Location Reference Points

Road roughness

Cracking (transverse, longitudinal, and alligator)

Potholing

The other data collected may later be processed either by the Consultant or the DOR as timepermits.

4 ROMDAS Survey Data File

Each ROMDAS survey generates a an MS Access database file. The tables in this database areshown below:

8/11/2019 Xyg

4/13



The tables to be processed for the immediate moment are as follows:

LRP (Location Reference Points) Roughness (Processed)

KeyCode (Raw)

5 ROMDAS Keycode Rating

The keyboard rating codes have been configured as perAppendix A.

As a departure from the rating criteria originally proposed by the International MaintenanceSpecialist (Mr. Phil Salt), the condition data has been modified to have only one severity level forthe three types of cracking (Transverse, longitudinal and alligator), drain condition, shouldercondition and edge break. This was done to accommodate the 40 odd road furniture events theDOR wanted to collect. Potholes however are measured in three severity levels (3m).

All the condition items are assumed to be absent or in good condition if not selected. Otherwisethey are in poor condition or full width pavement cracks for transverse and alligator cracking.

6 Base Elements in dTIMS CT

In dTIMS CT, all locations (i.e. from/to locations in every Perspective) are linearly referencedagainst a Base Element. In our case, Base Elements are the road routes defined in Mongolia(e.g. Route A0401).

8/11/2019 Xyg

5/13



The dTIMS CT database has already been populated with these Base Elements and minormodifications (e.g. adjusting the route length) would be made from within dTIMS CT.

7 Location ReferencingAll locations are linearly referenced against the start point of the Base Element (in kilometres).

In the event that a Base Element was surveyed in more than one survey, it is important to adjustthe chainages in each survey so that they line up properly and are referenced against the startpoint of the Base Element.

It is not necessary, by the way, that the start chainage location of a Base Element is zero either.For example, Route A0401 starts at kilometre 19 (because the first 19 km of that road is part ofthe Ulaanbaatar City).

Here is a working example for Base Element A0401:

First Survey File

1. Determine the start and end LRP chainages for the first survey for A0401. In ourexample, survey starts at chainage 0 and ends at chainage 43.956 (km post 63).

8/11/2019 Xyg

6/13



2. If the route does not start from km 0, then all the locations in the survey file needs to be

shifted. In this example, 19.0 km has to be added every location.

Note: ROMDAS records distances in metres while the dTIMS CT database stores them inkilometres. Therefore, convert all ROMDAS distances from metres to kilometres.

The dTIMS CT import file for the Location Reference Points would look like this:

dTIMS CT Import File for LRPPerspective

Subsequent Survey File

1. Check that the start location of the next survey is the same location as the end location ofthe previous survey.

2. Adjust the chainages so that they start at the end point of the previous survey along theBase Element. In this example, we would have to add 62.956 km (19.000 + 43.956) toevery location.

8 Roughness Data

In the Roughness_Processed table in the ROMDAS database, the CHAINAGE field representsthe TO location.

8/11/2019 Xyg

7/13



When preparing a dTIMS CT import file for this in spreadsheet form:

1. Insert a new column named FROM, and for each record, fill it with the TO location of theprevious record (or you can subtract the length of the section from the TO value of thesame record).

2. You will often find that the survey overruns the intended end of the survey. You need toadjust the last record(s) so that the TO chainage of the last record is the same as the endLRP for the survey. (For A0401-1, there are surplus records and the last valid record is

FROM = 43.866. The TO value for this record should be 43.956. Records after thisshould be deleted.)

3. Increment all FROM and TO chainages as per above (e.g. 19.000 km)4. Change the field names as necessary in order to match those attribute names in dTIMS

CT.

The import file would look like this:

dTIMS CT Import File for RoughnessPerspective

ROAD FROM TO SURVEY_DATE ELEMENTID SPEED BI_COUNT_LEFT BI_COUNT_RIGHT IRI

A0401 19.000 19.100 24/05/2010 A0401-0000 3.8 2240 2450 4.61

A0401 19.100 19.200 24/05/2010 A0401-0001 28.9 2700 2180 4.75

A0401 19.200 19.300 24/05/2010 A0401-0002 31.4 4180 3640 6.54

A0401 19.300 19.400 24/05/2010 A0401-0003 31.7 3250 2790 5.25

A0401 19.400 19.500 24/05/2010 A0401-0004 31.6 4270 3720 6.66

A0401 19.500 19.600 24/05/2010 A0401-0005 33 3700 3170 5.85

A0401 19.600 19.700 24/05/2010 A0401-0006 32.7 3710 3110 5.81

A0401 19.700 19.800 24/05/2010 A0401-0007 32.9 4840 3510 6.89

A0401 19.800 19.900 24/05/2010 A0401-0008 34.3 6960 6170 10.38

A0401 19.900 20.000 24/05/2010 A0401-0009 35.2 5260 3990 7.55

A0401 20.000 20.100 24/05/2010 A0401-0010 35.3 3840 3910 6.51

A0401 20.100 20.200 24/05/2010 A0401-0011 34 5880 4850 8.63

A0401 20.200 20.300 24/05/2010 A0401-0012 34.5 5350 3320 7.09

A0401 20.300 20.400 24/05/2010 A0401-0013 32.7 4490 4110 7.11

A0401 20.400 20.500 24/05/2010 A0401-0014 32.8 7420 5140 9.9

(and so on.....)

A0401 62.886 62.956 24/05/2010 A0401-0440 0.6 4758 5507 9.47

8/11/2019 Xyg

8/13



9 Cracking Data

The pavement cracking data is collected using the ROMDAS KeyCode rating system and storedin the KeyCode_Raw table (along with all the other KeyCode items).

The three types of cracking (transverse, longitudinal, and alligator) are each stored in its ownPerspective in dTIMS CT and therefore each must be extracted separately from the ROMDAS

data file and a separate dTIMS CT import file must be create for each.

CHAINAGE_START CHAINAGE_END EVENT_DESC

27 2,241 transverse crackings

4,430 4,527 transverse crackings





4,431 4,727 longitutinal crackings





27,697 27,823 alligator cracking35,617 35,747 alligator cracking

35,838 36,956 alligator cracking



Same principles with respect to location referencing are to be applied for this data.

In addition, because the data records are produced during survey by pressing an event keywhenever a defect is observed, there will be gaps for those sections of road where no defectswere observed. For purposes of indicating in the database that the absence of a record actuallymeans that it was observed to have no defect (as opposed to the data being missing), we needto create records with zero defect values for those gaps.

8/11/2019 Xyg

9/13



As the values in the EXTENT attribute field in dTIMS CT, enter either 100, if defect of that typewas recorded, or 0, if no defect was recorded for that section.

dTIMS CT Import File for Cracking_TransversePerspective

ROAD FROM TO ELEMENTID SURVEY_DATE EXTENT

A0401 19.000 19.027 A0401-0000 24/05/2010 0

A0401 19.027 21.241 A0401-0001 24/05/2010 100

A0401 21.241 23.430 A0401-0002 24/05/2010 0

A0401 23.430 23.527 A0401-0003 24/05/2010 100

A0401 23.527 23.708 A0401-0004 24/05/2010 0

A0401 23.708 54.313 A0401-0005 24/05/2010 100

A0401 54.313 54.352 A0401-0006 24/05/2010 0

A0401 54.352 54.805 A0401-0007 24/05/2010 100

A0401 54.805 56.016 A0401-0008 24/05/2010 0

A0401 56.016 62.956 A0401-0009 24/05/2010 100

dTIMS CT Import File for Cracking_LongitudinalPerspective


A0401 19.000 23.431 A0401-0000 24/05/2010 0

A0401 23.431 23.727 A0401-0001 24/05/2010 100

A0401 23.727 23.835 A0401-0002 24/05/2010 0

A0401 23.835 54.308 A0401-0003 24/05/2010 100

A0401 54.308 54.803 A0401-0004 24/05/2010 0

A0401 54.803 56.011 A0401-0005 24/05/2010 100

A0401 56.011 56.796 A0401-0006 24/05/2010 0

A0401 56.796 61.334 A0401-0007 24/05/2010 100

A0401 61.334 62.956 A0401-0008 24/05/2010 0

dTIMS CT Import File for Cracking_AlligatorPerspective


A0401 19.000 46.697 A0401-0000 24/05/2010 0

A0401 46.697 46.823 A0401-0001 24/05/2010 100

A0401 46.823 54.617 A0401-0002 24/05/2010 0

A0401 54.617 54.747 A0401-0003 24/05/2010 100

A0401 54.747 54.838 A0401-0004 24/05/2010 0

A0401 54.838 55.956 A0401-0005 24/05/2010 100

A0401 55.956 58.789 A0401-0006 24/05/2010 0

A0401 58.789 58.809 A0401-0007 24/05/2010 100

A0401 58.809 62.278 A0401-0008 24/05/2010 0

A0401 62.278 62.956 A0401-0009 24/05/2010 100

10 Pothole Data

First, all the pothole events must be extracted from the ROMDAS data:

8/11/2019 Xyg

10/13



CHAINAGE_START CHAINAGE_END EVENT_DESC

191.4 191.4 Pothole - S

8/11/2019 Xyg

11/13



ROAD FROM ELEMENTID SURVEY_DATE POTHOLE_RATING

A0401 19.191 A0401-0000 24/05/2010 1

A0401 19.209 A0401-0001 24/05/2010 1

A0401 19.227 A0401-0002 24/05/2010 1

A0401 19.316 A0401-0003 24/05/2010 1

A0401 19.339 A0401-0004 24/05/2010 1

A0401 19.360 A0401-0005 24/05/2010 1

A0401 19.401 A0401-0006 24/05/2010 2

A0401 19.493 A0401-0007 24/05/2010 1

A0401 19.504 A0401-0008 24/05/2010 1

A0401 19.526 A0401-0009 24/05/2010 1

A0401 19.560 A0401-0010 24/05/2010 1

A0401 19.684 A0401-0011 24/05/2010 2

A0401 19.698 A0401-0012 24/05/2010 2

A0401 19.752 A0401-0013 24/05/2010 1

A0401 19.774 A0401-0014 24/05/2010 1

A0401 19.829 A0401-0015 24/05/2010 1

A0401 19.885 A0401-0016 24/05/2010 1

A0401 19.924 A0401-0017 24/05/2010 1

A0401 19.944 A0401-0018 24/05/2010 1

A0401 19.977 A0401-0019 24/05/2010 1A0401 20.013 A0401-0020 24/05/2010 1

A0401 20.043 A0401-0021 24/05/2010 2

A0401 20.106 A0401-0022 24/05/2010 2

A0401 20.131 A0401-0023 24/05/2010 3

A0401 20.146 A0401-0024 24/05/2010 3

11 dTIMS CT Data Transformations

Once all of the ROMDAS data has been imported into dTIMS CT, several data transformationsare performed to prepare the data for LCC analysis.

The data items are transformed to the Contract_SectionsPerspective which will be the LCCanalysis sections.

The data items to be included are listed in Appendix B .

More to come.....

8/11/2019 Xyg

12/13

Appendix A:

ROMDAS Keycodes

8/11/2019 Xyg

13/13

Appendix B:

Data to be Transformed for LCC Analysis

Perspective Type Attributes Description

Base Section Road_ClassRoad_Number

Route_Number

Route_Description

Inventory Section Pave_type BIT. CON, GRA, EAE, EAT

Width Pavement width in m

HSNEW Thickness of most recent surfacing in mm

HSOLD Thickness of old surfacing(s) in mm

Roughness Section IRI Roughness m/km

Speed

Cracking_transverse Section Extent 0/ 100

Cracking_longitudinal Section Extent 0/ 100

Cracking_Alligator Section Extent 0/ 100

Potholing Point Rating 1,2,3

Pavement_history Section AGE3 Years since last resurfacing

AGE4 Years since construction or reconstruction

Pavement_strength Section Deflection Benkelman beam deflection

SNP Structural Number of Pavement

Traffic Section AADT_Car

etc

xyg

Documents