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 1 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.

The bits per value may differ across level types.
BitsPerValue value
Bits per value

The bitsPerValue determines the relative size of the data download required for each parameter. The bitsPerValue ranges from 1 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.

The bits per value may differ across level types.

Level Type
Bits per 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

Payment Failed

Please check your payment details are correct and resubscribe or contact dpt@metoffice.gov.uk for more information.

Close

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

Weather DataHub Accessibility Statement

This accessibility statement applies to Weather Data Hub - https://datahub.metoffice.gov.uk/

This website is run by the Met Office.

How accessible this website is

We know some parts of this website are not fully accessible. You can see a full list of any issues we currently know about in the Non-accessible content section of this statement.

Feedback and contact information

If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact us using the details below.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

We'll consider your request and get back to you as soon as possible.

Read tips on contacting an organisation about inaccessible websites.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations'). If you're not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

If you are in Northern Ireland and are not happy with how we respond to your complaint you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations') in Northern Ireland.

Technical information about this website's accessibility

The Met Office is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Pricing and Plans (Atmospheric)

Perceivable

  • The Register button is visually styled like a button, but functions like a link. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectation and their experience when they interact with the content.
  • The tables on this page do not have the necessary semantic structure for screen readers to perceive the information and relationships within the tables. This fails WCAG 1.3.1 Info and Relationships (A).
  • The heading structure used within the page goes from H1 to H3, skipping heading hierarchy. This creates a further gap between user expectation and experience and risks content been missed. This fails WCAG 1.3.1 Info and Relationships (A).

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).

Documentation (Getting Started)

Perceivable

  • The page contains a list of items that is visually styled as a list, but doesn't have the semantic structure to convey to users of an assistive technology that a list is present. This prevents users adapting this content. This fails WCAG 1.3.1 Info and Relationships (A).
  • The Get Support button is visually styled like a button, but functions like a link. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectations and their experience when they interact with the content.
  • The Get Support button has a focus indicator, but this indicator does not have the required contrast ratio for elements of the user interface. This may mean users struggle to perceive where they are when navigating through the page. This fails WCAG 1.4.11 Non-text contrast (AA).

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • The “Getting started with Weather Data Hub” heading is duplicated and this creates a situation where the meaningfulness and usefulness of the heading is diminished for users. This fails WCAG 2.4.6 Headings and Labels.

Documentation (Atmospheric / Overview)

Perceivable

  • The Get Support button is visually styled like a button, but functions like a link. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectations and their experience when they interact with the content.
  • The Hide details chevron conveys to users when the details section is open or closed. This element of the user interface does not have sufficient colour contrast. This may mean users struggle to see this element of the user interface, failing WCAG 1.4.11, Non-text contrast (AA).

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • Information for each of the “Model Specifications” cannot be opened / closed via keyboard. This prevents users using the information within this section of the page. This fails WCAG 2.1.1 Keyboard (A).

Documentation (Atmospheric / How to build)

Perceivable

  • Images on this page do not contain alt text descriptions that provide equivalent meaning and consequently users of assistive technology may struggle to “build” an order without that equivalent meaning, this fails WCAG 1.1.1 Non-text content (A)
  • The page contains a list of items that is visually styled as a list, but doesn't have the semantic structure to convey to users of an assistive technology that a list is present. This prevents users adapting this content. This fails WCAG 1.3.1 Info and Relationships (A).

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).

Documentation (Atmospheric / Sample Data)

Perceivable

  • Page contains a data visualisation within a video which uses colour to convey information. There is no additional visual cue. Because not everyone perceives colour in the same way, information within the video may not be conveyed. This fails WCAG 1.4.1 Use of Color (A).
  • The visualisation doesn't contain either a text alternative for the video-only content, transcript or an Audio description. This prevents the visual elements of the video from being conveyed to every user. This fails WCAG 1.2.1 Video Prerecorded and WCAG 1.2.5 Audio Description.
  • A checkbox is used for users to provide consent to terms and conditions associated with using the sample data. This element of the user interface does not have sufficient colour contrast. This fails WCAG 1.4.11, Non-text contrast (AA). This is likely to effect every page where a checkbox is used.
  • The checkbox conveys to users when the checkbox has focus for keyboard only users. This element of the user interface does not have sufficient colour contrast. This fails WCAG 1.4.11, Non-text contrast (AA). This is likely to effect every page where a checkbox is used.

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • The page title for this page is not unique. This is likely to create confusion for users who depend on the page title to distinguish between different tabs. This fails WCAG 2.4.2 Page Titled.
  • When the checkbox is checked a link is revealed on screen. This link isn't wrapped in text and therefore no in context is provided to users. This is a failure of WCAG 2.4.4 Link Purpose (In Context).

