Description

Note: Prior to 10, the query operation could only be performed on layers. From 10 onward, in addition to layers, the query operation can be performed on tables as well.

The query operation is performed on a layer / table resource. The result of this operation is a featureset. This featureset contains Feature objects including the values for the fields requested by the user. For layers, if you request geometry information, the geometry of each feature is also returned in the featureset. For tables, the featureset does not include geometries.

Note that all parameters related to geometry will be ignored when querying tables.

At 10.0 SP1, support for returning the count (number of features/records) that would be returned by a query, was added for both layers / tables.

Support for querying layers / tables based on time was added at 10. For time-aware layers, users can use the time parameter to specify the time instant or the time extent to query.

At 10, a new returnIdsOnly parameter was introduced. If set to false (default), the response will be a featureset. If true, the response will be an array of object IDs.

Note that while there is a limit on the number of features included in the feature set response, there is no limit on the number of object IDs returned in the ID array response. Clients can exploit this to get all the query conforming object IDs by specifying returnIdsOnly=true and subsequently requesting feature sets for subsets of object IDs.

At 10, support for query based on objectIds was added.

Supported for f=amf was also added at 10.

At 10, support for generalizing geometries returned by the query operation was added.

At 10, query operation returns additional fields array (JSON and AMF only) that contains array of field information for returned values.  This array contains only fields specified in outFields parameter. See Layer/Table for defails on fields.

NOTE: domains member is not included in field information objects returned with the response.

At 10, fieldAliases member is deprecated.

You can provide arguments to the query operation as query parameters defined in the parameters table below.

Parameters

Example Usage

Example 1: Query using the text parameter on the states layer of the ESRI_StateCityHighway_USA on sampleserver1:

Example 2: Query using a where statement on the same layer. The output is JSON format:

Example 3: Query strings are case sensitive. In this example, UPPER is used to make the query case insensitive:

Example 4: Querying the same states layer using geometry (envelope):

Example 5: Querying the states layer by both geometry (envelope) and a where statement:

Example 6: Querying the states layer by where statement, specifying a list of fields to return, and requesting no geometry in the results:

Example 7: Querying the states layer by text parameter and requesting the geometry with the well-known ID of 102113 (Web Mercator):

Example 8: Query a table using a WHERE clause and return OBJECTIDs only http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/SanFrancisco/311Incidents/MapServer/1/query?objectIds=&where=agree_with_incident+%3D+1&returnGeometry=true&returnIdsOnly=true&f=html

JSON Response Syntax (when returnIdsOnly=false and returnCountOnly=false)

{
"displayFieldName" : "<displayFieldName>",
//fieldAliases deprecated at 10
"fieldAliases" : {
  "<fieldName1>" : "<fieldAlias1>",
  "<fieldName2>" : "<fieldAlias2>"
},
"fields" : [
    {"name" : "<fieldName1>", "type" : "<fieldType1>", "alias" : "<fieldAlias1>", "length" : "<length1>"},
    {"name" : "<fieldName2>", "type" : "<fieldType2>", "alias" : "<fieldAlias2>", "length" : "<length2>"}
],
"geometryType" : "<geometryType>", //for layers only
"spatialReference" : <spatialReference>, //for layers only
"features" : [ //features may include geometry for layers only
  <feature1>, <feature2>
]
}

JSON Response Syntax (when returnIdsOnly=true)

{
"objectIdFieldName" : "<objectIdFieldName>",
"objectIds" : [ <objectId1>, <objectId2> ]
}

JSON Response Syntax (when returnCountOnly=true)

{
"count" : <count>
}

JSON Response Example when returnIdsOnly=false and returnCountOnly=false

{
"displayFieldName" : "AREANAME",

"fieldAliases" : {
    "ST" : "ST",
    "POP2000" : "Population - 2000",
    "AREANAME" : "City Name"

},

"fields" : [
{
    "name" : "ST",
    "alias" : "ST",
    "type" : "esriFieldTypeString",
    "length" : 2
},
{

    "name" : "POP2000",
    "alias" : "Population - 2000",
        "type" : "esriFieldTypeInteger"
},

{
    "name" : "AREANAME",
    "alias" : "City Name",
    "type" : "esriFieldTypeString",
    "length" : 255
}
],

"geometryType" : "esriGeometryPoint",
"spatialReference" : {"wkid" : 4326},
"features" : [
    {
    "attributes" : {
        "ST" : "CA",
        "POP2000" : 3694820,
        "AREANAME" : "Los Angeles"
    },
    "geometry" : { "x" : -118.37, "y" : 34.086 }
    },
    {
    "attributes" : {
        "ST" : "CA",
        "POP2000" : 461522,
        "AREANAME" : "Long Beach"
    },
    "geometry" : { "x" : -118.15, "y" : 33.80 }
    }
]
}

JSON Response Example when returnIdsOnly=true

{
"objectIdFieldName":"objectid",
"objectIds":[1,2,3,4,5,7]
}

JSON Response Example when returnCountOnly=true

{
"count":48
}