URI
<root_uri>[.<format>]
After SuperMap iServer starts, the default REST service access URI of the map service (Vectortiles Service V2) module is: http://<server>:8090/iserver/services/{vectorMapComponentName}/restjsr.
Supported Methods
Parent Resource
Child Resources
datas, styles, tiles, fonts, sprites, serverInfo, getMap, pickup
Introduction
The vectorMap resource is the root resource of all Vectortiles Service V2 resources. Its child resources provide the ability to obtain raw dataset information, style information, vector tiles and related sprites and fonts, as well as capabilities for raster tile retrieval and feature querying. It supports outputting vector tiles based on the MVT standard expressed by MapboxGL, and also supports raster tile output based on Leaflet. The vector tiles V2 service only supports publishing through PostGIS service.
Supported Methods:
- GET: Retrieves its child resources, i.e., the address information of datas, styles, tiles, fonts, sprites, serverInfo, getMap, pickup and other resources.
- HEAD: Checks whether the vectorMap resource exists and whether the client has permission to access it.
Supported Representation Formats: RJSON, JSON, HTML, XML, JSONP.
HTTP Request Method
Perform an HTTP request on the following URI, taking the rjson output format as an example. Here, supermapiserver is the server name.
http://supermapiserver:8090/iserver/services/vectorMap-DLTB-public/restjsr.rjson
GET Request
Retrieves its child resources.
Response Structure
When a GET request is performed on the vectorMap resource, the response message's entity body contains a resource description set, where the structure of a single resource description is as follows:
| Field | Type | Description |
| name | String | The name of the child resource. |
| path | String | The access path of the child resource. |
| resourceConfigID | String | The ID of the child resource configuration item. |
| resourceType | String | The resource type. |
| supportedMediaTypes | List<MediaType> | The representation formats supported by the resource. |
Example
Perform a GET request on the vectorMap resource, and the returned resource description in rjson format is as follows:
[
{
"resourceConfigID": "datas",
"supportedMediaTypes": null,
"path": "http://localhost:8090/iserver/services/vectorMap-DLTB-public/restjsr/v2/datas",
"name": "datas",
"resourceType": null
},
{
"resourceConfigID": "styles",
"supportedMediaTypes": null,
"path": "http://localhost:8090/iserver/services/vectorMap-DLTB-public/restjsr/v2/styles",
"name": "styles",
"resourceType": null
}
]
HEAD Request
Returns the same HTTP response headers as a GET request, but without a response entity. This allows obtaining metadata information contained in the response message headers without transferring the entire response content. Metadata information includes media type, character encoding, compression encoding, entity content length, etc.
A HEAD request can be used to determine whether the vectorMap resource exists or whether the client has permission to access it. By performing a HEAD request on a URI with .<format> appended, you can also quickly determine whether the vectorMap resource supports the <format> representation.
See Also
- root, datas, styles, tiles, fonts, sprites, serverInfo, getMap, pickup
- Building REST Requests on the Client
- Status Code List and Descriptions
- Introduction to Representation Formats
- GIS Service Resource Hierarchy