api.met.no/weatherapi is an interface to a selection of data produced by MET Norway. The data are available for use under a Creative Commons license. See also separate conditions for use of the service. Several people have developed third-party client libraries for various programming languages.
All regular users of the API are strongly recommended to subscribe to our API-users mailing list as this is the only channel on which we will communicate planned changes outside the API itself (see the archives for past notifications).
For operational status and maintenance notifications, see status.met.no (please bookmark in case there is a problem with the site).
Data owned by other institutions than MET Norway is not available for unrestricted public use. This is specified in the documentation of each product. Examples of such products are the Nordic radar images and some satellite images. Refer to the documentation of each product.
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".
All quiet on the Corona front 2020-04-20
Hope you are all doing ok in these difficult times. Here at MET Norway it's business as usual. Most of us are working from home, but since the API team already did this for half the week there's not much difference. Here's a summary of the changes so far this year:
End of Life'd products
The following products have been deprecated and will be removed on
The following have also been deprecated, probable EOL times as indicated:
Version 2.0 is nearing completion, the only major feature missing is documentation. We have decided to split the output into three different endpoints:
Also, the unit for temperature has been changed in JSON from "C" to "celsius" to conform with CF standards.
We are also happy to launch a new set of corresponding weather icons. Unlike the former numerical codes in 1.9, the 2.0 "symbol_code" variable is based on a mnemonic code and correspond exactly to the icon filename (minus extension). All icons are available in PNG, SVG and PDF formats, and can be downloaded as a gzipped TAR archive:
In addition you can also get a table matching the new and old symbol codes, as well as explanatory texts in English and several variations of Norwegian:
Radar have been upgraded to version 2.0, with new parameters, new areas, new sizes and a new projection. GIF animations will still be producted for the time being.
The new version 2.0 delivers both SIGMETS and AIRMETS, but now also includes wind shear warnings. You can now ask for each type separately, but by default you will get all in the same response. Also the long-standing bug where warnings would be included twice have finally been fixed.
This was previously part of Upperwindweather, but has now been launched as a separate product.
As mentioned last year we have deprecated the LocationforecastLTS product, which will be retired some time after we have launched the new Locationforecast 2.0. In the mean time, the background model for the Nordic area (MEPS) have been replaced with a new, improved model (CMEPS) which is run every hour.
Unfortunately, some little used parameters are no longer present in the new model, which means that some slight changes have been made to locationforecastlts:
These changes are only be visible for the Nordic area (Norway, Sweden, Denmark and Finland). The rest of the world (which uses the EC model) remains unchanged.
Some of you may have noticed that about half of the municipalities in Norway got new codes ("kommunenummer") this year. This was implemented in MetAlerts this March. As you cannot search on municipalites yet (only counties) rhis does not affect the API interface, but if you are extracting kommunenr from the CAP files you should search for both old and new numbers.
In March we changed the file storage backend for non-dynamic products. This should result in faster response times and greatly reduce the occurence of delivering stale data.
Future plans for 2020
Other data sources at MET Norway
- Frost, API for observations and climate data
- THREDDS for model and research data, including sea and ice models
See free meteorological data on met.no for a complete list of data services.