Geocode Error

Question

We have a corporate geocode service that it accessed across a number of portals and all are having issues when uploading a CSV.

Some records in CSV are not being matched due to either that the address does not exist or data issues. For example  1 Johnston St, WINDSOR does not exist in data.  1 W Portland Rd, SACKVILLE Should be 1 WEST Portland Rd

There seems to be a mismatch in the way that Portal is undertaking the suggestions.

* If I use the manual address find tool, I get a match (after data editing)

The URL for the following search is as follows

https://...../GeocodeServer/suggest?f=json&text=WEST%20PORTLAND%20RD%2C%20SACKVILLE%20NSW%202756&maxSuggestions=6&location=%7B%22x%22%3A16794313.136714328%2C%22y%22%3A-3962511.967191963%2C%22spatialReference%22%3A%7B%22wkid%22%3A102100%2C%22latestWkid%22%3A3857%7D%7D&distance=50000&callback=dojo_request_script_callbacks.dojo_request_script70

If I use the review process when loading the CSV the URL is as following

https://...../GeocodeServer/findAddressCandidates?SingleLine=1%20Johnston%20St%2C%20WINDSOR&f=json&outSR=%7B%22wkid%22%3A102100%2C%22latestWkid%22%3A3857%7D&outFields=*&callback=dojo_request_script_callbacks.dojo_request_script128

This case returns a 400 error.

Not sure why the find address tool is using the 'suggest' option but the review is using the 'findAddressCandidate'

Any help would be very much appreciated.

Regards

Dean

ChristaHash · Answer

Hi Dean, the magicKey is generated as part of the output of the suggest request, and is basically just a key we generate to link a suggestion to a record in the data used to build the locator:

dojo_request_script_callbacks.dojo_request_script70(
     {"suggestions":[
          {"text":"1 WEST PORTLAND RD, SACKVILLE NSW 2756","magicKey":"GANSW705879336","isCollection":false
          },
          {"text":"34 WEST PORTLAND RD, SACKVILLE NSW 2756","magicKey":"GANSW706501063","isCollection":false
          },
          {"text":"74 WEST PORTLAND RD, SACKVILLE NSW 2756","magicKey":"GANSW706501060","isCollection":false
          },
          {"text":"93 WEST PORTLAND RD, SACKVILLE NSW 2756","magicKey":"GANSW705892850","isCollection":false
          },
          {"text":"96 WEST PORTLAND RD, SACKVILLE NSW 2756","magicKey":"GANSW706524225","isCollection":false
          }]
     });

So when if you generate suggestions and choose one to use for search (findAddressCandidates), you can pull the magicKey and matching input text from the suggestion you choose.

DeanHowell1 · Answer

Thanks @ChristaHash , how is the 'MagicKey' generated?

ChristaHash · Answer

Hi Dean, in order to make use of a suggest result in a findAddressCandidates request, you will need to pass one extra parameter (magicKey). When I grab the magicKey from your suggest result and add it into your findAddressCandidates request, I get the following:

https://7cizrcsygj.execute-api.ap-southeast-2.amazonaws.com/UAT/NSWPoint/GeocodeServer/findAddressCandidates?SingleLine=1%20Johnston%20St%2C%20WINDSOR&magicKey=GANSW706501063&f=json&outSR=%7B%22wkid%22%3A102100%2C%22latestWkid%22%3A3857%7D&outFields=*&callback=dojo_request_script_callbacks.dojo_request_script128

You can think of a findAddressCandidates request as accepting either a text string or a suggest result object (the object containing both a text string attribute and a magicKey attribute, which helps our engine find the exact suggestion you're looking for). Please let me know if this helps or if you have additional questions. -Christa