How is the TIGGE data organised in MARS?
In general it is organised, as a huge tree, with the indentation below, showing different levels down that tree:
- type of level
- steps, origins (ie Centres), members, parameters (same tape file )
Best practise to iterate over all dates and all times for for a particular level type (eg Pressure levels)
The idea is to request as much data as possible from the .
The best approach is to iterate over the dates and for each date iterate over the times. At this point you may wish to check TIGGE availability.
for date in dates
for time in times
TIGGE-request(date, time, origin)
(Here you must add everything you need)
Example 1: Two TIGGE requests (sfc and pl), for some dates, for the same 'origin'
- The objective of this example is to demonstrate how to iterate efficiently over some dates (eg '2014-10-01' and '2014-11-01') two requests for 'perturbed forecast', 'pressure' and 'sfc' level, for TIGGE, ECMWF Center.
- It can be used as a starting point, please keep in mind that you have to adapt it to your needs eg to set the keyword, values according to your requirements ('param', 'levtype', 'step' etc).
- In this way you can extend these requests to download more data or a longer period of TIGGE.
The most efficient way to organise your requests is per dates and times
ie select a set of 'dates' and 'times' and add the 'steps', 'origins', 'levels' and 'parameters' that you need.
It is not efficient to organise your requests per parameter, per origin or per step. (eg to submit a different request per parameter or per origin for a list of dates)
Example 2: A TIGGE sfc request for some dates, for several 'origins'
If you wish to download the same data for more than one origins it is more efficient to request all of them in one go.
- The objective of this example is to demonstrate how you can get the same data for several origins in one request.
- Before you start writing your request, you need to check that the requested data are available on all the selected 'origins' .