As stated on the parameters page, the BADC archives the ECMWF ERA-40 data in its original format (GRIB) and grid types. These are the N80 Reduced Gaussian Grid for surface data and at T159 Spectral Resolution for upper air data.
The main reasons for keeping the data in these representations are (i) to maintain an archive of the original data and (ii) to keep the data in its most compressed format (both reduced gaussian and spectral resolutions are more efficient than a regular latitude/longitude grid).
Note that users that require 2.5° x 2.5° regular gridded data can access it via ECMWF's public data server.
Please note that you must apply for access to the ERA-40 dataset before you can access ERA-40 under the services mentioned below.
Please note that the regular gridded ERA-40 data is produced when requested by users. This is because the full dataset (if converted to NetCDF) would be 10s of terrabytes in volume. By storing the data in a more efficient format the data is all held on disk and is therefore more accessible to users.
This means that already the BADC LAS and ERA-40 Data Selector present the data as already present in our archive, it is actually a virtual dataset, parts of which are created via user requests. We have designed a Caching Architecture to create, store, delete and manage the virtual datasets.
Regular latitude/longitude datasets are available in the following resolutions:
Please be patient with the system. Multiple users may all be requesting the creation of particular files concurrently. Our computers are working as fast as they can to deliver the data to you. We will aim to provide you with a delivery time estimate to keep you informed at all times.
In order to provide data conversion and delivery at the request of the user the BADC has developed a caching system that is called when the user asks for some data (via either the BADC LAS or the ERA-40 Data Selector). A list of the required original files is produced and this is sent to the cache processor. For more information, please see our animated slide (95KB) of how the caching system works.
The cache is interrogated to find out if the regular gridded equivalents of the original files are already present. If not, they are created and stored in the cache. Otherwise, they are delivered directly. The cache manager makes sure that old files are deleted and that the cache does not exceed its volume limit.
The cache manager also evaluates the size of your request and will do one of the following depending on the volume of data you ask for: