A datasource is a collection used to store various types of datasets (such as point, line, region type data, TIN, GRID, Network, etc.). A datasource can contain one or more datasets of different types, which can be vector datasets or raster datasets. All data is stored in the datasource rather than in the workspace. The physical storage of a datasource can be either file-based or database-based, with the main distinction between different storage methods being the type of data engine used.
SuperMap SDX+ is the spatial database engine within the SuperMap GIS platform, providing the capability for all SuperMap GIS products to access spatial data. It implements the storage, indexing, reading, and updating of spatial data through SuperMap SDX+. Supported data engines include: Database Engines, File Engines, and Web Engines.
supports opening and creating multiple datasource types, categorized into File Databases, Database Datasources, and Web Datasources, corresponding to File Engines, Database Engines, and Web Engines, respectively. Additionally, the EMS datasource provided in the application also uses the file engine and is a type of temporary data source. Different data engines support different dataset types. For detailed information on supported dataset types, please refer to the Dataset Types Supported by SDX+.
File Database
Stores spatial data and attribute data directly in files. Supports UDB and UDBX type file databases.
Using a file database for small data volumes results in faster map display and convenient data migration.
File database supports four types of file engines: SuperMap's custom UDB Engine (read/write), UDBX Engine (read/write), Image Plugin Engines (directly access certain image data), and Vector File Engines (directly access external vector files).
- UDB Engine is a file-based spatial data engine using SuperMap Objects' custom format. This engine employs a traditional hybrid storage method of files + databases. A UDB engine data project includes two files: a file with the extension .udb, using OLE compound document technology to store spatial data; and a file with the extension .udd, using the Access MDB database format to store attribute data. The compound document technology used by UDB files provides the capability to store multiple datasets within a single UDB project. This differs from technologies like ArcInfo Coverage or MapInfo Table files. UDB primarily targets medium and small-scale systems and desktop applications, aiming to improve efficiency and compensate for the shortcomings of pure database engines in this regard.
- UDBX Engine can read, write, and manage Spatialite spatial data. Spatialite is an open-source library that extends the SQLite kernel, providing a complete and powerful spatial database management system with cross-platform and lightweight characteristics, and supports fully mature spatial SQL functionality. Furthermore, Spatialite uses R-Tree as a Spatial Index for efficient retrieval of spatial data. SuperMap's newly added UDBX file engine fully leverages Spatialite's capabilities for efficient spatial data management and the characteristics of a lightweight database.
- Using the UDBX file engine does not require installing or deploying a database system. Since a Spatialite database simply corresponds to a single file with no file size limitation, creating a datasource with the UDBX file engine will create a UDBX file database (*.udbx), which is essentially a database file. It has more open, secure, and stable data operation characteristics compared to the existing UDB file database.
- Within a UDBX file database, you can create datasets or import data from other sources. Dataset types supported by UDBX file databases include: Point, Line, Region, Text, CAD, Attribute Table, 3D Point/Line/Region, EPS Compound Point/Line/Region/Text, Grid, Image, and Mosaic Dataset.
- Additionally, the UDBX file engine features greater openness, supporting direct operation (such as display and editing) of spatial data imported into a Spatialite spatial database by third parties. In application, you only need to load the Spatialite spatial database file (*.sqlite) as a file database into the desktop software.
- Image Plugin Engines support read-only display of grid-type data in SuperMap. Currently supported formats include bmp, jpeg, raw, tiff, sci, sit, and ERDAS IMAGINE raster data types (BMP, JPEG are common raster data types; raw, tiff are remote sensing image data types; sci is a map pre-cached picture file defined by SuperMap; sit is a raster data type defined by SuperMap). Therefore, there are a total of 7 types of plugin engines: bmp read-only engine, jpg read-only engine, raw read-only engine, tiff read-only engine, sci read-only engine, sit read-only engine, and erdas imagine read-only engine.
- Vector File Engines target common vector formats such as shp, tab, dwg, etc., supporting editing and saving of vector files.
| File Database Engine Types | |
| Type | Description |
| UDB | UDB type, for UDB datasources. |
| UDBX | UDBX file engine, can read, write, and manage Spatialite spatial data. For UDBX datasources. Supported dataset types include: Point, Line, Region, Text, CAD, Attribute Table, 3D Point/Line/Region, EPS Compound Point/Line/Region/Text, Grid, Image, and Mosaic Dataset. |
| ImagePlugins | Image Plugins engine type, for common image formats such as bmp, jpg, tiff, and SuperMap's custom image format sit, etc. |
| Vector File | Vector File engine type, for common vector formats such as shp, tab, dwg, etc., supporting editing and saving of vector files. |
Database Datasource
Stores both the spatial geometry information and attributes of spatial data in databases. Provides over ten types of database datasource functionalities including SQLPlus, Oracle Plus, Oracle Spatial, PostgreSQL, PostGIS, Yukon, MySQL, POLARDBGanos, GaussDB 200, DMPlus, KingBase, HighGoDB, SHENTONG, and Vastbase. Typically used for storing large volumes of data, facilitating data management and access. Supports concurrent operations for easy modification and data synchronization. Users need to locally configure the relevant database environment and client when accessing the database.
SuperMap spatial databases use large relational databases as storage containers, managed and operated through SuperMap SDX+, storing spatial data and attribute data integrally in large relational databases such as Oracle, SQL Server, Sybase, and DM3. The spatial database types are as shown in the table below.
| Database Datasource Engine Types | |
| Type | Description |
| SQLPlus | SQL Server engine type, for SQL Server datasources. Must have a client, and environment variables configured correctly. |
| OraclePlus | OraclePlus engine type, for Oracle datasources, must install the client. |
| OracleSpatial | Oracle Spatial engine type, for Oracle Spatial Datasources, must install the client. Does not support network datasets. |
| MySQL | MySQL engine type. Does not require client installation, but the remote service end must ensure local machine has access permissions. |
| PostgreSQL | PostgreSQL engine type. Does not require client installation, but the remote service end must ensure local machine has access permissions. |
| PostGIS | PostGIS engine type, the spatial data extension for PostgreSQL. For PostGIS datasources, does not require client installation, but the remote service end must ensure local machine has access permissions. |
| POLARDBGanos | Alibaba Cloud's self-developed Ganos spatio-temporal engine, providing a series of data types, functions, and stored procedures for efficient storage, indexing, querying, and analytical computation of spatial/spatio-temporal data within the cloud-native relational distributed database PolarDB. |
| GaussDB 200 | GaussDB 200 engine type. For GaussDB 200 datasources, does not require client installation, but the remote service end must ensure local machine has access permissions. |
| Yukon | Yukon engine type. Yukon fully supports the Huawei ecosystem, achieving perfect adaptation from Huawei's self-developed operating system and CPU to the database. Supports extensions and applications of data models such as models and geographic entities. |
| DMPlus | DM engine type. For Dameng (DM) datasources, must install the client, and environment variables configured correctly. |
| DMSpatial | DMSpatial engine type. For Dameng (DM) datasources, must install the client, and environment variables configured correctly. |
| ES | Elasticsearch is a popular enterprise-level search engine. Requires a locally accessible Elasticsearch server. |
| HighGoDB | HighGoDB engine type. Does not require client installation, but the remote service end must ensure local machine has access permissions. |
| KingBase | Kingbase engine type, for Kingbase datasources, does not support multi-band data. Must have a client. |
| SHENGTONG | SHENGTONG engine type, the spatial data extension for PostgreSQL. For SHENGTONG datasources, does not require client installation, but the remote service end must ensure local machine has access permissions. |
| Vastbase | The Vastbase database is an enterprise-level relational database developed by HighGo Data based on the open-source openGauss kernel.Besides having the ultimate performance of openGauss, Vastbase adds a large number of Oracle compatibility features on top of the original functionalities, significantly enhances security following the EAL4+ standard, and integrates a series of enterprise-level functionalities for professional application domains such as GIS/stream computing. |
| ArcSDE for Oracle | ArcSDE_Oracle engine type, for ArcSDE for Oracle datasources. Currently only supports opening this datasource in read-only mode. |
| XUGU DB | The XUGU DB is positioned as a universal, transparent, high-performance, integrated single-machine distributed database. For XUGU DB datasources, does not require client installation. |
Warning: SuperMap supports the SDX+ data engine. The theoretical maximum number of record objects that can be stored in a dataset is 231-1, i.e., 2147483647 records. Records exceeding this value cannot be displayed.
SuperMap iObjects supports multiple database engines (as shown in the table below). Based on common engine requirements, the functional entries currently visible on the desktop include the aforementioned 12 types of databases. Users can customize the functional entries for database datasources by modifying configuration file parameters, adding or deleting various database datasources already supported by SuperMap iObjects.
Supports customizing the functional entries for database datasources by modifying configuration file parameters. The configuration file is the Desktop.Parameter.xml file located in the product package/Configuration/ folder. The configuration parameter codes are displayed by default as follows:
<engine extraEngineType="" hiddenEngineTypes=""/>
- Where extraEngineType="" is empty by default. In this case, the database entry is the default database datasource entry for the desktop. To add a new database type already supported by SuperMap iObjects, simply fill in the corresponding enumeration value for that database. For example, to add the GBase engine type, whose enumeration value is 2002, write the configuration file code as extraEngineType="2002".
- Where hiddenEngineTypes="" is empty by default. To delete a database datasource functional entry, simply fill in the corresponding enumeration value for that database. For example, to delete the OracleSpatial engine and SQLPlus engine types, whose enumeration values are 10 and 16 respectively, write the configuration file code as hiddenEngineTypes="10,16".
| Datasource Engine Types Supported by SuperMap iObjects | |
| Type | Enumeration Value |
| ArcSDE for Oracle | 2081 |
| DB2 | 18 |
| DMPlus | 17 |
| DMSpatial | 2062 |
| ES | 2011 |
| POLARDBGanos | 2057 |
| GaussDB 100 | 2060 |
| GBase | 2002 |
| HighGoDB | 2023 |
| HWPostgreSQL | 2056 |
| KingBase | 19 |
| MongoDB | 401 |
| MySQL | 32 |
| OraclePlus | 12 |
| OracleSpatial | 10 |
| PostGIS | 2012 |
| PostgreSQL | 221 |
| SHENTONG | 2055 |
| SQLPlus | 16 |
| SQLSpatial | 2013 |
| Yashan | 2073 |
| Yukon | 2072 |
| XUGU | 2058 |
Web Datasource
Stored on a server on the network. When using this type of datasource, the corresponding datasource is obtained through a URL address. For example, datasources such as OGC, iServerREST, MapWord, XYXZTile, geovis, siwei earth, Kailide, and jilin no.1 belong to Web datasources.
The Web engine can directly access Web services provided by WFS, WMS, WCS, etc. This type of engine treats Web servers on the network that comply with OGC standards as SuperMap datasources. Through it, maps and data published online can be fully integrated with SuperMap's maps and data, incorporating WFS and WMS applications into SuperMap's technical system, expanding the application field of SuperMap data engines. The Web engine is a read-only engine.
| Web Datasource Engine Types | |
| Type | Description |
| OGC | OGC engine type, for Web datasources. Currently supported types include WMS, WFS, WCS, and WMTS. |
| iServerRest | iServer Rest service engine type, based on REST protocol published map services. |
| MapWorld-Online | Map service from Map World (Tianditu) integrated with SuperMap Online. |
| MapWorld | Map World (Tianditu) service engine type, for map services published by Map World (Tianditu). |
| GoogleMaps | GoogleMaps engine type. For Google electronic map services. |
| World Terrain | Divided into topographic map and dark topographic map, these are global shaded relief map services published by SuperMap. |
| OpenStreetMaps | Also known as OSM engine type, it is a free, open-source map service created collaboratively by the online community. |
| iServer DataStore | iServer DataStore is a data service published by SuperMap. Data service is a type of GIS service. |
| XYZTile | It is an online map XYZ tile format, allowing access to online maps via URL. |
| geovis earth | geovis earth provides three types of map services: vector, image, and terrain shaded relief. |
| siwei earth | siwei earth provides global tiled image services that have undergone unified fusion and mosaic processing. |
| Kailide | Kailide can provide national map product data segmented by region and object. |
| century space images | century space images provides internet-based full-resolution online application services for imagery, with the main acquisition times being 2019 and 2020. |
| jilin no.1 | jilin no.1 launches an imagery service suite, providing the latest high-quality image tiled data covering the entire country. |
Note: Currently, OpenStreetMaps may not open normally within mainland China, but users outside mainland China can use this function normally. For users within mainland China, if you need to understand the details, please consult the technical support center, phone: 400-8900-866.
EMS Datasource
Data in an EMS datasource is saved in memory, making it a temporary data source that does not support saving. The corresponding data engine is the memory engine. Some intermediate analysis results can be stored in this datasource, which helps improve analysis efficiency. When final data is obtained, it can be exported from the EMS datasource to local data.
Related Topics