What data for this category includes
This category's data originates primarily from the territorial spatial basic information platform, natural resource survey and monitoring datasets, population and economic statistical sources, and remote sensing imagery. Commonly processed documents include territorial spatial overall plans, detailed plans, special plans, planning implementation evaluation reports, and public opinion summaries. Data updates occur annually. Document structures contain spatial coordinate layers, constrained indicator entries, statistical data tables, and opinion feedback text. Fields typically cover spatial scope, control rules, and population and economic parameters, with units including square kilometers, ten thousand people, percentage, and similar units.
What constraints these characteristics impose on tool calling and plugins
Annual updated data sources and multi-source heterogeneous documents require tool calling to support batch file upload and cross-data source pulling. Differences in field formats and units for spatial documents require plugins to preset standardized mapping rules to avoid data parsing mismatches. Unstructured long text from public opinion summaries requires tools to support long text splitting and semantic extraction steps. Collaborative verification of multi-source data requires workflows to connect the acquisition, cleaning, and integration steps of different data sources via API calls, while adapting to access permission configurations for different data sources.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | Set to auto | Supports automatic scheduling of multiple tools to match mixed processing needs for multi-source spatial data and documents |
| Single file size limit | 1000 MB | Accommodates uploads of large files such as remote sensing images and large planning reports |
| File upload interface timeout | 600 seconds | Supports complete upload and parsing processes for large files |
| Knowledge base binding rule | Bind the designated territorial spatial basic information platform knowledge base | Matches the fixed data source sources and document types for this category |
| SQL query timeout setting | 120 seconds | Accommodates complex associated query operations for spatial data |
functionCall | Enable explicit function calling | Ensures workflows execute tool calls according to preset steps to avoid scheduling chaos |
Three common mistakes
- An API-called workflow returns a missing parameter error when uploading planning files. The cause is failure to pass parameters according to the file field names preset in the workflow, and failure to match the metadata requirements for territorial spatial planning files.
- No results are returned when executing spatial data queries after configuring a MySQL database connection. The cause is incorrect configuration of the database's spatial data access permissions, or failure to specify the exclusive data source table for the territorial spatial basic information platform.
- Associated data retrieval is not triggered after data is sent to the knowledge base. The cause is failure to pass the knowledge base ID as a workflow input parameter, preventing tools from binding the designated planning data source.
How to confirm configurations are correct
Reference only; verify against the target FastGPT release and deployment documentation.
- Initiate a single upload test for a remote sensing image or planning report, and check whether the file ID returned by the interface is generated normally.
- Call the preset SQL query tool to verify whether designated spatial data entries from the territorial spatial basic information platform can be extracted.
- Trigger the workflow to call the bound knowledge base, and check whether relevant fragments of planning documents or public opinions can be returned.
- View workflow run logs to confirm that the
toolChoiceandfunctionCallconfiguration parameters have been correctly loaded.
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.