UK Hourly Rainfall data - Columns in the RH table
Table Description -
Columns in the RH table -
How to start filtering the rows of data out
The surface observation data are in a simple
Table Description: This entity contains rainfall amount (and duration from tilting syphon
gauges) during the hour (or hours) ending at the specified time. Normally it will NOT be used
to store precipitation measured over 24 hours or more - that will use the
Daily Rain (RD) table. However, where a station normally
reports 09-21Z and 21-09Z values, an original value which is deemed to be erroneous can be
replaced by a 24-hour value. ob_hour_count will be set to the
number of hours (always less than 24). The data in this table are of the following types:
The identifier is a rainfall station number.
- Hourly rainfall (ob_hour_count = 1)
- 09-21Z or 21-09Z rainfall from NCM and F7113 (ob_hour_count = 12)
- Rainfall amounts measured over a number of hours (e.g. 06-18Z from SYNOPS - not stored at present)
Columns in the RH table:
For the convenience of users, the RH file column headers are available for download in Excel or as a comma separated text file
** Details available to registered users only.
More information about the Met Office surface data is available
in the documentation provided by the
How to start filtering the rows of data out:
- As the data arrive at the Met Office it undergoes quality control to check that the data are correct and consistent with the surrounding data points. Whether the process has occured or not is indicated by the version number (1 is the one to use as indicated in the table above).
- To show the progress of the data through the quality control the various variables will have an associated _q value (e.g. prcp_amt_q). This _q value will have different values for each record (see details in table above).
- While the Met Office MIDAS system overwrites the existing entry in their database the BADC's MIDAS entries do not as the BADC takes snapshots of the the MIDAS database from time to time leading to duplicate entries occuring in our archive. If duplicate records are found, check the associated meto_stmp_time to determine which record is the most recent one - this is the one to use and the other(s) can be ignored.