address

URI

<root_uri>/{version}/address[.<format>]

Supported methods

GET, HEAD

Parent resource

root

Child resources

geocoding

geodecoding

Introduction

address is the root resource of address matching service. By sending a GET request to address resource you can get all supported nterfaces of SuperMap iServer address matching service, which includes forward matching and reverse matching, ie., find the location by the input address name or find the address name by the input location.

Supported Methods:

Supported output formats: RJSON, JSON, HTML, XML.

Resource hierarchy

p class="myNormal">

HTTP request methods

Execute HTTP request on the following URI, here we take rjosn as the output format as an example. Where, supermapiserver is the server name.

http://supermapiserver:8090/iserver/services/address-school/restjsr/v1/address.rjson

GET request

Gets the list of child resources supported by address matching service.

Response structure

By performing a GET request on address resource, the response entity is a description set of the child resources, and the description structure of one single resource is as follows:

Field Type Description
name String Resource name.
path String Resource access path.
resourceConfigID String The configuration item ID of the resource.
resourceType String Resource type.
supportedMediaTypes String[] The media-type of the supported representation.

Response example

The returned rjson format representation after executing the GET request on the address resource:

[

  {

    "name": "geocoding",

    "path": "http://192.168.17.180:8099/iserver/services/addressmatch-addressmatch/restjsr/v1/address/geocoding",

    "resourceConfigID": null,

    "resourceType": null,

    "supportedMediaTypes": null

  },

  {

    "name": "geodecoding",

    "path": "http://192.168.17.180:8099/iserver/services/addressmatch-addressmatch/restjsr/v1/address/geodecoding",

    "resourceConfigID": null,

    "resourceType": null,

    "supportedMediaTypes": null

  }

]

HEAD request

Returns the same HTTP response header as the GET request, but no response entity, which can be used to retrieve the meta data contained in response message header without having to transmit the entire response content. Meta data information includes media type, character coding, compression coding, entity content length, etc.

HEAD request is used to determine whether the address resource exists, or if the client has the authority to access it. By executing an HEAD request with a .<format> URI, you can quickly determine whether the address  resource supports the <format> representation.

 

See