Datasource Splitting

Instructions For Use

Datasource splitting refers to the process of dividing a large data source into multiple independent datasource files based on a specified property field. This function is suitable for multi-region collaborative data updates, mapping, and other tasks. For example, province-wide land use data can be split into multiple datasource files according to municipal administrative divisions, which can then be distributed to municipal units for field survey and updates.

When using this function, please note the following limitations:

  • Supported data types: 2D point/line/region, text, and CAD datasets.
  • Coordinate system handling: Supports clipping across coordinate systems. When the coordinate system of the source data is inconsistent with that of the clip data, the system will automatically perform temporary coordinate projection during the clipping process to ensure accurate clip bounds. After the splitting is complete, the coordinate system of each dataset remains in its original state and will not change.

SuperMap iDesktopX is available starting from version 2026.

Parameter Description

Parameter Name Parameter Interpretation Parameter Type
Source Datasource

Specifies the data source to be split.

Only UDB, UDBX, File GDB file-based data sources, and database datasources are supported. Only 2D point/line/region, text, and CAD datasets within them will be processed and output; other types of datasets will be ignored.

 Datasource
Clip Data Source Specifies the data source containing the clip bounds. Datasource
Clip Dataset Specifies the region dataset used for clipping. Each polygon object in this dataset will serve as an independent clip bound for generating one result datasource. DatasetVector
Clipping Field Specifies the field used to name the result datasource. After splitting, the filename of each result datasource will be based on the value of this field. String
Output Format

Specifies the storage format for the split data sources. The default is UDBX, with UDB and FileGDB also available as options.

When selecting the FileGDB format, due to its inherent limitations, text datasets and CAD datasets from the source datasource will not be output to the results.

 EngineType
Export Directory

Specifies the local folder to store the results. The naming rule for result datasources is as follows:

  • Each result datasource is named after the value of the Clipping Field from the corresponding polygon object. For example, Beijing.udbx.
  • If multiple polygon objects share the same Clipping Field value, the system will automatically add an "_n" suffix to subsequent files for distinction. For example, AreaA.udbx, AreaA_1.udbx, AreaA_2.udbx.
 String

Output Result

Multiple independent datasource files generated after the split. Each data source is saved in the specified export directory, with its internal dataset types, names, and table structure consistent with the source datasource.