Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

  • Data Delivery Web Service - the main service for accessing Solargis time series data. Both request and response is an XML document. The request parameters (XML elements and attributes) are formally described by XML Schema Definition documents (XSD). By using the schema, request or response can be verified programmatically. For this service, we provide two endpoints - the REST-like endpoint, and the SOAP endpoint. Look for more technical information here.  Authentication and billing is based on API key registered with the user. Please contact us to discuss details, set up trial or ask for a quotation.
  • pvPlanner Web Service - this simple web service provides monthly long-term averaged data (including yearly value) of PV, solar and meteorological data with global coverage. The service is aimed for prospection and pre-feasibility. By sending an XML request the user mimics the click on the Calculate button in the interactive Solargis pvPlanner application. Request and response for the service is not described in this user guide. More information can be found here.

...

satellite data regionhistorical data startdescription of satelliteslocal DAY-1 is available at

real-time and nowcasting (in dark red polygons)

GOES WEST1999-01-01

1999-20192020+:   GOES-S, 3010-minute time step2020+

2019 - 1999:  GOES-SW, 1030-minute time step

12:30 UTC
GOES EAST1999-01-01

1999-20172018+:   GOES-R, 3015-minute time step2018+

2017 - 1999:  GOES-RE, 1530-minute time step

08:30 UTCdata updated every 30 minutes, shipping by Push delivery every 1 hour
GOES EAST PATAGONIA2018-01-012018+: GOES-R, 15-minute time step08:30 UTC
METEOSAT PRIME1994-01-01

1994-20042005+: MSG 15-minute time step

2004 - 1994:  MFG, 30-minute time step2005+: MSG 15-minute time step

01:30 UTCdata updated every 30 minutes, shipping by Push delivery every 1 hour
METEOSAT IODC1999-01-01

1999-20162017+: MSG 15-minute time step

2016 - 1999:  MFG, 30-minute time step

2017+: MSG 15-minute time step

23:30 UTC data updated every 30 minutes, shipping by Push delivery every 1 hour
IODC-HIMAWARI1999-01-01

1999-20162017+: HIMAWARI 10-minute time step

2016 - 1999:  MFG, 30-minute time step

2017+: HIMAWARI 10-minute time step

20:30 UTCdata updated every 30 minutes, shipping by Push delivery every 1 hour
HIMAWARI2006-07-01

2006-20152016+: HIMAWARI 10-minute time step

2015 - 2006:  MTSAT, 30-minute time step2016+: HIMAWARI 10-minute time step

20:30 UTC

data updated every 30 minutes, shipping by Push delivery every 1 hour

...

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

...