densityJob

URI

<density_uri>/{jobID}[.<format>]

Supported methods

Parent resource

Introduction

densityJob indicates a denisty analysis job. Check the detail configuration information of denisty analysis job through sending GET request to denistyJob, such as: analysis range, address of source data, and so on. The densityJob resource can be got by ID {jobID}.

Supported Methods:

GET: Gets information of a denisty analysis job.
HEAD: Checks whether the densityJob resource exists or whether it has permission to access the resource.

Supported output formats: rjson, json, html, xml.

Resource hierarchy

HTTP request methods

Implement the HTTP request on the following URI, where supermapiserver is the server name, with rjson being the output format.

http://supermapiserver:8090/iserver/services/distributedanalyst/rest/v1/jobs/spatialanalyst/density/{jobID}.rjson

GET request

Gets information of a denisty analysis job.

Response structure

Execute a GET request on the densityJob resource. The representation structure for the returned resource is like this:

Field	Type	Description
id	String	Application ID.
state	Jobstate	The status of the task. Including execution status, start time, time consuming, and so on.
setting	JobSetting	Lists the detail information of current density analysis task.

Response example

Sending GET request to densityJob resource http://supermapiserver:8090/iserver/services/distributedanalyst/rest/v1/jobs/spatialanalyst/density/2d47e0bf_3629_4810_93cb_dc1c68630d08.rjson, the description for the returned rjson is:

{

"id": "2d47e0bf_3629_4810_93cb_dc1c68630d08",

"setting": {

"DEFAULT_MASTER_ADRESS": "local[*] ",

"analyst": {

"fields": "",

"meshType": "0",

"method": "0",

"query": "",

"radius": "0.01",

"resolution": "1000"

"appName": "kernelDensity",

"args": [

"--input",

"file:/E:/spark/newyork_taxi_2013_01_14k_new.csv",

"--separator",

",",

"--pointIndex",

"10",

"--resolution",

"1000",

"--radius",

"0.01",

"--method",

"0",

"--meshType",

"0",

"--output",

"E:\\supermapiserver\\supermap_iserver_*_win64_deploy\\webapps\\iserver\\processingResultData\\KernelDensity\\udbs\\ada2f56f-9c71-476d-8bb6-9056c4d73dbc",

"--datasetName",

"analystResult"

"contextSetting": null,

"input": {

"datasetInfo": {

"name": "dcsv_newyork_taxi_2013_01_14k_new",

"separator": ",",

"type": "CSV",

"url": "E:\\spark\\newyork_taxi_2013_01_14k_new.csv",

"xIndex": 10,

"yIndex": 11

"datasetName": "dcsv_newyork_taxi_2013_01_14k_new"

"mainClass": "com.supermap.bsp.main.DensityAnalystMain",

"output": {

"cacheName": null,

"cacheType": null,

"datasetName": "analystResult",

"outputPath": "E:\\supermap_iserver_900_14910_2648_win64_deploy\\supermap_iserver_900_14910_2648_win64_deploy\\webapps\\iserver\\processingResultData\\KernelDensity\\udbs\\ada2f56f-9c71-476d-8bb6-9056c4d73dbc"

"serviceInfo": null,

"serviceRoot": "http://localhost:8090/iserver/services/"

"state": {

"elapsedTime": 0,

"endState": false,

"endTime": 0,

"errorMsg": null,

"errorStackTrace": null,

"publisherelapsedTime": 0,

"runState": "RUNNING",

"startTime": 1494832059228

}

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