View
215
Download
0
Category
Tags:
Preview:
Citation preview
Welcome to Special Session 13 EuroRoadS
− a pan European road data infrastructure
ITS World Congress 9 October 2006
Programme
• Objectives and results• Specification framework• Evaluation and quality management• Results from test activities• Deployment of project results
Objectives and results
Mia Wallberg & Ulf SandgrenLantmäteriet, National Land Survey of Sweden
mia.wallberg@lm.seulf.sandgren@lm.se
Scope
• To lay the ground for the creation of a pan-European standardised, seamless, updated and quality assured digital road data infrastructure built on identified user requirements
• To simplify exchange of digital road data within and between different countries
Vision 2012
• To establish a European wide public road data infrastructure delivering access, through a single portal, to harmonised and quality assured road information for multipurpose use
• That the EuroRoadS-compliant national road databases will cover the EU25+ by end of 2012.
• That the INSPIRE Directive will, for the European road network, be based on the EuroRoadS specifications and other results.
Principles for EuroRoadS
•To support collection and maintenance of data within the organisational level where it can be most effectively carried out
•To make use of existing data and create efficient tools to achieve seamless interoperability between existing data bases
•To involve all relevant stakeholders
•Use existing standards
•Set up efficient quality models
•Focus on core European road data
Operational goals
Identify the business environment and common user groups
Provide a detailed description of user requirements
Develop a road data specification framework
Provide processes for quality control
Develop a prototype and carry out tests
Propose implementation solution
Develop exploitation plan
Business environment
• Navigation & Routing• Mobility and Society planning• Traffic management• Traffic & Trip Information• Emergency services and Disaster planning• Safety (including ADAS)• Asset Management• Fleet, freight, logistics management• Road charging (tolling)• Military and Security planning
User requirements
• Data structure
• Data content
• Data quality & quality assurance- data access- handling of changes & updates
• Road network information model• Core European road data (content)• Quality model• Road network exchange model• Road network exchange format• Metadata catalogue• Terminology catalogue
Specification framework
INSPIRE – Framework Directive
I. General provisionsII. MetadataIII. Interoperability of spatial data
sets and servicesIV. Network servicesV. Data-sharing and re-useVI. Coordination and
complementary measuresVII. Final provisions
Road data and INSPIRE
Road data as basis for • measurement of traffic noise,
pollution & energy consumption• management & monitoring of traffic• road tolling & pricing• transport planning• emergency & security
EuroRoadS contribution to INSPIRE
• Finding the right balance between far reaching harmonisation and making use of existing data
• Focus on core European road network data & create efficient solutions
• Create efficient tools to achieve interoperability
• Involve all relevant stakeholders in the entire process
• Set up efficient quality models
• Use existing standards
Transportation network
Hydrography
Topography
Administrative boundaries
xxx
INSPIRE
EuroRoadS
Quality control
The EuroRoadS quality models contains all sub-elements of ISO19 113 but with some extensions.
Demonstration – verifying the results
• Demonstrate a complete data chain from acquisition to final services: - data capture & maintenance,- data processing, - showcase ”Speed Advice”, - metadata server
• Demonstrate and validate the use of the road data specification
• Support dissemination and networking through concrete implementation results
Plans for implementationand exploitation
Recommendations to:• support a rapid creation of an
infrastructure for European road data
• support a wide use of the European road data infrastructure• facilitate services built on it
Address structures, mechanisms and arrangements needed.
Ulrich HaspelBavarian Board of Building
ulrich.haspel@stmi.bayern.de
Specification Framework
Objectives for the specification framework
• Increase and simplify the possibility for many different parties to access public core road data.– Core road data is that data that is “static”, and is of
interest to many different user groups.– The above goal describes the mechanism to enable
the exchange of core road data, both within and between different countries and organizations.
• Achieve a harmonization of core road data within Europe.
• The aim of the work should be to prepare for a European standard
Work Directives
• Product models and exchange formats should be based on TC211/ISO 19100 (the international standard for geographical information)
• The road data exchange format must be able to handle both whole data sets and just data changes
• It is important to solve border linking (the merging of adjacent road datasets)
The framework documents
– Road data network information model (conceptual model)
– Core European road data specification– Metadata catalogue (conceptual model)– Quality model– Road network exchange model specification– Road network exchange format specification– Terminology catalogue
All framework documents are available at www.euroroads.org
EuroRoadS
DataData Maintenance
ContentNational/Regional Road Databases
InformationCommercial
Road Databases
ServiceDifferent applications
Attributes Road data Road Users Service x
Attributes
Road Network
yyyy
xxxx Road Owners Application A
Application BMap Producers
Information Refinement Chain
Identified requirements
Road network model requirements:– Support existing road data solutions (at public
authorities)• Topology/geometry and only geometry• Linear referencing and geometry attributes• Validity and snapshot• Stable identities when changes occur (linear
referencing)– Support possibility to supply attributes only, using
linear referencing (a published road network ID = common reference system)
Solution
The EuroRoadS project decided to develop a flexible road network model:
– The advantage is that many organisations can support the EuroRoadS model with relatively little effort (mapping)
– The disadvantage is that the EuroRoadS file can describe a road network in many different ways.
Supplier’s application
data
User application
schema
Supplier application
schema
Transformation
Application schema
Application schema
User’s application
data Transfer dataset
Transformation
Mapping Mapping
EuroRoadS
EuroRoadS
Three types of road network attributes and features:
1. Mandatory attributes • Data that must be given in an exchange file
2. Optional attributes and features• Optional data that have common descriptions
3. User defined attributes and features• Possibility to define and supply unique data
Definitions have been reused from GDF and RADEF, except for Speed Limit that has used definitions from the Speed Alert project.
Road attributes and features
Road attributes and features
Solution for Border Node Information– Agree on geometry for the border (neighbours
need to communicate and agree with each other)– Identify roads that cross the border– Add a node attribute to each border node
NOR SWE
Road nodeId=”123”Attributes={ER_BorderNodeInfo(ER_NationalBorderNodeType,”NOR”,”SWE”,”abc”)}
Road nodeId=”abc”Attributes={ER_BorderNodeInfo(ER_NationalBorderNodeType,”SWE”,”NOR”,”123”)}
Mandatory attributes
– Geometry– Universal ID– Form of Ferry– Form of Node– Form of Way– Functional Road Class
Optional attributes
– Addresses– Access– Border Node
Information– Flow Direction– Manoeuvre– Grade Separated
Crossings– Mountain Pass– Number of Lanes– Junction Information– Object Identification– Obstruction
– Restrictions for Vehicle
– Road Length– Road or Street Name– Road Number– Road Width– Road Surface– Seasonal
Restrictions– Services – Speed Limit– Structure– Steep Gradient
Steps to take
An organisation which would like to supply a EuroRoadS exchange file, needs to:
– Convert existing data in accordance to the EuroRoadS framework specification (mapping data)
– Adjust data at borders (“talk to the neighbours”)– Transform coordinates to the common coordinate
system (ETRS 89)
The efforts depend on how existing data is structured and stored!
Benefits of the framework
– Facilitates the exchange of road data– Offers a model for quality assurance– Offers a common metadata catalogue– Offers a common terminology catalogue– Minimises the number of exchange formats to support– Makes it easier to combine road data from different
sources– Facilitates combinations of road data with other data
themes (based on ISO 19 100)– Offers a common, standardised definition of road
network and road attributes
Evaluation and quality management
Evaluation and quality management of data flow and processes from acquisition and updating to be used in
final applications
Thomas WiltschkoUniversity of Stuttgart
thomas.wiltschko@iagb.uni-stuttgart.de
Motivation
• New applications require enhanced content with high and assured quality
• New contents exist partly in administration authorities– Closeness to public data
sources enhancesup-to-dateness, quality, and coverage
– Integration of quality management concept to assure quality of road data
ADAS-Karte8080
8080
8080
ADAS-Karte8080
8080
8080
Quality assurance
Quality assurance
Quality assurance
Quality management within the public-privat information chain
Information chain
Provision of quality assured data in applications needs a quality management within the entire information process
Eu
roR
oa
dS
i
nte
rfa
ce
capturing
commercialroad data
(road network)
Data provider
Contentprovider
Informationprovider
Serviceprovider
8080public road data
(e.g. speedlimit)
public road data(e.g. speedlimit & road)
applicationdatabase
capturing
processing...integration
conversion
= fixed set of inherent quality characteristics
Requirements for quality management concept
• A uniform and understandableQuality description– suitable for each actor
• Evaluation methods to determine aquality value– allows quality determination with reasonable effort
• Quality assurance measures to realize processes fulfilling the quality requirements– integration of efficient error avoidance and
error control mechanisms • Documentation of quality values
and processes– for internal and external purposes
Structure of the quality model
Fixed set of inherent quality characteristics ensures uniform quality description
Various quality parameters ensures necessary flexibility to describe heterogeneous data types
formulated
by
Qualitycharacteristic
Qualitäts-parameterQuality
parameter value
Qualitäts-parameterQuality
parameter
Qualityphenomenon
describe
makeconcrete
quantify
determine Qualityevaluation
method
Qualitäts-forderungQuality
requirement
correctness
consistency
completeness
accuracy
availability
up-to-dateness
correctness
consistency
completeness
correctness
consistency
completeness
accuracy
availability
up-to-dateness
availability
up-to-dateness
Metadata for documentation and exchange of quality
• Contains quality description, quality values, used evaluation methods and explanations of data flow
• Application Metadata Server (PTV)
Data
Metadata
XML/GML- based Exchange Format (Vägverket)
ISO 19115
EuroRoadS Metadata Catalogue
Subset
QualityQuality
User can check whetherdata fulfil hisquality requirement
Quality values can be transferred within the entire information chain
Speed limit capturing and maintenance
(test site Bavaria)
– Explicit SL settings based on road attribution (due national laws)
– Motorway data sheets
– Queries of responsible personnel
– Enquiries executed by road surveillance centres
– Use of photo database
– Field surveying (with GPS)
Data entry via editor (VISUM)
Quality evaluation of data capturing in test site Bavaria
• Implicit speed regulation assures completeness• Motorway data sheets deliver high quality with less effort
Data source
Degree of correctnessin relation to GPS survey
Geometric accuracy
Effort in days per 100 kmHighways
Federal roads
State roads
Community roads
Implicit speed regulation 71 % 86 % 87 % 85 % 25 - 100 m 0.01
ABD-N list 100 % - - - 10 - 30 m 0.1
Local expert knowledge - - - 91 % 25 - 100 m 0.5
Authorities’ survey paper - 91 % 90 % - 25 - 100 m 1.4
Photo database - 93 % 92 % - 10 - 20 m 1.3
GPS survey (Reference) 100 % 100 % 100 % 100 % 10 - 30 m 1.8
Rate of changes of speed limit regulations in test site Bavaria
• Biannual up-date ensures rate of up-to-dateness > 98.5 %• Most changes in spring and summer• About 80 % of temporary speed limit regulations have
duration less than 3 months
biannualupdate
Net-Matching variants concerning corridor widthfor test site France: FRA3 = 80 m; FRA4 = 15 m
Impact of data processeson quality
• Data processes may influence data quality, for example– fuzzy procedure (e.g. net-matching)– generalisation procedure (e.g. coordinate thinning)
• Impact on qualitydepends on – Algorithm– Parameter settings– Quality of input data
• Impact can be evaluatedby comparison – of variants– input and output
• Less effort due to an internal evaluation method
Summary
• EuroRoadS quality concept is a profile, guideline, and case study of ISO 19100-series taking into consideration the data user side demands
• Quality management is firstly connected with cost, but new markets can be supplied with quality assured road data
• EuroRoadS delivers quality management concept for data providing processes to assure data quality within the entire information chain from supplier to user
Recommendations
EuroRoadS quality management concepts support an implementation step-by-step
– Analysing your existing processes and development of additional quality assurance measures
– Testing quality assurance measure by simulation before implementation
– Determine your data quality by using knowledge and internal methods
– Document your processes and quality values– Extend your quality management step-by-step
Demonstration
Lessons from using the EuroRoadS Specification Framework
Michael Landwehr
PTV AG
michael.landwehr@ptv.de
Objectives
• Demonstrate and validate the use of the EuroRoads specification framework
– experiences with transfer and use of similar data from different public sources
– experiences with metadata and related services
• Demonstrate a complete data chain from data acquisition to final services
– validation of EuroRoadS quality framework– show case for a concrete data chain from end to end with
one application operating in different test fields based on the respective supplier’s data
Data and information chain
Data acquisition
Local data-bases
EuroRoadS Framework
Application specific format
Application& service
Public Sector Private Sector
Data transfer/use & meta-data services
Exemplaric data chain & services
Demonstration area
Sweden (SRA, NLS): NRDB
Norway (SV):
France (IGN): BD Uni database
Germany (Bavaria, OBB): INTREST-Database
Austria (BEV): Cooperation with Tirol state data base (TIRIS)
Demonstration components
1. Data capture & maintenance
(test bed Bavaria)
2. EuroRoadS data supply and
processing
3. End-user application: SpeedAdvice
4. Metadata server and services
Information model50 50
50 50
500,0652
0,0654
50 50
SpeedAdviceapplication
Eu
roR
oad
S d
ata
su
pp
ly
Austria, France:
Sweden, Norway:
50 50Bavaria:
Data supply through EuroRoadS framework
• Austria, France: – Network (geometrical link-description only)– 1:1 speed limit reference to link direction
• Bavaria:– Network (geometry + topology)– 1:1 speed limit reference to link direction
• Sweden, Norway:– Network (geometry + topology)– Route (1:n aggregation of links)– Link reference to route, between start- and end-offset from the route start
► Information model offers different levels and possibilities to suppliers for delivery of their (network and speed limit) data
• SpeedAdvice requires– Network (geometry + topology) with routing capabilities– 1:1 speed limit reference to link direction
Data processing – two options
1. ‘Selective’ use of EuroRoadS content:– EuroRoadS provided speed limit data are
transferred from supplier map to third party map for the application
– Low level network description sufficient– Demonstration for France, Austria
2. ‘Exhaustive’ use of EuroRoadS data set:– Transferred data (network + speed limits)
are used in final application– More complete network description needed
than for ‘selective’ use scenario– Demonstration for Sweden, Norway,
Bavaria
Processing steps
AU, F
XML-Import
Netmatching to NavTeq
NetMerging: ‚fuzzy’ transfer of SLs
NetMerging: Link splitting at SL change
+ Transfer of SLs
Generation of binary format for client
SpeedAdvice Client
GDF
GDF loading (coordinate
thinning etc.)
Swe, Nor
Pre-processing (invalid links, routes etc.)
XML-Import
Link splitting at SL change
SL transfer from LR to link attribute
Data set integration (border
linking etc.)
Generation of binary format for
client
SpeedAdvice Client
Pre-Processing
Coordinate thinning‘S
ele
ctiv
e’
use
‘Exh
au
stive’ u
se
Main processing steps: Sweden/Norway
– Pre-processing: invalid links, generalisation of neighbouring, identical speed limits
– Splitting of links at speed limit change
– Transfer of speed limit reference: linear reference to route to a direct link reference
– Creating the topological connection at borders (border linking)
– Coordinate thinning
split points
Main processing steps: Austria/France
– Processing of GDF data– Net-matching: identification
of corresponding links with target road network (from GDF)
– Transfer of speed limit reference to target data set:
• Approximate transfer• ‚Precise‘ transfer
Lessons (I)
• EuroRoadS framework documents generally of high quality, documentation is consistent
• Concepts of the information model are well described
• EuroRoadS exchange format (GML) for complete data sets covering large areas leads to very large data volumes.
– Requires special techniques to handle it
– good for transfer of changes only
Lessons (II)
• Information model for network description offers a lot of flexibility and liberty for usage/interpretation by supplier;– Low entry barrier for supplier with regards to data model and
mapping issues– Currently harmonisation effort on the data user side if
different suppliers are used as input– Balance for harmonisation of supply side and use side
efforts to be found• Border linking (Sweden/Norway) is required if routing
is needed:– EuroRoadS information model provides good basis to
resolve ‚topological‘ linking
Processing steps and effort depends on – The supplier information model and the target
application model• Supplier model differs for demonstrator for each
supplier!– Use scenario: selective vs. exhaustive
• Selective requires some reference transfer technique: Net-matching introduces some errors
– Desired quality: approximate vs. ‚precise‘ transfer of references
– Data user efforts are increasing as soon as provided data have to be changed for the use in the final application,
• e.g. link splitting (for linear reference transfer or precise net-matching transfer)
Lessons (III)
Deployment of project results
Implementation
Exploitation
Project results Vision
Vision 2012
• A European wide
• harmonised
• standardised
• seamless
• updated and
• quality assured
• road data infrastructure
• covering EU25+EuroRoadS will not be implemented overnight
Benefits from the results
• Maximising the use and knowledge of public road data• Contribute to ITS developments & projects
– ADAS applications (Advanced Driver Assistance Systems)
– Location-based services & navigation
– Commercial vehicle applications
• Easier cross border cooperation and networking with a common infrastructure
• Support development of road databases in Europe– Exchanging data
– Building up a road data infrastructure - ‘starting’ countries
– Common Specification Framework
– EuroRoadS as a road data standard
Examples of early adoption
• INSPIRE• Cross border applications
– Norwegian – Swedish border cooperation• Traffic planning• Permissions for transport of heavy and dangerous goods
– Barents GIT project• Harmonised road data infrastructure for the Barents Region
(Norway, Sweden, Finland, Russia)• Data available in EuroRoadS exchange format from a
Barents GI portal• Exchange of road data
– Norwegian Road Administration• Exchange of road data between NRA and the municipalities
– EuroRoadS’ Exchange model and format and – Quality model
• Trans-European road Network– TERN (Trans-European road network)
• To facilitate the data exchange related to TERN
Recommendations
Step by step approach– Best practice– Make gradual implementation
and changes at a national level– Short term targets – Organisational cooperation– Cross border cooperation
Future steps
• Promote EuroRoadS take-up– In data supplier communities - CEDR, EG– In customer communities - ERTICO– By European Commission - INSPIRE
• Ensure continuity of basic support services– Provide user support, help desk, bug reports…– Documentation: best practice examples, supplier & user guides
• Promote implementation of the framework in commercial GIS• Establish quality certification & compliance testing
procedures • Specification maintenance
– Bug fixes, enhancements, extensions
• Promote standardisation of EuroRoadS results
• Dissemination & liaison: – Web site, newsletters, conferences, project links, R&D
requirements…
Objectives for EuroRoadS Forum
• Promote the implementation • Provide a forum for collaboration• Support, correct and improve the framework• Support suppliers and users e.g. metadata• Represent the EuroRoadS achievements in the
INSPIRE process• Identify needs for further R&D• Develop guidelines and distribute information on best
practice• Develop a commercial environment aiming to facilitate a
widespread market adoption of EuroRoadS compliant data
Organisation of EuroRoadS Forum
• Agree on aims and terms in a common Memorandum of Understanding
• Define central support services• Agree on distribution of tasks
Bringing EuroRoadS forward
Invitation to providers and users of public/private sourced road data to a strategic meeting on 30 November in Malmö, Sweden• Agreement of content of the MoU• Organisation of a EuroRoadS Forum to promote and exploit the results• Undertakings from interested parties
www.euroroads.org
Recommended