(Required)

The point from which to search for the closest address or place. The point can be represented as a simple, comma-separated syntax or as a JSON point object.

The default spatial reference of the comma-separated syntax is the same as the data used to build the locator on which the geocode service is based.

Use JSON formatting to specify another coordinate system for the input location. Specifically, set the spatial reference using its well-known ID (WKID) value. For a list of valid WKID values, see Using spatial references.

//simple syntax (with default WGS84 SR)
location=-117.196,34.056

//JSON (with default WGS84 SR)
location={x: 103.876722, y: 1.3330736}

(Required)

Specifies a token that provides the identity of a user who has the necessary permissions to access the service.

(Optional)

The spatial reference of the x,y coordinates returned by a geocode request. This is useful for applications using a map with a spatial reference different than that of the geocode service.

The spatial reference can be specified as either a WKID or as a JSON spatial reference object. If outSR is not specified, the spatial reference of the output locations is the same as that of the service. The default spatial reference of the geocode service is the same as the data used to build the locator on which the geocode service is based.

For a list of valid WKID values, see Using spatial references.

outSR=102100

(Optional)

Sets the language in which geocode results are returned. Addresses and places in many countries are available in more than one language; in these cases, the langCode parameter can be used to specify which language to use for results returned by the findAddressCandidates operation. This is useful for ensuring that results are returned in the expected language. For example, a web application can be designed to get the browser language and pass it as the langCode parameter value in a findAddressCandidates request.

See the table of supported countries for valid language code values in each country. Full language names cannot be used in the langCode parameter. Only one language code value can be included for the langCode parameter in a findAddressCandidates request.

If the langCode parameter isn't included in a request, or if it is included but there are no matching features with the input language code, the resultant match is returned in the language code of the primary matched component from the input search string. Typically, this is either place-name or street name, depending on the search string.

It is important to note that langCode is limited by the address data sources used to build the locator for the geocode service. This parameter will be ignored when not supported by the data.

langCode=fr

(Optional)

Limits the possible match types returned by the reverseGeocode operation. Valid values are listed in the feature type hierarchy table. Single or multiple values can be included in the request. If a single value is included, the search tolerance for the input feature type is 500 meters. If multiple values are included, the default search distances specified in the feature type hierarchy table are applied.

Values: Subaddress | PointAddress | Parcel |StreetAddress | StreetInt | StreetName | POI | DistanceMarker | Locality | Postal

//Single featureTypes value
featureTypes=PointAddress

//mMultiple featureTypes values
featureTypes=PointAddress,StreetAddress

(Optional)

Specifies whether the output geometry of PointAddress and Subaddress matches will be the rooftop point or street entrance location. Valid values are rooftop and street. The default value is rooftop.

Geocode results include one geometry object (the location object) that defines the location of the address, as well as two sets of x,y coordinate values within the attributes object X/Y and DisplayX/DisplayY. In most cases, for geocode results with PointAddress or Subaddress, the X/Y attribute values describe the coordinates of the address along the street, and the DisplayX/DisplayY values describe the rooftop, or building centroid, coordinates. By default, the geometry returned for geocode results represents the rooftop location of the address (if the rooftop location is available in the source data). This is useful for most spatial analysis and map display purposes. However, for routing scenarios, it may be better to use the street location because the rooftop location of some addresses may be offset from a street by a large distance. For these cases, the locationType parameter can be used to specify that the street entrance geometry should be returned.

It is important to note that locationType is limited by the address data sources used to build the locator for the geocode service. Not all PointAddress and Subaddress features include rooftop and street location coordinates. For some addresses, only a rooftop location is available; for others, only a street location is provided by the data source. In these cases, the locationType parameter may not function as expected. For example, if only rooftop location coordinates are available for an address, the rooftop geometry will be returned for the geocoded address even when street is requested.

Values: street | rooftop

(Optional)

Allows simple configuration of output fields returned in a response from the geocode service by specifying which address component values will be included in output fields. A single value or a comma-delimited collection of values are supported as input. If the parameter is blank or excluded from a request, default address label formats will be used.

A particular address may have multiple city names associated with it. In the United States for example, all addresses have a ZIP code (postal code) assigned to them. Each ZIP code has one or more associated locality names, which are known as postal cities. There is always one primary postal city value for each ZIP code. ZIP codes typically have no set boundaries, and the primary postal city name for the ZIP code that is assigned to an address may be different than the name of the local city that the address is in.

Additional details:

• The preferredLabelValues parameter takes a comma-delimited collection of values as input.
• The parameter values correspond to two groups: a City group and a Street group, indicated by the suffix of the value name. The postalCity, localCity, and matchedCity values are part of the City group. The primaryStreet and matchedStreet values are part of the Street group.
• A geocode request can include one City value and one Street value, for example, preferredLabelValues=primaryStreet,postalCity.
• A request can only include one value per group. In other words, a request with preferredLabelValues=matchedCity,postalCity is invalid.

preferredLabelValues=matchedCity,primaryStreet

(Required)

The response format. The default response format is html.

Values: html | json| pjson | kmz

StreetInt

10 meters

Intersections are only returned when StreetInt is included in the request.

StreetAddress (near), DistanceMarker, or StreetName

3 meters

Candidates of type StreetName are only returned if StreetName is included in the request.

POI centroid

25 meters

A business or landmark that can be represented by a point.

Parcel centroid

25 meters

A plot of land that can be represented by a point.

Subaddress

10 meters

Subaddress candidates, which can be features such as apartments or floors in a building, are not returned if multiple subaddresses exist at the same x,y location and one of the following conditions is met:

• The subaddress units cannot be collapsed into a contiguous range.
• The subaddresses have different street address, postal code, or administrative zone values.

PointAddress

50 meters

A PointAddress match is not returned if it is on the opposite side of the street as the input location, even if it is within 50 meters of the location.

StreetAddress (distant), DistanceMarker, or StreetName

100 meters

Candidates of type StreetName are only returned if StreetName is included in the request.

POI area

Within boundary

A business or landmark that can be represented by an area, such as a large park or university. This is not available unless supported by the data used to build the locator on which the geocode service is based.

Parcel area

Within boundary

A plot of land that can be represented by an area, such as a parcel or tax lot. This is not available unless supported by the data used to build the locator on which the geocode service is based.

Postal or Locality area

Within boundary

If the input location intersects multiple boundaries, the feature with the smallest area is returned.