Page History

...

• Name of the server where ECMWF should fetch the data from. Note this server will have to be visible from outside the firewall of your organisation for the following incoming IP addresses
  

  • 193.61.196.106

  • 193.61.196.107

  • 193.61.196.108

  • 193.61.196.109

  • 193.61.196.110

• For each cycle:
  • Path to the cycle, for example:
 /dir1/dir2/$yyyy/$mm/$dd/
  • Filename(s) for that cycle, for example:

z_s2s_c_${centre}_${yyyyversion}_${mmstream}_${ddyyyy}${cyclemm}0000_glob_${versiondd}_${typehh}_${lastTimeSteplevelType}_${EnsembleMember}.grib2ensembleMember}.grib2

centre: eccodes/mars acronym as per https://apps.ecmwf.int/codes/grib/format/mars/centre/

version: test/prod

stream: enfo/enfh for real-time/reforecast outputs

levelType: pl/sl/pt/pv/ol  for pressure/surface/potential temp/potential vorticity/ocean level

ensembleMember: 000, 001, 002.... (000 for control forecast, 001 for the 1st epsmenber etc)

example (UKMO):  s2s_egrr_prod_enfo_2019101000_pl_002.grib2

=> model outputs are split into separate files only by type of forecast (real-time or reforecast), level type and ensemble number (all steps and parameters are merged into one file)

• Preferred transfer protocol (currently supported: ftp, sftp and http)
• Username and password for the above
• Estimated size (bytes and fields) of the real-time forecast per cycle as well as the re-forecast. Please add this information to the table on S2S Data Provider Information and contacts 

• Technical contact point for testing all of the above

...