You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2021. It is now read-only.
Going to re-open this. I think we've been misusing the findAddressCandidates endpoint. From the description:
The findAddressCandidates operation geocodes one location per request
It is meant to transform a well formed address into a point or polygon. We are using it for this, but we're also using for auto-completion. It's not very good at this. Here's a quick gif of my making multiple requests w/ insomnia - you can see it cuts out in the middle, and only gives me useful auto completions once I've correctly typed in most of my address:
Something like the Google Autocomplete API is purpose built for this, and should be used instead (plus it comes w/ a nice widget). In the meantime, we should disable auto-completion and just have an error message that says "We couldn't find your address" or something.
mshenfield
changed the title
As an API client, I want to get canonical address candidates for a given address, so that I can pick an address recognized by the Nashville Metro parcel data services
As a user, I want a reliable source of address autocompletion to help me pick a valid address.
Apr 1, 2018
Just want to note that whatever we build, we'll need to provide the coordinates the our autocompletion API resolves to using Web Mercator coordinates (wkid 3857),
Acceptance criteria:
The text was updated successfully, but these errors were encountered: