Velkommen til api.met.no
api.met.no/weatherapi er et grensesnitt mot et utvalg av data fra Meteorologisk institutt. Dataene er fritt tilgjengelige for bruk under disse betingelsene. Se også egne vilkår for bruk av tjenesten. Det finnes mange tredjepartsbiblioteker for tjenesten i forskjellige programmeringsspråk.
Alle jevnlige brukere av API anbefales på det sterkeste å abonnere på vår epostliste for API-brukere siden dette er den eneste kanalen vi vil kommunisere planlagte endringer på utenom websidene (se arkivet for tidligere meldinger).
For driftsstatus and vedlikeholdsmeldinger, se status.met.no (vennligst lag bokmerke i tilfelle siten er utilgjengelig).
For informasjon over hvilke data som er tilgjengelig, samt hvordan disse kan brukes, se dokumentasjonen (engelsk tekst).
Data som eies av andre enn Meteorologisk institutt er ikke tilgjengelig for allmenn bruk. Dette står spesifisert i dokumentasjonen for hvert enkelt produkt. Denne problemstillingen gjelder spesielt radarbildet over Norden og satellittbildene. Les dokumentasjonen for hvert enkelt produkt før bruk.
New Nowcast and return of Geosatellite 2020-10-02
Nowcast 2.0 beta
After the very successfull update to our Locationforecast service, we have now upgraded Nowcast to a similar modern spec. New features include:
While some parts are still missing (documentation, JSON Schema, radar data for the rest of Denmark) it is currently useable enough that you can familiarize yourself with the new data format and start upgrading your clients. Currently we do not have any estimate for how long the current 0.9 version will be supported.
After having been unavailable for two years due to licencing issues, we have finally resolved the situation. Unlike previously when only a small subset was available, we are now able to offer you the whole range of EUMETSAT image products under the CC BY 4.0 license.
With over 4000 different images at any one time this also means that the complete available list is very large and may result in timeouts. We therefore urge you to filter this on your specific requirements, e.g. area, type and size.
Future works in progress
We are currently working on updating our Oceanforecast service to the new JSON standard. We have also started on a new project for improving our map services (as seen on Yr.no). During our cooperation with the University of Oslo we have gotten valuable feedback from students regarding map integrations on mobile app development, but we are also very interested to hear from web developers what kind of maps you would like to see and which protocols and formats you would like to see supported.
If you have any feedback, please send us an email at firstname.lastname@example.org with the subject "Map feature requests". We will later collate this and use for planning new map products which hopefully should be available next year.
For the last couple of years we have been working on a new forecast backend (FORTI) to replace the decade-old, PostgreSQL-based store (WDB). While Locationforecast/1.9 has been running from FORTI for some months now in "compatibility mode", we have finally finalized the new JSON format which will become standard for all weather forecasts soon.
Version 2.0 comes in three different flavours:
This service endpoint will return a response with all available forecast parameters. As we make new forecast parameters available, they will be added to the responses for this service endpoint (we expect to include probability percentile data fairly soon). Also, some geographical areas will have more forecast parameters available than others.
This service endpoint will return a response with only a core set of forecast parameters. All forecast parameters in this endpoint will be available for every location. We will add new parameters to this endpoint as well, but much more rarely, and the size will not increase much. If you feel there is some useful parameters missing here, please let us know.
This service endpoint exists only for backwards compatibility purposes. The parameters in this endpoint and the XML format provided are identical with /locationforecast/1.9, but with more time intervals. Use this if you have an existing application and want to do minimal work to update it. We don't expect adding any more parameters (XML tags) to this format in the future.
We have also introduced an improved topography for the entire world, which should give more accurate temperature forecasts in some areas. This topography will be used if you do not specify altitude in your request. Note that the improved topography is still relatively coarse. We therefore recommend that you specify your own altitude in the request if you have access to your own topography data.
With great power comes great responsibility. Regardless if you're Voltaire, Churchill or Spider-Man, all users must now adhere to the Terms of Service (more below) more stringently. In particular you must pay more attention to the following rules:
Termination of old products
Locationforecast 2.0 will be officially launched on Wednesday 17 June 2020. At the same time version 1.9 will be deprecated. A final termination date has not been set yet, but we plan on turning it off before xmas.
The already deprecated LocationforecastLTS will terminate on 1 Sept 2020. This gives you almost three months to port your applications to Locationforecast 2.0, if you havent already started.
UVforecast has been deprecated as UV data is now included in Locationforecast 2.0 JSON, and will also be terminated on 17 June.
We also expect to launch a version 2.0 of Nowcast in about a month, using FORTI and the same JSON format as Locationforecast.
Terms of Service
This is mainly a rewrite and clarification of the existing rules. While there is nothing radically new under the sun, the old TOS was confusing and badly organized, so many users missed vital points like User-Agent identification and started asking why they were being throttled. Hopefully this version should be clearer and more detailed.
The new TOS is still in draft state, but if you have any questions please let us know before we finalize it later this month.
There have been some minor changes to some specialized products:
The "airquality" profile has been removed
New names of counties and municipalities according to the 2020 reform. E.g. "Buskerud/Røyken/Midtbygda/Røyken" has been changed to "Viken/Asker/Midtbygda/Røyken".
Andre datakilder ved Meteorologisk institutt
- Frost, API for observasjoner og klimadata
- THREDDS for modeller og forskningsdata, inkludert hav og is
Se frie meteorologiske data på met.no for en komplett liste over tilgjengelige for data nedlasting.