Feature Description

The custom topology check scenario is used to organize geometric topology rules and attribute check rules into reusable check scenarios, consolidating business quality inspection rules and reducing repetitive configuration work.

This function is based on validate topology rules and supports configuring groups, check items, check methods, topology rules, check data, reference data, tolerance values, filter expressions, and attribute check-specific parameters within the same scenario. After saving the scenario, you can perform quality inspection on actual data through the perform a topology check scenario function.

Application Scenarios

• DLG produce data: Pre-configure geometric topology rules and attribute check rules according to data standards, providing unified rules for self-inspection and result review during production.
• District/county level result aggregation: Create a unified check scenario for aggregated data from multiple map sheets or areas, checking spatial relationships, field completeness, ID uniqueness, and cross-layer association consistency.
• Project scenario reuse: Export a check scenario for a certain type of business data as a scenario file, then import it in other projects or teams for reuse, maintaining consistent check rule configuration.

Functional Conditions

• When creating or importing a topology check scenario, a template check data must be specified. The check data set and reference dataset during the scenario design phase are selected from the template check layer bounds.
• The same scenario can include both geometry check items and attribute check items. Attribute checks are not fixed independent groups in the scenario tree. After creating a new check, you must first set the check method, then select the corresponding topology rules.
• The topology check scenario supports saving, importing, and exporting as .tcs scenario files. Only valid .tcs files are supported for import.

Version Information

SuperMap iDesktopX provides the custom topology check scenario feature starting from version 2026.

Feature Entry

• Inspect Data Quality tab > Custom Topology Check group > Check the Scheme Design.

Operation Instructions

1. On the Inspect Data Quality tab, click the Check the Scheme Design button to open the topology check scenario design view.
2. Click the New button to create a scenario, or click the Import button to import an existing .tcs scenario file.
   • New Scenario: In the new topology check scenario dialog, confirm the name of the scenario and specify the check data.
   • Import Scenario: After selecting a .tcs scenario file, specify the check data for subsequent check item parameter configuration.
3. Organize check items in the scenario tree.
   • New: Create a check item group when a scenario node is selected. Groups cannot be nested.
   • Create a New Check: Create a check item under a scenario node or group node.
   • Rename: After selecting a scenario, group, or check item, you can modify the name via the context menu or the F2 shortcut key.
