crosswalk_overtake_check — DRIVE crossing op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.crosswalk_overtake_check(ego, others, *, crosswalk_start: 'float', crosswalk_end: 'float', zone: 'float' = 30.0, v_moving: 'float' = 0.5) -> 'Dict[str, object]' (to call the implementation directly, import drivecrossing; drivecrossing.crosswalk_overtake_check(ego, others, *, crosswalk_start: 'float', crosswalk_end: 'float', zone: 'float' = 30.0, v_moving: 'float' = 0.5) -> 'Dict[str, object]'; from the registry, opsdrive.get("crosswalk_overtake_check"))

Usage

Whether the vehicle moved ahead of a vehicle traveling in front within a crosswalk etc. or the zone m before it (Art. 38(3)).

ego, others[i] = {"t", "x"[, "v"], "kind"} (x = front end). The moment one's own front end passes another vehicle's front end from behind (linear interpolation) is regarded as "moving ahead"; it is a violation if one's own front-end position at that time is in [crosswalk_start − zone, crosswalk_end], the other is moving (speed > v_moving, assumption), and it is not a specified small motorised bicycle etc. (EXEMPT_KINDS). Return value: ok, events = [{"other", "t", "x", "in_zone", "exempt", "moving", "violation"}].

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

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