Parameters for configuring 3D service provider |
SuperMap iServer supports the following types of 3D providers:
UGC 3D service provider encapsulates the GIS functionality from the SuperMap workspaces.
Table 1. Configuration parameters of UGC 3D service provider
| Parameter name | Description | ||
General settings |
Service provider name | [Required parameter] Uniquely identifies this service provider. The prefix of the default name is "3DProvider-". | |
Basic settings |
Workspace type | [Required parameter] The types of workspaces are divided into file type and database type (SQL Server, Oracle workspace). The SQL Server workspace indicates the workspace is stored in the SQL Server database. The Oracle workspace indicates the workspace is stored in the Oracle database. The parameter settings of the database workspace is shown in table 2. |
|
| Workspace path | Remote file system | Required while the workspace is of the file type.
Please refer to Table
2 Parameter of database workspace information setttings if
the database is of the database type. While the server is not
at local, select "Remote browse" to use files on the
server or local files uploaded to the server; while the server
is at local, select "Local browse" . The SuperMap workspaces (*.smwu, *.sxwu, *.smw, *.sxw) store the GIS data information. |
|
| Local file system | |||
Password |
The password of the workspace. When there is no password for the workspace, you can have it blank or enter any characters. | ||
3D cache directory |
[Required parameter] As the data volume of 3D services is generally huge, caches files will be dynamically generated after a request operation on a 3D service.Copyright©2000-2012 SuperMap Software Co., Ltd. All Rights Reserved. | ||
REST 3D service provider uses REST 3D service to realize the spatial analysis.
Table 2. Configuration parameters of REST 3D service provider
| Parameter name | Description | ||
| General settings | Service provider name | [Required parameter] Uniquely identifies this service provider. The prefix of the default name is "rest3DProvider-". | |
| Basic settings | REST service URL | REST 3D service address, pointing at the root resource path, such as http://localhost:8090/iserver/services/3D-sample/rest. | |
| Advanced settings | Token or API-Key | When enabling the security mechanism, visiting the protected REST resource needs to provide Token or API-Key. | |
| Enable caching | Whether to use caches. Default is true. After opening the REST cache, the REST request to the resource will be cached locally. For the later same requests will be read directly in the cache. | ||
| Cache policy | Maximum capacity of disk | The maximum capacity of the disk. Unit is MB, and default is 2048MB. | |
| Survival time | Sets the upper limit for the survival of the cache, beginning at the creation of the record. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival. | ||
| Idle time | Sets the upper limit for the idle time of the cache, beginning at the last visit. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival. | ||
3D service provider encapsulates the 3D related functions get from MongoDB distributed storage tiles.
Table 3. Configuration parameters of MongoDB 3D service provider
| Parameter name | Description | |
| General settings | Service provider name | [Required parameter] Uniquely identifies this service provider. The prefix of the default name is "mongoDB3DProvider-". |
| Basic settings | distributed tile repository | Select the existing distributed tile repository. There is no need to set the service URl of MongoDB. |
| Service URL | [Required parameter] The service URL of MongoDB |
|
| Add Replication Set | Check this to add the copy sets. Multiple copy set can improve the tile performance of speaking, reading and writing data, and data security. | |
Database |
Used to store the tiles of the map services. | |
User name |
The name of the user who have the permission to access dababase. | |
| Password | The password of the user. | |
| The published 3D layers | If there are multiple 3D layer tiles saved in the MongoDB server, it needs to select the 3D tiles to publish. You can also publish all 3D tiles. |