This page contains detailed documentation on each of the data feeds associated specifically with mountain area forecasts.
Here we provide detailed descriptions of the following feeds:
The mountain area forecast capabilities data feed provides a summary of which results are available from the get mountain area forecast by site ID data feed, specifying the creation dates, valid from and to dates, and the general risk for each mountain area.
The capabilities web service returns the output of the capabilities data feed in either XML or JSON format. It is recommended that you query the capabilities web service to check whether the forecasts have been updated when querying for new data from the mountain area forecasts web service rather than calling the mountain area forecasts web service repeatedly, as this reduces the amount of data that has to be transferred, enhancing the user experience.
Since the mountain area forecast capabilities web service concerns script forecast data, whenever this web service is used the data category field in the URL should be set to txt, and the resource category field should be set to wxfcs. You should also set the data format in the URL to specify whether the web service should return XML or JSON, and include your API key in the query string.
The following examples show a typical result of a call to the capabilities web service requesting a complete list of timesteps available from the mountain area forecasts web service for a given site ID.
The XML that follows is a representative response to a call to the following URL, with a valid key:
http://datapoint.metoffice.gov.uk/public/data/txt/wxfcs/mountainarea/xml/capabilities?key=<APIkey>
The JSON that follows shows the structure of a representative response to a call to the following URL, with a valid key:
http://datapoint.metoffice.gov.uk/public/data/txt/wxfcs/mountainarea/json/capabilities?key=<APIkey>
The XML and JSON responses produced by this web service are identical in terms of their high level structure and the information they represent. Each contains a single MountainForecastList object (or node in XML), defined as follows:
The MountainForecastList object comprises a number of MountainForecast objects, defined below.
A MountainForecast object defines a single mountain forecast, and contains the following elements:
The mountain area forecast site list data feed provides a list of the locations (also known as sites) for which results are available for the mountain area forecast data feed. You can use this data feed to find details such as the ID of the site that you are interested in finding data for.
The mountain area forecast site list web service is used to check which locations the mountain area forecast data feed provides data for. You should set the data format in the URL to specify whether the web service should return XML or JSON, and include your API key in the query string.
The following examples show a typical result of a call to the mountain area forecast site list web service requesting a complete list of sites for which mountain area forecasts are available.
The XML that follows is a representative response to a call to the following URL, with a valid key:
http://datapoint.metoffice.gov.uk/public/data/txt/wxfcs/mountainarea/sitelist?res=daily&key=<API key>
The JSON that follows shows the structure of a representative response to a call to the following URL, with a valid key:
http://datapoint.metoffice.gov.uk/public/data/txt/wxfcs/mountainarea/sitelist?res=daily&key=<API key>
The response produced by this web service contains a single Locations element, which in turn contains a set of Location elements, defined as follows:
A Location element defines a single site, and contains the following attributes:
This provides access to mountain area forecasts covering the four day period after their issue date. The data provided by the web service is updated once a day at least, but may be updated more often. For a full list of the sites, call the mountain area forecasts site list data feed [HL].
Since this web service supplies forecast data, whenever this web service is used the resource category field in the URL should be set to wxfcs. You should also set the data format in the URL to specify whether the web service should return XML or JSON, and include your API key in the query string.
The following examples show a typical result of a call to the mountain area forecasts web service requesting the mountain area forecast for Brecon Beacons. The following section provides a detailed description of the structure and content of the responses.
The XML that follows is a representative response to a call to the following URL, with a valid key:
http://datapoint.metoffice.gov.uk/public/data/txt/wxfcs/mountainarea/xml/100
The JSON that follows shows the structure of a representative response to a call to the following URL, with a valid key:
http://datapoint.metoffice.gov.uk/public/data/txt/wxfcs/mountainarea/json/100
The XML and JSON responses produced by this web service are identical in terms of their high level structure and the information they represent. Each contains a single report object (or node in XML), defined as follows:
The report object comprises contains the following attributes:
It also contains the following elements:
title: This is always Mountain Forecasts
location: This is the name of the location to which the report refers
issue: This is a user friendly representation of the issue date. It has two attributes, date [B], which represents the date of issue, and time, which represents the time of issue
ValidFrom: This is the start of the validity period
ValidTo: This is the end of the validity period
Validity: This is a textual representation of the validity period
IssuedDate: This is a textual representation of the issue date
Hazards: This is a summary of the hazards that may be encountered and the current level of risk presented by each. The structure of the Hazards object is described below
Overview: This is an overview of the weather in the relevant area
Forecast_Day0: This is a detailed forecast for day 0. The structure of the Forecast_Day0 object is described below
Forecast_Day1: This is a detailed forecast for day 1. The structure of the Forecast_Day1 object is described below
Outlook_Day2: This is a short paragraph giving the general outlook for day 2
Outlook_Day3: This is a short paragraph giving the general outlook for day 3
Outlook_Day4: This is a short paragraph giving the general outlook for day 4
The Hazards object comprises a number of Hazard objects, defined below.
A Hazard object comprises contains the following attribute:
no: This gives the number of the Hazard
It also contains the following elements:
element: This describes the type of Hazard
risk: This gives the level of risk
comments: This gives additional comments
The Forecast_Day0 object represents the forecast for day 0, and contains the elements listed below.
The WeatherPPN object represents the weather per period, and contains a number of WxPeriod elements, whose structure is defined below.
Each WxPeriod object represents a single period. A WxPeriod object contains a period attribute, which gives the number of the period. It also contains the following elements:
The Forecast_Day1 object represents the forecast for day 1, and is identical in structure to the Forecast_Day0 object, except that there is no WeatherPPN element.
The Outlook_Day2 object gives a textual description of the outlook for the weather on day 2.
The Outlook_Day3 object gives a textual description of the outlook for the weather on day 2.
The Outlook_Day4 object gives a textual description of the outlook for the weather on day 2.
A guide to choosing the right product
If you want to use our data you will need an API key
Last updated 10:00 on 17 May 2013
Log out of Met Office DataPoint