crossing op• Data kinds: any → table
• Call: import fullseye as fs; fs.ledger.exit_room_check(queue_rear, far_edge: 'float', car_length: 'float', *, gap: 'float' = 1.0, beyond: 'float' = 0.5) (to call the implementation directly, import drivecrossing; drivecrossing.exit_room_check(queue_rear, far_edge: 'float', car_length: 'float', *, gap: 'float' = 1.0, beyond: 'float' = 0.5); from the registry, opsdrive.get("exit_room_check"))
Whether there is room on the far side of the railroad crossing (likewise for crosswalks and intersections) for the vehicle to stop (Art. 50(2)). Arrays allowed.
If you stop queue_rear behind the rear end gap of the car ahead, your own rear end = queue_rear − gap − car_length. If this is at least far_edge + beyond, you may enter. Return values: room = queue_rear − far_edge, need = car_length + gap + beyond, ok, rear_if_stopped. If there is no car ahead, queue_rear = +∞.
Empty input (queue_rear with 0 elements) raises ValueError.
• 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.
• poc_driving_crossing — py -3.11 examples/poc_driving_crossing.py
table as input)course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same
crossing)crossing_timing_check · crossing_gate_state · crossing_lamp_signal · lamp_pair_phase · crossing_clear_time · crossing_stop_check · track_sight_distance · sight_triangle_distance
*Provenance: drivecrossing.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.