/findAddressCandidates

f

The response format.

1
f=json

token

An access token with the required privileges.

• ArcGIS Location Platform: premium:user:geocode:temporary or premium:user:geocode:stored
• ArcGIS Online: premium:user:geocode or premium:user:geocode:stored

1
token=<ACCESS_TOKEN>

1
2
3
4

GET <SERVICE_REQUEST> HTTP/1.1
  Host: <SERVICE_DOMAIN>
  X-Esri-Authorization: Bearer <ACCESS_TOKEN>

Learn more about access tokens and privileges in the Security and authentication developer guide.

SingleLine

The SingleLine parameter specifies the location to be geocoded. This can be a street address, place-name, postal code, or POI. The input address components need to be formatted as a single string.

Example

1
SingleLine=380 New York St, Redlands, California 92373

address

A string that represents the first line of a street address. In most cases, this field will be used for street name and house number input, but it can also be used to input building name or place-name.

Example of address field input in the United States

1
address=380 New York Street

Example of address field input in Mexico

1
address=Avenida Revolucion 8208

address2

A string that represents the second line of a street address. This can include street name/house number, building name, place-name, or subunit.

Example address2 field input

1
address2=Beetham Tower

address3

A string that represents the third line of a street address. This can include street name/house number, building name, place-name, or subunit.

Example address3 field input

1
address3=Suite 4208

neighborhood

The smallest administrative division associated with an address, typically, a neighborhood or a section of a larger populated place. A neighborhood is a subdivision of a city.

Example of a neighborhood in Mexico (colonia)

1
neighborhood=Herrera

city

The next largest administrative division associated with an address, typically, a city or municipality. A city is a subdivision of a subregion or a region.

Example of a city in the U.S.

1
city=Los Angeles

Example of a city in Mexico

1
city=Tijuana

subregion

The next largest administrative division associated with an address. Depending on the country, a subregion can represent a county, state, or province.

Example of a subregion (department) in France

1
subregion=Vienne

region

The largest administrative division associated with an address, typically, a state or province.

Example of a region in the U.S. (state)

1
region=Florida

Example of a region in Mexico (estado)

1
region=Baja California

postal

The standard postal code for an address, typically, a three– to six-digit alphanumeric code.

Example

1
postal=92373

postalExt

A postal code extension, such as the United States Postal Service ZIP+4 code, provides finer resolution or higher accuracy when also passing postal .

Example

1
postalExt=1112

countryCode

A value representing the country. Providing this value increases geocoding speed. Acceptable values include the full country name in English or the official language of the country, the two-character country code, or the three-character country code. A list of supported countries and codes is available in the Service data topic.

Example

1
countryCode=USA

magicKey

The findAddressCandidates operation retrieves results quicker when you pass in valid SingleLine and magicKey values than when you don't pass in magicKey . However, to get these advantages, you need to make a prior request to suggest , which provides a magicKey . This may or may not be relevant to your workflow.

The suggest operation is often called on to improve the user experience of search boxes by analyzing partial text and providing complete names of places, addresses, points of interest, and so on. For instance, typing Mbu into a search box produces Mbuji-Mayi, Democratic Republic of the Congo as a suggestion, so the user doesn't need to type the complete name.

Looking at the suggestion process from another perspective, as the user types, the suggest operation performs a text search, which is a redundant part of the overall search that the findAddressCandidates operation can also perform. The user chooses a place-name or type—narrowing the results to a specific record. The results from suggest include text and magicKey values that contain the information the user chose; passing these values from suggest into findAddressCandidates results in faster and more accurate operations.

In summary, using the magicKey parameter in findAddressCandidates is a two-step process:

• Make a request to suggest . The response includes text and magicKey properties.
• Make a request to findAddressCandidates and pass in the text and magicKey values returned from suggest as the SingleLine and magicKey input parameters, respectively. The magicKey parameter will not function correctly if passed alone. Both magicKey and SingleLine must be included in a findAddressCandidates request so the output matches the selected suggestion.

Example

1
magicKey=JS91CYhQDS5vDPhvSMyGZby0YFbaUDoaM5bHMoFF

searchExtent

A set of bounding box coordinates that limit the search area to a specific region. This is especially useful for applications in which a user will search for places and addresses within the current map extent.

You can specify the spatial reference of the searchExtent coordinates, which is necessary if the map spatial reference is different than that of the ArcGIS Geocoding service; otherwise, the spatial reference of the coordinates is assumed to be the same as that of the ArcGIS Geocoding service.

The input can either be a comma-separated list of coordinates defining the bounding box or a JSON envelope object. The spatial reference of the bounding box coordinates can be included if an envelope object is used.

Refer to the Search within an extent section below for more details about using searchExtent .

Example without a spatial reference

1
searchExtent=-104,35.6,-94.32,41

Example with a spatial reference

1
2
3
4
5
6
7
8
9
10
searchExtent=
{
    "xmin": -13052769,
    "ymin": 3951172,
    "xmax": -13019630,
    "ymax": 3978490,
    "spatialReference": {
        "wkid": 3395
    }
}

location

The location parameter defines an origin point that is used to prefer or boost geocoding candidates based on their proximity to the location. Candidates near the location are prioritized relative to those farther away. This is useful in mobile applications in which a user wants to search for places in the vicinity of their current GPS location, or in mapping applications in which users want to search for places near the center of the map.

The location can be represented with a simple comma-separated syntax (x,y), or as a JSON point object. If the comma-separated syntax is used, the spatial reference of the coordinates must be WGS84; otherwise, the spatial reference of the point coordinates can be defined in the JSON object.

Example using simple syntax (WGS84)

1
location=-117.196,34.056

JSON example with a spatial reference

1
2
3
4
5
6
7
8
location=
{
    "x": -13046165.572,
    "y": 4036389.847,
    "spatialReference": {
        "wkid": 102100
    }
}

category

A place or address type that can be used to filter findAddressCandidates results. The parameter supports input of single category values or multiple comma-separated values. The category parameter can be passed in a request with the SingleLine or address parameters. It can also be passed in a request on its own without the singleline or address parameters. See Category filtering for details about the category parameter.

Example of category filtering with a single category

1
category=Address

Example of category filtering with multiple categories

1
category=Address,Postal

outSR

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 well-known ID (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 ArcGIS Geocoding service spatial reference is WGS84 (WKID = 4326).

For a list of valid WKID values, see Projected coordinate systems and Geographic coordinate systems.

Example (102100 is the WKID for the Web Mercator projection)

1
outSR=102100

outFields

The list of fields to be returned within the attributes object of the response. Descriptions for each of these fields are available in the Output fields section of this document.

The address , location (x,y coordinates of the match location), score , extent , and spatialReference objects are returned in the response by default. If the outFields parameter is excluded from the request, or if it is included but no fields are specified, the attributes object in the corresponding response is blank.

Example that returns all output fields

1
outFields=*

Example that returns the specified fields only

1
outFields=AddNum,StName,City

maxLocations

The maximum number of locations to be returned by a search, up to the maximum number allowed by the service. If not specified, all matching candidates up to the service maximum are returned.

The ArcGIS Geocoding service allows up to 50 candidates to be returned for a single request.

Example

1
maxLocations=10

forStorage

The forStorage parameter specifies whether the results of the operation will be persisted. The default value is false , which indicates the results of the operation can't be stored, but they can be temporarily displayed on a map, for instance. If you store the results, in a database, for example, you need to set this parameter to true .

Applications are contractually prohibited from storing the results of geocoding transactions unless they make the request by passing the forStorage parameter with a value of true and the token parameter with a valid token. Instructions for composing a request with a valid token are provided in Security and authentication.

To learn more about free and paid geocoding operations, see details about stored versus not stored geocoding.

Example

1
forStorage=true

matchOutOfRange

A Boolean that specifies whether StreetAddress matches should be returned even when the input house number is outside of the house number range defined for the input street. Out-of-range matches have =StreetAddressExt . The geometry of such matches is a point corresponding to the end of the street segment where the range value is closest to the input house number. If matchOutOfRange is not specified in a request, its value is set to true by default.

With matchOutOfRange , better spatial accuracy is provided for inexact street address searches. Most street segments are assigned house number ranges. For example, Main Street may include house numbers from 2–100 on one side of the street and 1–99 on the other. A user may search for a house number that is not within this range, such as 109 Main Street. If matchOutOfRange=false is passed in this request, the geocode service will return a StreetName-level match to Main Street, with geometry corresponding to the centroid of a street segment that most closely matches the input values. StreetName matches can be ambiguous because there may be multiple street segments with the same name that equally match the input. However, if matchOutOfRange=true , in this case, a more precise geometry is returned to the specific side of the segment of Main Street with house number range 1–99.

Example

1
matchOutOfRange=false

locationType

The locationType parameter specifies whether the output geometry of PointAddress and Subaddress matches should 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, while 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 desirable 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 by the ArcGIS Geocoding 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. For cases such as this, 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 locationType=street is requested.

Example

1
locationType=street

langCode

The langCode parameter 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 should be used 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 could 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. The Supported Language Codes column provides the valid input values for the langCode parameter. Full language names cannot be used with 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.

Similarly, when there are multiple supported languages for a country, it doesn't mean that every address in the country is available in each of the languages. It may be the case that addresses are available in multiple languages for only one region of the country, or that each language is exclusive to a different region and there is no overlap. The following are some examples:

• French, German, and Italian are listed as supported languages for Switzerland. However, there is no overlap between the languages for addresses in most regions of the country. For instance, in the city of Geneva, only French addresses are available, while German is the only language used for addresses in the city of Bern.
• In Belgium, where three languages are supported (Dutch, French, and German), addresses are available in the city of Brussels in both Dutch and French. However, in the majority of the country, only a single language is used for addresses.
• In Greece, there is complete address coverage in both Greek and transliterated Greek languages (Greek words represented with Latin characters).

Due to variability of language coverage, the following logic is used to handle the different scenarios that may be encountered.

Example

1
langCode=fr

sourceCountry

The sourceCountry parameter limits the candidates returned by the findAddressCandidates operation to the specified country or countries. For example, if sourceCountry=USA is included in the request, it is assumed that the address is in the United States, so only matching addresses in the U.S. are returned. Using this parameter prevents potential unexpected results in other countries for ambiguous searches.

Acceptable values include the three-character country code. You can specify multiple country codes to limit results to more than one country.

A list of supported countries and codes is available in Service data.

Example: Single country

1
sourceCountry=USA

Example: Multiple countries

1
sourceCountry=FRA,DEU,ESP

preferredLabelValues

The preferredLabelValues parameter allows simple configuration of output fields returned in a response from the ArcGIS Geocoding service by specifying which address component values should be included in output fields. The parameter supports a single value or a comma-delimited collection of values 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 within.

For addresses in the United States, the ArcGIS Geocoding service includes the primary postal city in response output fields by default. As an example, postal code 45420 in Ohio has the primary postal city value Dayton. Addresses in the city of Kettering are assigned this postal code. It means that the default output fields for all geocoded addresses with postal code 45420, even those within the city of Kettering, will include Dayton as the city. To illustrate, if a user searches for 2109 E Dorothy Ln, OH, 45420 , the default match label returned in the response is 2109 E Dorothy Ln, Dayton, Ohio, 45420, even though the address is within the Kettering city limits.

Some organizations may prefer to include the local city name in the response instead of the postal city. The preferredLabelValues parameter can be used for this purpose. For the previous example, if preferredLabelValues=localCity is included in the request, the output match label in the response will be 2109 E Dorothy Ln, Kettering, Ohio, 45420.

Similarly, streets may be known by multiple names. This is especially true with highways. For example, Pearblossom Hwy in California, which is the primary name, is also known as CA-138. The ArcGIS Geocoding service allows matching to addresses using either name as input, and by default will return the name that was matched to in the response.

Some organizations may prefer that the primary street name be returned in the response even if a user searches for an alternate street name, and they can use the preferredLabelValues parameter to accomplish this. In other words, if a user searches for CA-138, Pearblossom, CA , and preferredLabelValues=primaryStreet is included in the request, the match label returned in the response is Pearblossom Hwy, Pearblossom, California, 93553.

See the following table for supported parameter values.

Here are additional details about the preferredLabelValues parameter:

• 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 instance: preferredLabelValues=primaryStreet,postalCity .
• A request can only include one value per group. In other words, a request with preferredLabelValues=matchedCity,postalCity is invalid.

Example: Single label value

1
preferredLabelValues=matchedCity

Example: Multiple label values

1
preferredLabelValues=matchedCity,primaryStreet

searchWithin

The searchWithin parameter is used to specify the feature types for a collection of places that should be returned for a geocoded object. For example, searchWithin may be used to return all addresses that exist within a postal code, or all businesses located at a particular address.

Collections can be returned for geocoded PointAddress and PostalExt records only.

• For geocoded PointAddress records, collections of Subaddresses or POIs (or both) are supported.
• For geocoded PostalExt records, collections of PointAddresses, Subaddresses, or POIs (or any combination of these) are supported.

The searchWithin parameter also supports pagination. Because there may be hundreds or thousands of places that exist at or within a geocoded location, the searchWithin parameter is used along with the start and num parameters to break up large collections into manageable result sets, or pages, of 50 or fewer candidates. This is accomplished by passing consecutive requests to the ArcGIS Geocoding service with different start values.

To support pagination, the JSON response includes the following properties at the end of the response when a collection is returned for a searchWithin request:

If searchWithin is included in a findAddressCandidates request, the request must also include a valid token; otherwise the request fails with an error.

See the following table for supported parameter values.

Example: Single feature type

1
searchWithin=POI

Example: Multiple feature types

1
searchWithin=PointAddress,Subaddress,POI

start

The start parameter is used along with the searchWithin and num parameters to page through large result sets of more than 50 candidates. It defines the result number to be returned as the first candidate in a page. The default value of start is 1.

The start parameter only functions when included in a request along with the searchWithin parameter.

Example

1
start=51

num

The num parameter is used along with the searchWithin and Start parameters to page through large result sets of more than 50 candidates. It defines the number of candidates to be included in each page. The default value of num is 50. Valid values include any integer between 1 and 50. If a value larger than 50 is specified, no more than 50 candidates are returned in the response.

The num parameter only functions when included in a request along with the searchWithin parameter.

Example

1
num=20

matchID

The matchID parameter allows you to search for an ID string value that represents an address or place. MatchID is also an output field which is available in a findAddressCandidates response. The MatchID value can be obtained from a findAddressCandidates response and then passed in a request at a later time. In most cases the MatchID value for a particular address will be constant across releases of the ArcGIS Geocoding service.

Example

1
matchID=AQFV9QAAmeQBAJUBBAAAAAAMD05FVyBZT1JLIFNUUkVFVBUDMzgwZgNFTkc

returnMatchNarrative

The returnMatchNarrative parameter is used to return detailed information about how a geocoding result was obtained by describing the way that each portion of an input string in a findAddressCandidates request was processed, or classified, by the ArcGIS Geocoding service. This information is included in the findAddressCandidates response as an additional JSON object called match-narrative.

To illustrate the type of information that is provided by returnMatchNarrative, if "380 New York Street, Redlands" is searched for, the match-narrative object describes which part of the input was matched as house number ("380"), which part was matched as street name ("New York"), and so on.

Within the match-narrative object each part of the input search string is represented with a sub-object, the order of which corresponds to that of the input parts. Each sub-object includes the following properties:

This is how the complete match-narrative sub-object for "380" in "380 New York Street, Redlands" would appear:

1
2
3
4
5
6
7
{
  "field": "HouseNumber",
  "input": "380",
  "datum": "380",
  "narrative-code": "cm",
  "narrative-desc": "classified+matched"
}

The following table provides descriptions of the possible values for the narrative-code and narrative-desc properties.

Example

1
returnMatchNarrative=true

Input address examples

• Street addresses

  • 27488 Stanford Ave, Bowden, North Dakota
  • 380 New York St, Redlands, CA 92373

• Street intersections

  • New York St and W Redlands Blvd, Redlands, CA
  • Jacques Veltmanstraat & Pieter Calandlaan, Amsterdam, NLD

• Points of interest (POI) by name and type

  • Disneyland
  • banks in Paris
  • los angeles starbucks
  • mount everest

• Administrative place names, such as city, county, state, province, or country names

  • Seattle, Washington
  • State of Mahārāshtra
  • Liechtenstein

• Postal codes

  • 92591
  • TW9 1DN

• Coordinates

  • -117.155579,32.703761

• Street blocks

  • 4400 Block of Perry St, Houston, Texas
  • 2400-3100 Block of San Bruno Ave, San Francisco

• Streets between two cross streets

  • Conway Dr between Sheridan Ave and E El Norte Pkwy, Escondido
  • I-10 between exit 75 and exit 76, Redlands, CA

Search for a street address

You can pass the address components in a single parameter or separated into multiple parameters. Examples of each are shown. Note that in each case, the JSON response is the same for both the single- and multiple-parameter requests. See Match accuracy for more information about obtaining optimal results for address searches.

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?SingleLine=380 New York Street, Redlands, CA 92373&category=&outFields=*&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "380 New York St, Redlands, California, 92373",
   "location": {
    "x": -117.194790019279,
    "y": 34.057264995788
   },
   "score": 100,
   "attributes": {
    "Loc_name": "World",
    "MatchID": "AQFV9QAAmeQBAJUBBAAAAAAMD05FVyBZT1JLIFNUUkVFVBUDMzgwZgNFTkc",
    "Status": "M",
    "Score": 100,
    "Match_addr": "380 New York St, Redlands, California, 92373",
    "LongLabel": "380 New York St, Redlands, CA, 92373, USA",
    "ShortLabel": "380 New York St",
    "Addr_type": "PointAddress",
    "Type": "",
    "PlaceName": "",
    "Place_addr": "380 New York St, Redlands, California, 92373",
    "Phone": "",
    "URL": "",
    "Rank": 20,
    "AddBldg": "",
    "AddNum": "380",
    "AddNumFrom": "",
    "AddNumTo": "",
    "AddRange": "",
    "Side": "",
    "StPreDir": "",
    "StPreType": "",
    "StName": "New York",
    "StType": "St",
    "StDir": "",
    "BldgComp": "",
    "BldgType": "",
    "BldgName": "",
    "LevelType": "",
    "LevelName": "",
    "UnitType": "",
    "UnitName": "",
    "SubAddr": "",
    "StAddr": "380 New York St",
    "Block": "",
    "Sector": "",
    "Nbrhd": "",
    "District": "",
    "City": "Redlands",
    "MetroArea": "",
    "Subregion": "San Bernardino County",
    "Region": "California",
    "RegionAbbr": "CA",
    "Territory": "",
    "Zone": "",
    "Postal": "92373",
    "PostalExt": "8118",
    "Country": "USA",
    "CntryName": "United States",
    "LangCode": "ENG",
    "Distance": 0,
    "X": -117.195649834906,
    "Y": 34.057251584743,
    "DisplayX": -117.194790019279,
    "DisplayY": 34.057264995788,
    "Xmin": -117.195790019279,
    "Xmax": -117.193790019279,
    "Ymin": 34.056264995788,
    "Ymax": 34.058264995788,
    "ExInfo": "",
    "StrucType": "Commercial",
    "StrucDet": ""
   },
   "extent": {
    "xmin": -117.195790019279,
    "ymin": 34.056264995788,
    "xmax": -117.193790019279,
    "ymax": 34.058264995788
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?Address=380 new york st&City=redlands&Region=CA&Postal=92373&outFields=*&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "380 New York St, Redlands, California, 92373",
   "location": {
    "x": -117.194790019279,
    "y": 34.057264995788
   },
   "score": 100,
   "attributes": {
    "Loc_name": "World",
    "MatchID": "AQFV9QAAmeQBAJUBBAAAAAAMD05FVyBZT1JLIFNUUkVFVBUDMzgwZgNFTkc",
    "Status": "M",
    "Score": 100,
    "Match_addr": "380 New York St, Redlands, California, 92373",
    "LongLabel": "380 New York St, Redlands, CA, 92373, USA",
    "ShortLabel": "380 New York St",
    "Addr_type": "PointAddress",
    "Type": "",
    "PlaceName": "",
    "Place_addr": "380 New York St, Redlands, California, 92373",
    "Phone": "",
    "URL": "",
    "Rank": 20,
    "AddBldg": "",
    "AddNum": "380",
    "AddNumFrom": "",
    "AddNumTo": "",
    "AddRange": "",
    "Side": "",
    "StPreDir": "",
    "StPreType": "",
    "StName": "New York",
    "StType": "St",
    "StDir": "",
    "BldgComp": "",
    "BldgType": "",
    "BldgName": "",
    "LevelType": "",
    "LevelName": "",
    "UnitType": "",
    "UnitName": "",
    "SubAddr": "",
    "StAddr": "380 New York St",
    "Block": "",
    "Sector": "",
    "Nbrhd": "",
    "District": "",
    "City": "Redlands",
    "MetroArea": "",
    "Subregion": "San Bernardino County",
    "Region": "California",
    "RegionAbbr": "CA",
    "Territory": "",
    "Zone": "",
    "Postal": "92373",
    "PostalExt": "8118",
    "Country": "USA",
    "CntryName": "United States",
    "LangCode": "ENG",
    "Distance": 0,
    "X": -117.195649834906,
    "Y": 34.057251584743,
    "DisplayX": -117.194790019279,
    "DisplayY": 34.057264995788,
    "Xmin": -117.195790019279,
    "Xmax": -117.193790019279,
    "Ymin": 34.056264995788,
    "Ymax": 34.058264995788,
    "ExInfo": "",
    "StrucType": "Commercial",
    "StrucDet": ""
   },
   "extent": {
    "xmin": -117.195790019279,
    "ymin": 34.056264995788,
    "xmax": -117.193790019279,
    "ymax": 34.058264995788
   }
  }
 ]
}

