terrain_height — DRIVE `terrain` op

• Data kinds: image2d × image2d × table → image2d

• Call: import fullseye as fs; fs.ledger.terrain_height(x, y, p: 'dict', course=None) -> 'np.ndarray' (to call the implementation directly, import driveterrain; driveterrain.terrain_height(x, y, p: 'dict', course=None) -> 'np.ndarray'; from the registry, opsdrive.get("terrain_height"))

Usage

z = fbm(x, y)·w(d(x, y)) + undulation(x, y). Without a course, w = 1 (relief only).

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)

• poc_world_terrain — py -3.11 examples/poc_world_terrain.py

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

flow_from_depth_motion · ttc_truth · ttc_from_flow · foe_from_flow · perlin2 · fbm_height · fbm_gradient · radial_periodogram

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_height — DRIVE terrain op