-
Notifications
You must be signed in to change notification settings - Fork 5
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
Addresses using "#" for apartment number aren't matching #95
Comments
It is only related to 46 in the sense that we do not use unit numbers when geocoding currently. You could remove them as you will get the same result with or without it as you noted above. But to address the underlying issue you are experiencing, there are certain characters that have special meaning in urls and therefore need to be encoded to not confuse the browser and api. Read about it on stack overflow and then encode the values being sent to the api and you should be good to go. |
Ok, yeah, that explains it. I guess atlas.utah.gov was throwing me off because I was seeing the same behavior there, so I assumed it was something to do with the geocoder itself. |
ok then we should open an issue on https://github.com/agrc-widgets/dart-board/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc |
I opened an issue in agrc-widgets/dart-board... |
Addresses that use a number sign ("#") to specify the apartment number don't seem to generate a match.
Random example:
It seems like the "#" is throwing the locator off completely. In a set of 1000 addresses, 36 had a Utah address with a "#" sign in the street field and none of them geocoded. Perhaps this is related to or could be fixed with #46?
The text was updated successfully, but these errors were encountered: