summaryAttributesJob

URI

<summaryAttributes_uri>/{JobID}[.<format>]

Supported methods

GET, HEAD

Parent resource

summaryAttributes

Introduction

summaryAttributesJob resource represents a summary attributes analysis job. By sending a GET request to summaryAttributesJob, you can get a summary attributes job's detailed configuration information, which can be retrieved by {jobID}.

Supported Methods:

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

Resource hierarchy

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/distributedanalyst/rest/v1/jobs/spatialanalyst/summaryattributes/{jobID}.rjson

GET request

Gets a summary attributes job's detailed configuration information.

Response structure  

After executing a GET request on the resource, the response fields are as follows:

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 detailed information of the current summary attributes job.

Response example

Execute a GET request on summaryAttributesJob resource: http://supermapiserver:8090/iserver/services/distributedanalyst/rest/v1/jobs/spatialanalyst/summaryattributes/d2146eb4_69b8_402b_bd90_268543087d7f.rjson, then the returned result in rjson format is as follows:

{

    "id": "d2146eb4_69b8_402b_bd90_268543087d7f",

    "setting": {

        "DEFAULT_MASTER_ADRESS": "local[*] ",

        "analyst": {

            "attributeField": "",

            "groupField": "",

            "resultField": null,

            "statisticModes": ""

        },

        "appName": "SummaryAttributes",

        "args": [

            "--input",

            "{\"sliceNum\":20,\"type\":\"udb\",\"info\":[{\"server\":\"F:\\\\1.package\\\\20171014\\\\supermap_iserver_901_15413_4668_win64_zip\\\\samples\\\\data\\\\ProcessingData\\\\processing.udb\",\"datasetNames\":[\"newyorkZone_R\"]}]}",

            "--output",

            "{\"server\":\"192.168.120.21\",\"password\":\"supermap\",\"database\":\"supermap2\",\"datasetName\":\"analystResult_1302299475\",\"blockingWrite\":null,\"type\":\"pg\",\"user\":\"postgres\"}"

        ],

        "contextSetting": null,

        "input": {

            "datasetInfo": {

                "available": true,

                "bounds": "Left=-74.25551784310493,Bottom=40.496084221255856,Right=-73.70014827248451,Top=40.91538866049913",

                "datasetName": "newyorkZone_R",

                "datasetType": "REGION",

                "epsgCode": 4326,

                "name": "samples_processing_newyorkZone_R",

                "readOnly": false,

                "type": "UDB",

                "url": "../../samples/data/ProcessingData/processing.udb"

            },

            "datasetName": "samples_processing_newyorkZone_R",

            "numSlices": 0

        },

        "mainClass": "com.supermap.bdt.main.SummaryAttributesMain",

        "output": {

            "datasetName": "analystResult_1302299475",

            "datasourceInfo": {

                "alias": "supermap2_pg",

                "connect": true,

                "dataBase": "supermap2",

                "driver": "PostgreSQL ANSI",

                "engineType": "POSTGRESQL",

                "exclusive": false,

                "openLinkTable": false,

                "password": "supermap",

                "readOnly": false,

                "server": "192.168.120.21",

                "user": "postgres"

            },

            "outputPath": "F:\\1.package\\20171014\\supermap_iserver_901_15413_4668_win64_zip\\webapps\\iserver\\processingResultData\\Analyst\\d2146eb4_69b8_402b_bd90_268543087d7f\\summaryAttributes.smwu",

            "type": "pg"

        },

        "serviceInfo": {

            "targetDataPath": "F:\\1.package\\20171014\\supermap_iserver_901_15413_4668_win64_zip\\webapps\\iserver\\processingResultData\\Analyst\\d2146eb4_69b8_402b_bd90_268543087d7f\\summaryAttributes.smwu",

            "targetServiceInfos": [

                {

                    "serviceAddress": "http://supermapiserver:8090/iserver/services/data-summaryAttributes2/rest",

                    "serviceType": "RESTDATA"

                }

            ]

        },

        "serviceRoot": "http://supermapiserver:8090/iserver/services/",

        "sparkLogFile": null

    },

    "state": {

        "elapsedTime": 12189,

        "endState": true,

        "endTime": 1508228890036,

        "errorMsg": null,

        "errorStackTrace": null,

        "publisherelapsedTime": 2429,

        "runState": "FINISHED",

        "startTime": 1508228872083

    }

}

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 summaryAttributesJob resource exists, or if the user has the authority to access it. By executing an HEAD request with a .<format> URI, you can quickly determine whether the summaryAttributesJob resource supports the <format> representation.

See