| Table of Contents |
|---|
Overview
The purpose of the Solargis API (specifically the Solargis WS API) is to provide flexible automated access to various Solargis data products and services - specifically namely for Monitor, Forecast and Prospect solutions. Developers can automate the integration of Solargis products into customized solutions.
| Response dataset type | Availability of PV, solar and meteorological data | Technical features | |||||||
historical | operational | real-time and nowcasting | numerical weather forecasting | long-term average | mode of communication | request formats | response formats | state | ||
|---|---|---|---|---|---|---|---|---|---|---|
DataDelivery Web Service
| timeseries | YES | YES | YES | YES | NO | synchronous | XML | XML | stateless |
Long-term Averages Web Service (LTA API) | long-term averages, 12 monthly +1 yearly value | NO | NO | NO | NO | YES | synchronous | XML | XML | stateless |
Solargis WS API consists of two different endpoints:
DataDelivery Web Service - the main service for accessing Solargis timeseries data for Monitor or Forecast. Both request and response are XML documents. The request parameters are based on the XML Schema Definition documents (XSD). By using the schema, request or response can be verified programmatically. Authentication and rate limiting is based on API key registered with the user. Please contact us to discuss details, set up trial or ask for a quotation. Look for more technical information here and https://solargis.atlassian.net/wiki/spaces/public/pages/7602367/Solargis+WS+API+User+Guide#Data-Delivery-Web-Service .
Long-term Averages Web Service (LTA API) - a simple web service provides monthly long-term averaged data (including also the yearly value) of PV, solar and meteorological data. The service is aimed for automation of prospection and pre-feasibility of PV projects. More information can be found here.
Additionally, Solargis provides the automated Push Delivery service where the request (a CSV file) is stored in the user's remote directory (SFTP, Azure, S3). The service is then scheduled to push CSV data files regularly e.g., once a day or every hour. The CSV request allows for multiple locations in a single file. The availability of data is the same as with the DataDelivery Web Service. For pricing and setting up a trial account, please contact us. For more information see https://solargis.atlassian.net/wiki/spaces/public/pages/7602367/Solargis+WS+API+User+Guide#Push-data-delivery .
...
Regions with the orange color are updated every few minutes (satellite based real-time and nowcasting models are available in the current day).
In the yellow regions the satellite data is updated every day (so that the DAY-1 is available). For the timing of updates, see https://solargis.atlassian.net/wiki/spaces/public/pages/7602367/Solargis+WS+API+User+Guide#Description-of-the-satellite-data-regions.
...
| 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). |
...