What the data for this category looks like
Daily documents for this category include territorial spatial overall plans, detailed plans, special plans, planning implementation evaluation reports, and public opinion summaries. Data sources are the territorial spatial basic information platform, natural resource survey and monitoring data, population and economic statistics, and remote sensing images. The update frequency is once per year. Documents contain fields such as spatial coordinates, binding indicators, approval nodes, and public feedback opinions. Some documents include geospatial layer data, and data volume increases as the planning hierarchy rises.
What constraints do these characteristics impose on the "citation sources and traceability" link
Annual updated data sources require citation traceability to be linked to the latest version of planning documents, to avoid planning approval delays caused by mixing cross-version documents. Multi-source spatial data must clearly mark the data source platform and collection time, to ensure traceability information can correspond to specific natural resource survey links. Unstructured content in public opinion summaries must match the original source, and vague source markings are not allowed. In addition, regional-level planning documents have a large volume, so the content length of a single citation must be limited to avoid traceability information overload affecting query efficiency.
How to configure settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 1500–2000 token | Adapts to the single-paragraph citation length of regional-level planning documents, avoiding exceeding context limits |
responseData | Return only associated file IDs and source platforms | Meets the business requirement of clearly marking data sources for this category, avoiding redundant information |
detail | Full traceability information | Includes data collection time and updated version number, meeting traceability compliance requirements for planning management |
| Single search limit | Top 8 entries | Covers the main sources of multi-source data, avoiding traceability confusion caused by too many results |
| Maximum context | 8000–10000 characters | Adapts to the context length of annually updated planning documents, ensuring complete citations |
Three common configuration errors
- Phenomenon: Only the global ID of the knowledge base collection is displayed in citation traceability results, and the unique identifier of a single planning document is not associated. Cause: The
responseDataparameter is not configured correctly, only returning the overall ID of the knowledge base without matching the specific ID of a single document. - Phenomenon: After setting the variable reference mode, the temperature setting button disappears, and generation parameters cannot be adjusted. Cause: Some interface configuration logic locks model parameter adjustment by default in variable reference mode, and the temperature setting entry is not retained.
- Phenomenon: The context of multi-turn conversations is not correctly brought into the citation traceability link, and traceability information is not associated with the planning version mentioned in historical conversations. Cause: The context reference rule for multi-turn conversations is not configured in the prompt, resulting in traceability only being associated with the current round of queries.
How to confirm the configuration is complete
- Initiate a query containing planning document keywords, and check whether the returned traceability information includes the unique ID, source platform, and update time of a single data entry.
- Adjust the
quoteMaxTokenparameter value, and verify that the citation content truncation logic meets expectations, with no missing or overly long content. - Switch to the variable reference mode, and confirm that the temperature setting button is normally displayed and parameters can be adjusted normally.
- Initiate two consecutive conversations, and check whether the traceability information of the second query is associated with the planning document version mentioned in the first conversation.
The values given 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.