Search for standard intersections

An intersection is where two streets cross each other. An intersection search consists of the intersecting street names plus the containing administrative division or postal code. For example, redlands blvd and new york st 92373 is a valid intersection search, as is redlands blvd & new york st redlands ca . For street intersection matches, Addr_type=StreetInt .

The valid intersection connectors can be found by looking up the IntersectionConnectors property from the service info URL: https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer?f=pjson.

Single-field

More info

There are several types of intersections that can found by the ArcGIS Geocoding service. A typical simple intersection is formed by two street segments crossing each other. An example of this is W Park Ave and Tennessee St, Redlands, CA .

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&SingleLine=W Park Ave and Tennessee St, Redlands, CA&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "W Park Ave & Tennessee St, Redlands, California, 92373",
   "location": {
    "x": -117.200080508925,
    "y": 34.059249411365
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": -117.201080508925,
    "ymin": 34.058249411365,
    "xmax": -117.199080508925,
    "ymax": 34.060249411365
   }
  }
 ]
}

Multifield

1
 GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&Address=W Park Ave and Tennessee St&City=Redlands&Region=CA&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "W Park Ave & Tennessee St, Redlands, California, 92373",
   "location": {
    "x": -117.200080508925,
    "y": 34.059249411365
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": -117.201080508925,
    "ymin": 34.058249411365,
    "xmax": -117.199080508925,
    "ymax": 34.060249411365
   }
  }
 ]
}

