Met. Office Operational NWP Products -Background Information


Go to: [ Contents | Introduction | Data | Using Data | End ]

Contents

  1. Introduction
  2. The UM data
  3. Obtaining and using UM data from the BADC


Go to: [ Contents | Introduction | Data | Using Data | End ]

IMPORTANT: byte swapping of these data files may be required before they can be read on your systems. Utilities are available to perform the byte-swapping and convert these files into several other formats such as NetCDF.

Byte swapping software has been available for some time from the BADC and is described at http://badc.nerc.ac.uk/help/software/xconv/index.html .

1. Introduction

This document describes the UK Met. Office Operational NWP data products (based on the Unified Model (UM)) which have been retrieved from the Met. Office since 23 October 2000. Data files are recovered every 6 hours, which contain analysis fields and forecast fields out to 6 days. These files are processed by the BADC to convert then into a format more suited to the UM community (binary PP), with the analysis fields and forecasts out to 12 hours being archived at the BADC.

1.1 The UK Unified Model

The UK operational Mesoscale model uses a rotated latitude and longitude coordinate system in which the computational north pole is shifted to an actual position of 37.5 deg. N, 177.5 E. This is done to obtain fairly uniform horizontal resolution over the area of interest. The corners of the computational area are approximately in actual latitude/longitude: (60.1N, 16.6W; 60.2N, 10.7E; 46.6N, 12.7W; 46.7N, 7.1E). The grid-length is 0.15 deg. in each direction which is approximately 16.8 Km, giving 92x92 grid points running from the north - west corner.


Go to: [ Contents | Introduction | Data | Using Data | End ]

2. The UM data

2.1 Model output data fields

Model dumps are retrieved from the UKMO twice each day. These consist of global and mesoscale data (on model and standard levels) generated at 0, 6, 12, and 18 Z. The output data from each model run include a variety of field types and have forecasts out to 6 days. This gives a data rate of almost 10Gb per day. These files are processed to extract all analysis fileds and forecasts out to 12 hours. As a result of this processing, the final data are around 1Gb per day in size. The format of the saved filenames is described in section 3.

The following table shows the most common stash codes.

 

Table of common pp stash codes.

1
 Height

8
Pressure, p

16
 Temperature, T

28
 d(p*)/dt p*=surface pressure

39
 Coriolis parameter

40
 Omega (=dp/dt)

43
 Eta dot

56
 Westerly cpt of wind, u

57
 Southerly cpt of wind, v

61
 'x' cpt of wind stress

62
 'y' cpt of wind stress

79
 QCL- liquid cloud water

95
 Specific Humidity, q

Note that all winds are held on the U-grid. The U and V winds on Pressure levels are true Westerly and Southerly wind components but all other winds are orientated with the model grid.

A text file describing the Met Office full list of stash codes for the UM model is also available.


Go to: [ Contents | Introduction | Data | Using Data | End ]

2.2 Spatial coverage and resolution

2.2.1 Horizontal coverage

Global Data: The data points are given on a global (432 x 324) longitude-latitude grid, giving a resolution of 0.83 and 0.56 deg.respectively.

Mesoscale Data: The data points are given on a (146 x 181) longitude-latitude grid, giving a resolution of 0.11 deg, which is approximately 12.3 Km.

The corners of this grid are located at (353.00 368.96 11.44 -8.36), on a non-standard polar axis system (polar lat,lonitude= 37.5,177.0).

 

2.2.2 Vertical coverage

The data fields are output on standard pressure levels and model (hybrid) levels, for global and mesoscale runs.

There are 21 standard pressure levels in the output global datafiles, and 13 pressure levels for the mesoscale data.

 

UM Data Standard Pressure levels

 Pressure (mbar)

 Global

Mesoscale

1000

 ˆ

 ˆ

950

 ˆ

 ˆ

925

 ˆ
 

900

 ˆ
 

850

 ˆ

 ˆ

700

 ˆ

 ˆ

600

 ˆ
 

500

 ˆ

 ˆ

400

 ˆ

 ˆ

300

 ˆ

 ˆ

