Everything Vindrose shows comes from Norwegian public sources. This page says who, and what we know is missing.
From dronesoner.no (Luftfartstilsynet, the Norwegian Civil Aviation Authority), which aggregates five bodies:
| Dataset | NOR_ED269_compliant_geozones_July-2026 |
|---|---|
| Published | July 2026 |
| Zones | 4,383 (31 identical duplicates removed) |
| Format | ED-269, the EU standard for UAS geographical zones |
The app always shows the age of the data. We stamp it with the dataset's publication date — not with when we happened to run a build job — precisely so a July dataset does not look like it was updated yesterday.
Nine security areas are published without map geometry. They exist as records in the dataset but carry no polygon, so they cannot be checked automatically against your position. Vindrose warns about them by name instead:
This has been reported upstream.
NOTAM are not in the ED-269 file. Temporary restrictions are published continuously, and the file contains no time information at all. So always check ippc.no.
Seasonal variation exists only in prose. Some conservation regulations apply for part of the year, but the dataset has no structured time windows. Vindrose reproduces the text verbatim and never guesses whether a ban applies today.
The altitude limits in the file are a placeholder. Every zone is given as 0–300 m with no real variation, so Vindrose does not use them and treats zones as flat.
From MET Norway (Locationforecast 2.0). The forecast is for ground level and is explicitly not valid at altitude — see the front page for what that means in practice.
Basemap from Kartverket, ©Kartverket, licensed under CC BY 4.0.