4. Select a check item and configure check parameters in the parameters area on the right.
   • Name of the Scenario: Displays the name of the scenario where the check item resides.
   • Group Name: Displays the group name of the check item.
   • Check Item Name: Sets the current check item name, which is synchronized with the scenario tree node.
   • Check Item Description: Fills in supplementary notes for the current check item, used to record rule purpose, business constraints, or configuration basis.
   • Check Method: Sets the check category for the current check item, including Geometry Check and Attribute Check. The default is geometry check. When switching the check method, the system re-filters the topology rules drop-down list; if the current rule does not belong to the new check method, the current rule and rule-specific parameters are cleared.
   • Topology Rules: Rules used for validate topology. For detailed rule descriptions, see Validate Topology Rules.
   • Error Type: Enter the error classification for the check result.
   • Geometry Check Parameters: When the check method is geometry check, set the following parameters:
     • Dataset: Select the dataset for geometric validate topology.
     • Tolerances: Tolerance values used for geometric validate topology and topology preprocessing, such as the distance between nodes. Different topology rules require different tolerances; it is recommended to use the default tolerance. The tolerance unit is consistent with the dataset unit. The default tolerance depends on the coordinate system of the dataset. For details, see Tolerance Description.
     • Filter Expression: You can filter participating objects using a filter expression, so that only objects that meet the conditions participate in the check.
   • Attribute Check Parameters: When the check method is attribute check, the corresponding parameters are displayed according to the selected topology rules.
     • Non-Empty Check: Checks whether the specified field value is empty.
       • Check Field: Select the fields to participate in the non-empty check. Multiple selections are supported. If any selected field is empty, an attribute check error is generated.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Enumeration Value Check: Checks whether the specified field value belongs to a preset set of enumeration values.
       • Check Field: Select the field to perform the enumeration value check.
       • Enumeration Value: Set the set of allowed field values. Supports selection from the drop-down list or manual input; multiple enumeration values are separated by English semicolons (;), for example: road;bridge;tunnel.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Unique Value Check: Checks whether the specified field value is unique, used to identify duplicate records.
       • Check Field: Select the field for uniqueness check. This rule only supports single-field checks.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Length Check: Checks whether the field value length meets the constraint condition.
       • Check Field: Select a character-type field for length check.
       • Length Comparison: Set the comparison method between the actual length of the field and the field length, such as equal, greater than, no less than, less than, or no more than.
       • Field Length: Set the length value for comparison. The field length must be a positive integer and is calculated by character length.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Range Check: Checks whether the field value falls within a set range.
       • Check Field: Select a numeric field for range check.
       • Min: Set the lower limit of the allowed range. At least one of the minimum and maximum values must be filled.
       • Max: Set the upper limit of the allowed range. When both the minimum and maximum values are filled, the minimum value cannot be greater than the maximum value.
       • Include Lower Limit: Set whether to include the minimum value in the check. When checked, an actual value equal to the minimum passes; when unchecked, the actual value must be greater than the minimum.
       • Include Upper Limit: Set whether to include the maximum value in the check. When checked, an actual value equal to the maximum passes; when unchecked, the actual value must be less than the maximum.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Field Relationship Check: Checks whether the values of two fields in the same record of the same dataset satisfy a specified comparison relationship.
       • Check Field 1: Select the first field for comparison.
       • Comparison Relationship: Set the comparison relationship between check field 1 and check field 2, such as equal, not equal, greater than, no less than, less than, or no more than.
       • Check Field 2: Select the second field for comparison. The types of the two check fields must be consistent or comparable.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Association Consistency Check: Checks the record association and attribute consistency between two datasets based on the association field.
       • Association Field: Select the field in the check data set used for association matching.
       • Check Field: Select the field in the check data set that participates in the field value consistency comparison. If only checking record association completeness, this parameter can be left unset.
       • Filter Expression: Set the range of records in the check data set to participate in the check. If empty, perform the check on all records in the current check data set.
     • Geometric Properties Consistency Check: Checks whether the property field value is consistent with the object's geometric area or geometric length.
       • Check Field: Select a numeric field that stores area or length values.
       • Geometric Quantity Type: Set the geometric quantity involved in consistency judgment. Area data supports area check, and line data supports length check.
       • Allowed Error: Set the allowed error range between the property field value and the geometric calculation value. The allowed error must be no less than 0.
       • Filter Expression: Set the range of records to participate in the check. If empty, perform the check on all records in the current check data set.
     • Custom SQL Check: Express complex attribute check logic through SQL statements.
       • SQL Statement Input: Enter a query-type SQL statement. Each record in the SQL query result is considered a problem record; if the query result is null, the check passes.
   • Reference Data: When the selected topology rules require reference data, select the corresponding reference dataset.
     • Dataset: Select the reference dataset used for participation in the check.
     • Reference Association Field: This parameter is available when the check method is Attribute Check and the topology rule is Association Consistency Check. It is used to select the field in the reference data set that matches the association field of the check data set.
     • Reference Field: This parameter is available when the check method is Attribute Check and the topology rule is Association Consistency Check. It is used to select the field in the reference data set that participates in the field value consistency comparison.
5. Click the Save button to save the scenario. If there are multiple modified scenarios, a save dialog will appear, allowing you to check the scenarios you want to save.
6. To reuse a scenario, select the scenario node and click the Export button to export the current scenario as a .tcs file.
7. To execute the scenario on actual data, open the Perform a Topology Check Scenario function, select the saved scenario and check data, then perform the check.

Notes:

• Deleting a scenario will delete all groups and check items under that scenario. Deleting a group will also delete the check items contained in the group. Please confirm before performing the deletion operation.
• When a filter expression, check data set, or reference dataset is invalid, the relevant check items may fail during scenario execution. Please check the parameter configuration before execution.

Related Topics

• Perform a Topology Check Scenario
• Validate Topology
• Error Inspector