Put forecast context beside the pilot, not in another browser tab.
This mock instrument surface shows how point forecasts and time-aware corridor samples can support a flight computer, vario, or companion app before and during a task.
Companion display
Task forecast ahead
2.1 m/s
30 km ahead, 12:54 UTC
5,200 ft
At estimated arrival
10 km
Spacing along bearing
9 kt WNW
Surface, plus winds aloft
Conditions ahead remain usable, but the forecast weakens after the valley crossing. Treat this as model guidance beside live sky, traffic, terrain, airspace, and pilot judgement.
{ "route": { "time_aware": true, "sample_spacing_km": 10 }, "samples": [ { "along_track_km": 30, "estimated_arrival": "12:54", "valid_time": "13:00", "wstar_ms": 2.1, "cloudbase_agl_ft": 5200, "surface_wind_speed_ms": 4.6 } ]}Fetch server-side, cache against forecast runs, then sync compact summaries to an app or instrument. Do not put live Convek API keys into public firmware or browser code.
Small payloads for cockpit and companion-app displays.
Flight computers and companion apps do not need a full weather map to be useful. They need compact forecast context: expected lift, usable height, cloudbase, wind, convergence, and what changes along the next part of the task.
Convek is designed for server-side integration. Fetch the forecast, cache it against the model run, then sync the small subset your device or app needs. Keep API keys off public firmware and browser-only clients.