Finds the distance any given point is, in metres or miles, from the locations in a specified dataset. The use of this service requires additional setup of a dataset containing relevant locations you wish to be compared.
For the best results, a full postcode should be supplied. However, the service will also accept partial postcodes or other parts of an address.
To connect to this service you'll need to use one of these endpoints:
Protocol | URL |
---|---|
JSON |
JSON
https://webservices.data-8.co.uk/Location/FindMyNearest.json |
OPEN API |
OPEN API
https://webservices.data-8.co.uk/swagger/Location/swagger.json |
SOAP |
SOAP
https://webservices.data-8.co.uk/location.asmx |
Name | Description |
---|---|
username | username
See the available authentication methods. If you are using username & password authentication, specify the username to authenticate as. If you are using API Key authentication and you are not using the JSON, Javascript or ADO APIs, use your API Key here with the prefix |
password | password
If you are using username & password authentication, specify the password to use for authentication. Otherwise leave this blank. |
licence | licence
The licence type under which you are accessing the service. If you are not sure which value to pick, please contact your account manager |
point | point
The point to use as the origin of the find my nearest search. This can be either a full postcode or a partial address. Using a full postcode will ensure the most accurate results are achieved. |
dataset | dataset
The name of the predefined dataset of locations to find the nearest one from. |
options | options
An array of options that control further details of how this method operates. See the |
option
parameter. Each option is specified as a key/value pair.
The list of available names is shown below, along with a description of the allowable values for that name.
Name | Description |
---|---|
Common Options | |
ApplicationName |
ApplicationName
Gives the name of the calling application - used to break down usage by application in the usage reports on the dashboard.
|
Service Specific Options | |
DatumEPSG | DatumEPSG
The EPSG code of the datum to use when converting the original OS grid coordinates to latitude and longitude |
MaxMatches | MaxMatches
The number of addresses to limit the response to. |
Name | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Status | Status
Indicates whether the method call was successful, or if some error occurred. If the | ||||||||
Distances | Distances
The cleansed address of the initial point stored in the Each
|
Each request to this method consumes 1 Location credit and 1 Find My Nearest credit.
Request Format
{ "licence": "WebClick", "point": "CH2 4NE", "dataset": "Demo", "options": { "DatumEPSG": 4326, "MaxMatches": 5 } }
Response Format
{ "Status": { "Success": true, "CreditsRemaining": 1000 }, "Distances": null }
Depending on your chosen authentication method you will need to modify this request slightly:
API Key
https://webservices.data-8.co.uk/Location/FindMyNearest.json?key=your-api-key
and do NOT include the
username
or password
properties in the request JSON document.
Username and Password
https://webservices.data-8.co.uk/Location/FindMyNearest.json
and include
username
and password
properties in the request JSON document.Do not use for client-side requests!
JWT Token
https://webservices.data-8.co.uk/Location/FindMyNearest.json
Include the JWT token in the request headers as:
Authorization: Bearer your-jwt-token
Parameter | Value |
---|---|
Parameters | |
licence | licence
|
point | point
|
dataset | dataset
|
Common Options | |
ApplicationName |
ApplicationName
|
Service-Specific Options | |
DatumEPSG |
DatumEPSG |
MaxMatches |
MaxMatches |
Credits Remaining Today: 10 |