...
The original FEWS import from WIWB data is done through a direct soap connection. Because this method is not intended to be used for bulky data downloads, another second so-called asynchronous download option has been developed. This asynch async option is to be used for non-operational and larger datasets. The normal importType is WIWB, while the asynch asynchronous option is WIWB_asynchasync. Note that the async option is only used in case of gridded. Scalar data is always imported through the norma, direct way.
The WIWB_async import type works as follows:
- It first sends a request to the WIWB API for a later download, this request contains all info about what data is requested.
- The API then returns a unique id which can be used to track the progress of the download, which will return one of the following status:
- Idle : this means it is on the waiting list for being processed, process will always be 0%
- Processing : the download is being prepared this involves getting the data, processing the data and writing to netcdf files and zipping them. This will always have a progress larger than 0% and lower than 100%.
- Error : something went wrong on the API server side, currently there will be no explanation provided on why it went wrong, therefor FEWS has now ability to provide an explanation for it since it is out of FEWS control.
- Finished : The download is ready.
- When the download is ready a separate request is done for this specific download. First the whole zip is downloaded, then unzipped in a temporary directory and finally those files are imported one by one.
Missing values
If the WIWB specifies the missing value for a datasource, this will be used by FEWS. The missing value can also be specified in the import configuration as well. The default value for missing value is -9999 for the WIWB API.
...