terrain op• Data kinds: table × table → table
• Call: import fullseye as fs; fs.ledger.world_apply_terrain(world: 'dict', p: 'dict', step: 'float' = 2.0) -> 'dict' (to call the implementation directly, import driveterrain; driveterrain.world_apply_terrain(world: 'dict', p: 'dict', step: 'float' = 2.0) -> 'dict'; from the registry, opsdrive.get("world_apply_terrain"))
Applies the terrain to the output of world_build (a flat world) (in place; returns the same dict).
Replaces the road-surface mesh (objects[0] "ground") with terrain_mesh; objects that have a pose (assets, trees, pedestrians) are lifted rigidly by the height at the pose's (x, y), and objects without one (kerbs, white lines, stop lines, rails, slopes) are lifted per vertex. Records world["terrain"] = p.
• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).
• Operator provenance and references — the sources of the research/methods this op family came from.
• The canonical algorithm (author, year) and its uses are named in the family usage guide above.
• poc_world_terrain — py -3.11 examples/poc_world_terrain.py
table as input)course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same
terrain)perlin2 · fbm_params · fbm_height · fbm_gradient · radial_periodogram · spectral_slope · course_distance · terrain_params
*Provenance: driveterrain.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*
© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.