<root_uri>/realspace[.<format>]
With SuperMap iServer launched, the 3D service can be accessed through the default URI for the corresponding REST service: http://<server>:8090/iserver/services/3D-sample/rest/realspace.
scenes、datas、symbols、allDataConfigs
3D resource is the root node of the 3D service in SuperMap iServer services. A 3D service module includes three components: 3D scene, 3D dataset and symbol resource, which respecitively provide information and operations of 3D scene, 3D data and the 2D symbols and 3D symbols used in the data.
Furthermore,3D resource also includes the allDataConfigs resource which can get all the data's configuration files, that is, the data config files for all the 3D layers.
SuperMap iServer supports real-time update of published 3D workspaces. That is, if the published 3D workspace is changed externally, it can be reflected in the published services in time.
Supported methods
Supported output formats: RJSONJSON, JSONP, HTML, XML.
Below is an example of performing an HTTP request on a URI with rjson as the output format
http://supermapiserver:8090/iserver/services/realspace-sample/rest/realspace.rjson
Get the representation of the realspace resource, providing the entry to the 3D scenes, the 3D datasets and symbol resources.
| Field | Type | Definition |
| _cache | boolean | [Optional parameters] Whether to use cache, the default is True. False means close all the cache. |
Performing a GET request on the realspace resource, a response message with an entity body which is a set of resource descriptions will be returned. Each resource description has the following structure:
| Name | Type | Description |
| name | String | The resource name. |
| path | String | The access path of the resource. |
| resourceConfigID | String | ID of the resource configuration. |
| resourceType | ResourceType | Resource type. |
| supportedMediaTypes | String | Supported media types for descriptions. |
Performing a GET request on the realspace resource, the following resource representation in rjson format will be returned:
[
{
"name": "datas",
"path": "http://localhost:8090/iserver/services/3D-sample/rest/realspace/datas",
"resourceConfigID": "map3DDatasets",
"resourceType": "CatalogList",
"supportedMediaTypes": [
"application/xml",
"text/xml",
"application/json",
"application/rjson",
"text/html",
"application/jsonp",
"application/x-java-serialized-object"
]
},
{
"name": "scenes",
"path": "http://localhost:8090/iserver/services/3D-sample/rest/realspace/scenes",
"resourceConfigID": "scenes",
"resourceType": "CatalogList",
"supportedMediaTypes": [
"application/xml",
"text/xml",
"application/json",
"application/rjson",
"text/html",
"application/jsonp",
"application/x-java-serialized-object"
]
},
{
"name": "symbols",
"path": "http://localhost:8090/iserver/services/3D-sample/rest/realspace/symbols",
"resourceConfigID": "symbols",
"resourceType": "StaticResource",
"supportedMediaTypes": [
"application/xml",
"text/xml",
"application/json",
"application/rjson",
"text/html",
"application/jsonp",
"application/x-java-serialized-object"
]
}
]
Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. The meta-information includes the media-type, content-encoding, transfer-encoding, content-length, etc.
HEAD request can be used to check if the 3D resource exists, or if the resource can be accessed by clients. It can also determine if the 3D resource supports an output format <format> if performing on a URI with .<format> included.