Search for overpass intersections

You can also find intersections between streets that aren't physically connected. This includes cases where streets are separated by elevation, such as a highway overpass crossing over another street. An example of this is Pacific Hwy and W Washington St, San Diego, CA 92140 .

More info

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&SingleLine=Pacific Hwy and W Washington St, San Diego, CA 92140&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Pacific Hwy & W Washington St, San Diego, California, 92140",
   "location": {
    "x": -117.184382796839,
    "y": 32.740451997491
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": -117.185382796839,
    "ymin": 32.739451997491,
    "xmax": -117.183382796839,
    "ymax": 32.741451997491
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&Address=Pacific Hwy and W Washington St&City=San Diego&Region=CA&Postal=92140&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Pacific Hwy & W Washington St, San Diego, California, 92140",
   "location": {
    "x": -117.184382796839,
    "y": 32.740451997491
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": -117.185382796839,
    "ymin": 32.739451997491,
    "xmax": -117.183382796839,
    "ymax": 32.741451997491
   }
  }
 ]
}

Search for disconnected intersections

An intersection can also be formed by two disconnected streets when one street ends close to another, such as a cul-de-sac or a dead end. In cases such as this, if the streets are within a certain distance of each other, the ArcGIS Geocoding service returns a StreetInt match when they are searched for. This near-intersection tolerance is currently 60 meters. An example of this type of near-intersection is Knowlton St and Turner Ct, Somerville, Massachusetts, USA .

