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

Migration to new API gateway service

As part of our ongoing commitment to improving our services, and your user experience, we are making changes to the API gateway that powers Met Office Weather DataHub.

In January 2024 we are starting a migration process to a new API gateway service for all existing users. This essential change will facilitate the growth and improvement of the Met Office Weather DataHub and enable us to accelerate the delivery of new data sets to our valued users.

All users with an existing data plan will have until Tuesday 30 April 2024 to migrate over to the new API gateway service to avoid loss of service.

For more information, please visit our frequently asked questions (FAQs).

Step by step overview

If your subscription is marked as 'legacy', you will be required to migrate your data plan. We recommend testing your new subscription in parallel to your existing plan before migrating. Please see our FAQs to understand how.

Please follow the steps below.

Step 1:

Within your subscriptions, plans that require migrating to the new API gateway will be labelled as legacy. In order to continue downloading data you will need to select the 'migrate' button which will begin your migration process.

IBM Subscription

Step 2:

You will be asked to confirm if you would like to continue with the migration process and be given the option to review the changes that have been made along with the API documentation.

Migrate Warning

Step 3:

Once you have confirmed you would like to continue with the migration process you will be presented with your new API key that you can use to continue requesting data.

New Credentials

Step 4:

On completion of the migration process the legacy notification will then disappear.

You will need to update your client code to use our new APIs. The changes include the base URL and request headers, and you will need to ensure that you are using URL encoding. Documentation and sample code will be available to assist you.

Subscription Migrated

Please note:

The above steps will also need to be completed for any additional subscriptions you may have.