Autonomous Driving Software - Ch.10: HD Map and Localization [EN]
STATERA Library · Series 08 · Volume 12 · Chapter 10 · EN
Volume 12. Autonomous Driving Software
Chapter 10. HD Map and Localization
10.01. HD Map Standards NDS OpenDRIVE Lanelet2 Overview
High-definition maps provide autonomous driving systems with a structured representation of the environment that extends beyond the geometric information available from conventional navigation maps.
They may encode lane boundaries, centerlines, road topology, intersections, traffic rules, landmarks, curbs, stop lines, and other semantic elements required by localization and planning.
Within the autonomous-driving software structure, HD maps therefore form a critical interface between perception, localization, behavior planning, and trajectory generation.
An HD map is not simply a more accurate version of a consumer navigation map. Its primary purpose is machine interpretation.
Autonomous systems must understand where the vehicle or robot can move, how neighboring road or path segments are connected, which regulatory constraints apply, and which geometric features can support localization.
Consequently, HD map representations usually combine geometric, topological, semantic, and regulatory information rather than relying only on geographic coordinates.
The geometric layer describes the physical structure of the operating environment. It can represent lane boundaries, reference lines, road surfaces, curbs, intersections, parking areas, shoulders, and other spatial features.
Depending on the application, coordinates may be expressed in geographic or projected reference systems and transformed into local frames used by the autonomous stack. High geometric consistency is especially important when map features are used as references for centimeter-level localization.
The topological layer represents connectivity and relationships rather than physical shape alone. It describes which lanes or paths precede, follow, merge with, cross, or neighbor one another.
This information allows a route planner to reason about feasible transitions through the transportation network. A semantic layer adds meaning to geometric objects, while regulatory information associates elements such as speed limits, right-of-way rules, stop requirements, and permitted movements with specific map regions.
Several map formats and ecosystems have evolved because different parts of autonomous mobility require different abstractions. Navigation Data Standard, commonly known as NDS, focuses on standardized automotive map databases and map distribution.
ASAM OpenDRIVE describes road networks using a road-centered mathematical representation that is particularly valuable for simulation and scenario-based development. Lanelet2 uses an extensible lane-level representation designed around atomic drivable segments and their regulatory relationships.
NDS
NDS is an industry-oriented specification for automotive navigation and map data. Rather than treating a map as one monolithic file, the NDS ecosystem is designed around structured databases and standardized interfaces that can support navigation, automated driving, map updates, and vehicle deployment.
This is important for production systems in which map information must be stored, distributed, updated, versioned, and consumed consistently across vehicle platforms and geographic regions.
From an autonomous-driving perspective, the strength of an NDS-oriented architecture lies in lifecycle management as much as representation. Production vehicles may operate over very large geographic areas, making full-map replacement inefficient.
Map databases therefore benefit from mechanisms that support partitioning, incremental updates, version management, and controlled delivery. Such capabilities distinguish fleet-scale map infrastructure from the smaller static maps frequently used during robotics experiments or limited-site AMR deployments.
ASAM OpenDRIVE
ASAM OpenDRIVE approaches mapping from a different perspective. It describes road networks primarily through analytically defined road geometry and associated lane structures.
A reference line forms the geometric foundation of a road, and lanes are defined relative to this reference. Road elevation, lateral profiles, lane widths, junctions, signals, objects, and other properties can then be associated with the road model, creating a compact mathematical description of structured transportation infrastructure.
This representation makes OpenDRIVE particularly useful in driving simulation. Instead of storing only sampled polylines, a simulator can reconstruct continuous road geometry from mathematical definitions and generate corresponding surfaces, lanes, and junction structures.
The same logical road description can support scenario generation, virtual validation, and automated-driving software testing. OpenDRIVE therefore often serves as an infrastructure description that connects road modeling with simulation-oriented development workflows.
Lanelet2
Lanelet2 uses a graph-oriented representation that is highly suitable for planning and localization pipelines in autonomous vehicles and mobile robots. Its central concept is the lanelet, an atomic lane segment typically bounded by left and right line strings.
Lanelets can be connected into a routing graph, while additional map primitives represent points, line strings, areas, and relationships. This structure allows complex road networks to be decomposed into manageable semantic elements.
A major characteristic of Lanelet2 is its regulatory-element model. Traffic rules are not merely attributes attached loosely to geometry; they can be represented as explicit relationships between map primitives and regulatory concepts.
Stop lines, traffic lights, right-of-way relationships, speed limits, and other rules can therefore be associated with the lanelets to which they apply. This helps planning software convert a geometric route into behavior that respects the mapped operational constraints.
For outdoor AMRs, Lanelet2 can also describe environments that do not resemble conventional public roads. Industrial campuses, logistics yards, ports, pedestrian-shared paths, service roads, and large outdoor facilities may contain drivable corridors with locally defined operational rules.
Lane-level primitives can be adapted to represent these corridors, while areas and regulatory relationships describe intersections, restricted zones, docking approaches, crossings, or other mission-relevant regions.
NDS, OpenDRIVE, and Lanelet2 should therefore not be interpreted as three interchangeable file formats solving exactly the same problem.
- NDS emphasizes scalable automotive map databases and deployment-oriented map ecosystems.
- OpenDRIVE emphasizes precise road-network description and is strongly aligned with simulation and virtual road environments.
- Lanelet2 emphasizes semantic lane-level modeling, routing relationships, and practical integration with autonomous-driving and robotics software.
A real autonomous-driving development environment may consequently use more than one representation. Road-network data could originate from a commercial or enterprise map database, be converted into an OpenDRIVE representation for simulation, and be transformed into a Lanelet2 map for an autonomy stack.
Conversion is not necessarily lossless because each representation has different semantics and assumptions. A robust pipeline must therefore define which objects, coordinate systems, attributes, and regulatory relationships constitute the authoritative map information.
HD maps also interact directly with localization. A point-cloud map may provide dense three-dimensional features against which LiDAR observations can be registered, while a vector map provides semantic and topological context.
GNSS and RTK can supply global position constraints, and cameras may observe mapped lane markings, poles, signs, or other landmarks. The autonomous system can combine these sources so that localization is not dependent on a single sensor or map representation.
This distinction between localization maps and planning maps is operationally important. A dense point-cloud map can be excellent for scan matching but inefficient for route reasoning, whereas a vector map can represent lane connectivity and traffic rules efficiently without containing enough environmental texture for precise LiDAR registration.
Practical architectures therefore often maintain multiple complementary map layers connected through consistent coordinate frames, timestamps, map identifiers, and version information.
Map freshness becomes another fundamental requirement. Roads, construction zones, barriers, vegetation, lane markings, loading areas, and industrial layouts can change after mapping.
A geometrically precise but outdated map can be more dangerous than a lower-detail map whose uncertainty is correctly represented. Production systems therefore require mechanisms for detecting environmental changes, validating candidate updates, distributing approved map revisions, and ensuring that vehicles know which map version is currently active.
These requirements connect HD-map standards to the broader autonomous-driving software lifecycle. The chapter structure places map standards before Lanelet2 map creation, point-cloud map building, NDT localization, sensor-fusion localization, GNSS RTK integration, map updating, map-free approaches, localization recovery, and outdoor AMR deployment.
This progression reflects the role of map representation as the foundation upon which later localization and operational mechanisms are constructed.
For system architects, the important design question is therefore not which HD-map standard is universally superior, but which representation should serve each interface in the autonomy pipeline. The choice depends on geographic scale, required semantics, simulation compatibility, routing needs, localization methods, update frequency, tool support, and deployment architecture.
Explicitly separating these concerns prevents the map from becoming an opaque dependency shared inconsistently across software modules.
A mature HD-map architecture ultimately behaves as a continuously managed digital representation of the operational environment. Geometry provides spatial structure, topology provides connectivity, semantics provide meaning, regulations constrain behavior, and localization layers connect the digital representation to real sensor observations.
NDS, OpenDRIVE, and Lanelet2 illustrate complementary approaches to these requirements and provide a useful foundation for understanding map-centered autonomous-driving software.
10.02. Lanelet2 Map Creation and Editing for AMR [w/Code]
Lanelet2 map creation for an autonomous mobile robot begins by defining the operational environment as a structured network of navigable corridors rather than as a conventional road image.
The map must represent where the AMR may travel, how individual path segments connect, and which operational constraints apply. For outdoor AMRs, these elements may include service roads, pedestrian-shared paths, loading zones, intersections, docking areas, and restricted regions.
The fundamental Lanelet2 representation is built from map primitives. Points define geographic or spatial positions, line strings connect ordered points into boundaries or reference features, and lanelets combine left and right boundaries into atomic navigable segments.
Areas represent regions that cannot be described naturally as lane-shaped corridors, while regulatory elements associate traffic or operational rules with the map objects to which those rules apply.
Map creation normally starts from a reliable spatial reference. Surveyed coordinates, GNSS RTK measurements, aerial imagery, existing CAD or GIS data, LiDAR maps, and field observations can provide geometric references.
For AMR deployment, the selected source should match the required localization accuracy and operational scale. Coordinate-system consistency is essential because map geometry, localization output, sensor data, and planned trajectories must eventually describe positions within compatible reference frames.
The first practical modeling task is usually the construction of boundary line strings. Instead of drawing only a center path, the map designer defines the left and right limits of each navigable corridor.
These boundaries can correspond to lane markings, curbs, walls, fences, pavement edges, virtual safety boundaries, or operational limits. The resulting representation gives planning software explicit information about the spatial region assigned to robot movement.
A lanelet is formed by pairing compatible left and right boundaries while preserving their directional interpretation. The ordering of boundary points is important because it contributes to the lanelet orientation and travel direction.
Adjacent lanelets can share boundary line strings, reducing duplicated geometry and maintaining consistency when a common boundary is edited. Complex routes are then represented as connected sequences of relatively simple lanelet segments.
Lanelet segmentation should reflect meaningful changes in geometry, connectivity, or operational rules. A long corridor does not always need to be represented as one lanelet.
It can be divided near intersections, merges, crossings, speed-zone transitions, docking approaches, or areas where different rules become active. Appropriate segmentation makes routing relationships clearer and allows regulatory information to be attached precisely to the portions of the environment where it applies.
Topology is created by establishing valid relationships among lanelets. Successor and predecessor relationships describe longitudinal connectivity, while neighboring relationships support lateral reasoning where applicable. At intersectio
Comments
No comments yet. Start the discussion.