Versions Compared

Version Old Version 268 New Version Current
Changes made by

Marek Caltík

Marek Caltík

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

  1. Primary satellite data availability delay after actual scanning of a location depends on its latitude and satellite region as follows:

    • PRIME, IODC - delay is 2-16 minutes  (increases from north to south) 

    • HIMAWARI - delay is 5-15 minutes  (increases from south to north)

    • GOES-EAST & WEST - delay is 2-12 minutes  (increases from south to north)

  2. Data processing delay (including retrieval, preprocessing and nowcasting model run) takes 5-15 min. Data is available immediately after the data processing is finished.

  3. Processing frequency is 10 minutes (HIMAWARI, GOES-EAST & WEST) or 15 minutes (PRIME, IODC), i.e. after each new satellite image. This also determines the window when any given nowcast run is available for delivery, before it is replaced by the next run. The timing of a customer's request after the start of this interval represents the user request delay, which is thus in the range 0-10 or 0-15 minutes.

...

Nowcasting and forecasting update frequency

...

Origin of the meteorological data

...

parameter

description

GHI

Global Horizontal Irradiation [kWh/m2, Wh/m2, W/m2]. Regarding units see below note.

GHI_C

Clear-sky Global Horizontal Irradiation [kWh/m2, Wh/m2, W/m2]

GHI_UNC_HIGH

GHI high estimate (10 % probability of exceedance) [kWh/m2, Wh/m2, W/m2]

GHI_UNC_LOW

GHI low estimate (90 % probability of exceedance) [kWh/m2, Wh/m2, W/m2]

DNI

Direct Normal Irradiation [kWh/m2, Wh/m2, W/m2]

DNI_C

Clear-sky Direct Normal Irradiation [kWh/m2, Wh/m2, W/m2]

DIF

Diffuse Horizontal Irradiation [kWh/m2, Wh/m2, W/m2]

GTI

Global Tilted Irradiation [kWh/m2, Wh/m2, W/m2]

GTI_UNC_HIGH

GTI high estimate (10 % probability of exceedance) [kWh/m2, Wh/m2, W/m2]

GTI_UNC_LOW

GTI low estimate (90 % probability of exceedance) [kWh/m2, Wh/m2, W/m2]

GTI_C

Global tilted clear-sky irradiance [W/m2]

CI_FLAG

Cloud identification quality flag [categories], this parameter is represented as 'flagR' in the response

FLAG_R

alias for CI_FLAG

KTM

Deprecated alias of KC. Can be discontinued in future versions.

KC

Clear-sky index [unitless]

KT

clearness index, values range (0, 1.1), during the night -9

PAR

Photo-synthetically Active Irradiation [kWh/m2, Wh/m2, W/m2]

SE

Sun Altitude (Elevation) Angle [deg.]

SA

Sun Azimuth Angle [deg.]

TEMP

Air Temperature at 2m [deg. C]

TD

Dew Point Temperature [deg. C]

WBT

Wet Bulb Temperature [deg. C]

AP

Atmospheric Pressure [hPa]

RH

Relative Humidity [%]

WS

Wind Speed [m/s]

WD

Wind Direction [deg.]

PREC

Precipitation Rate [kg/m2]

PWAT

Precipitable Water [kg/m2]

PVOUT

Photovoltaic Output [kW, kWh]. Regarding units see below note.

PVOUT_UNC_HIGH

PVOUT high estimate (10 % probability of exceedance) [kW, kWh]

PVOUT_UNC_LOW

PVOUT low estimate (90 % probability of exceedance) [kW, kWh]

SDWE

Water equivalent of accumulated snow depth [kg/m2]

SWE

Deprecated alias of SDWE. Can be discontinued in future versions. SDWE will be returned in a response.

TMOD

Module temperature [deg. C]. This parameter needs a PV system defined in the request., at least in a mimimal setup like:
<pv:system installedPower="1"><pv:module type="CSI"/><pv:inverter/><pv:losses/></pv:system>

WG

Wind Gust [m/s]

WS100

Wind speed at 100 m [m/s]

WD100

Wind direction at 100 m [deg.]

SFWE

Water equivalent of fresh snowfall rate [kg/m2/hour] - source ERA5 , the latest data available is approx. one month backward (no data for very recent or forecast period)

INC

Incidence angle of direct irradiance [deg.], this parameter needs GTI or PVOUT in the request

TILT

