14.6.2007 / Reijo Prokkola, Matti Raekallio I - Road Data Bank in the Finnish Road Administration...

14.6.2007 / Reijo Prokkola, Matti Raekallio

I - Road Data Bank in the Finnish Road Administration (Finnra)

Reijo Prokkola, Road Data ExpertMatti Raekallio, Data ManagerFinnra, Central AdministrationIT and Road Data Services

Road Data Bank in the Finnish Road Administration (Finnra)


Contents of the presentation

Use of road data in Finnra

Back ground for Development

Details of Road Data Bank

Guidelines for the development of RDB in Russia



Use of Road Data in Finnra

Information for decision makers

Asset management• planning of road maintenance actions• budgeting in national and regional level• counting asset value of road network

Level of service of road network / road section• to guarantee the fluency of traffic

Traffic safety• identify reasons for accidents• make roads safer for road users



Data transfer through life cycle: a Vision

Planning & Desing Construction

STANDARD PRODUCT MODEL

Real-time, shared and updated

Maintenance



Challenges

Two levels of information:• Network level, network model, 100 %, +/- 3 meters • Design level, product model, projects only, +/- 1 cm

Cost / benefits of collecting data for decision making

Maintenance and quality of data

Several experiments of procurement going on:• Long term contracts for maintenance / whole life cycle• Pavement, bridge, lightning etc. management contracts

Outsourcing / insourcing information services

Short life cycle of information technology



Goals of system development

SupportSupport

DBDB

ProcurementProcurement

RDBRDB

PlanningPlanning

GISGISDBDB

CustomCustom

DBDB

TrafficTrafficmanagementmanagement

BDBBDB

IntegrationIntegration

Data WarehouseData Warehouse Additional valueAdditional value DOCDOCDWDWIMSIMS

Distribution of InformationDistribution of Information

Data InformationData Information ServicesServices TPTP

Data ArchitectureData Architecture

Development of data servicesDevelopment of data services

UDDIUDDI

Gen

era

l Info

rmatio

n S

erv

ice M

od

el



Development of Centralized Data Warehouse

GIS-BaseLocation

RDBRoads&Condition

BDBBridges&Cond.

ROADSegment



RDB in Finnra

First RDB in 1970's• ADB, BDB and ADB• Condition data and management systems in 1980's• Personal computers and GIS in 1990's

Latest version of RDB introduced beginning of 2006• The technical frame is based on Oracle IAS10i (J2EE, Forms 9 etc.) and

Oracle10.2 database. • Web-based applications

40 data types, 1-10 data/each type, total 150 different data• most used data types: functional class, maintenance class and traffic

amounts (ADT)• condition data is not in the RDB



Interfaces of the Road Data Bank today

Point, section and areal data

Maps

Road geometry

Road address

Data description

Data 1 Data4 Data5Data3Data2 DataX

Batchupdating

FilesViewDirect

updating

Data tables

Updating

Web-applications

Input Output

GIS

RDB

Mobile use

Othersystems

and services

Ex.Digiroad

Interface co

mp

on

ents

(EJB

, PL

SQ

L, X

ML

, So

nic)

obj

objobj

obj


10


Data model of the RDB

FEATUREWITH LENGTH

CARRIAGEWAY

POINTFEATURE

POINT

CONTACTPOINT

NODE

JUNCTION

FEATURES OFJUNCTION

ADDRESS-HISTORY

ROAD

POINT

FEATUREWITH LENGTH

FEATUREWITH LENGTH

POINTFEATURE

POINTFEATURE

Start End

SEGMENT GEOMETRY

ROAD-SECTION

GIS

POINTFEATURE

BRIDGE

BDB


11


Road Address Code System

• Each road has an unique number• Roads are divided into sections in main

junctions• The average lenght of sections is 5 km• Direction of measuring is the increasing

numbering of sections

• The object is located by distance along the road measured from the start of the section

• An object with length is defined by the location of its start- and endpoints

The address is: 512 / 002 / 2893 m

001

Road = 512Sections 1, 2 and 3

003

002


12


The information stored in the RDB

1. Name of the road

2. Links length (m)

type: public road, ferry, street etc.

history of address code system

road region and administrative road class

3. Nodes and intersectionscoordinates

name of intersection or crossing

classification: grade intersection / grade-separated, reference points, others

traffic lights

pre-selection lane, canalization, right-of-way

4. Data by distance

Sight distancesight distances of 150, 300 and 460 m, percent of the length of road section

