The submitJob operation is performed on an asynchronous GP task resource. The result of this operation is a GP job resource. You can provide arguments to the submitJob operation as query parameters defined in the parameters table below.

With this operation, the majority of the parameters that you include in your request are dependent on the input parameter types of the geoprocessing task that you are submitting. Note that the GP execute and submit job operations share the same syntax for all input parameter types and examples of all input parameter types are discussed below.

Example 1: Submit a job to the Mailing List task for Parcel ID '1N1E34CC  -06600' within a search distance of 100 feet:

Example 2: Submit a job to the task similar to Example 1 but request the output spatial reference to be Web Mercator (102113):

See the JSON Response Syntax and Examples for the GP job resource.

InputBoolean=true&InputDouble=345.678&InputLong=345&InputString=MyString

{ "distance" : 345.678, "units" : "esriMiles" }

• "geometry": can be points, lines or polygons. The structure for the geometries is same as the structure of the json geometry objects returned by the ArcGIS REST API.
• "attributes": key-value pairs where the key is a field name in the list of fields of the record set, and the value is the value for the corresponding field.

Note that values for GPFeatureRecordSetLayer contain the "geometry" field while values for GPRecordSet do not.

{ 
"features"  : [
{
    "geometry" : {"x" : -104.44, "y" : 34.83},
    "attributes" : {"Id" : 43, "Name" : "Feature 1"}
},
{
    "geometry" : {"x" : -100.65, "y" : 33.69},
    "attributes" : {"Id" : 67, "Name" : "Feature 2"}
}
]
}

For "schema-less" input features, those feature sets where the geometry type or spatial reference is not specified by the model publisher, you must provide the geometry type and the spatial reference in addition to the features as specified below:

{ 
"geometryType" : "esriGeometryPoint",
"spatialReference" : {"wkid" : 4326},
"features"  : [
{
    "geometry" : {"x" : -104.44, "y" : 34.83},
    "attributes" : {"Id" : 43, "Name" : "Feature 1"}
},
{
    "geometry" : {"x" : -100.65, "y" : 33.69},
    "attributes" : {"Id" : 67, "Name" : "Feature 2"}
}
]
}

The geometryType can be esriGeometryPoint, esriGeometryPolyline, or esriGeometryPolygon. If the geometry type is not specified, it is assumed to be esriGeometryPoint. If the spatialReference is not specified, it is defaulted to an unknown coordinate system.

For a large set of geometries, you can specify a URL to the input geometries stored in a JSON structure in a file on a public server.

{ "url" : "http://myserver/myfeatures/afile.txt" }

GPDate

The parameter value for GPDate is a JSON structure with the following fields.

• "date": a string value representing the date.
• "format": a string specifying the format for the date.

{ "date" : "4/6/07", "format" : "M/d/y" }

GPDataFile

The parameter value for GPDataFile is a JSON structure with a "url" field. The value of the "url" field is a URL to the location of the input data file.

{ "url" : "http://myserver/myfile" }

GPRasterData and GPRasterLayer

The parameter value for GPRasterData and GPRasterDataLayer data types is a JSON structure with the the following fields.

• "url": URL to the location of the input raster data file.
• "format": the format of the raster data such as "jpg", "tif", etc.

{ "url" : "http://myserver/myraster.jpg", "format" : "jpg" }