What this category of data looks like
The core documents for this category include territorial spatial master plans, detailed plans, special plans, planning implementation evaluation reports, and public opinion summary materials. Data is primarily sourced from the territorial spatial basic information platform, natural resource survey and monitoring data, population and economic statistics data, and remote sensing image results. Daily processed documents are mostly regional-level spatial planning texts, containing fields such as spatial layout, binding indicators, and departmental coordination opinions. The data update frequency is annual, and the volume of documents processed in a single batch is large, involving multi-source heterogeneous spatial and non-spatial data.
What constraints these characteristics impose on the deployment and upgrade link
Annual updated data sources require the deployment to support access to multi-source heterogeneous data, and reserve docking configurations for official data sources such as the territorial spatial basic information platform. The processing requirements for large-volume planning documents and multi-source data require adjusting storage and computing resource configurations during deployment. Documents contain professional fields such as spatial coordinates and binding indicators, so the accuracy of field mapping during data parsing must be ensured. For intranet deployment scenarios, dependence on external networks must be avoided, while the stability of data storage must be guaranteed to prevent data loss after restart.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@internal-host:27017/fastgpt?authSource=admin | Adapts to the unstructured storage requirements of multi-source planning documents; planning texts and evaluation reports require persistent storage |
REDIS_URL | redis://:internal-redis-pass@internal-host:6379/0 | Caches frequently accessed public opinion summary data and remote sensing image indexes to reduce repeated calculation overhead |
DB_MAX_LINK | 50–80 | Matches the annual updated batch data processing scenario, prevents document import interruptions caused by insufficient connection count |
STORAGE_S3_ENDPOINT | Configure according to the intranet storage node address | Adapts to intranet deployment scenarios, does not rely on external network storage services, ensures local storage security of planning data |
FILE_TOKEN_KEY | Randomly generate a 32-bit string | Ensures permission security for planning document upload and download, prevents unauthorized access to sensitive spatial data |
ROOT_KEY | Randomly generate a 64-bit string | Ensures permission security for system background operations, prevents unauthorized modification of planning-related configurations |
Three common configuration mistakes
- Connection timeout errors occur during intranet deployment, making it impossible to access the territorial spatial basic information platform. The cause is that intranet-specific data source docking parameters are not configured, and the external network access policy is enabled by default.
- After restarting the server, all planning configurations and data in the Docker container are cleared. The cause is that the storage directories of MongoDB and Redis are not mounted to local persistent paths, and temporary stored data is cleared after the container restarts.
- Large planning documents cannot be imported normally, and the system prompts file processing timeout. The cause is that the
DB_MAX_LINKparameter is not adjusted to adapt to batch import of large-volume documents, and the default connection count is insufficient to support parallel processing of multi-source data.
How to confirm the configuration is complete
- Perform an intranet data source connectivity test to confirm that public data interfaces of the territorial spatial basic information platform can be pulled normally.
- After restarting the Docker container, check the local mount directories of MongoDB and Redis to confirm that previously imported planning documents and configuration information are retained.
- Upload a standard-volume planning text to confirm that the system can parse it normally and generate corresponding index content.
- Log in to the system background to confirm that the configuration values of
FILE_TOKEN_KEYandROOT_KEYmatch the preset values, and there is no tampering.
The values provided here are common starting points and should be evaluated against the reader's own samples.
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-28.