In this document
You will learn what the Solargis Monitor API service is and gather detailed information about its subscription plans and specifications.
Overview
Solargis Monitor API service provides access to solar resource and climate data, and some calculated parameters such as PVOUT from up to 1 year back till now (Nowcast). Figure 1 displays the Monitor data timeline in relation to the data sources and the Forecast service.
The data provided by Solargis Monitor API is sourced from a combination of high-resolution satellite observations and advanced atmospheric models, ensuring robust and reliable information for solar resource assessment and forecasting. You can read more about the data sources and quality here.
Figure 1: Solargis Monitor API data sources and transition to the Solargis Forecast data service.
Solargis Monitor service offers dedicated subscription plans to accommodate your monitoring needs.
Subscription to Solargis Monitor consists of multiple API services, each covering different use cases and providing different datasets. For each API service, a separate API access is required, which includes an access token with its validity period and usage limits. For more details, refer to the subscription plans below.
Note: The Monitor API shares an endoint with the Forecast service and you can learn about how to set it up in our API documentation.
Solargis Monitor API service plans & specifications
Subscription plan: Monitor Basic
Solargis Monitor Basic consists of three API services: Operational data, monthly reanalysis, and historical data.
API service for accessing updates of operational data every day. Includes recent history.
Recommended: Requesting past 1-2 days every day, and requesting longer history only occasionally for e.g. gap filling.
Not recommended: Requesting 40 days of history every day.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
DAY -40 | DAY -1 | 1x Per Day | Hourly |
The specific API service is designed to pull monthly reanalyzed (definitive) solar and PV data. Reanalyzed datasets become available on the 3rd day of each month.
Recommended: Requesting reanalyzed dataset after the 3rd day of the month, and replacing operational data (from D11-M1 service) with the reanalyzed data in the internal archive.
Updating analyses made using operational data with reanalyzed data.
Not recommended: Requesting reanalyzed datasets before the 3rd day of the month. Not updating analyses made using operational data.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
MONTH -1 START | MONTH -1 END | 1x Per Month | Hourly |
API service for one-time pull of historical datasets and for backfilling purposes.
Recommended: Data for the previous month should be interpreted as reanalyzed (definitive) only if the request was sent on the 3rd calendar day or later.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
MONTH -3 START | DAY -1 | One-time data | Hourly |
Subscription plan: Monitor Professional
Solargis Monitor Professional consists of three API services providing operational data, monthly reanalysis, and historical data.
API service for accessing updates of operational data every day. Includes recent history.
Recommended: Requesting past 1-2 days every day, and requesting longer history only occasionally for e.g. gap filling.
Not recommended: Requesting 40 days of history every day.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
DAY -40 | DAY -1 | 1x Per Day | 5 minutes |
Specific API service is designed for pulling monthly reanalyzed (definitive) solar and PV data. Reanalyzed datasets become available on the 3rd day of each month.
Recommended: Requesting reanalyzed dataset after the 3rd day of the month, and replacing operational data (from D11-M1 service) with the reanalyzed data in Customer’s internal archive.
Updating analyses made using operational data with reanalyzed data.
Not recommended: Requesting reanalyzed datasets before the 3rd day of the month. Not updating analyses made using operational data.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
MONTH -1 START | MONTH -1 END | 1x Per Month | 5 minutes |
API service for one-time pull of historical datasets and for backfilling purposes.
Recommended: Data for the previous month should be interpreted as reanalyzed (definitive) only if the request was sent on the 3rd calendar day or later.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
MONTH -12 START | DAY -1 | One-time Data | 5 minutes |
Subscription plan: Monitor Real Time
API service for real-time monitoring that can be accessed every 5, 10, or 15 minutes, depending on the region (please check the map in the Rapid updates section).
Recommended:
Treating the data for now as coming from Nowcast, and hence with slightly higher uncertainty than operational data (approx. 15 min ago and older).
The operational data will be updated in the reanalysis runs the next 2 days, and the next month, and hence data from Monitor Real-Time should be updated from Monitor Basic/Professional service.
Not recommended:
Expecting data for now (coming from the nowcasting) to be definitive and not changing.
Expecting the data for now (coming from the nowcasting) to be completely accurate.
Access to data from | Access to data to | Update rate | Maximum time resolution |
|---|---|---|---|
Start of the current day | End of the current day | 5 minutes |
Rapid updates
Rapid update is a shortcut term for sub-hourly update rate. The precise update rate depends on the geographical location, since the update rate of the relevant satellite mission determines it. Refer to the map below for Rapid Updates update rates - note that even if the map shows update rate of Forecast data, this is relevant to Monitor services as well, since the values of Monitor Real Time for now come from the nowcast satellite data (Cloud Motion Vector model).
