Datasource (Datasource) is a collection used to store various types of Dataset (such as point, line, surface type data, TIN, GRID, Network, etc.). A Datasource can contain one or more Datasets of different types, either Vector or Raster. All data is stored in Datasource, not Workspace. The physical storage of Datasource can be either file mode or database mode, and the main difference between different storage modes lies in the type of data engine used.

SuperMap SDX + is the Spatial Data database engine in SuperMap GIS platform, which provides the ability to access Spatial Data for all products in SuperMap GIS. SuperMap SDX + is used to store, index, read and update Spatial Data. Supported data engines include: database engine, file engine, and Web engine.

Support opening and creating multiple Datasource types, including File Database, Database-type Datasource and WebDatasource, which correspond to File Engine, Database Engine and Web Engine respectively. In addition, the EMS Datasource provided in Application also uses the file engine, which is a Temporary Data source. Different data engines support different Dataset Types. For detailed Dataset Supportive Type, please refer to Dataset Types Supported by SDX + Introduction.

File Database

Stores Spatial Data and attribute data directly in a file. Supports UDB and UDBX types of File Database.

In the case of small amount of data, the display of File Database map is faster, and Data Migration is convenient.

File Database supports four types of file engines: SuperMap customized UDB engine (read-write), UDBX engine (read-write), image plug-in engine (direct access to some Image Data) and Vector File engine (direct access to external Vector File).

• UDB Engine is a file-based Spatial Data engine in the SuperMap Objects custom format. This engine uses the traditional file + database hybrid storage mode. A data project of the UDB engine includes two files: the file with the extension of UDB uses the OLE compound document technology to store Spatial Data; the file with the extension of UDD uses the MDB database format of Access to store attribute data. The compound document technology used by UDB files provides the ability to store multiple Datasets in a UDB project. This is different from technologies such as ArcInfo Coverage and MapInfo Table files. UDB is mainly for small and medium-sized systems and desktop applications, aiming to improve efficiency and make up for the shortcomings of pure database engine in this respect.
• UDBX Engine, which can read, write, and manage Spatialite Spatial Data. Spatialite is an open source library used to extend the kernel of SQLite. It provides a complete and powerful spatial Database Management system with cross-platform and lightweight features, and supports fully mature spatial SQL functions. In addition, Spatialite uses R-Tree as Spatial Index to retrieve Spatial Data efficiently. SuperMap's new UDBX file engine makes full use of Spatialite's ability to efficiently manage Spatial Data and the characteristics of lightweight databases.
  There is no need to install and deploy the database system
  • when using the UDBX file engine. Because the Spatialite database simply corresponds to a single file and the file size is not limited, when using the UDBX file engine to create the Datasource, A UDBX File Database (*.udbx) will be created, which is essentially a database file. Compared with the existing UDB File Database, it has the characteristics of more openness and safer and more stable data operation.
  • In the UDBX File Database, you can Create a Dataset or import data from other sources. Dataset types supported by UDBX File Database include: point, line, surface, text, CAD, property sheet, 3D point/line/region, EPS composite point/line/region/text, grid, image, and Mosaic Dataset.
  • In addition, the UDBX file engine is more open and supports direct operation of Spatial Data imported into the Spatialite Spatial Data database by a third party, such as display and Edit Data. To apply, simply load the Spatialite Spatial Data library file (*.sqlite) to the desktop software as a File Database.
• Image Plug-in Engine supports read-only display of raster data in SuperMap, and currently supports Raster Data (BMP) in formats of BMP, JPEG, raw, tiff, sci, sit and ERDAS IMAGINE. JPEG is the general Raster Data type, raw, tiff is the remote sensing Image Data type, sci is the map pre-cache Picture File defined by SuperMap, and sit is the Raster Data type defined by SuperMap. Therefore, there are seven types of plug-in 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 Engine supports editing and saving of Vector File for general vector formats such as SHP, tab, DWG, etc.

