|Parameter name in FTP data delivery||Required||Value type||Value unit||Default value||Value Range||Description||WS request equivalent (XPath)|
|siteId||Yes||string||Unique identification of one request (one row in CSV request). example: "DETROIT_roof_1"||/dataDeliveryRequest/site/@id|
|fromDate||No||string||String formatted as "yyyymmdd" (example "20150101").||/dataDeliveryRequest/@dateFrom|
|toDate||No||string||String formatted as "yyyymmdd" (example "20150101").||/dataDeliveryRequest/@dateTo|
|forecastFromDay||Yes (if forecast is needed)||integer|
For forecast request only. In case of FTP data delivery, forecast processing is indicated by file name of the CSV request file. Then this parameter is taken into account. 0= DAY+0, 1=DAY+1, etc.
|forecastToDay||Yes (if forecast is needed)||integer|
For forecast request only. In case of FTP data delivery, forecast processing is indicated by file name of the CSV request file. Then this parameter is taken into account. 1= DAY+1, 2=DAY+2, etc. up to 10.
|summarization||Yes||string||This parameter defines time resolution of output data. Original satellite and meteorological data are in various time steps (e.g. MSG satellite: 15 min, GOES-EAST satellite: 30 min, GFS weather model: 3 hour). When finer summarization is requested, the data will be interpolated into desired time step. In other words, you can request time resolution of 10 minutes even if the original dataset is not available in such resolution. The "monthly-longterm" summarization means 12 long-term monthly averaged entries + 1 annual entry i the response.||/dataDeliveryRequest/processing/@summarization|
The white-space-separated list of variable codes which will be included in the response (example: "GHI DIF TEMP WS WD"):
|timeZone||No||int||0 (=UTC+0)||-12, 12||Signed integer. Time zone with hourly precision. Value defines the time zone of output data and it is used for all summarizations. For daily and monthly summarization, the time zone it is activated automatically in the background. This is important for summarization of whole days, otherwise daily summary in UTC+0 would for Japan or Hawaii end up in putting together data from two different local days. For hourly and shorter time steps time zone must be specified, otherwise UTC+0 is used. All the satellite model results are calculated and internally stored in UTC+0. Therefore depending on the requested time zone value, the data reader automatically extends period from which data are read to acquire completed local day. For example, one whole day D (0-24h) in the time zone of UTC-5 will be read from UTC database as D (5-24 hours) and D+1(0-5 hours).||/dataDeliveryRequest/processing/timeZone, timeZone must be in format \"GMT+hh\" or \"GMT-hh\"|
|timeStampType||No||string||CENTER||The parameter can be used in hourly or even in sub-hourly time steps when averaging of more values occurred within time interval. Example: let's say the value is the result of averaging of more occurrences within hourly interval from 15:00 to 16:00. If the value of the parameter is "CENTER", the value is time-stamped at 15:30, in case of "END" at 16:00 and finally "START" at 15:00.||/dataDeliveryRequest/processing/timeStampType, value START is not supported in Web services|
|satelliteTimeStamp||No||string||TRUE||TRUE or FALSE||This parameter is used to preserve time stamp of satellite data acquisition. The data for given position are recorded by satellite in exact moment given by scanning speed of the instrument. For example MSG data scan starts nearby south pole at time T and data for Europe are recorded with 10-13 minutes delay from nominal (start) scan time. To present the original satellite information and avoid degradation of the information content by temporal interpolation it is good to preserve local time stamp of satellite data acquisition.|
|terrainShading||No||string||FALSE||TRUE or FALSE||Apply or not terrain (or horizon) shading (whether default SRTM terrain or local horizon passed by user).||/dataDeliveryRequest/processing/@terrainShading|
|userHorizon||No||string||Formatted string describing custom local horizon. The horizon can be in any resolution, it will be interpolated internally. Example (sun azimuth:sun elevation pairs): 0:16.2,0.5:16.2,1:16,1.5:16,2:16,2.5:16,3:15.8,...358.5:16,359:16.2. Azimuth is true north-based (North=0 degree).||/dataDeliveryRequest/site/horizon|
|active||No||string||TRUE||TRUE or FALSE||User can toggle if particular request (=site, =row in CSV request file) should be processed or not.||N/A|