...
The following CEMIG data files have been tested for the importer: ANNA25, CPTEC15, ETA_CEMIG and TRMM. The CPTEC15 format is currently still under construction and not supported yet.
The importer has to be configured with some properties. Possible configuration properties are:
forecast (optional): Possible values are true or false. Default is false. If forecast is set to true, the forecast issue date will be registered as T0 and the first import value will be assumed to start at T0 + the configured timeStep.
vars (required): should contain one or more parameters separated by a comma (,) . The parameters are expected to be present in the binary file in the specified order. If more than one variable is specified, only one time step is assumed. Specifying a tdefUnit and tdefValue is considered an error in this case. Always specify all parameters that are available in the input file.
fileNameDateTimePattern (required): pattern of the filename where the date is marked with single quotes ('). For example "prec_'yyyyMMdd'.bin". The date is used to determine T0 or the forecast issue date from the file name.
tdefUnit (optional): Required if more than one timestep is available in the binary format. Possible values are: second, minute, hour, day, month, year. Only equidistant timesteps are supported.
tdefValue (optional): Specifify the amount of units specified in the tdefUnit.
- bytesToSkipBetweenTimeSteps (optional): The number of bytes between each time step that should be skipped. Default is 0. (For the cptec15 format the value should be set to 8).
The import files can be gzipped. They should have the .gz extension. In the fileNameDateTimePattern the .gz extension doesn't have to be specified.
Configuring the Import
To make the importer known to FEWS, the import module has to be declared in the moduleInstanceDescriptors.xml in the RegionConfigFiles directory of the FEWS configuration:
...