parking_position_check — DRIVE `crossing` 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.parking_position_check(rear: 'float', front: 'float', zones_result: 'dict') -> 'Dict[str, object]' (to call the implementation directly, import drivecrossing; drivecrossing.parking_position_check(rear: 'float', front: 'float', zones_result: 'dict') -> 'Dict[str, object]'; from the registry, opsdrive.get("parking_position_check"))

Usage

Whether the car body [rear, front] overlaps a no-stopping-or-parking section. zones_result = return value of no_stopping_zones.

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

返り値: ok、overlap = 重なりの長さの最大 [m]、reasons = 重なった区間の (kind, 号)。端に触れるだけは重ならない。

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

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 (`crossing`)

crossing_timing_check · crossing_gate_state · crossing_lamp_signal · lamp_pair_phase · crossing_clear_time · exit_room_check · crossing_stop_check · track_sight_distance

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

parking_position_check — DRIVE crossing op