A datasource is a collection for storing various types of datasets (e.g., point, line, polygon data, TIN, GRID, Network, etc.). A datasource may contain one or multiple datasets of different types, which can be vector datasets or raster datasets. All data are stored in datasources rather than workspaces. The physical storage of datasources can be file-based or database-based, with the key difference lying in the type of data engine used.
SuperMap SDX+ is the spatial database engine in SuperMap GIS platform, providing spatial data access capabilities for all SuperMap GIS products. It implements storage, indexing, retrieval, 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 as file databases, database datasources, and web datasources, corresponding to file engines, database engines, and web engines respectively. Additionally, the EMS datasource provided in applications uses file engines as temporary data sources. Different data engines support different dataset types. For detailed supported dataset types, please refer to SDX+ Supported Dataset Types.
File Database
Stores spatial data and attribute data directly in files, supporting UDB and UDBX file databases.
File databases offer faster map display for small data volumes and convenient data migration.
File databases support four types of file engines: SuperMap's custom UDB engine (read-write), UDBX engine (read-write), image plugin engine (direct access to image data), and vector file engine (direct access to external vector files).
- UDB Engine, SuperMap Objects' custom file-based spatial data engine using traditional file+database hybrid storage. A UDB project consists of two files: the .udb file uses OLE compound document technology to store spatial data; the .udd file uses Access MDB format for attribute data. UDB's compound document technology enables storing multiple datasets in a single project, differing from ArcInfo Coverage and MapInfo Table approaches. Primarily designed for medium/small systems and desktop applications to enhance efficiency.
- UDBX Engine reads/writes/manages Spatialite spatial data. Spatialite is an open-source library extending SQLite with complete spatial database management capabilities, featuring cross-platform support, lightweight design, and full spatial SQL support. It uses R-Tree for spatial indexing.
- UDBX engine requires no database installation. Each Spatialite database corresponds to a single *.udbx file without size limits, offering more open and stable operations compared to UDB.
- Supported dataset types in UDBX: point, line, polygon, text, CAD, attribute table, 3D point/line/region, EPS composite point/line/region/text, raster, image, mosaic dataset.
- Directly supports third-party spatial data in Spatialite databases (e.g., display and editing) by loading *.sqlite files as file databases.
- Image Plugin Engine provides read-only display for raster formats: BMP, JPEG, RAW, TIFF, SCI, SIT, and ERDAS IMAGINE. Includes seven types: BMP, JPG, RAW, TIFF, SCI, SIT, and ERDAS Imagine read-only engines.
- Vector File Engine supports editing and saving common vector formats like SHP, TAB, DWG.
| File Database Engine Types | |
| Type | Description |
| UDB | For UDB datasources |
| UDBX | Manages Spatialite spatial data in UDBX format. Supported datasets include: point, line, polygon, text, CAD, attribute table, 3D point/line/region, EPS composite features, raster, image, mosaic dataset. |
| ImagePlugins | Supports common image formats (BMP, JPG, TIFF) and SuperMap's SIT format. |
| Vector File | Supports editing common vector formats (SHP, TAB, DWG). |
Database Datasource
Stores spatial geometries and attributes in databases. Supports SQLPlus, Oracle Plus, Oracle Spatial, PostgreSQL, PostGIS, Yukon, MySQL, POLARDBGanos, GaussDB 200, DMPlus, KingBase, HighGoDB, SHENTONG, Vastbase, etc. Suitable for large-scale data storage with concurrent access. Requires local database environment configuration.
SuperMap spatial databases utilize RDBMS (Oracle, SQL Server, etc.) through SDX+ for integrated storage. Supported types include:
| Database Datasource Engine Types | |
| Type | Description |
| SQLPlus | For SQL Server. Requires client and correct environment variables. |
| OraclePlus | For Oracle. Client installation required. |
| OracleSpatial | For Oracle Spatial. Client required. Network datasets unsupported. |
| MySQL | No client needed. Requires remote access permissions. |
| PostgreSQL | No client required. Remote access permissions needed. |
| PostGIS | PostgreSQL spatial extension. Remote access permissions required. |
| POLARDBGanos | Alibaba Cloud's Ganos spatiotemporal engine for PolarDB. |
| GaussDB 200 | For GaussDB 200. Remote access permissions required. |
| Yukon | Supports Huawei ecosystem with model and geospatial entity extensions. |
| DMPlus | For Dameng (DM) databases. Client and environment setup required. |
| DMSpatial | Dameng spatial engine. Client and environment setup required. |
| ES | Elasticsearch engine. Requires accessible Elasticsearch server. |
| HighGoDB | Remote access permissions required. |
| KingBase | For Kingbase. Client required. Multiband data unsupported. |
| SHENGTONG | PostgreSQL-based spatial extension. Remote access permissions needed. |
| Vastbase | Enterprise RDBMS based on openGauss with Oracle compatibility and enhanced security. |
| ArcSDE for Oracle | Read-only access for ArcSDE Oracle datasources. |
| XUGU DB | Lightweight distributed database. No client required. |
Warning:SuperMap SDX+ supports maximum dataset records up to 231-1 (2,147,483,647). Exceeding this limit causes overflow.
SuperMap iObjects supports multiple database engines. Users can customize database entries via configuration file (Desktop.Parameter.xml):
<engine extraEngineType="" hiddenEngineTypes=""/>
- extraEngineType="": Add supported engines using enumeration values (e.g., "2002" for GBase).
- hiddenEngineTypes="": Remove entries using enumeration values (e.g., "10,16" removes OracleSpatial and SQLPlus).
| SuperMap iObjects Supported Engine Types | |
| 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 remote servers accessed via URLs. Includes OGC, iServerREST, MapWorld, GoogleMaps, WorldTerrain, OpenStreetMap, iServer DataStore, XYZTile, geovis, siwei earth, and Kailide datasources.
Web engines provide read-only access to OGC services (WFS, WMS, WCS), integrating web-published data with SuperMap.
| Web Datasource Engine Types | |
| Type | Description |
| OGC | Supports WMS, WFS, WCS, WMTS services. |
| iServerRest | REST-based map services from iServer. |
| MapWorld-Online | SuperMap Online map services. |
| MapWorld | Tianditu map services. |
| GoogleMaps | Google Maps electronic services. |
| World Terrain | Global shaded relief maps (topographic/dark variants). |
| OpenStreetMaps | Community-driven open-source map service. |
| iServer DataStore | SuperMap's GIS data service. |
| XYZTile | Online XYZ tile format access. |
| geovis earth | Vector, imagery, terrain services. |
| siwei earth | Global mosaic imagery service. |
| Kailide | Regional map data provider. |
| Century Space Images | Online full-resolution imagery (mainly 2019-2020). |
Note:OpenStreetMap may be inaccessible in mainland China. Contact technical support at 400-8900-866 for details.
EMS Datasource
In-memory temporary storage for analysis intermediates. Uses memory engine, not persistable. Export results to local storage when needed.
Related Topics