What the data for this category looks like
The data for environmental monitoring intelligent due diligence reports comes from three main sources: fixed automatic monitoring stations, portable handheld monitoring devices, and satellite remote sensing imagery. Data update cycles fall into three categories: real-time (5-minute intervals), hourly, and daily. A single report includes multiple sets of pollutant data for dozens to hundreds of monitoring points. The document structure of each report centers on monitoring points as core units. Each unit contains fields such as point number, longitude and latitude, monitoring time, pollutant concentration (such as PM2.5, SO₂ in μg/m³ units), equipment operating status, and quality control verification results. Some reports also include a summary of environmental impact analysis for the area around the monitoring point.
Constraints imposed on HTTP interfaces and external systems
Frequently updated monitoring data requires interface response speeds to match the data refresh rhythm. Overly long polling intervals can cause due diligence report data to lag. The multi-point, multi-field structure of the data requires external interfaces to support batch point queries and custom field returns. This reduces invalid data transmission. Some environmental protection department monitoring APIs have a single request data volume limit. The size of request parameters and response bodies must be controlled. Data fields have strict unit and format requirements. When connecting external systems, retain original fields and units to avoid data distortion.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
external_api_timeout | 300–600 seconds | Environmental monitoring data interfaces return large data volumes per request. Some third-party monitoring station interfaces have high response delays. This interval covers most scenarios |
request_batch_size | 10–20 point IDs per request | This prevents HTTP 413 errors from overly long single request parameters. It also adapts to batch request limits for most public environmental monitoring APIs |
auth_type | bearer_token | Most environmental protection department public APIs and OneAPI use token authentication. This is compatible with FastGPT's external interface authentication logic |
response_pagination | Enable automatic pagination | Multi-period monitoring data for a single point may exceed the single return limit. Automatic pagination fully retrieves all monitoring records |
field_mapping_mode | Map according to official fields | This retains original pollutant concentration units and quality control fields. It avoids format deviations in due diligence report data |
global_var_sync_mode | Pass synchronously during interface requests | This supports dynamic updates of global parameters such as monitoring points and report cycles during external calls. It adapts to flexible due diligence requirements |
The parameter values provided on this page are conventional recommendations used as a starting point for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require specific analysis. It is recommended to test on your own samples before finalizing the settings.
Three Common Configuration Mistakes
- Phenomenon: Calling an external monitoring interface returns
Cannot read property 'concentration' of null. Cause: Field mapping rules are not correctly configured. The core pollutant concentration field in the response body is not extracted, leading to missing dependent data in downstream processing steps. - Phenomenon: A null value error appears after configuring the OneAPI token. Cause: The token parameter is not correctly bound in FastGPT's external interface configuration. Or the token is not granted access permission to the environmental monitoring API.
- Phenomenon: Global variables do not take effect when calling the workflow interface externally. Cause: The
globalVarsparameter is not correctly included in the interface request body. Or the workflow's global variable synchronization switch is not enabled.
How to Verify Correct Configuration
- Initiate a single point query test. Confirm the HTTP response status code is 200, and the response body includes the expected point number, monitoring time, and pollutant concentration fields.
- Simulate an external call. Pass custom global variables, and confirm that the monitoring point parameters used in the workflow are updated synchronously with the global variables.
- Send a request with an invalid token. Confirm the 401 Unauthorized status code is returned, verifying that the authentication logic works correctly.
- After configuring the batch request parameters, send a request containing 20 point IDs. Confirm the interface does not return a 413 error and the returned data is complete.
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.