Select to view content in your preferred language

REST World Geocoding Service not returning Subaddress info

236
1
Jump to solution
3 weeks ago
Labels (1)
KyliaHilton
New Contributor

I'm using the World Geocoding Service REST API /suggest endpoint to try and obtain subaddress information. I'm setting the subaddressAfterBaseAddress parameter equal to true and sending a base address like this: 

https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/suggest?text=4141 NW Expressway, Oklahoma City, OK 73116&category=Address&subaddressAfterBaseAddress=true&token=<YOUR_TOKEN>&f=pjson

I get the following response:

{\n \"suggestions\": [\n  {\n   \"text\": \"4141 NW Expressway, Oklahoma City, OK, 73116, USA\",\n   \"magicKey\": \"MAGIC_KEY\",\n   \"isCollection\": false\n  }\n ]\n}

I've tried the same address with a suite number:

https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/suggest?text=4141 NW Expressway, Suite 200, Oklahoma City, OK 73116&category=Address&subaddressAfterBaseAddress=true&token=<YOUR_TOKEN>&f=pjson

{\n \"suggestions\": [\n  {\n   \"text\": \"4141 NW Expressway, #200, Oklahoma City, OK, 73116, USA\",\n   \"magicKey\": \"MAGIC_KEY\",\n   \"isCollection\": false\n  }\n ]\n}

So there is clearly at least one suite to return. Am I doing something incorrectly? Any help would be greatly appreciated!
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
BradNiemand
Esri Regular Contributor

You are doing everything correctly on your side.

It looks like there are a small number of cases where this can happen currently.  We will look into filling this gap for a future release.

Brad

View solution in original post

1 Reply
BradNiemand
Esri Regular Contributor

You are doing everything correctly on your side.

It looks like there are a small number of cases where this can happen currently.  We will look into filling this gap for a future release.

Brad