Locationforecast - Weather forecast for a specified place
This modules implements a full forecast for one location, that is, a forecast with several parameters for a nine-day period.
The parameters are temperature, wind speed, wind direction, pressure, precipitation, cloudiness, fog, lowClouds, mediumClouds, highClouds and humidity.
Since version 1.8 it will also have probability-elements for temperature, wind and symbol (norwegian locations only). A probability element specifies certainty of prognoses for a given parameter for a given time. This certainty is defined by a probabilitycode in the following manner:
probabilitycode certainty values --------------- ---------------- 0 [90% , 100%] 1 [50% , 90%> 2 [ 0% , 50%>
While we only serve current forecasts via the API, you can find historical forecast model data in NetCDF format on http://thredds.met.no/thredds/metno.html.
The availability and content of this product may change without further notice.
latitude in decimal degrees, mandatory
longtitude in decimal degrees, mandatory
whole meters above sea level (integers), optional. This option will only be used outside Norway. In Norway the height will always be taken from our own topographical model.
Operational status for each model can be checked like this:
The schema for the xml delivered by this product is available from
- Q. Until now I have been looking at the 'runended' parameter to tell me when the forecast model was last updated (i.e. how "fresh" the forecast is). How do I find out when the underlying forecast model was updated for the received data?
A. The "runended" parameter is only meaningful when comparing two different forecasts for the same location (the newer one hopefully being more correct). To find out when to download newer versions, use the "nextrun" parameter.
Note however that the "nextrun" timestamp is *not* an exact promise, but an approximate guess of when the next model will be ready (variable depending on supercomputer load) plus a random delay to allow for model copying latency, XML caching timeouts etc.
- Q. Why can't I just add a constant time interval to the "runended" parameter?
A. In addition to the reasons above, the model update periods for the various areas is expected to change without notice as we get more data and constantly try to improve the product. When the model update frequency increases, this will be reflected in the "nextrun" parameter.
- Q. Are historical weather forecasts available via the api?
A. Unfortunately no, as the sheer amount of data makes it impossible. Our Nordic model run data are available as NetCDF files as described in the API documentation. Unfortunately we cannot distribute global models due to licensing issues.
We are launching a new backend with a unified model. The XML output should identical in structure and validate against the existing schema, but may have some different time intervals.
The main differences are:
- Only 1- and 6-hour forecasts will be supported, the (rarely used) 2- and 3-hour intervals will be removed.
- We have added precipitation minvalues and maxvalues for the whole forecast for the Nordic and Arctic regions, not just the first two days.
- The EPS, LOCAL and EC* models in the meta header are no longer relevant. We now how only one model (met_public_forecast), with a single pair of runended and nextrun timestamps.
- The global forecast (outside the Nordic and Arctic regions) will be shortened by 6 hours. As a compensation it will update every 6 hours, instead of every 12 hours as previously (not 3/6 as stated in email).
Should you experience any problems with the new backend, we suggest switching to LocationforecastLTS until you can make the necessary changes.
- New version 1.9. Old version, 1.8, will expire on 2014-09-09
- new weather symbols are added for finer scale representation of the weather situation, see https://aa0206x0905nfqpv5.api.met.no/weatherapi/weathericon/1.1/documentation .
- weather symbol ids changed to CamelCase
- "celcius" unit name corrected to "celsius"
Version 1.5 of locationforecast will expire at 2011-10-01. Note that log entry below stating that version 1.5 will be available until version 1.9 is released is no longer correct.
New attributes for the precipitation element: minvalue, maxvalue and probability. Note that these attributes will only be available for locations in a limited area in Europe. Longterm forecast/EC-data for norwegian locations will have fewer parameters available than version 1.5.
1.8 is meant as a transitional version, you may use 1.5 until we release version 1.9. Version 1.7 will be available until 2010-10-01.
Precipitation and symbol values for the first time intervals have been missing in all earlier versions. This has now been corrected.
1.7 is meant as a transitional version, you may use 1.5 until we release version 1.8.
Version 1.6 will be available until 2010-09-01.
- probability elements added.
- fewer elements available for EC-data.
1.6 is meant as a transitional version, meaning that you may use 1.5 until we release version 1.8.
- new element, humidity, added to location.
- version 1.4 will expire 2008-11-01.
- changes in
<model>element: Added attribute termin, replaced attribute timespan with the attributes from and to.
- version 1.3 will be available up to and including 2008-03-01.
- New version, 1.3, available.
- v1.3 includes element
<meta>, with info about the forecast models.
- v1.2 will be available up to and including 2007-11-15.
- New version, 1.2, available.
- Version 1.1 will be available up to and including 2007-10-02.
- Added xml-elements: fog and low/middle/high - clouds.
- Value of xml-element 'temperature' now originates from a different model-parameter.
- Locationforecast has now limited access
- Locationforecast is might return the XML as plain xml or zipped.
- Initial release version