modelIndex


URI

/modelIndex[.<format>]

Supported methods

GET, HEAD

Parent resource

data

Introduction

The modelIndex resource represents the index file of cached 3D model data, thus only exists when the 3D dataset ({dataName}) is cached model data. The model index file of a specific cached 3D model dataset ({dataName}) can be retrieved by performing a GET request on the modelIndex resource. The only output format supported by this resource is the index type (the index file). A model index file is always returned even when no output format is specified.

Supported methods

Supported output format: index

GIS Services Resource Hierarchy

root realspace datas data modelindex

HTTP request methods

Below is an example of performing an HTTP request on a URI with index as the output format. In the URI: supermapiserver is the name of the server; OlympicGreen is the name of the cached 3D model dataset, i.e., {dataName}.

http://supermapiserver:8090/iserver/services/3D-sample/rest/realspace/datas/OlympicGreen/modelIndex.index

GET Request

Gets the index file of a cached 3D model dataset ({dataName}).

Request parameters

Field Type Definition
_cache boolean [Optional parameters]
Whether to use cache, the default is True. False means close all the cache.

Response structure

Performing a GET request on the modelIndex resource returns a model index file (*.index).

Example usage

Below is an example of performing a GET request on an example modelIndex resource with the parameters included in the URI:

http://supermapiserver:8090/iserver/services/3D-sample/rest/realspace/datas/OlympicGreen/modelIndex.index

The index file (modelIndex.index) of the cached model dataset OlympicGreen is returned.

HEAD Request

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 modelIndex resource exists, or if the resource can be accessed by clients. It can also determine if the modelIndex resource supports an output format <format> if performed on a URI with .<format> included.

See