Each link below produces an OpenAir file (.txt) compatible with
FlySkyHy, XCTrack, XCSoar, and other XC apps.
Coordinates are written as DMS with cardinal direction; classes are
Q (Danger, fire), R (Restricted, NOTAM), and W (Wave Window, no-landing).
Situational awareness only — not for sole navigation. Wildfire and NOTAM data are pulled live from BC Wildfire Service / CWFIS / NAV CANADA; no-landing zones are community-maintained polygons. FlySkyHy keeps only one custom OpenAir file at a time — importing one file replaces any previously imported custom airspace.
Fetches NAV CANADA NOTAM polygons, wildfire 5 NM advisory no-fly polygons (same shapes as the website's red advisory rings — buffered hull or 5 NM disk per fire), and all enabled no-landing overlays — one OpenAir file with the same semantics as each section below.
NAV CANADA polygon NOTAMs (CFPS-derived) — wildfire / mil exercise / skydiving / glider /
UAV / CYR / training / general categories whose lateral limits could be parsed
(BOUNDED BY polygons or RADIUS … CENTRE … disks).
Altitudes (AH / AL) come from each NOTAM's
F) / G) lines; falls back to GND .. UNLIM.
For every active fire (BC Wildfire Service for BC; CWFIS for the rest of Canada):
a 5 NM outward buffer of the published perimeter, or a
5 NM geodesic disk for incidents with no published outline.
These are the same red advisory rings shown on the website map. Class
Q (Danger) with GND .. UNLIM — fires with status
OUT are dropped.
Every enabled community no-landing overlay (from CONFIG.noLandingOverlays),
emitted as AC W (Wave Window) so apps render them as informational and don't
alarm on entry. Use your XC app's per-class styling to make them outline / shaded.
How alarms behave — XCTrack / XCSoar / FlySkyHy will alarm on
Q and R by default, and treat W as informational.
Final behaviour depends on each pilot's per-class settings on the device.