What the data for this use case looks like
Wind power yield and market daily report data comes primarily from three sources: grid settlement data from provincial power trading platforms, power generation data from wind farm SCADA systems, and effective wind speed radiation data from meteorological monitoring stations. Financial institutions use this data to calculate wind power project revenue, while insurance institutions use it for project risk control analysis.
Data updates follow a daily schedule: the system updates full data from the previous day in the early morning, then generates structured CSV or JSON format documents. These documents include core fields such as unique station identifier, actual daily power generation, unit power generation cost, grid settlement electricity price, and daily revenue amount. Field names vary slightly across different data sources, and no unified mandatory standard exists.
Constraints for deployment and upgrade
The multi-source data nature of wind power yield daily reports requires configuring multiple API authentication and IP whitelists during deployment. Access keys and permissions for power trading platforms and farm station systems must be obtained in advance.
The daily full update feature requires deploying scheduled pull tasks. Sufficient time for parsing and storage must be reserved to avoid task timeouts that disrupt daily report generation for financial institutions.
Differences in field names require configuring custom field mapping rules during deployment. This avoids adaptation failures caused by hardcoding, which would affect the accuracy of risk control and calculation results.
Wind power data has high compliance requirements. Data verification rules must be configured during deployment to filter invalid or abnormal data.
If electricity price or cost fields change due to adjustments to power policies during upgrades, the mapping configuration must be updated quickly without recompiling the deployment package. A dynamic configuration loading mechanism must therefore be adopted.
How to set configuration parameters
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Wind power daily report data contains multiple rows of records from multiple farms, so parsing takes a long time. The default timeout duration is insufficient to complete full data parsing |
UPLOAD_FILE_MAX_SIZE | 2000 MB | The daily report file volume for all wind farms usually exceeds the general upper limit. Adjusting this value supports batch data import or pull |
SERVER_HOST | 0.0.0.0 | The default binding of the local loopback address only supports local access. Setting it to 0.0.0.0 allows access to local area network or public network segments |
CRON_SCHEDULE | 0 0 1 * * | Matches the schedule where the power trading platform updates the previous day's data in the early morning, for scheduled pulling of the latest daily report data |
FIELD_MAPPING_CONFIG | Map by station ID to system standard fields | Field names differ across data sources. Custom mapping rules unify data formats within the system |
HIDE_DEFAULT_QRCODE | true | Removes the default official promotion QR code on the page, adapting to usage scenarios for internal farm stations or financial institutions |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration mistakes
- Symptom: The default official QR code is displayed at the bottom of the page and cannot be hidden. Cause: The
HIDE_DEFAULT_QRCODEenvironment variable is not configured totrue, so official promotion content is retained by default. - Symptom: The service is only accessible locally on the server, and other devices on the local area network cannot connect. Cause:
SERVER_HOSTis not configured to0.0.0.0, so the service only binds to the local loopback address and does not open access to external network segments. - Symptom: Data cache inconsistency occurs between nodes after cluster deployment, and some nodes display outdated data. Cause: The
REDIS_CLUSTER_ENABLEDparameter is not enabled, or shared storage is not configured, so nodes cannot synchronize the latest configuration and data.
How to verify configurations are correct
- Access the server's local area network IP or public network IP plus the corresponding port, check if the page displays the custom station identifier and no default official QR code, to confirm the QR code hiding configuration takes effect.
- Manually trigger a scheduled pull task, check the system logs, confirm that the
PARSE_FILE_TIMEOUT_SECONDSconfiguration does not trigger a timeout error, and that the field mapping rules correctly match data source fields. - Check the server firewall rules, confirm that the port corresponding to
SERVER_PORTis open to external access, and that other devices on the local area network can normally access the service page. - View the synchronization logs of cluster nodes, confirm that the
REDIS_CLUSTER_ENABLEDparameter is enabled, and that there are no data synchronization failure errors between nodes, and cached data is consistent.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.