-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for searching for addresses that do not show up in Address Point data #707
Comments
@gregbunce can we look into this address for geocoding? |
I don't think that 802 West 100 South is a good address. I checked in google maps and didn't see it. The closest that I found was 804 W. |
@stdavis Can expand on, "geocoding addresses that are not found in the address point data"? |
I don't think that I was very clear. This is not a geocoding issue. @gregbunce I don't think that there is anything that you need to check on this issue. The project does not geocode at the moment. It just auto-completes using address point data. The fix is for me to add geocoding to this project. |
Another address issue reported:
Acknowledgement: The address in the PST data is not the same as the source data for the search. The solution still stands to add geocoding to the project. |
More addresses from Michelle:
|
Yes, that is expected. Currently, this app auto-completes with address points only. It needs to be updated to use masquerade for autocomplete and geocoding if nothing is selected. |
🥳 This issue is included in v2.0.17 |
Michelle reported an issue with a user not being able to find this address: 802 West 100 South, SLC
This is an address that shows up in DEQ data.
To fix this, we could use masquerade for typeahead as well as geocoding addresses that are not found in the address point data.
The text was updated successfully, but these errors were encountered: