Foresight Vehicle Project Completion Day: ProbeIT · Foresight Vehicle Project Completion Day: ......

Preview:

Citation preview

Foresight Vehicle Project Completion Day: ProbeIT

Dr Jill Hayden2 February 2006

Introduction

ProbeIT PM was Filip Hermans

Costs:Total project spend £ 960,22050% funded by HA

Structure of presentation:PartnersObjectivesAchievementsPlans for the future

Consortium

Atkins

Jaguar Cars LtdTransportation Research Group

Kingston University

Essex County Council

Navigation Technologies

Highways Agency

|

Objectives

The ProbeIT objective was to develop a process (end-to-end) for the sourcing and exchange of position-related information between

traffic management systemsa uniform data sourcevehicles

The aim was to provide timely and accurate location based information in the vehicle using a telematic link to enable NextGeneration Advanced Driver Assistance Systems (ADAS).

Three phasesnon-dynamic data flowdynamic data flowfloating vehicle application

Phase 1

Non-dynamic data flowdigital maps for navigation –underlying map data

Phase 2

Dynamic data flow‘static’ speed limits and parking restrictionsdynamic navigationreal-time variable speed limit informationreal-time traffic information

Phase 3

Advanced probe vehicle informationroadworksairbag alert

?

(proved but not fully integrated during project)

Framework design

ProbeIT open architecture model

Achievements: Acquisition of static information

Speed limits and waiting restrictions in EssexLocation referencing depends on format

Road centrelines for speed limits – use road name and end pointsZones for parking restrictions –find intersections between zone and ProbeIT segments

Match location to ProbeIT databaseSpecify information type

margin

margin

margin

margin

RoadStart

RoadEnd

TILE

Achievements: Acquisition of dynamic information

Variable speed limits on M25Accessed using TIH, QMISS CORBA-based information serviceMatch information to location in ProbeIT database

Location referencing uses Point Level DatabaseFixed Point Marker Post ID for start and endMatch bearing between point and segment for each PLD pointIdentify route between start and end segment

PLDstart

PLDfinish

ProbeITstart seg

ProbeITfinish seg

shortest route

Achievements: Server architecture

SubSegmentDatabase

Dynamic-SubSegmentDatabase

Base-Geometry Database

Gazetteer

Uniform data sourceSub-segment information types

Achievements:Vehicle-server interface

Vehicle

ProbeIT ServerCellular LinkIn-vehicle server

interface adapting custom protocol to CORBA IDL

CORBA Interface defined in IDL methods and data structuresData partitioning – IDL structures

BaseGeometryTileDynamicTileMapDrawingTileLexiconGazetteer

Custom protocolRaw sockets transportCompression

Achievements: In-vehicle application

In-vehicle server interface

Data Marshaller (cache)

Server

In-Vehicle

Application

Navigation components

Interface to hardware (GPS, gyro, speed pulse, CAN bus)

User Interface Guidance

Vehicle PositioningElectronic Horizon

Route CalculationMap Display

=> CORBA Interface

Further Work

National speed limit database (SLD)Atkins performed feasibility study for DfTvery positive business casewide support for database and in-vehicle speed limit informationDfT ITS policy framework – considering options for SLD and also Road Information Framework (RIF)

Possibility for links between ProbeIT concept andISACVHS RUClocation-related vehicle safety applications

Further Work

In-vehicle systems will be available within 3-5 years assuming the data is availableMany manufacturers and map providers are interested

NAVTEQ demonstrated Vehicle Infrastructure Integration (VII) technology at the ITS 2005 World Congress

location and severity of road hazardsprobe vehicles provide informationinformation is processedbroadcast to vehicles

Recommended