...
Support checks (on provider's end)
Organisation | Data acquisition method | Data transfer check | Data delay check | Data completeness check | Data quality check |
---|---|---|---|---|---|
BoM (ammc) | ecpds (ftp) | ||||
DMI (ekmi) | ecpds (ftp) | ||||
DWD (edzw) | ecpds (https) | ||||
ECCC (cwao) | ecpds (http) | ||||
ECMWF (ecmf) | MARS | N/A | YES | YES | YES |
JMA (rjtd) | ecpds (push) | ||||
KMA (rksl) | ecpds (push) | ||||
METEOAM (cnmc) | ecpds (pull from ecgb) | ||||
NIWA (niwa) | ecpds (ftp) | ||||
PRTOS (lemm) | ecpds (push) | YES | YES | ||
SHNSM (sabm) | ecpds (ftp) | ||||
UKMO (egrr) | ecpds (push) | YES | YES | YES | NO |
- Data acquisition method: Acquisition method is pull from the provider's location to ECMWF's premises if not specified
- Data transfer check: Is the data transfer checked to avoid any technical issues on the way from provider's location to ECMWF's premises? Was the data delivered bit identical?
- Data delay check: Is the potential delay of data availability checked on the provider's side?
- Data completeness check: Is the data content (number of expected fields; reference field list etc) checked on the provider's side?
- Data quality check: Is there any data quality control to avoid e.g. unrealistic parameter values due to interpolation or any other kind of error either scientific or technical?
...