1. SP2 Integration Workshop Short Introduction to the LDM
Tobias Schendzielorz (TUM)
Paul Mathias (MAT.TRAFFIC)
SAFESPOT

2. Local Dynamic Maps – Requirements & Vision
A real time updatable Local Dynamic Map is defined as
Integration of standard digital maps with dynamic (short time) and local (short range) layers of information collected by the infrastructure or by the vehicles (road status, obstacle presence, etc.).
Focus on new contents and information that is provided in real-time
need of high efficiency algorithms
spatial functions to support data fusion and processing mechanism
definition of an adaptive optimal coverage range (only for in-vehicle)
compatibility with standard digital maps
The main target is to provide a representation of vehicle’s and infrastructure surroundings with all static and dynamic safety relevant elements!
© LDM workshop 08/ Gent

3. Local Dynamic Maps – Map Layers
com nodes,
fusion result
ego
pos
vel …
rsu id
type
veh
temporary regional info !
accident id
pos …
fog
a,b
congestion
length
dir
map from provider
landmarks for
referencing
tree id
pos
curbs…
© LDM workshop 08/ Gent

4. Local Dynamic Map database and client architecture
Client – server architecture
The LDM database and client architecture fulfils the SAFESPOT needs of a node as it serves several units that are connected via Ethernet
each client can setup a
connection to the LDM
several clients can be
implemented for different
environments and
programming languages
(C++, Java for CVIS)
© LDM workshop 08/ Gent

5. PG-LDM Implementation using PostgreSQL
PG-LDM facts and figures
PostgreSQL database enabled with spatial functions
PSF – AGORA-C and further function support for CVIS
Windows, Linux, C++
The Level 1 API provides access functions to the PostgreSQL database. The Level 2 API encapsulates functions that support more sophisticated data retrieval.
© LDM workshop 08/ Gent

6. Intersection example data - Dortmund
Green belt (landmark)
Curbs (landmark)
Reference tracks
Crossings (pedestrian, bicycle)
Dividers, stop line (landmark)
Traffic lights, signs, poles
Lighting
Arrows and further road markings
Pedestrian wakling and bicycle path
(landmark)
slip road
Building facades
© LDM workshop 08/ Gent

7. NQ-LDM Implementation using SQLite
Proprietary map engine solution:
map database in physical storage format (PSF)
layer 2, 3 and 4 databases stored separately (SQLite)
API Manager will translate T/Q-API into calls to the appropriate database
SQLite offers small-footprint, quick access ideal for embedded system
Use of existing tools to access static map data
Remote access now provided
Simple Feature spec. spatial functionality to be provided on- demand
© LDM workshop 08/ Gent

8. Overview of Level 1 Queries
Be aware, this is for the PG-LDM!!
© LDM workshop 08/ Gent

9. Useful links and information
Latest PG-LDM version and information:
Latest Navteq-LDM version and information:
Material of the LDM Workshop in Gent:
Contact PG-LDM: Contact Navteq-LDM