Page History

To help users to improve S2S BoM MARS requests performance via the WebAPI.

A good understanding of the MARS efficiency issues is essential especially for users that are interested in downloading large amounts of data.

In general it is organised, as a huge tree, with the indentation below, showing different levels down that tree:

• centre (BoM, ECMWF, NCEP, JMA, ...)
  • realtime or reforecast
    •  type of data (control forecast or perturbed forecast)
      • type of level (single level or pressure level or potential  temperature)
        • model version date (2014-01-01 or ...)
          
          • hindcast dates (2013-09-01, 2013-09-06, 2013-09-11, 2013-09-16,  2013-09-21, 2013-09-26, ...)
            •  time and steps
              • members (for perturbed forecast)
                • levels (for pl or pt)
                  • parameters

The idea is to request as much data as possible from the same tape file. The natural way to group requests would be:
all parameters, all levels, all members, all time-steps for 1 hindcast date for a type of level for a type

Note the following:

1. 'all' means 'all' that the user wants. It doesn't have to be all parameters.
2. If a user is interested only on z500,  he may request more hindcast dates in one go, since the overall request will not be so big.