For BVLOS, the operator can't see the aircraft. 3D Map Explorer fuses every contact source into one beyond-visual-range picture, samples the terrain along the GCS↔aircraft path to tell you whether the radio link clears the ridge, and flags closing traffic for deconfliction. The two questions a BVLOS operator actually needs answered, on one map.
BvlosService folds three live stores — Remote ID, MAVLink (own-ship + friendly), and ADS-B (crewed, via SDR/Beast/SBS1) — into a single picture, normalized into one contact shape. Any source is optional; the picture renders with whatever's available.
// normalized contact — source-tagged { "id": "DAL488", "kind": "Adsb", "rangeM": 1840, "closingKt": 42, "threat": "Warning" } → red overlay + SSE proximity alert
Two capabilities sit on top of the fused picture — and they're the ones that actually matter when the aircraft is over the horizon.
Per non-own-ship contact: range + bearing + closing-rate → threat level. Caution within radius; Warning when closing.
Samples the registered DEM along the GCS↔aircraft great-circle path — does the radio/telemetry link clear the terrain?
Enter/exit edge detection on threat-level changes → SSE fan-out at /api/bvlos/events.
Yellow = Caution, red = Warning — driven straight from the deconfliction classifier.
CautionRadiusM / WarningRadiusM tune to airspace class or mission profile.
Each feed optional; absent sources don't break the picture — it renders with what's live.
| Capability | Endpoint | Notes |
|---|---|---|
| Capability discovery | GET /api/bvlos/capabilities | Which feed sources are live |
| Fused picture | GET /api/bvlos/picture | Normalized contacts (?gcsLat&gcsLon) |
| Traffic list | GET /api/bvlos/traffic | Per-contact range/bearing/closing/threat |
| Comm-link LOS | GET /api/bvlos/commlink | DEM path profile GCS↔aircraft |
| Active alerts | GET /api/bvlos/alerts | Current proximity alerts |
| Live alerts (SSE) | GET /api/bvlos/events | Enter/exit edge-detection stream |
| Schema | GET /api/bvlos/schema | Contract for integrators |
Fusion + deconfliction reflect BvlosService on commit 5e21700c4 (feat/bvlos-awareness). Comm-link LOS accuracy depends on the registered DEM resolution. This is situational-awareness tooling, not a certified detect-and-avoid system.
Fused traffic, terrain-sampled comm-link line-of-sight, and closing-rate deconfliction — the BVLOS picture a crew station needs.