Documentation (API / Atmospheric model)

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • The page title for this page is not unique. This is likely to create confusion for users who depend on the page title to distinguish between different tabs. This fails WCAG 2.4.2 Page Titled.
  • Not all links are wrapped in text and therefore no in context is provided to users. This is a failure of WCAG 2.4.4 Link Purpose (In Context)

Documentation (API / Orders)

Perceivable

  • The focus indicator used to show keyboard only users their position on the page does not have sufficient colour contrast. This fails WCAG 1.4.11, Non-text contrast (AA). This is likely to affect every element on the page.
  • Some of the text on the page does not have sufficient colour contrast with the background. This is likely to create instances where text becomes much harder to read. This fails WCAG 1.4.3 Contrast Minimum (AA).
  • There is no heading level 1 element on the page. This is likely to create challenges for users who use headings to navigate the page. This fails WCAG 1.3.1 Info and Relationships.

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • The page title for this page is not unique. This is likely to create confusion for users who depend on the page title to distinguish between different tabs. This fails WCAG 2.4.2 Page Titled.
  • Some elements of the page are not keyboard accessible and prevent keyboard only users from autopopulating the form in an equable manner. These elements fail WCAG 2.1.1 Keyboard (A).

Glossary

Perceivable

  • The “Clear filters” element is visually styled like a link, but functions like a button. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectations and their experience when they interact with that element.
  • Each glossary term incorporates a table. These tables do not have the necessary semantic headings to enable the relationships within the table to be conveyed. This fails WCAG 1.3.1. Info and Relationships (A).
  • Information within the sections on the page becomes unreadable when zoomed at 400%. This fails WCAG 1.4.4 Resize Text (AA).

Operable

  • The tool tips provide additional information to users when they are interacted with. Keyboard only users are not able to access this information. This fails WCAG 2.1.1 Keyboard (A).

Robust

  • There is no association between the name / value for the “1.5m” and “10m” checkboxes. This prevents some users filtering using either of these options when using assistive technology. This fails WCAG 4.1.2 Name, Role, Value (A).

Support (FAQ's)

Perceivable

  • A chevron conveys to users when an accordion element is open or closed. This element of the user interface does not have sufficient colour contrast. This may mean users struggle to see this element of the user interface, failing WCAG 1.4.11, Non-text contrast (AA).
  • When the “Stack Overflow” button receives focus, the indicator isn't sufficiently visible. This may mean users struggle to see this element of the user interface, failing WCAG 1.4.11, Non-text contrast (AA).
  • The “Stack Overflow” element is visually styled like a button, but functions like a link. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectations and their experience when they interact with that element.

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).

Support (Raise a ticket)

Perceivable

  • The Raise a support ticket form has a number of required fields. These are indicated using a red asterisk. These fields do not have semantic attributes that convey to users of assistive technology that these elements are required. This fails WCAG 1.3.1 Info and Relationships (A).
  • Required fields within the raise a ticket form are designated using a red asterisk. What this red asterisk means is not specified until the end of the form. There is a lack of meaningful sequence (WCAG 1.3.2) within the form.

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).

Support (Service Status)

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • Links within the accordions link to relevant models. These links use generic text and provide no in context to users. This is a failure of WCAG 2.4.4 Link Purpose (In Context).

Support (Service Status / Details)

Perceivable

  • The “Back” and “Reload” elements are visually styled like a button, but function like a link. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectations and their experience when they interact with that element.

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).
  • There is no focus indicator for the back button on this page. Sighted keyboard users depend on focus indicators to understand which element has focus. Without this, users may not be able to use those elements effectively. This fails WCAG 2.4.7 Focus Visible (A).
  • The back link provides no in context to users. This is a failure of WCAG 2.4.4 Link Purpose (In Context) (A).

