Skip to content
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

"cannot resolve address" on primary address #31

Open
wstlabs opened this issue Jul 21, 2017 · 1 comment
Open

"cannot resolve address" on primary address #31

wstlabs opened this issue Jul 21, 2017 · 1 comment
Labels

Comments

@wstlabs
Copy link
Collaborator

wstlabs commented Jul 21, 2017

Recently observed cases where the BBL is recognized, but an address search on the primary address (that is, the pluto address) fails, for the reason given (after the address)

3039720012 - 259 Essex Street, Brooklyn, NY, United States - "[malformed response from geoclient]"

@wstlabs wstlabs added the bug label Jul 22, 2017
@wstlabs
Copy link
Collaborator Author

wstlabs commented Jul 22, 2017

While ultimately a bug from the user's perspective, in any case this issue appears to derive from a bug in geoclient, so there's not much we can do.

What's happening is that Geoclient is telling us, in either the 'message' or 'message2' field (it seems to vary):

'message2': 'ADDRESS NUMBER OUT OF RANGE',

When in fact the address is in range (and seems to correspond to the lot, according to the digital taxmap. So there may not be much we can do, for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant