town_stop_lines — DRIVE `town` op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.town_stop_lines(layout, *, side: 'str' = 'left') -> 'List[dict]' (to call the implementation directly, import drivetown; drivetown.town_stop_lines(layout, *, side: 'str' = 'left') -> 'List[dict]'; from the registry, opsdrive.get("town_stop_lines"))

Usage

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

町の停止線を弧長順に並べる: ``[{"s", "x", "y", "yaw", "kind", "element", "crossing_zone": (s0, s1) | None,

"drawn": bool}, ...]``。

交差点: 要素の `stop_lines(線分 (2, 2))のうち **中心線に端点が載り、進行方向の side` の側へ延びる物** が走行路の

停止線(4 本のうち 1 本。左側通行なら左、右側通行なら鏡像の 1 本)。踏切: 停止線の位置は 踏切面 − stop_setback の閉形式

(drivecourse は左車線にしか白線を描かないので side に依らない。`drawn` = その側に白線が描かれているか)。

`s は中心線上の弧長、yaw はそこでの進行方向。踏切は踏切面の弧長の範囲 crossing_zone` も付ける。

Raises `ValueError`: layout が town_chain の物でない、side が left/right でない。

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_layout · town_world · town_centerline · 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_stop_lines — DRIVE town op