File Database Engine Type
Type	Description
UDB	UDB type, for UDB Datasource.
UDBX	UDBX file engine, which can read, write, and manage Spatialite Spatial Data, for UDBX Datasource. Dataset types supported include: point, line, surface, text, CAD, property sheet, 3D point/line/region, EPS composite point/line/region/text, grid, image, Mosaic Dataset.
ImagePlugins	Image Plugins engine type, for common image formats such as BMP, JPG, tiff, and hypergraph custom image formats such as sit.
Vector File	Vector File engine class, for general vector formats such as SHP, tab, DWG, etc., supports editing and saving of Vector File.

Database-type Datasource

The Spatial Geometry Info and Attributes of Spatial Data are stored in the database. Offers SQLPlus, Oracle Plus, Oracle Spatial, PostgreSQL, PostGIS, Yukon, MySQL, POLARDBGanos, GaussDB 200, DMPlus, KingBase, More than ten Database-type Datasource functions such as HighGoDB, SHENTONG and Vastbase. It is generally used for Data Save with a large amount of data to facilitate data management and access. Support concurrent operations to facilitate modification and data synchronization. Users need to configure the relevant database environment and client locally when accessing the database.

The SuperMap Spatial Data database takes a large relational database as a storage container, manages and operates through SuperMap SDX +, and stores Spatial Data and attribute data into the large relational database. Such as Oracle, SQL Server, Sybase, and DM3. Spatial Data library types as shown in the following table.

Database-type Data source engine type
Type	Description
SQLPlus	SQL Server engine type, for SQL Server Datasource. There must be a client, and the Environment Variable is configured correctly.
OraclePlus	OraclePlus engine type. For Oracle Datasource, client must be installed.
OracleSpatial	Oracle Spatial engine type. For Oracle Spatial Datasource, client must be installed. Network Dataset is not supported.
MySQL	MySQL engine type. There is no need to install the client, but the Remote Service side must ensure that there are Access Permissions on the local machine.
PostgreSQL	PostgreSQL engine type. There is no need to install the client, and the Remote Service side must ensure that the local machine has Access Permissions.
PostGIS	PostgreSQL's Spatial Data extension PostGIS engine type. For PostGIS Data source, there is no need to install the client, and the Remote Service side must ensure that there are Access Permissions on the local machine.
POLARDBGanos	Alibaba Cloud's self-developed Ganos spatio-temporal engine provides a series of Data Types, functions, and stored procedures to efficiently store, index, query, and analyze spatial/spatio-temporal Data in the cloud-native relational distributed database PolarDB.
GaussDB 200	GaussDB 200 engine type. For GaussDB 200Datasource, there is no need to install the client, and the Remote Service side must ensure that the local machine has Access Permissions.
Yukon	Yukon engine type. Yukon fully supports Huawei ecosystem, from Huawei's own operating system, CPU to database, to achieve perfect adaptation. Support the extension and application of data models such as Model and geographic entity.
DMPlus	Type of DM engine. For DM Datasource, the client must be installed and the Environment Variable must be configured correctly.
ES	Elastics earch is a popular enterprise search engine. A natively accessible Elastics earch server is sufficient.
HighGoDB	High GoDB engine type. There is no need to install the client, and the Remote Service side must ensure that the local machine has Access Permissions.
KingBase	Kingbase engine type, for Kingbase Datasource, does not support multi-band data. There must be a client.
SHENGTONG	PostgreSQL's Spatial Data extension SHENGTONG engine type. For SHENGTONG Data source, there is no need to install the client, and the Remote Service side must ensure that there are Access Permissions on the local machine.
VastBase	Vastbase database is an enterprise-level relational database based on the open source openGauss kernel. In addition to the extreme performance of openGauss , Vastbase also adds a large number of Oracle compatibility features on the basis of the original functions, and carries out substantial security enhancements in accordance with the EAL4 + standard, while integrating enterprise-level functions in a series of professional application areas such as GIS/stream computing.
ArcSDE for Oracle	ArcSDE _ Oracle engine type, for ArcSDE for OracleDatasource.

SuperMap iObjects supports a variety of database engines (as shown in the following table). According to the requirements of common engines, the function entries that can be viewed on the desktop currently include the above 12 types of databases. The user can customize the function entry of Database-type Datasource through the Modify Configuration file parameter, and add or delete various database Datasources supported by SuperMap iObjects.

