Find

The response format. The default response format is html.

Values: html | json

(Required)

The search string. This is the text that is searched across the layers and fields the user specifies.

Example: searchText=Los

If false, the operation searches for an exact match of the searchText string. An exact match is case sensitive. Otherwise, it searches for a value that contains the searchText provided. This search is not case sensitive. The default is true.

Values: true | false

The names of the fields to search. The fields are specified as a comma-separated list of field names. If this parameter is not specified, all fields are searched.

Syntax: searchFields=<fieldName1>,<fieldName2>

Where fieldName1, fieldName2 are the field names returned by the layer resource.

Example: searchFields=AREANAME,SUB_REGION

The well-known ID of the spatial reference of the output geometries. If sr is not specified, the output geometries are returned in the spatial reference of the map.

Allows you to filter the features of individual layers in the exported map by specifying definition expressions for those layers. A definition expression for a layer that is published with the service will be always honored.

Syntax: { "<layerId1>" : "<layerDef1>" , "<layerId2>" : "<layerDef2>" }

Where layerId1, layerId2 are the layer ids returned by the map service resource.

Example: {"0":"POP2000 > 1000000","5":"AREA > 100000"}

Note:

As of 10.5, simple syntax is no longer supported.

(Required)

The layers on which to perform the find operation. The layers are specified as a comma-separated list of layer ids.

Syntax: layers=<layerId1>,<layerId2>

Where layerId1 ,layerId2 are the layer ids returned by the map service resource.

Example: layers=2,4,7

If true, the resultset includes the geometries associated with each result. The default is true.

Values: true | false

This option can be used to specify the maximum allowable offset to be used for generalizing geometries returned by the find operation.

The maxAllowableOffset is in the units of the sr. If sr is not specified, the maxAllowableOffset is assumed to be in the unit of the spatial reference of the map.

Example: maxAllowableOffset=2

This option can be used to specify the number of decimal places in the response geometries returned by the find operation. This applies to x- and y-values only (not m- or z-values).

Example: geometryPrecision=3

Use the dynamicLayers property either to modify the data source of existing layers in the current map service or to add new layers. The new layer should have its source pointing to one of the registered workspaces that was defined at the time the map service was created. When defining a dynamic layer, the source is required.

Syntax:

[
  {
    "id": <layerOrTableId>,
    "source": <layer source>,
    "definitionExpression": "<definitionExpression>"
  },
  {
    "id": <layerOrTableId>,
    "source": <layer source>,
    "definitionExpression": "<definitionExpression>"
  }
]

Example:

[
  {
    "id": 501,
    "source":
    {
      "type": "mapLayer",
      "mapLayerId": 0
    }
  },
  //add a new layer from registered workspace
  {
    "id": 502,
    "source":
    {
      "type": "dataLayer",
      "dataSource":
      {
        "type": "table",
        "workspaceId": "MAP",
        "dataSourceName": "MAP.user1.Taxlots"
      }
    }
  },
  //change the Version of existing map service layer
  {
    "id": 503,
    "source":
    {
      "type": "mapLayer",
      "mapLayerId": 1,
      "version": "USER1"
    },
    "definitionExpression": "neighborhood = 'French Quarter'"
  }
]

If true, z-values will be included in the results if the features have z-values. Otherwise, z-values are not returned. The default is true.

Note:

This parameter only applies if returnGeometry=true.

If true, m-values will be included in the results if the features have m-values. Otherwise, m-values are not returned. The default is false.

Note:

This parameter only applies if returnGeometry=true.

Switch map layers to point to an alternate geodatabase version.

Syntax: gdbVersion=<geodatabase version>

Example: gdbVersion=sde.USER1

//This option was added at 10.5.

If true, the values in the result will not be formatted, in other words, numbers will be returned as is and dates will be returned as epoch values.

Note:

• The default value is false, in other words, numbers and dates are formatted based on the server's setting.
• If true, subtype and domain values are returned as numeric values instead of descriptions.

//This option was added at 10.5.

If true, field names will be returned instead of field aliases.

Note:

• The default value is false.
• For layers with joins, fully qualified field names will be returned.

//This option was added at 10.5.

Use this parameter to apply one or more datum transformations to the map when sr is different than the map service's spatial reference. It is an array of transformation elements.

Transformations specified here are used to project features from layers within a map service to sr.

Note:

While specifying transformation, you need to think about which datum transformation is best applicable to project a layer or layers (not the map service) to the sr. The sourceSpatialReference property in a layer resource reports which spatial reference features are stored in the source dataset.

For a list of valid datum transformation ID values and well-known text strings, see Geographic transformations.

Syntax: datumTransformations=[wkid1, wkid2].

Examples: datumTransformations=[1623, 4078] to apply multiple transformations.

Syntax: datumTransformations=[{<dt1>}, {<dt2>}].

Examples: datumTransformations=[{"wkid":108889}, {"geoTransforms":[{"wkid":108889,"transformForward":true},{"wkid":1622,"transformForward":false}]}] to apply multiple transformations including a composite transformation.

For more information on datum transformation, see the transformation parameter in the Project operation.

//This option was added at 10.5.

It allows you to filter features in the exported map from all layer that are within the specified range instant or extent.

Note:

Check rangeInfos at the layer resources for the available ranges.

Syntax:

