terrain_mesh — DRIVE `terrain` op

• Data kinds: table × table → table

• Call: import fullseye as fs; fs.ledger.terrain_mesh(p: 'dict', course, bounds, step: 'float' = 2.0) -> 'dict' (to call the implementation directly, import driveterrain; driveterrain.terrain_mesh(p: 'dict', course, bounds, step: 'float' = 2.0) -> 'dict'; from the registry, opsdrive.get("terrain_mesh"))

Usage

Grid mesh that divides (xmin, xmax, ymin, ymax) into cells of size step, with z = terrain_height.

> The detailed description below is the original text — the summary and the headings are translated.

{"V", "F", "face_label" (0 = 道の内側、10 = 地形), "face_color"}。面のラベルは重心の内外判定。

References (sample data, literature)

• 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.

Runnable examples (verified samples that actually call this op)

• (none yet)

Ops the type connects to (they accept `table` as input)

course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same

Same category (`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).*

terrain_mesh — DRIVE terrain op