More info

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&SingleLine=Knowlton St and Turner Ct, Somerville, Massachusetts, USA&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Knowlton St & Turner Ct, Somerville, Massachusetts, 02145",
   "location": {
    "x": -71.086933487601,
    "y": 42.382329186603
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": -71.087933487601,
    "ymin": 42.381329186603,
    "xmax": -71.085933487601,
    "ymax": 42.383329186603
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&Address=Knowlton St and Turner Ct&City=Somerville&Region=Massachusetts&CountryCode=USA&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Knowlton St & Turner Ct, Somerville, Massachusetts, 02145",
   "location": {
    "x": -71.086933487601,
    "y": 42.382329186603
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": -71.087933487601,
    "ymin": 42.381329186603,
    "xmax": -71.085933487601,
    "ymax": 42.383329186603
   }
  }
 ]
}

Search for roundabout intersections

Another type of disconnected intersection supported by the ArcGIS Geocoding service occurs at roundabouts. A roundabout is formed when two or more streets connect to a circular roadway, which is often unnamed. The participating streets typically don't connect directly to each other, but when they are searched for and are within the near-intersection tolerance, the service returns a StreetInt match. An example of a roundabout intersection is Rue Jean Laurent & Avenue Jean Mermoz, Le Vésinet, FRA .

More info

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&SingleLine=Rue Jean Laurent and Avenue Jean Mermoz, Le Vésinet, FRA&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Rue Jean Laurent & Avenue Jean Mermoz, 78110, Le Vésinet, Yvelines, Île-de-France",
   "location": {
    "x": 2.134517483476,
    "y": 48.895231987767
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": 2.133517483476,
    "ymin": 48.894231987767,
    "xmax": 2.135517483476,
    "ymax": 48.896231987767
   }
  }
 ]
}

Multifield

1
GET https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type&forStorage=false&Address=Rue Jean Laurent & Avenue Jean Mermoz&City=Le Vésinet&CountryCode=FRA&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Rue Jean Laurent & Avenue Jean Mermoz, 78110, Le Vésinet, Yvelines, Île-de-France",
   "location": {
    "x": 2.134517483476,
    "y": 48.895231987767
   },
   "score": 100,
   "attributes": {
    "Addr_type": "StreetInt"
   },
   "extent": {
    "xmin": 2.133517483476,
    "ymin": 48.894231987767,
    "xmax": 2.135517483476,
    "ymax": 48.896231987767
   }
  }
 ]
}

Find an ambiguous intersection

Sometimes there may be multiple possible matches for an intersection search. This typically occurs when divided roads cross each other. A divided road consists of two street segments separated by a median. In a scenario such as this, there could be up to four equivalent intersection matches consisting of the same street names at different locations. The ArcGIS Geocoding service uses an ambiguous intersection tolerance with such searches to remove redundant intersection candidates from the response. The ambiguous intersection tolerance is currently 30 meters. Specifically, if there are multiple intersection candidates with the same street names that are located in the same locality (meaning same neighborhood, city, postal code), and if they are within 30 meters of each other, the service returns only one of the candidates.

More info