Support (Upcoming changes)

Perceivable

  • At 200% and 400% the content of the “Parameter name corrections” and “Grib Changes” container overflows its content-block. This makes reading the content unreadable. This fails WCAG 1.4.4 Resize Text (AA).
  • When zoomed at 400% scrolling across both axis is required to read content this fails WCAG 1.4.10 Reflow (AA).
  • A chevron conveys to users when an accordion element is open or closed. This element of the user interface does not have sufficient colour contrast. This may mean users struggle to see this element of the user interface, failing WCAG 1.4.11, Non-text contrast (AA).
  • The heading structure used within the page goes from H2 to H4, skipping heading hierarchy. This creates a gap between user expectation and experience and risks content been missed. This fails WCAG 1.3.1 Info and Relationships (A).

Operable

  • Skip to content across all pages of the website does not move the user to the main content of a page. This will increase the length of time keyboard only users spend navigating through repeated content. This fails WCAG 2.4.1 Bypass Blocks (A).

My Subscriptions

Perceivable

  • When zoomed at 400% scrolling across both axes is required to read content. This fails WCAG 1.4.10 Reflow (AA).
  • The heading structure used within the page goes from H1 to H3, skipping heading hierarchy. This creates a gap between users' expectations and experience and risks content been missed. This fails WCAG 1.3.1 Info and Relationships (A).

Operable

  • It is not possible for keyboard users to expand accordions for “Atmospheric”, “Site Specific”, “Images” and “Observations” as the expand element is not keyboard accessible. This fails WCAG 2.1.1 Keyboard (A).
  • The image within the “Map Images” section has continual movement that cannot be paused, stopped or hidden. Some users with cognitive disabilities and attention deficits cannot concentrate with continual movement. This fails WCAG 2.2.2 Pause, Stop, Hide (A).
  • Several links on this page do not provide in context for users. This is a failure of WCAG 2.4.4 Link Purpose (In Context) (A).

My Payments

Operable

  • The “Add Card” link does not provide in context for users. This is a failure of WCAG 2.4.4 Link Purpose (In Context) (A).

Home

Perceivable

  • When zoomed at 400%, scrolling across both axes is required to read content this fails WCAG 1.4.10 Reflow (AA).
  • When a focus indicator is applied to The Met Office Logo it becomes entirely obscured with the text having insufficient colour contrast with the focus indicator. This may mean users struggle to see the logo / text, failing WCAG 1.4.11, Non-text contrast (AA).
  • A chevron conveys to users when an accordion element is open or closed. This element of the user interface does not have sufficient colour contrast. This may mean users struggle to see this element of the user interface, failing WCAG 1.4.11, Non-text contrast (AA).
  • Some of the text on the page does not have sufficient colour contrast with the background. This is likely to create instances where text becomes much harder to read. This fails WCAG 1.4.3 Contrast Minimum (AA).
  • The Find out more button is visually styled like a button, but functions like a link. This fails WCAG 1.3.1 Info and Relationships (A). This creates a likely gap between users' expectations and their experience when they interact with the content.
  • The heading structure used within the page goes from H3 to H1, skipping heading hierarchy. This creates a further gap between users' expectations and experience and risks content been missed. This fails WCAG 1.3.1 Info and Relationships (A).

Operable

  • There is no focus indicator for the Skip Link, Menu elements. Sighted keyboard users depend on focus indicators to understand which element has focus. Without this, users may not be able to use those elements effectively. This fails WCAG 2.4.7 Focus Visible (A).

If you find an issue that we have yet to identify, please contact us using one of the routes described in the 'Feedback and contact information' section of this statement.

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that's not within the scope of the accessibility regulations

3rd party content

Some of our services include third party content which we have no control over. The accessibility regulations do not require us to manage this content, but if you have a problem with any of the content hosted on this website, please contact us using the methods above and we will try to help.

Preparation of this accessibility statement

This statement was prepared on 11 March 2026. It was last reviewed on 21 January 2026.

This website was last tested during October 2025. The test was carried out by our internal UCD team. The testing included manual testing, using semi-automated tools, testing with assistive technologies.

Testing was completed against WCAG 2.2 as the latest version of WCAG at the time of testing.