crosswalk_mesh — DRIVE terrain op

• Data kinds: none → table (an op determined by its arguments alone — it takes no image or data input)

• Call: import fullseye as fs; fs.ledger.crosswalk_mesh(a, b, length: 'float' = 4.0, stripe: 'float' = 0.45, gap: 'float' = 0.45, z: 'float' = 0.006) -> 'dict' (to call the implementation directly, import driveterrain; driveterrain.crosswalk_mesh(a, b, length: 'float' = 4.0, stripe: 'float' = 0.45, gap: 'float' = 0.45, z: 'float' = 0.006) -> 'dict'; from the registry, opsdrive.get("crosswalk_mesh"))

Usage

> This operator's description has not been translated yet. The original text follows as it is.

横断歩道(ゼブラ): 道を横切る線分 a→b に沿って幅 `stripe・間隔 gap` の縞を、a→b に直交する向きに

`length だけ伸ばす(a→b の左手側)。{"V", "F", "color", "label" (12), "n_stripes", "area"}`。

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_driving_crossing — py -3.11 examples/poc_driving_crossing.py

• poc_driving_humanoids — py -3.11 examples/poc_driving_humanoids.py

• poc_world_terrain — py -3.11 examples/poc_world_terrain.py

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).*

© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.