What this category of data includes
Data for this category primarily comes from the national land spatial planning unified map, project approval and supervision platform, current land use database, and ecological protection red line data. Update frequency is irregular. Daily circulating documents include Land Pre-examination and Site Selection Opinion, Construction Land Planning Permit, Construction Engineering Planning Permit, Red Line Drawing, and Planning Conditions. Data fields include project site selection coordinates, land scale, control boundaries, pre-examination approval conditions, and other items. There are no unified standard units, and corresponding national land spatial planning indicators are matched based on actual project conditions.
Constraints on HTTP Interfaces and External Systems
Scattered data sources and irregular update cycles require HTTP interfaces to support connection to multiple external systems and adapt to different authentication rules. Diverse daily circulating document types require interfaces to support transmission and parsing of multiple formats, including vector files, PDFs, and structured approval forms. Data includes core control fields such as project site selection and red line scope. Structured data returned by interfaces must match the standard field format of national land spatial planning, to enable internal office systems to complete site selection conflict checks and pre-condition coordination. Interfaces must also have abnormal data interception capabilities to prevent incorrect data from entering approval workflows.
Configuration Guidelines
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Authorization | Bearer external system API key | Complies with OAuth2 standard authentication requirements when connecting to external approval and supervision platforms, national land spatial planning unified map, and similar systems |
variables | Pass project ID, red line coordinate range, ecological protection red line layer identifier | Accurately pull planning data for the corresponding project, avoid full data pulls that consume bandwidth |
responseData | Only return project site selection conflict items, missing pre-examination approval items, and compliance check results | Reduce invalid data transmission, adapt to review process requirements for internal office systems |
| Timeout period | 600 seconds | Land pre-examination data pulling involves multiple layer checks, sufficient response time must be reserved |
| Retry count | 3 times, 10 second interval | Respond to temporary fluctuations in external systems, prevent approval workflow blockages caused by a single failed request |
Three Common Configuration Mistakes
- Symptom: Returns "401 Unauthorized" status code when calling the interface. Cause: The
Authorizationparameter is not configured correctly, or the external system API key has expired. - Symptom: Received PDF or vector files cannot be parsed, and empty
responseDatais returned. Cause: Transmission headers adapted to multi-format documents are not configured, or the uploaded file size exceeds the external system's limits. - Symptom: Streaming responses are interrupted, and complete check results cannot be obtained. Cause: Reasonable timeout parameters are not set, or the external system does not enable streaming transmission support.
How to Confirm Proper Configuration
- Call the test interface, pass known compliant project parameters, and check if the returned
responseDataincludes expected compliance check results. - Check if the
Authorizationparameter matches the external system's authentication requirements. This can be verified by calling the external system's public health interface. - Upload single and multiple documents that meet the required formats, and confirm that the interface can receive them normally and return parsing results.
- Simulate a temporary timeout of the external system, and confirm that the interface executes retry operations according to the configured retry rules.
The values provided here are common starting points, and should be evaluated against samples from the actual deployment.
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.