town_layout — DRIVE `town` 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.town_layout(name: 'str' = 'default', *, overlap: 'float' = 0.05) -> 'dict' (to call the implementation directly, import drivetown; drivetown.town_layout(name: 'str' = 'default', *, overlap: 'float' = 0.05) -> 'dict'; from the registry, opsdrive.get("town_layout"))

Usage

Default towns. "default" = road(30) → intersection → road(20) → crossing (railroad crossing) → road(20) → slope → road(20) → parallel_parking → road(30) (all 7 m wide; stop lines: 1 at the intersection and 1 at the railroad crossing). "short" = road(20) → crossing → road(20) (fast test gate).

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

Raises ValueError: 名前が TOWN_NAMES に無い。

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_town — py -3.11 examples/poc_driving_town.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 (`town`)

town_chain · town_world · town_centerline · town_stop_lines · town_rules · town_crossing_state · town_run · town_checks

*Provenance: drivetown.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

town_layout — DRIVE town op