Curvature - angle, radius and direction

Inclination longitudinal inclination

direction

Municipality, province and region Maintenance area Road classes

functional class

European road

Maintenance classeswinter

pavement


13



4. Data by distance

Constructive measures method and time

Administrative measures change of the administrative road class

Motorways and number of carriage ways Width of roadway (0.1 m) Pavement of the road Land use & Built-up areas

status in the network of the built-up area

type of land use

Groundwater area class of area

protection

Subgrade layer specialities

4. Data by distance

Geogrids in pavement Auxiliary lanes

number of lanes

type: overtaking, public transport etc.

Width of shoulder (0.25 m) Pedestrian and bicycle way

ID and type

separation from road

responsibility of maintenance

Lightning type of pole

maintenance contractor

Speed limit (permanent) type of limit

speed limit (km/h)


14



4. Data by distance

Special investigations project, identification

Width of pavement (0.1 m) Traffic volumes

year of census

Average Daily Traffic (ADT) by vehicle types

types of yearly variations

peak hour traffic

Bearing capacity value of spring bearing capacity

standard deviation of mean

Maintenance contractor area Pavement type by lane Pavement maintenance actions

information about materials

method and impact

5. Data by point

Sight distance (m) Fixing points and landmarks

description of point by type and location

Railway grade crossingsafety equipment

Technical devicesService and rest areas

type/level of service

Bus stops Location of traffic census Bearing investigation

bearing capacity

deflection by various dimensions

thickness of pavement


15



5. Data by point

Intersections of private roads various information (main roads only)

Bridge ID (connection to Bridge Data Base) and name

type of bridge: waterway bridge etc.

weight limit

Underpass number and name of underpass

type of underpass

detour possibility

Height restrictionWidth restriction

6. Traffic accidents

Various data about the conditions, participants and consequences of accidents

7. Data types of regions

Several types, optional not nationwide


16

14.6.2007 / Reijo Prokkola

Maintenance of data in RDB

Road regions are responsible for updating data• measurement programs (preparing or approving)• data quality (regional level)

Central administration is responsible for coordination of principles and rules for updating • managing the contents of RDB• preparation of procurement contracts• developing procurement models• data quality (national level contracts)

Users are responsible for reporting faults in data quality


17


Data Quality

Accuracy of geometry is 1 - 3 meters.

Accuracy of attribute data is 0,5 % within the length of road section.

The data base will not contain real time data but the changes of the road network and attributes are updated continuously.

>>> Statistics made per 1.1. each Year

1.6.2007 / Markku Tervo

II - Guidelines for development of RDB in Russia

Markku Tervo, Procurement ManagerFinnish Road Administration,Oulu Road Region


19

1.6.2007 / Markku Tervo 19

2007 2010 2015

Steps to the visio

VISION2015 -2020

VISION2015 -2020

Strategy - pipe

STEPS TO THE FUTURE !!!• plan the future – take/make goals• take small steps – do not try jump to the visio• FIRST principles – then regional work – then RDB of Russia

Guidelines for development of RDB in Russia 20


FIRST STEP

Creating common principles of road data bank• numbering roads• creating principles for data record

• road number, • road section, • length from the beginning of road section• etc

• creating the structure of RDB

THOSE PRINCIPLES MUST BE COMMON IN RUSSIA• regional roads• federal roads

10

22



SECOND STEP

Planning and implementing regional RDBs - using (according) common principles of road register

• there can be several projects but common principles must be same !!!

One really BIG question is how to organise RDB work in regions

• how to implement projects, how to collect data, how to maintain data, etc...

=> there should be a collective management group of RDB = helps regions to organise work (for example RADOR can help to organise this group work)



THIRD STEP

As soon as RDB work in regions proceed there should been developed how to combine regional RDBs

• goal should be possibility to combine automatically (without ”handwork”) RDB of whole Russia

Why MUST be possibility to combine regional RDBs to the RDB of Russia?• For example – how to implement car navigation systems if combining is not possible ?• How to make road network plans of Russia systems if combining is not possible ?• Etc...



TIMETABLE OF RDB OF RUSSIA

2007 2010 2015 2020

STEP ONE

STEP TWO

STEP THREE

Date post:	29-Dec-2015
Category:	Documents
Upload:	jason-mccormick
View:	216 times
Download:	4 times

14.6.2007 / Reijo Prokkola, Matti Raekallio I - Road Data Bank in the Finnish Road Administration...

Documents