Versions Compared

Key

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

...

The table below shows how the solar data are integrated into the API response (Data Delivery Web Service timeseries):

Stage of the solar data

Origin of data

Validity period

Description

historical

satellite model

  • Start: the beginning of the archive

  • End: the last completed calendar month (MONTH-1)

Data for any location enters this stage upon completion of the calendar month. The reanalysis of the previous month takes effect on the 3rd day of each calendar month. Historical data can be regarded as final or of archive quality. The oldest solar data stored by Solargis dates back to 1994.

operational

satellite model

  • Start: the beginning of the current calendar month

  • End: the last completed calendar day (DAY-1)

Operational stage of the solar data is created as soon as the calendar day is completed at the location.

real-time

satellite model

  • Start: the beginning of the current calendar day (DAY+0)

  • End: the current time

The real-time data stage is actually ending shortly before the current time due to processing delays of the satellite model.

nowcasting

satellite model

  • Start: the current time

  • End: 4 hours after the current time

The beginning of this stage at the current time is approximate. The nowcasting data is generated from the series of satellite scenes. Solargis predicts solar data parameters by utilizing CMVs (Cloud Motion Vectors). After approximately 3-4 hours, the satellite nowcasting model output begins to blend with the numerical weather prediction data.

numerical weather prediction (NWP)

post-processed outputs of NWP models

  • Start: 4 hours after the current time

  • End: DAY+14 (15 days in a row including the current day)

The NWP based solar data is asembled from multiple NWP data sources: IFS forecast model (ECMWF), ICON forecast model (DWD), GFS forecast model (NOAA), HRRR model (NOAA). Find more information about the forecasting here.

...

The table below shows how the meteorological data are integrated into the API response (Data Delivery Web Service timeseries):

Origin of data

Validity period

Description

ERA5 reanalysis of the global climate (ECMWF)

  • Start: the beginning of the archive

  • End: DAY-11

The TEMP data parameter is extracted from the ERA5-Land reanalysis dataset (ECMWF).

IFS forecast model (ECMWF)

  • Start: DAY-10

  • End: DAY+3

GFS forecast model (NOAA)

  • Start: DAY+4

  • End: DAY+14

...

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).

...