Instructions for use
The new dataset function in SuperMap can create 16 types of datasets, including point, multipoint, line, polygon, text, CAD, model, attribute table, 3D point, 3D line, 3D polygon, LAS, raster, image, mosaic, and video.
Function Access
- Start tab -> New Dataset group.
- Context menu of a data source in the workspace -> New Dataset -> dataset type item.

- The gallery control in the new dataset group is only available when there is an open data source in the current workspace.
- Based on the selected new dataset type, the new dataset list in the New Dataset dialog will prioritize displaying the chosen type. The New Dataset dialog allows creating multiple datasets of the same or different types at once.
Operating Steps
Taking the creation of a region dataset as an example, the operating steps are as follows:
- Click Start -> New Dataset group, select Polygon, and the New Dataset dialog will pop up.
- In the dialog list, set parameters such as new dataset name, target datasource, type, etc.
- Target datasource: Used to set the target datasource where the new dataset will be located. Its drop-down button menu lists aliases of all open data sources in the current workspace. Select one data source to specify the target datasource for the new dataset.
- Type: Defaults to the dataset type corresponding to the function control you initially clicked, which is Polygon type here. You can reselect the target dataset type via its drop-down button.
- Dataset name: Used to set the name of the new dataset. Double-click the cell to rename it. For valid dataset naming rules, refer to Dataset Naming Rules.
- Add to map: Default is not added. Use the drop-down button to select No, New Map, or Current Map (displayed when the current workspace has an open map). If New Map is selected, the dataset will be added to a new map after creation. If Current Map is selected, the dataset will be added to the currently open map.
- After setting the parameters in the list, select whether to create the dataset using a template in the dialog's right section. Specific parameter descriptions are as follows:
- No Template: Requires setting the dataset's encode type, charset, and coordinate system.
- Encode type: This can only be set when the new dataset type is line or region dataset. The dataset encode type refers to the compression encode type used during storage. For details, see: Dataset Compression Encode Type.
- Charset: Select an appropriate charset for the new dataset. For the standard desktop version, the charset defaults to ASCII (Default). For the Unicode version, it defaults to UTF-8. For supported charsets and descriptions, see: Charset List.
- Coordinate system settings: Supports setting the coordinate system for new datasets. The default coordinate system matches the data source coordinate system. For details on coordinate system settings, see: Projection Settings.
- Use Template: Specify a template dataset to create the dataset based on the template. The created dataset's table structure and most attributes will match the template dataset, such as projection, charset, value range, etc.
Tip:
The bounds of the newly created dataset are 0, the spatial index is no spatial index, and the object count is zero.
- Storage method: If the data source selected for storing the dataset is a PostGIS database datasource, you can choose between SuperMap and WKB data save methods. WKB is a binary format for representing spatial data (e.g., point, line, polygon geometries), while SuperMap is a custom storage format defined by SuperMap.
- SmID type: If the data source selected for storing the dataset is a PostGIS database datasource, you can choose between int and long types.
- Coordinates include M value: When creating a vector dataset (2D point, line, region dataset, or 3D point, line, region dataset), check the "Coordinates include M value" option to add an independent M value attribute to the geometry, supporting storage of non-spatial measurement data like mileage, time, pressure, etc. Default is unchecked.
- Supported Database scenarios for M values:
- Supported database types: UDB, UDBX, PostGIS, PostgreSQL, OraclePlus, DMPlus, DMSpatial, XUGU DB, MySQL, SQLPlus, Yukon, ArcSDE Oracle;
- Unsupported database types: GaussDB 200, Yashan, OracleSpatial;
- M value (Measurement Value) is an additional coordinate dimension for geometries (e.g., points, lines, polygons), used to store supplementary measurement information related to the shape. It is typically associated with X (longitude), Y (latitude), and Z (elevation) but is independent of spatial coordinates, specifically for representing linear reference systems (LRS) or dynamic measurement data.
- Difference between M value and X/Y/Z
- X/Y: Represent geographic spatial positions (e.g., longitude/latitude or projected coordinates).
- Z: Represents elevation or vertical dimension.
- M: Represents dynamic measurement values related to the geometry (e.g., time, mileage, temperature), independent of position.
- Typical application scenarios for M values:
-
Linear reference systems (LRS)
-
Road management: Store highway mileage post data (e.g., M=0, 100, 200) for incident location and facility management.
-
Railway/waterway: Record mileage markers for stations or navigation aids along the route.
-
-
Dynamic attribute binding
-
Pipeline monitoring: Embed pressure or flow values (M=pressure value) at pipeline vertices to support segment analysis.
-
Movement trajectories: Attach timestamps (M=time) to trajectory points for spatiotemporal path analysis.
-
-
Engineering and geographic analysis
-
Dynamic segmentation: Map attribute data to M value intervals of line features (e.g., pollutant concentration in a river section from M=100 to 200).
-
Dynamic labeling: Display location labels based on M values (e.g., "150 meters from start point").
-
-
- Supported Database scenarios for M values:
- No Template: Requires setting the dataset's encode type, charset, and coordinate system.
- After completing all settings for the new dataset, click the OK button at the bottom of the New Dataset dialog to finalize the new dataset operation.

- If multiple data sources are selected under the data source node in the workspace manager, clicking the button control in the New Dataset group will default the target datasource to the topmost selected data source.
- Since the vector plugin lacks the SmUserID field, creating a new dataset directly in gpkg or gdb data sources will not automatically create this field.
- Dataset naming rules:
- Consist of Chinese characters, letters, numbers, and underscores, but cannot start with a number or underscore.
- Length must not be zero and cannot exceed 59 characters, i.e., 59 English letters or 59 Chinese characters. If the dataset name exceeds 59 characters, the excess part will be truncated automatically.
- Must not contain illegal characters such as spaces or parentheses.
- Must not conflict with reserved fields of various databases.
Related Topics
Database Reserved Keywords List