Tilt of inclined surface [deg.], this parameter needs GTI or PVOUT in the request

ASPECT

Aspect of inclined surface [deg.], this parameter needs GTI or PVOUT in the request

...

Code Block
languagexml
<ws:dataDeliveryRequest dateFrom="2017-09-22" dateTo="2017-09-30"
    xmlns="http://geomodel.eu/schema/data/request"
    xmlns:ws="http://geomodel.eu/schema/ws/data"
    xmlns:geo="http://geomodel.eu/schema/common/geo"
    xmlns:pv="http://geomodel.eu/schema/common/pv"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      
    <site id="demo" lat="48.61259" lng="20.827079">
       <geo:terrain elevation="120" azimuth="180" tilt="5"/>
       <geo:horizon>0:3.6 123:5.6 359:6</geo:horizon>
       <pv:geometry xsi:type="pv:GeometryFixedOneAngle" azimuth="180" tilt="25"/>
       <!-- <pv:geometry xsi:type="pv:GeometryOneAxisHorizontalNS" rotationLimitEast="-90" rotationLimitWest="90" backTracking="true" azimuth="180"/>  -->
       <!-- <pv:geometry xsi:type="pv:GeometryOneAxisInclinedNS" axisTilt="30" rotationLimitEast="-90" rotationLimitWest="90" backTracking="true" azimuth="180"/> -->
       <!-- <pv:geometry xsi:type="pv:GeometryOneAxisVertical" tilt="25" rotationLimitEast="-180" rotationLimitWest="180" backTracking="true"/> -->
       <!-- <pv:geometry xsi:type="pv:GeometryTwoAxisAstronomical" rotationLimitEast="-180" rotationLimitWest="180" 
   				tiltLimitMin="10" tiltLimitMax="60" backTracking="true"/> -->
        <pv:system installedPower="1000" installationType="FREE_STANDING" dateStartup="2014-01-03" selfShading="true">
            <pv:module type="CSI">
                <pv:degradation>0.3</pv:degradation>
                <pv:degradationFirstYear>0.8</pv:degradationFirstYear>
                <pv:nominalOperatingCellTemp>45</pv:nominalOperatingCellTemp>
                <pv:PmaxCoeff>-0.38</pv:PmaxCoeff>
            </pv:module>
            <pv:inverter>
                <pv:efficiency xsi:type="pv:EfficiencyConstant" percent="97.5"/>
                <!--<pv:efficiency xsi:type="pv:EfficiencyCurve" dataPairs="0:20 50:60 100:80 150:90 233:97.5 350:97 466:96.5 583:96 700:95.5 750:93.33 800:87.5 850:82.35 900:77.8 950:73.7"/>-->
                <pv:limitationACPower>900</pv:limitationACPower>
            </pv:inverter>
            <pv:losses>
                <pv:acLosses cables="0.1" transformer="0.9"/>
                <pv:dcLosses cables="0.2" mismatch="0.3" snowPollution="3.0"/>
                <!-- <pv:dcLosses cables="0.2" mismatch="0.3" monthlySnowPollution="5 5.2 3 1 1 1 1 1 1 1 2 4"/> -->
            </pv:losses>
            <pv:topology xsi:type="pv:TopologySimpleTopologyRow" relativeSpacing="2.4" type="UNPROPORTIONAL2"/>
            <!-- <pv:topology xsi:type="pv:TopologyColumn" relativeSpacing="2.5" type="UNPROPORTIONAL2"/> -->
        </pv:system>
    </site>   
    <processing key="GHI GTI TEMP WS PVOUT" summarization="HOURLY" terrainShading="true">
      <timeZone>GMT+01</timeZone>
      <timestampType>END</timestampType>
    </processing>  
</ws:dataDeliveryRequest>

...

Note

Timestamps used in the XML response comply with the ISO 8601 standard for date and time representation https://en.wikipedia.org/wiki/ISO_8601. Time stamps are also aware of time zone (offset from UTC). Time zone designators are appended after the the time part of timestamp string. If the time is in UTC (https://en.wikipedia.org/wiki/Coordinated_Universal_Time), Z is added directly after the time without a space. Z is the zone designator for the zero UTC offset e.g., 2017-09-22T01:00:00.000Z . If there is an offset from UTC, this is designated by appending +/-HH:MM after the timestamp string, e.g., 2017-09-22T01:00:00.000-05:00 (UTC-5).

...