What This Category's Data Looks Like
Data for this category mainly comes from the territorial spatial basic information platform, natural resource survey and monitoring data, population and economic statistics, and remote sensing images. The update frequency is annual.
Commonly processed documents include territorial spatial overall plans, detailed plans, special plans, planning implementation evaluation reports, and public opinion summaries. Most documents contain regional spatial scope, binding indicators, departmental and public opinions, and other content. Fields involve spatial layout, indicator values, opinion entries, and similar elements. There are no unified fixed units, and adjustments are made based on the specific document type.
Constraints on Workflow Orchestration From These Characteristics
The data sources for this category are scattered and updated annually. Workflow configurations must include scheduled synchronization nodes for official data sources to avoid outdated data.
There are various document types. Different parsing rules must be set in the workflow to adapt to different document structures.
The feature of mixed spatial data and text content requires distinguishing between spatial attribute extraction and text question-and-answer nodes during workflow orchestration. This avoids mixed processing of these elements.
The business requirement for multi-source data aggregation requires connecting data verification and format unification nodes. This reduces the probability of errors in subsequent processing.
Consequences of errors in this category include planning approval delays, project landing conflicts, and similar issues. Exception alert nodes must be added to the workflow to intercept content that does not meet policy requirements in a timely manner.
How to Set Configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Single Search Limit | Top 5 entries | Policy basis documents for this category are mostly structured entries; excessive recall results will increase context redundancy |
| Maximum Context | 800–1200 characters | The core content length of planning-related policies and regulatory basis is concentrated in this range, which can cover key question-and-answer needs |
| Question Classification Node | Triggered by document type | Different types of planning documents correspond to different policy basis libraries; accurate matching can be achieved after classification |
variables | Bound to territorial spatial planning annual version number | Association with official updated data for the corresponding year is required to ensure question-and-answer content aligns with the latest policies |
| Timeout Threshold | 600 seconds | Spatial data parsing and multi-source data aggregation links take a long time; sufficient processing time must be reserved |
Three Common Configuration Mistakes
- An error prompt appears for fields prefixed with
$schemaduring workflow configuration, preventing normal startup. The cause is that the input parameter structure of the workflow is not configured correctly, and an undefined metadata field was added by mistake. - After enabling the image upload function, the returned image link uses the IP plus port format and cannot be replaced with a custom domain. The cause is that no link format conversion node was added to the workflow, and no custom domain replacement rule was configured via
variables. - The expected knowledge base matching is not triggered after the question classification node is configured, and the question-and-answer results deviate from the policy basis scope. The cause is that the classification trigger conditions were not set according to document type, and the classification node was not bound to the knowledge base corresponding to the planning document.
How to Confirm Configuration Is Complete
- Run workflow test cases, check whether the execution order of each node matches the orchestration logic, and confirm that the
nodeIdbinding is correct. - Upload test planning documents, check whether the image links are automatically replaced with custom domains, and confirm that the
variablesconfiguration takes effect. - Submit different types of policy questions, check whether the question classification node correctly matches the corresponding knowledge base, and confirm that the classification trigger conditions are set reasonably.
- Wait for the workflow execution to complete, check whether the preset timeout threshold is exceeded, and confirm that the timeout threshold configuration meets business requirements.
The values provided are common starting points and should be measured 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.