iServer Data Preparation

Feedback


SuperMap iServer supports to publish various kinds of data as the GIS services. The datasources of SuperMap iServer include: SuperMap workspaces (*.smw, *.sxw, *.smwu, *.sxwu), remote WMS 1.1.1 services, remote WFS 1.0.0 services, remote iServer REST services.

Workspace is the users' working environment, which stores the organized relations of all the datasources and maps in a project (in the same transaction process). Generally speaking, users' data is organized in the form of SuperMap workspace. SuperMap iServer suggests users to manage data using SuperMap UGC 6.x workspace (*.smwu/*.sxwu), and to store data using Oracle Plus datasource, SQL Server Plus datasource, Mongodb datasource or UDB datasource (For details please see: SuperMap iDesktop 11i(2022) online help).

Table 1. Datasources supported by SuperMap iServer

Datasource type Datasource
File datasource UDB datasource (*.udb), SIT image data (*.sit), TIFF image data (*.tif, *.tiff), bitmap files (*.bmp), JPG files (*.jpg, *.jpeg), PNG files (*.png), GIF files (*.gif).
Database datasource Oracle Plus datasource, SQL Server Plus datasource, Mongodb datasource.

 

Note:

  1. UDB datasource, Oracle Plus datasource and SQl Server Plus datasource support to import data of other types, such as AutoCAD DXF files (*.dxf), AutoCAD Drawing files (*.dwg), ArcInfo GRID files (*.grd), ArcView Shape files (*.shp), MapInfo TAB files (*.tab), bitmap files (*.bmp), JPG files (*.jpg, *.jpeg), PNG files (*.png), GIF files (*.gif), Erdas Image files (*.img), RAW files (*.raw), SIT image data (*.sit), TIFF image data (*.tif, *.tiff), etc. Therefore, SuperMap iServer can indirectly publish the above data as GIS services.
  2. SuperMap iServer dose not support to publish "*.sdb" data which is a  SuperMap old-format data. If you want to use SuperMap iServer to publish the *.sdb data, you can convert the data into UDB data or database datasource in the SuperMap iDesktop. The steps are as follows:

(1). Open the existing SDB datasource, and set its name as data_ori.

(2). Create a new Oracle Plus datasource, and set its name as data (take Oracle Plus datasource for example).

(3). Select all the datasets in the SDB datasource, and drag them to the Oracle Plus datasource with the mouse.

(4). Save the datasource and workspace.

Note: In order to guarantee that the maps originally made using SDB datasource are valid, you can first rename the original SDB datasource and then set the name of the new Oracle Plus datasource (take Oracle Plus datasource for example) as same as the name of the original SDB datasource.

  1. The file workspace of Mongodb datasource type only supports to be published as map services and data services. When perform queryResults and featureResults query, you need to pay attention to following points:

 (1). Supported dataset types or query: point, line, region, text.

 (2). Supported field types for query: numeric, string, date type.

 (3). Support query conditions: >, <, =, or, and.

Note:  1. When querying, field names must be case sensitive and do not support field expression.

           2. When performing spatial query, only these query modes are supported: contain, intersection, overlay, separation .

2D Data Preparation

The preparation of 2D data is generally implemented as follows:

1. Open SuperMap iDesktop.

2. Create a new datasource or open an existing datasource.

3. Edit datasets. Right-clicks on the datasource, and then the menu of new datasets, import datasets and delete datasets will appear. The original data can be edited in the SuperMap iDesktop 11i(2022).

4. Make maps. Make maps according to the requirements, and save the maps.

5. Save the workspace.

Where, the method of creating a datasource is as follows:

Find the group "datasource" in the tab "start" in SuperMap iDesktop 11i(2022) and click "new", or right-clicks on "datasource" in "workspace manager" and select in the pop-up menu. In this way, a datasource can be created.

Select "new file datasource", select "save as type" as "SuperMap UDB file (*.UDB)" and choose the location to save, then a UDB datasource is created. Note: SuperMap iServer does not support SDB datasource.

First prepare an Oracle database, and build a table space and configure "local Net service name".

In iDesktop, select "new Oracle Plus datasource" and input instance name (Oracle client configuration and connection name), username (the username corresponding to Oracle), password and datasource alias in the dialog box. Then, an Oracle Plus datasource is created.

First prepare a SQL Server database. Then, in SuperMap iDesktop 11i(2022), select "new SQL Server Plus datasource" and input server name, database name, username, password and datasource alias in the dialog box. Then, a SQL Server Plus datasource is created.

 

After the data preparation, the quick publishing of GIS services can be implemented through the iServer Manager.

 

3D Data Preparation

The 3D services published by SuperMap iServer are based on the 3D scene in the workspace. We normally use SuperMap iDesktop to make data.

1. Open SuperMap iDesktop.

2. Create a new 3D scene

Click "scene" in the tab "start" and select "new scene window", or right-click "scene" in the workspace manager and select "new scene", then a blank 3D scene can be created.

After creating a new 3D scene, it can be seen in the layer manager that the layers in the 3D scene are divided into three classes to be managed by SuperMap U series products: screen layer, general layer (3D layer) and terrain layer. For details of the three classes of layers, please see: 3D topics.

3. Add data in the 3D scene

At present, SuperMap iServer not only supports to publish the 3D scene generated by cache files, but also supports to dynamically publish the 3D scene created using SuperMap vector data, map data, terrain data and image data.

Note: SuperMap iServer only supports model index of SCM format and does not support model index of KML format at present.

After the data preparation, the quick publishing of GIS services can be implemented through the iServer Manager.