Copied to clipboard

Lightbox title

Unit
Unit value
Time steps
Hourly
3 Hourly
6 Hourly
Daily
Time interpretation
Time interpretation value
Bits per value

The bitsPerValue determines the relative size of the data download required for each parameter. The bitsPerValue ranges from 12 to 20 bits for our current parameters.

Note the data download size is not a direct multiplier of the bitsPerValue as there are standard overheads within the generated GRIB files which are common for all parameters. However, the bitsPerValue is a good guide to the relative cost of each parameter.
BitsPerValue value
Level Type
Level type value
Parameter ID
Parameter ID value
Ok

Application name

Your application name is used as a link to our gateway through which your API requests are processed. On subscription we automatically create an application for you with a default name. The application name has no bearing on how things are processed.

Close

Notification title

Message

By ordering products from the Met Office Weather DataHub and clicking “confirm”, you are agreeing to be bound by the Met Office Weather DataHub Terms and Conditions which apply to the order.

Should you wish to discuss licensing terms, then please call 0033 678 3454 or email licensing@metoffice.gov.uk

Cancel

About monthly data usage

Data plans

All data plans are managed in GBs worth of data but note we use 1,024 conversion for all our plans. So 1,024 GB is equivalent to 1 TB (Terabyte). Strictly speaking this is TiB and GiB i.e. Tebibyte and Gigibyte

Close

About monthly data usage

Estimate monthly usage

Estimated order size if all selected data for all runs is taken based on an expected file size per parameter. Note this is a guide only and actual sizes for each parameter will vary.

Whilst every effort has been made to make the estimated file download sizes accurate customers should check the projected figures which are based on actual downloads as well as the estimated file sizes.

Usage this month

This figure is the actual data transferred for this calendar month so far.

Projected Monthly Usage

The projected monthly usage is calculated by:

  • retrieving the amount of data downloaded in the last 30 days
  • divide by the number of active days (>0 bytes downloaded) to get a daily average
  • multiply by the number of days in the current month for maximum monthly usage
Close

Order Naming

Note when used in the API the order name/ id is transformed by substituting spaces with hyphens and all letters are lowercase e.g. 'GLOBAL10k 12amRun' becomes 'global10k-12amrun'

For the avoidance of doubt the transformed order id to use in the API reproduced below in the Delivery section

Close

You're about to be taken to a new tab

The button below will take you to the Billing page on Weather Data Hub, which will open in a new tab.

Please update your details there and then return to this tab to proceed with your subscription.

If you have been logged out, you can find the Billing page by clicking on your email address in the top-right corner and then going to 'My Organisation', after logging back in.

Close Open Billing Page

Taxpayer Identification Number (TIN)

The taxpayer identification number (TIN) is the unique identifier assigned to the Account Holder by the tax administration in the Account Holder’s jurisdiction of tax residence. It is a unique combination of letters and/or numbers used to identify an individual or entity for the purposes of administering the tax laws of that jurisdiction.

For more information, please see https://www.gov.uk/hmrc-internal-manuals/international-exchange-of-information/ieim402040

Close
Login/Register

File naming conventions

This page describes the conventions used in generating the file names made available via our atmospheric model data api.

By Latest run / Specific Run

There are two different ways to request the atmospheric model data file

  • by latest run for that model run
  • by specific run

The two different request profiles will retrieve the same data so in normal operation both options are not required.

Latest Run (+RR)

This request retrieves the latest data available for a particular run e.g. +00 or +15 for the midnight and 3pm run respectively.

Specific Run (YYYYMMDDRR)

This requests a specific run on a specific day.

2021030906 will retrieve the data files for the 06:00 run on the 9-Mar 2021

We retain atmospheric model data files for the last two days

File Name Components

When files are generated we always try to honour any preferences you have set on the order but we may require to deliver your files with a lower level of granularity (splitting by parameter, level or time step) as we restrict files to a maximum size.

The files generated for each order are listed on the order summary page and follow the convention below.

<leveltype>_{parameterid}_(level)_<run>_(timestep)

Naming Component

Optionality

Notes

leveltype

always present

One of atmosphere, atmospheretop, ground, maxwind, meansea, zeroisotherm, isbl, agl

More on level types

parameterId

at least one entry, can repeat

Multiple parameterids exist in a list separated by '+' if file sizes permit aggregation

level

optional

Height (agl - above ground level) or pressure (isbl - isobaric pressure level)

run (RR)

always present

Depends on the api request used.

For a specific date 'YYYYMMDDRR' where RR is the run time in the day.

For latest data, date is discarded and only 'RR' included which will be in the range of 00-23.

More on api requests and integration

time step (T)

optional

When split by time step forecast time step is appended

member (mnn)

optional for ensemble models (MOGREPS-G)

prefixed with 'm' and a member id that varies by run time, so suffixes range from

  • 00/ 12 runs: ‘m0’ to 'm17’
  • 06/ 18 runs: ‘m0’ and ‘m18' to 'm34’

Sample file names

File per timestep

atmosphere_total-cloud-cover_+RR_T
atmosphere_total-cloud-cover_YYYYMMDDRR_T

  • Example
    atmosphere_total-cloud-cover_+00_0
    atmosphere_total-cloud-cover_2020070600_0

Multiple timesteps in one file

atmosphere_total-cloud-cover_+RR
atmosphere_total-cloud-cover_YYYYMMDDRR

  • Example
    atmosphere_total-cloud-cover_+00
    atmosphere_total-cloud-cover_2020070600

Ensemble model split by member

atmosphere_total-cloud-cover_+RR_mnn
atmosphere_total-cloud-cover_YYYYMMDDRR_mnn

  • Example
    atmosphere_total-cloud-cover_+00_m0
    atmosphere_total-cloud-cover_2020070600_m25