[
  {
    "name" : "<rangeName1>",           //range id
    "value"   : <value> |               //single value or 
                [ <value1>, <value2> ] //a value-range 
                     // null is allowed in value-range case -- that means infinity
                     // e.g. [null, 1500] means all features with values <= 1500
                     // [1000, null] means all features with values >= 1000

  },
  {
    "name" : "<rangeName2>",
    "value" : <value> |  [ <value3>, <value4> ]
  }
]&

Example:

[{
  "name" : "salinity",
  "value" : 5            //a range instant (or single) value passed

 }, {
  "name" : "elevation",
  "value" : [1000, 1500] //a range extent is passed

}]

//This option was added at 10.5.

It allows you to filter features for each individual layer that are within the specified range instant or extent.

Note:

Check rangeInfos at the layer resources for the available ranges.

Syntax:

{
  "<layerId1>" : [
    {
      "name" : "<rangeName1>",           //range id
      "value"   : <value> |               //single value or 
                  [ <value1>, <value2> ] //a value-range 
                       // null is allowed in value-range case -- that means infinity
                       // e.g. [null, 1500] means all features with values <= 1500
                       // [1000, null] means all features with values >= 1000

    },
    {
      "name" : "<rangeName2>",
      "value" : <value> |  [ <value3>, <value4> ]
    }
  ],
  "<layerId2>" : [
    {
      "name" : "<rangeName1>",
      "value"   : <value> | [ <value1>, <value2> ]

    }
  ]
}&

Example:

{
  "0" : [
    {
      "name" : "salinity",
      "value" : 5            //a range instant (or single) value passed
    },
    {
      "name" : "elevation",
      "value" : [1000, 1500] //a range extent is passed
    }
  ],
  "1" : [
    {
      "name" : "floor",
      "value" : [null, 5]   //selects features with values <= 5
    }
  ]
}

//This option was added at 10.5.

Allows you to filter the features of individual layers by specifying a value or values to an array of preauthored parameterized filters for those layers. When a value is not specified for any parameter in a request, the default value, which is assigned during authoring time, gets used instead.

When a parameterInfo allows multiple values, you must pass them in an array.

Note:

Check parameterInfos at the layer resources for the available parameterized filters, their default values, and expected data type.

Syntax:

[
   {
     "<layerId1>" : {
       "<parameterName1>" : <value>,               //when the multipleValues=false in the parameterInfo
       "<parameterName2"> : [<value1> | <value2>]  //when the multipleValues=true in the parameterInfo
     },
     "<layerId2>" : {
       "<parameterName3>" : <value>
    }
  }
]&

Example:

[
   {
     "0" : {
       "floor" : 10,
       "incidentDate" : 1475877014000    //date time value needs to be passed in as epoch value
     },
     "1" : {
       "crimeType" : ["burglary", "theft"]
    }
  }
]&

This option was added at 10.6.1.

The historic moment to find. This parameter applies only if the layer is archiving enabled and the supportsQueryWithHistoricMoment property is set to true. This property is provided in the layer resource.

If historicMoment is not specified, the search query will apply to the current features.

Syntax: historicMoment=<Epoch time in milliseconds>

Example: historicMoment=1199145600000

This parameter was added at 10.8. It allows you to mask out layers outside of the clip polygon in the exported map. Clipping can mask out any layer type i.e. feature layers, raster layers, TIN layers etc.

Optionally you can use excludedLayers to excludes layers from being clipped.

Note: geometry must be a polygon or an envelope.

Syntax:

{
     "geometryType" : "<esriGeometryPolygon | esriGeometryEnvelope>",
     "geometry": { <geometry> },
     "excludedLayers" : [ <layerId>, <layerId> ] //optional
   }

Example:

{
     "geometryType" : "esriGeometryPolygon",
     "geometry": { "spatialReference": {"wkid": 102008},
                   "rings": [[[-816126, 216280], [-565859, 199948], [-607349, -50318], [-785229, -38842], [-816126, 216280]]] },
     "excludedLayers" : [ 1, 4 ] //optional
   }

This parameter was added at 10.8. It allows you to filter out features from all features layers based on the input spatial filter. It is like layerDefs but instead of using attribute filter, map service uses spatial filter to determine which features can be queried.

Note:

• Spatial filters only works against feature layers.
• When both clipping and spatialFilter are provided, clipping takes precedence and spatialFilter gets ignored.

Syntax:

{
     "spatialRel" : "<esriSpatialRelIntersects | esriSpatialRelContains | esriSpatialRelCrosses | esriSpatialRelEnvelopeIntersects 
                      | esriSpatialRelIndexIntersects | esriSpatialRelOverlaps | esriSpatialRelTouches 
                      | esriSpatialRelWithin | esriSpatialRelRelation>", //default = esriSpatialRelIntersects
     "geometryType" : "<esriGeometryPoint | esriGeometryMultipoint | esriGeometryPolyline | esriGeometryPolygon | esriGeometryEnvelope >",
     "geometry": { <geometry> }
   }

Example:

{
     "spatialRel" : "esriSpatialRelIntersects",
     "geometryType" : "esriGeometryPolygon",
     "geometry": 
     { 
       "spatialReference": {"wkid": 102008},
       "rings": [[[-816126, 216280], [-565859, 199948], [-607349, -50318], [-785229, -38842], [-816126, 216280]]]
     }
   }