250

 ˆ

 ˆ

200

 ˆ

 ˆ

150

 ˆ

 ˆ

100

 ˆ

 ˆ

70

 ˆ

 ˆ

50

 ˆ
 

30

 ˆ

 ˆ

25

 ˆ
 

20

 ˆ
 

15

 ˆ
 

10

 ˆ
 

 

 

2.3 Temporal coverage and resolution

The datafiles available at the BADC are extracted from raw UM dump files, which contain both analyses and forecasts out to 6 days.

Analyses are available every 6 hours for most of the fields, and corresponding forecasts up to 12 hours are current archived at the BADC. These forecasts are at 1 or 3 hour intervals.

It may be possible to retrieve UM data for dates prior to 23 October 2000, if required -please contact the BADC for further information.


Go to: [ Contents | Introduction | Data | Using Data | End ]

3. Obtaining and using UM data from the BADC

3.1 The UM data files

The filenaming convention for the archive is in the process of being redesigned in order to allow bring it in line with other model datasets helpd by the BADC (especially ECMWF).

"New conventions"

The raw data are held in binary pp data as before, although due to problems with the extraction of historical NWP data from MASS, soem of the data are WGDOS packed, and some are unpacked.

The new directory structure is of the form

Global:

/badc/ukmo-um/data/global/ag/[am|ap|fm|fp]

Mesoscale:

/badc/ukmo-um/data/meso/lb/[]

The filenames reflect the path structure:

"Old Filenames"

These data are IEEE binary files in Met. Office "PP" format, consisting of unpacked headers (mostly integer data) followed by floating point field data. There are text files available descibing the Met Office format for the PP file header, and a full list of the stash codes used.

The directory structure is of the form year, month, day, creation time, um-type, filename, where creation time is 00, 06, 12, 18 and um-type file is : mg (model levels/global), mm (model levels/mesoscale), sg (standard levels/global), sm (standard levels/mesoscale).

The individual datafiles are in pp format, with a separate file for each paramter and timestep. They have filenames of the form:

 m  g 2000 11 13 00  p8 s00 .pp
 1  2 3 4 5 6 7 8  

1: m/s (model/standard) levels
2: g/m (global/mesoscale) data
3: year
4: month
5: day
6: time of file (00,06,12,18)
7: parameter stash code (pp)
8: step(hr from time of file (6))

for example:

mg2000111300p8s00.pp : model levels, global, yr=2000, m=11, d=13, run at 00hrs, parameter=1 (pressure), step=0 (analysis).

mm2000111300p8s00.pp : model levels, mesoscale ..(as above).

sg2000111300p8s00.pp : standard levels, global ..(as above).

sm2000111300p8s00.pp : standard levels, mesoscale ..(as above).

The parameter codes are as given in the UM model documentation, and the forecast steps are up to 12 hrs only.


Go to: [ Contents | Introduction | Data | Using Data | End ]

3.2 Software to read the data

As mentioned above, the UM data are stored in very large binary files, so software is required to read the files and extract the fields of interest.

Xconv/convsh:

Xconv is a program designed to convert model output into a format suitable for use in various plotting packages (such as NetCDF). The package is simple to use, and has a X-windows based interface. It can be used to see what fields are contained within a data file, and to look at the data values, either directly or via a graphical plot of the data. Xconv can also be used to manipulate the input data before it is converted into chosen output format.

Convsh is a command line package which allows scripts to be written to automate various xconv tasks. Convsh uses the Tcl scripting language, plus various extensions for reading, writing and manipulating data files.

http://www.ugamp.rdg.ac.uk/~jeff/xconv/

These utilities are now available from the BADC . These also allow the user to convert these files into several other formats such as NetCDF. A subsetting utility based on Xconv/convsh is also provided.

3.3 Software to manipulate and plot the data

Ferret: http://ferret.wrc.noaa.gov/Ferret

Xconv/convsh: http://www.ugamp.rdg.ac.uk/~jeff/xconv/

Software to rotate the co-ordinates to allow for the offset pole position of the mesoscale data may also be required.

Please report any problems with this page to: BADC support.