DL0163 Map-Based vs Mapless World Models

How do map-based world models conditioned on HD-maps differ from end-to-end mapless world models that predict from raw sensor observations, for a driving stack like Waymo’s or Wayve’s?

Answer

Both families learn a latent transition model that rolls the scene forward under a candidate ego action, so the architectural difference is not the dynamics head but what the dynamics head is allowed to condition on. A map-based world model receives a local HD-map crop m_t, a rasterized or vectorized patch of lane centerlines, stop lines, crosswalks, and traffic-light-to-lane associations, indexed out of a global map by the pose that the localization stack estimates. That crop enters as a hard geometric prior, so the network never has to learn road topology from pixels and can spend capacity on agent behavior. A mapless model sees only the sensor history o_{t-k:t} and must reconstruct that same topology inside its latent on every frame, which is statistically much harder but works on roads nobody has surveyed. The practical result is a swap of error sources rather than a strict improvement: the map-based system inherits map staleness and localization error, the mapless system inherits data hunger and weaker long-horizon geometric consistency.

(1) Conditioning Set: map-based factorizes as p(z_{t+1} \mid z_t, a_t, m_t) with an extra exogenous input, while mapless factorizes as p(z_{t+1} \mid z_{t-k:t}, a_t) and must carry topology in the recurrent state.
(2) Where The Prior Lives: in one system lane geometry is a surveyed asset refreshed by a mapping fleet, in the other it is weights learned from driving video.
(3) Sample Efficiency: handing the model the road graph removes an enormous nuisance factor, so map-conditioned models converge on thousands of hours where mapless generative models are trained on tens of thousands to millions.
(4) Failure Signature: a stale or misaligned map produces confidently wrong rollouts, whereas a mapless model facing an ambiguous road typically produces a wide, visibly uncertain distribution.
(5) Pose Coupling: the map crop is only meaningful in the correct frame, so map-based prediction quality is bounded by localization accuracy; mapless prediction has no pose dependency at all.
(6) Scaling And ODD: map-based scales with surveyed kilometers and re-survey cadence, mapless scales with data and compute, which is why geofenced robotaxi and everywhere-consumer programs made opposite choices.

Two stacked pipelines: the upper map-based pipeline encodes surround camera and LiDAR into a latent state, takes an HD map crop selected by ego pose as an extra conditioning input to the transition model, and decodes BEV occupancy, agent futures, and an ego plan; the lower mapless pipeline tokenizes surround camera video, feeds a spatio-temporal transformer or diffusion prior conditioned only on past tokens and the action, and decodes future frames, an implicit map, and an ego plan

Figure 1: The two stacks share an encoder, a latent transition model, and a decoder. Only one extra edge differs: the HD map crop selected by the estimated pose feeding the transition model. That single edge is what buys sample efficiency and what imports two new failure sources, map staleness and localization drift.

The interesting behavior appears when the map and the world disagree. Because the map is treated as ground truth during training, the model learns to trust it, and at inference it has no mechanism to discount it: a lane that was closed for construction last week is still a valid lane inside m_t, so the imagined rollout drives straight through the closure with low predictive variance. A mapless model never had that crutch, so its estimate of drivable space comes from the same pixels that show the cones. It pays for this with weaker long-horizon geometry, since nothing anchors an eight-second rollout to a globally consistent lane graph and errors compound in the latent. This is also why the honest comparison is not accuracy on a nominal benchmark, where the map-conditioned model almost always wins, but accuracy conditioned on map validity.

Two bird's-eye-view panels of the same two-lane road with a lane closure marked by cones. In the left map-based panel a blue HD map centerline runs straight through the closure and the predicted rollout follows it with a narrow uncertainty band, ending in a red cross at the cones. In the right mapless panel there is no map centerline, the predicted rollout bends into the adjacent lane around the cones, and the uncertainty band is visibly wider.

Figure 2: Same scene, same closure, different conditioning. The map prior keeps the rollout tight and correct whenever the map matches reality, and keeps it tight and wrong when it does not. The mapless rollout is wider but reactive, because the only evidence it ever had for drivable space is the current image.

Mathematical Formulation:
z_t = E_\theta(o_{t-k:t})
m_t = \Pi(M, \hat{T}_t), \quad \hat{T}_t = T_t + \epsilon_{\mathrm{loc}}
p_{\mathrm{map}} = p_\theta(z_{t+1} \mid z_t, a_t, m_t)
p_{\mathrm{free}} = p_\phi(z_{t+1} \mid z_{t-k:t}, a_t)
\mathcal{L} = \sum_{h=1}^{H} \ell(D(z_{t+h}), o_{t+h})

Where:

  • z_t \in \mathbb{R}^{d} is the latent scene state produced by encoder E_\theta from the observation window o_{t-k:t} of surround camera, radar, and optionally LiDAR frames.
  • M is the global HD map, T_t \in SE(3) the true ego pose, \hat{T}_t the estimate produced by localization, and \Pi the operator that crops and transforms M into the ego frame.
  • \epsilon_{\mathrm{loc}} is localization error. It is not observation noise: it rigidly shifts the entire conditioning input, so a 0.5 m lateral bias moves every lane boundary by 0.5 m.
  • a_t is the candidate ego action, which is what makes both models action-conditioned and therefore usable for planning rather than passive video prediction.
  • \theta and \phi are the two parameter sets; \phi must additionally encode road topology that \theta receives for free through m_t.
  • D is the decoder (future frames, BEV occupancy, or agent boxes), H the rollout horizon in steps, and \ell the per-step loss, typically reconstruction plus a KL or diffusion denoising term.
Schematic line chart of mean lateral rollout error in metres against prediction horizon in seconds, with three curves: a map-based model with a fresh map staying lowest, a mapless model rising moderately faster, and a map-based model with a stale or misaligned map rising steepest and crossing the others within about one second, plus a dashed horizontal line at 0.5 metres marking lane-keeping tolerance

Figure 3: Schematic, but the ordering is the point. With a valid map the conditioned model dominates at every horizon; with a stale or misaligned map the same model becomes the worst of the three within roughly a second, because the prior is applied with full confidence in the wrong place. A mapless model has no best case that good and no worst case that bad.

PropertyMap-based (HD-map conditioned)Mapless (raw sensor)
Conditioning inputSensor latent plus a pose-indexed vector or raster map cropSensor history and the ego action only
What must be learnedAgent behavior and interaction; road topology is givenTopology, drivable space, and behavior, jointly from pixels
Data appetiteThousands of hours plus a surveyed and maintained mapTens of thousands of hours upward; Cosmos-class pretraining uses about 20M hours of video
Dominant failure modeStale map or localization drift produces low-variance wrong rolloutsAmbiguous or occluded geometry produces drifting, globally inconsistent rollouts
Scaling axisSurveyed kilometers and re-survey cadence, so expansion is operationalData and compute, so expansion is a training-run problem
VerifiabilityMap is an auditable artifact; behavior can be certified per mapped intersectionTopology lives in weights, so guarantees come only from aggregate evaluation
Traffic-light and rule handlingLight-to-lane association and speed limits come from the mapAssociation must be inferred visually, a known long-tail weakness

Login to view more content


Log in to track your progress

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *