no_stopping_zones — DRIVE `crossing` op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.no_stopping_zones(features: 'Iterable[dict]', *, in_service: 'bool' = True) -> 'Dict[str, object]' (to call the implementation directly, import drivecrossing; drivecrossing.no_stopping_zones(features: 'Iterable[dict]', *, in_service: 'bool' = True) -> 'Dict[str, object]'; from the registry, opsdrive.get("no_stopping_zones"))

Usage

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

道に沿った施設から、44 条 1 項の駐停車禁止の区間を作る。

features[i] = {"kind", "start", "end"}(バス停は "at" = 標示板の位置でもよい)。kind ∈ `NO_STOP_DISTANCE`。

区間 = [start − d, end + d] (d = その号の距離)。バス停は運行時間中(`in_service`)だけ。

返り値: `zones = [(a, b, kind, 号)] (元の順)、merged` = 重なりを併せた (k, 2) の配列(昇順・互いに素)。

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

no_stopping_zones — DRIVE crossing op