An example of an ambiguous intersection search is Cambie St and W King Edward Ave, Vancouver, British Columbia . Both Cambie St and W King Edward Ave are divided streets, so there are four potential intersection candidates with the same street names. However, there is a boundary between the neighborhoods of South Cambie and Riley Park which happens to follow the middle of Cambie St. Because of this, there are actually two sets of equivalent intersections—one within South Cambie (on left side of Cambie St) and the other within Riley Park (on the right side of Cambie St). The locations of the potential intersection candidates in each set are within the ambiguous intersection distance from each other, so two intersection candidates are returned in the response for this search—one in South Cambie, and the other in Riley Park.

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type,Nbrhd&forStorage=false&SingleLine=Cambie St and W King Edward Ave, Vancouver, British Columbia&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Cambie St & King Edward Ave W, Vancouver, British Columbia, V5Z",
   "location": {
    "x": -123.115292006692,
    "y": 49.248915989533
   },
   "score": 99.96,
   "attributes": {
    "Addr_type": "StreetInt",
    "Nbrhd": "Riley Park"
   },
   "extent": {
    "xmin": -123.116292006692,
    "ymin": 49.247915989533,
    "xmax": -123.114292006692,
    "ymax": 49.249915989533
   }
  },
  {
   "address": "Cambie St & King Edward Ave W, Vancouver, British Columbia, V5Z",
   "location": {
    "x": -123.115300891509,
    "y": 49.249055967317
   },
   "score": 99.96,
   "attributes": {
    "Addr_type": "StreetInt",
    "Nbrhd": "Riley Park"
   },
   "extent": {
    "xmin": -123.116300891509,
    "ymin": 49.248055967317,
    "xmax": -123.114300891509,
    "ymax": 49.250055967317
   }
  },
  {
   "address": "Cambie St & King Edward Ave W, Vancouver, British Columbia, V5Z",
   "location": {
    "x": -123.115498033872,
    "y": 49.248924036161
   },
   "score": 99.96,
   "attributes": {
    "Addr_type": "StreetInt",
    "Nbrhd": "South Cambie"
   },
   "extent": {
    "xmin": -123.116498033872,
    "ymin": 49.247924036161,
    "xmax": -123.114498033872,
    "ymax": 49.249924036161
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?f=pjson&outFields=Addr_type,Nbrhd&forStorage=false&Address=Cambie St and W King Edward Ave&City=Vancouver&Region=British Columbia&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Cambie St & King Edward Ave W, Vancouver, British Columbia, V5Z",
   "location": {
    "x": -123.115292006692,
    "y": 49.248915989533
   },
   "score": 99.96,
   "attributes": {
    "Addr_type": "StreetInt",
    "Nbrhd": "Riley Park"
   },
   "extent": {
    "xmin": -123.116292006692,
    "ymin": 49.247915989533,
    "xmax": -123.114292006692,
    "ymax": 49.249915989533
   }
  },
  {
   "address": "Cambie St & King Edward Ave W, Vancouver, British Columbia, V5Z",
   "location": {
    "x": -123.115300891509,
    "y": 49.249055967317
   },
   "score": 99.96,
   "attributes": {
    "Addr_type": "StreetInt",
    "Nbrhd": "Riley Park"
   },
   "extent": {
    "xmin": -123.116300891509,
    "ymin": 49.248055967317,
    "xmax": -123.114300891509,
    "ymax": 49.250055967317
   }
  },
  {
   "address": "Cambie St & King Edward Ave W, Vancouver, British Columbia, V5Z",
   "location": {
    "x": -123.115498033872,
    "y": 49.248924036161
   },
   "score": 99.96,
   "attributes": {
    "Addr_type": "StreetInt",
    "Nbrhd": "South Cambie"
   },
   "extent": {
    "xmin": -123.116498033872,
    "ymin": 49.247924036161,
    "xmax": -123.114498033872,
    "ymax": 49.249924036161
   }
  }
 ]
}

Search for POIs

A POI is a point location that can represent a cultural or geographic landmark, business, or administrative division. For example, you can find amusement parks, museums, schools, restaurants, hotels, gas stations, or other types of businesses or landmarks; geographic features, such as mountains, lakes, rivers, or deserts; or administrative places, such as neighborhoods, cities, states, counties, or countries. The findAddressCandidates operation supports geocoding POIs by name or by type. The supported types are listed in this table.

Find a business name

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?SingleLine=starbucks sydney AUS&outFields=type,city,region&maxLocations=1&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Starbucks",
   "location": {
    "x": 151.2067464,
    "y": -33.8723561
   },
   "score": 100,
   "attributes": {
    "type": "Coffee Shop",
    "city": "Sydney",
    "region": "New South Wales"
   },
   "extent": {
    "xmin": 151.2017464,
    "ymin": -33.8773561,
    "xmax": 151.2117464,
    "ymax": -33.8673561
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?Address=starbucks&Neighborhood=&City=sydney&Subregion=&Region=&CountryCode=AUS&outFields=type,city,region&maxLocations=1&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Starbucks",
   "location": {
    "x": 151.2067464,
    "y": -33.8723561
   },
   "score": 100,
   "attributes": {
    "type": "Coffee Shop",
    "city": "Sydney",
    "region": "New South Wales"
   },
   "extent": {
    "xmin": 151.2017464,
    "ymin": -33.8773561,
    "xmax": 151.2117464,
    "ymax": -33.8673561
   }
  }
 ]
}

Find a business type

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?SingleLine=hotels orlando FL&outFields=type,city,region&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Disney's Art of Animation Resort",
   "location": {
    "x": -81.5484489,
    "y": 28.3504096
   },
   "score": 100,
   "attributes": {
    "type": "Hotel",
    "city": "Orlando",
    "region": "Florida"
   },
   "extent": {
    "xmin": -81.5534489,
    "ymin": 28.3454096,
    "xmax": -81.5434489,
    "ymax": 28.3554096
   }
  }
 ]
}

