<root_uri>/networkanalyst[.<format>]
With SuperMap iServer launched, the network analysis service can be accessed through the default URI for the corresponding REST service: http://<server>:8090/iserver/services/transportationanalyst-sample/rest/networkanalyst.
The networkanalyst resource is the root resource of transportation analysis functions. A GET request can be performed on the networkanalyst resource to retrieve a set of names of the network data for transportation analysis from the server.
Supported methods:
Supported output formats: rjson, json, html, xml, jsonp.
Below is an example of performing a HTTP request on a URI with rjson as the output format. supermapiserver in the URI is the name of the server.
http://supermapiserver:8090/iserver/services/analyst-sample/rest/networkanalyst.rjson
Gets the names of all the network data that can be used in transportation analysis.
None.
After a GET request is performed on the networkanalyst resource, the entity body of the response message is a set of network datasets. The representation of each individual dataset has the following structure:
Field | Type | Description |
name | String | The name of the network data. |
path | String | The path for accessing the network data. |
resourceConfigID | String | The ID of the resource configuration. |
resourceType | String | The type of the resource. |
supportedMediaTypes | String[] | Supported media types for representation. |
Below is the returned description of the resource representation in rjson format after performing a GET request on the networkanalyst resource:
[{
"name": "RoadNet@Changchun",
"path": "http://localhost:8090/iserver/services/transportationanalyst-sample/rest/networkanalyst/RoadNet@Changchun",
"resourceConfigID": "networkDataName",
"resourceType": "StaticResource",
"supportedMediaTypes": [
"application/xml",
"text/xml",
"application/json",
"application/rjson",
"text/html",
"application/jsonp"
]
}]
Returns the same HTTP response header as GET does, but no response entity is included. HEAD request can be used to get metadata from the response message header without transporting the entire response content. Metadata includes information about the media type, character encoding, compression encoding, the length of the entity content, etc.
HEAD request can be used to check if the networkanalyst resource exists and can be accessed by clients. It can also determine if the networkanalyst resource supports an output format <format> if performed on a URI with .<format> included.