Child pages
  • Solargis API User Guide

Versions Compared


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


The purpose of Solargis API is to provide programmatic automated access to Solargis database and services for computers over the web. API is a "user interface" for developers. Developers can automate getting Solargis products by using standard internet protocols (FTP , or HTTP) and integrate Solargis data values into their processing chain (for evaluation. monitoring, forecasting, validation, calibration etc.). 


Schema below shows how data sources are integrated on an example of the the WS response having 9 days of data (generated at 12:00 of a given day).

Satellite based PV and solar data (used in time range from history up to current day)

Current spatial coverage of satellite data available through API. Click image to enlarge:


Note: the data from orange zones in the map is also available by using interactive application pvSpot (daily operational data) and is accessible within minutes after purchase via climData online shop (as historical multi-year archived data).

Meteorological data from


numerical weather models (used in time range from history up to current day)

Main data parameters include air temperature (TEMP), wind speed (WS), wind direction (WD), relative humidity (RH). Meteorological data comes from post-processed numerical weather models and is available globally. The DAY-1 and DAY-2 values are taken from NWP models - NOAA GFS (resp. ECMWF IFS) data sources (they are forecasted values). The preliminary meteorological data from GFS model is later updated with data from the NOAA CFS v2 data source (re-analysed archive data). Meteorological data for period DAY-3 and older can be considered as definitive.

PV, solar and meteorological data from Numerical Weather Prediction (NWP) models (used in time range from current day up to 10 days ahead)

Solargis forecast is based on post-processing of outputs from NWP models. The forecast time series include the following data parameters: