<datas_uri>/{dataName}[.<format>]
<datas_uri>/{dataIndex}[.<format>]
clearCache, modelIndex, config, tileDataVersion, tileData
The data resource is a 3D data resource representing a specific 3D dataset (i.e., dataName). Currently, 3D data in SuperMap iServer include: vector data, image data, terrain data, 3D model data, and KML data. tileData resource can be used to retrieve a certain tile of the cached files of all the above data except for KML data, for which the dataset itself is retrieved by tileData resource.
The modelIndex child resource is a special child resource for cached 3D model data. It can be used to retrieve the model index.
Note: The concepts of index, configuration file, and data version are not applicable for KML data. Therefore the tileDataVersionchild resource is not meaningful to KML data. The config child resource can only retrieve the KML dataset itself.
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. In the URI: supermapiserver is the name of the server; and OlympicGreen is the name of the 3D dataset, i.e., dataName.
http://supermapiserver:8090/iserver/services/3D-sample/rest/realspace/datas/OlympicGreen.rjson
Gets the representation of a 3D dataset.
| Field | Type | Definition |
| _cache | boolean | [Optional parameters] Whether to use cache, the default is True. False means close all the cache. |
After a GET request is performed on the data resource, the representation of the 3D dataset is returned with the following structure (the resource representation is included in the entity body of the response message):
| Name | Type | Description |
| dataName | String | The name of the 3D dataset. |
| dataType | realspaceDataType | The type of the 3D dataset. |
Performing a GET request on the example data resource returns the representation of 3D dataset OlympicGreen, as shown below:
{
"dataName": "OlympicGreen",
"dataType": "VECTOR"
}
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 dataset resource exists, or if the data resource can be accessed by clients. It can also determine if the data resource supports an output format <format> if performed on a URI with .<format> included.