A WHERE clause for the query filter. SQL-92 WHERE clause syntax on the fields in the layer is supported for most data sources. Some data sources have restrictions. For more information, see Query (Feature Service/Layer).

The object IDs of the layer or table to be queried.

objectIds=<objectId1,objectId2>

objectIds=42,93

The time instant or the time extent to query.

//Time instant
time=<timeInstant>

//Time extent
time=<startTime>, <endTime>

//Time instant (1 Jan 2008 00:00:00 GMT)
time=1199145600000

//Time extent (1 Jan 2008 00:00:00 GMT to 1 Jan 2008 00:00:00 GMT)
time=1199145600000, 1230768000000

A null value specified for start time or end time will represent infinity for start or end time, respectively.

time=null, 1230768000000

The JSON parameters that define the aggregation of the data. groupByFields defines the field or fields used to aggregate the data. topCount defines the number of features returned from the top features query and is a numeric value. orderByFields defines the order in which the top features will be returned. orderByFields can be specified in either ascending (asc) or descending (desc) order. The default is ascending.

{
  "groupByFields": <"field1, field2, ..., <fieldN">,
  "topCount": <topCount>,
  "orderByFields": <"field1">
}

{
  "groupByFields": "worker",
  "topCount": 1,
  "orderByFields": "employeeNumber"
}

The geometry to apply as the spatial filter. The structure of the geometry is the same as the structure of the JSON geometry objects returned by the ArcGIS REST API. In addition to the JSON structures, you can specify the geometry of envelopes and points with a simple comma-separated syntax.

//JSON structures
geometryType=<geometryType>&geometry={geometry}

//Envelope syntax
geometryType=esriGeometryEnvelope&geometry=<xmin>,<ymin>,<xmax>,<ymax>

//Point simple syntax
geometryType=esriGeometryPoint&geometry=<x>,<y>

//JSON structure example
geometryType=esriGeometryEnvelope&geometry=-104,35.6,-94.32,41

//Envelope example
geometryType=esriGeometryEnvelope&geometry={xmin: -104, ymin: 35.6, xmax: -94.32, ymax: 41}

//Point simple example
geometryType=esriGeometryPoint&geometry=-104,35.6

The type of geometry specified by the geometry parameter. The geometry type can be an envelope, a point, a line, or a polygon. The default geometry type is an envelope.

Values: esriGeometryPoint | esriGeometryMultipoint | esriGeometryPolyline | esriGeometryPolygon| esriGeometryEnvelope

The spatial reference of the input geometry. The spatial reference can be specified as either a well-known ID or as a spatial reference JSON object. If the inSR parameter is not specified, the geometry is assumed to be in the spatial reference of the map.

The spatial relationship to be applied to the input geometry while performing the query. The supported spatial relationships include intersects, contains, envelope intersects, within, and so on. The default spatial relationship is intersects ( esriSpatialRelIntersects).

Values: esriSpatialRelIntersects | esriSpatialRelContains | esriSpatialRelCrosses | esriSpatialRelEnvelopeIntersects | esriSpatialRelIndexIntersects | esriSpatialRelOverlaps | esriSpatialRelTouches | esriSpatialRelWithin

The buffer distance for the input geometries. The distance unit is specified by units. For example, if the distance is 100, the query geometry is a point, units is set to meters, and all points within 100 meters of the point are returned.

The geodesic buffer is created based on the datum of the output spatial reference if it exists. If there is no output spatial reference, the input geometry spatial reference is used. Otherwise, the native layer spatial reference is used to generate the geometry buffer used in the query. This parameter only applies if supportsQueryWithDistance is true.

distance=<distance>

distance=100

The unit for calculating the buffer distance. If units is not specified, the unit is derived from the geometry spatial reference. If the geometry spatial reference is not specified, the unit is derived from the feature service data spatial reference. This parameter only applies if supportsQueryWithDistance is true.

Values: esriSRUnit_Meter | esriSRUnit_StatuteMile | esriSRUnit_Foot | esriSRUnit_Kilometer | esriSRUnit_NauticalMile | esriSRUnit_USNauticalMile

The list of fields to be included in the returned result set. This list is a comma-delimited list of field names. You can also specify the wildcard (*) as the value of this parameter. In this case, the query results include all the field values.

//General example
outFields=NAME,ST,AREA

//Wildcard example
outFields=*

If true, the result includes the geometry associated with each feature returned. The default is true.

Values: true | false

The maximum allowable offset to be used for generalizing geometries returned by the query operation. The maxAllowableOffset is in the units of outSR. If outSR is not specified, maxAllowableOffset is assumed to be in the unit of the spatial reference of the map.

maxAllowableOffset=2

The number of decimal places in the response geometries returned by the query operation. This applies to x- and y-values only (not m- or z-values).

geometryPrecision=3

The spatial reference of the returned geometry. The spatial reference can be specified as either a well-known ID or as a spatial reference JSON object. If outSR is not specified, the geometry is returned in the spatial reference of the map.

If true, the response only includes an array of object IDs. Otherwise, the response is a feature set. The default is false. While there is a limit to the number of features included in the feature set response, there is no limit to 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 as true and subsequently requesting feature sets for subsets of object IDs.

When objectIds are specified, setting this parameter to true is invalid.

Values: true | false

If true, the response only includes the count(number of features or records) that would be returned by a query. Otherwise, the response is a feature set. The default is false. This option supersedes the returnIdsOnly parameter. If returnCountOnly is set to true, the response will return both the count and the extent.

Values: true | false

If true, the response only includes the extent of the features that would be returned by the query. The default is false. If returnCountOnly is set to true, the response will return both the count and the extent. This parameter applies only if the supportsReturningQueryExtentproperty of the layer is true.

Values: true | false

If true, z-values are included in the results if the features have z-values. Otherwise, z-values are not returned. The default is false. This parameter only applies if returnGeometry= is true, and the layer's hasZ property is true.

If true, m-values are included in the results if the features have m-values. Otherwise, m-values are not returned. The default is false. This parameter only applies if returnGeometry is true, and the layer's hasM property is true.

(Optional)

The resultTypeparameter can be used to control the number of features returned by the query operation. Support for the resultType parameter is advertised on the layer resource's metadata (supportQueryWithResultType as true). The tile value is used when the client is using a virtual tiling scheme when querying features. A virtual tiling scheme works similar to tiles in a tile map service layer. The standard value is used with a nontiled query in which the client will send only one query for the full extent. For more information, see the Considerations for resultType section below.

Values: none | standard | tile

The response format. The default response format is html. The values supported are defined by the "supportedQueryFormats" layer property.

Values: html | json | pbf | geojson