Find a business on a specific street

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?singleLine=starbucks 5th ave san diego&langCode=&outFields=Place_Name,Place_addr,Phone,Type,Addr_type&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "Starbucks",
   "location": {
    "x": -117.159904,
    "y": 32.707748
   },
   "score": 100,
   "attributes": {
    "Addr_type": "POI",
    "Type": "Coffee Shop",
    "Place_addr": "209 5th Ave, San Diego, California, 92101",
    "Phone": "(619) 234-0749"
   },
   "extent": {
    "xmin": -117.160904,
    "ymin": 32.706748,
    "xmax": -117.158904,
    "ymax": 32.708748
   }
  },
  {
   "address": "Starbucks",
   "location": {
    "x": -117.160513,
    "y": 32.731089
   },
   "score": 100,
   "attributes": {
    "Addr_type": "POI",
    "Type": "Coffee Shop",
    "Place_addr": "2440 5th Ave, San Diego, California, 92101",
    "Phone": "(619) 702-2113"
   },
   "extent": {
    "xmin": -117.161513,
    "ymin": 32.730089,
    "xmax": -117.159513,
    "ymax": 32.732089
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?address=starbucks&address2=5th ave&city=san diego&outFields=Place_Name,Place_addr,Phone,Type,Addr_type&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
{
"spatialReference": {
 "wkid": 4326,
 "latestWkid": 4326
},
"candidates": [
 {
  "address": "Starbucks",
  "location": {
   "x": -117.159904,
   "y": 32.707748
  },
  "score": 100,
  "attributes": {
   "Addr_type": "POI",
   "Type": "Coffee Shop",
   "Place_addr": "209 5th Ave, San Diego, California, 92101",
   "Phone": "(619) 234-0749"
  },
  "extent": {
   "xmin": -117.160904,
   "ymin": 32.706748,
   "xmax": -117.158904,
   "ymax": 32.708748
  }
 },
 {
  "address": "Starbucks",
  "location": {
   "x": -117.160513,
   "y": 32.731089
  },
  "score": 100,
  "attributes": {
   "Addr_type": "POI",
   "Type": "Coffee Shop",
   "Place_addr": "2440 5th Ave, San Diego, California, 92101",
   "Phone": "(619) 702-2113"
  },
  "extent": {
   "xmin": -117.161513,
   "ymin": 32.730089,
   "xmax": -117.159513,
   "ymax": 32.732089
  }
 }
]
}

Search for administrative place names

The findAddressCandidates operation supports single-field and multifield searches for administrative place-names. This includes searches for neighborhoods, cities, counties, states, provinces, or countries. If a search for a city name results in multiple matches with the same name, the ArcGIS Geocoding service will sort the candidates in order of their relative importance to each other (as indicated by the value of the Rank output field), with priority generally based on population and capital status.

Find a city name

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?SingleLine=San Francisco&forStorage=false&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "San Francisco, California",
   "location": {
    "x": -122.4201615,
    "y": 37.7800771
   },
   "score": 100,
   "attributes": {

   },
   "extent": {
    "xmin": -122.7151615,
    "ymin": 37.4850771,
    "xmax": -122.1251615,
    "ymax": 38.0750771
   }
  },
  {
   "address": "San Francisco, Agusan Del Sur, Caraga",
   "location": {
    "x": 125.978219,
    "y": 8.5025332
   },
   "score": 100,
   "attributes": {

   },
   "extent": {
    "xmin": 125.856219,
    "ymin": 8.3805332,
    "xmax": 126.100219,
    "ymax": 8.6245332
   }
  }
 ]
}

Multifield

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?address=San Francisco&f=pjson&token=<ACCESS_TOKEN>

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
{
 "spatialReference": {
  "wkid": 4326,
  "latestWkid": 4326
 },
 "candidates": [
  {
   "address": "San Francisco, California",
   "location": {
    "x": -122.4201615,
    "y": 37.7800771
   },
   "score": 100,
   "attributes": {

   },
   "extent": {
    "xmin": -122.7151615,
    "ymin": 37.4850771,
    "xmax": -122.1251615,
    "ymax": 38.0750771
   }
  },
  {
   "address": "San Francisco, Agusan Del Sur, Caraga",
   "location": {
    "x": 125.978219,
    "y": 8.5025332
   },
   "score": 100,
   "attributes": {

   },
   "extent": {
    "xmin": 125.856219,
    "ymin": 8.3805332,
    "xmax": 126.100219,
    "ymax": 8.6245332
   }
  }
 ]
}

Search for a city in a state

Single-field

1
GET https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?SingleLine=oxford OH&forStorage=false&f=pjson&token=<ACCESS_TOKEN>