In this document
This guide explains how to structure and prepare Push Delivery data requests in CSV format and interpret the response files, with examples for both monitoring and forecasting scenarios.
Overview
Push Delivery is a service designed to automate the delivery of Solargis data directly to a user’s remote directory in CSV format. This process ensures seamless integration into your systems, enabling efficient use of solar and PV data for monitoring, forecasting, and other applications.
The data request file specifies the parameters required for data delivery, while the response files contain the requested data in an easy-to-process CSV format.
Request Format: Submit a CSV file specifying multiple locations in one request.
Schedule: Data is pushed at regular intervals (e.g., daily or hourly).
Data Availability: Matches the coverage of the DataDelivery Web Service.
Use Case: Ideal for large-scale monitoring or forecasting setups.
Setup and Pricing: Contact us to configure your trial or discuss pricing.
Data request format
To initiate Push Delivery, you must provide a properly formatted data request file. The file should follow these guidelines:
File format: The data request must be a CSV file.
Header row: The first row of the file must contain parameter names (input parameters).
Data rows: Each subsequent row represents one request, with parameter values corresponding to the header row. There can be multiple rows in the file, each treated as an individual request.
Order of parameters: The order of parameters in the header is flexible and does not affect processing.
Validation: Data requests are typically prepared, maintained, and validated by Solargis to ensure accuracy and compliance with delivery requirements.
The parameters used in the data request file are consistent with those available in the Monitor & Forecast XML requests.
Example 1: Data request for monitoring
In monitoring requests, there are no fromDate or toDate parameters because the date range is determined by contract and managed automatically (e.g., delivering data for the last completed day or month).
Example CSV structure:
siteId | lat | lng | geometry | azimuth | summarization | terrainShading | processingKeys | pvModuleTechnology | pvInstallationType | pvInstalledPower | pvDateStartup | pvTrackerBackTrack | pvTrackerRotMin | active |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
example1 | 48.61259 | 20.827079 | OneAxisHorizontalNS | 180 | hourly | TRUE | GHI GTI DIF TEMP PVOUT | CSI | FREE_STANDING | 40020 | 20150701 | TRUE | -45,45 | TRUE |
Example 2: Data request for forecasting
In forecasting requests, you must specify forecastFromDay and forecastToDay parameters to define the forecast period relative to today (e.g., forecastFromDay=0 means today, forecastToDay=7 means seven days ahead).
Example CSV structure:
siteId | forecastFromDay | forecastToDay | lat | lng | summarization | terrainShading | processingKeys | active |
|---|---|---|---|---|---|---|---|---|
example2 | 0 | 7 | 48.61259 | 20.827079 | hourly | TRUE | GHI DNI DIF TEMP WS WD | TRUE |
Response format
The Push Delivery responses are stored as CSV files in a user’s remote directory, making them suitable for automated processing and integration into your systems. Each response file includes:
Title section: Identifies the content of the file (e.g., site details, time period).
Metadata section: Provides additional information about the dataset (e.g., units, summarization).
Data section: Contains timestamped values corresponding to your requested parameters.
Examples of response files:
Hourly timeseries: Solargis_TS_hourly_sample.csv
Monthly timeseries: Solargis_TS_monthly_sample.csv