Support the customization of the function entry of the Database-type Datasource through the Modify Configuration file parameter. Config File SuperMap. Desktop. Startup. XML file in the package/Configuration/folder. Configure the parameter code Default Display as follows:

<parameters> < engine extraEngineType="" hiddenEngineTypes="" > </parameters >

• Where extraEngineType = "" is empty by default. At this time, the database entry is the default database Datasource entry on the desktop. To add a new database supported by SuperMap iObjects, you only need to fill in the enumeration value corresponding to the database. For example, if an Altibase engine type is added and the corresponding enumeration value is 2004, the Config File code is extraEngineType = "2004".
• Where, hidden EngineTypes = "" is empty by default. To delete the function entry of Data database Datasource, you only need to fill in the corresponding enumeration value of the database, for example, to delete OracleSpatial engine and SQLPlus engine types. If the corresponding enumeration values are 10 and 16 respectively, the Config File code can be written as hiddenEngineTypes = "10, 16".

Datasource engine types supported by SuperMap iObjects
Type	Enumeration value
SDE	4
OracleSpatial	10
SQLPlus	16
DMPlus	17
Kingdbase	19
MySQL	32
PostgreSQL	221
MongoDB	401
BeyonDB	2001
GBase	2002
HighGoDB	2003
Altibase	2004
KDB	2005
SRDB	2006
MYSQLPlus	2007
DRDS	2008
GBase8T	2009
Kadb	2010
ES	2011
PGGIS	2012
SQLSpatial	2013
SinoDB	2050
DataServer	2051
GreenPlum	2052
Esgyn	2053
Tibero	2014
ShenTong	2055
HWPostgreSQL	2056
Ganos	2057

Web Datasource

It is stored on a server on the network. When using this type of Datasource, the corresponding Datasource is obtained through the URL address. Such as OGC, iServerREST, MapWord, GoogleMaps, WordTerrain, OpenStreetMap, iServer DataStore, XYXZTile, Geovis, SIWEI earth and Kellett Data source belong to Web Data source.

Web engine can directly access the Web services provided by WFS, WMS, WCS, etc. This kind of engine is to process the Web server that conforms to the OGC standard on the network as the Datasource of SuperMap. Through it, the map and data published on the network can be completely combined with the map and data of SuperMap, and the application of WFS and WMS can be integrated into the technical system of SuperMap, which expands the application field of SuperMap data engine. The Web engine is read-only.

WebData source engine type
Type	Description
OGC	OGC engine type. For Web Datasource, currently supported types are WMS, WFS, WCS, and WMTS.
iServerRest	IServer Rest service engine type, Map Service published based on REST protocol.
MapWorld-Online	Sky Map Service connected with SuperMap Online.
MapWorld	The map service engine type refers to the Map Service released by the map.
GoogleMaps	Google Maps engine type. For Google eMap Service.
World Terrain	It is divided into California Map and Dark Top ographic Map, and is the global halo map Map Service published by SuperMap.
OpenStreetMaps	Also known as OSM engine type, it is a free and open source Map Service jointly created by the network public.
iServer DataStore	The iServer Data Store is the Data Service published by the hypergraph, and the Data Service serves GIS.
XYZTile	Is the Online MapXYZ Tile format, and the Online Map can be accessed via URL.
GEOVIS Earth	GEOVIS Earth provides three Map services: vector, image and terrain shading.
SIWEI earth	SIWEI earth provides global slice imaging services with unified fusion and mosaic processing.
Kellett	Kailide can provide national map product data by region and object.
Century Space Images	The Century Space Images provides Internet-based full-resolution online application services, and the shooting time is mainly in 2019 and 2020.

EMS Datasource

The data in EMS Datasource is saved in memory. It is a Temporary Data source and cannot be saved. The corresponding data engine is the memory engine. Some intermediate results of the analysis can be stored in the Datasource, which is conducive to improving the efficiency of the analysis. When the final data is obtained, it can be exported from EMS Datasource as Local Data.

Related topics

Create Datasource

Open Datasource