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
Opencage lookup broken #292
Comments
Also another question, before if I did the following:
It would just print None if there wasn't a result. Now it gives an error and I have to first do:
is this the new intended behavior? |
Hi @nyejon ,
Could you please provide the initial call you made (to allow me to reproduce) and the full stack (I can't see enough in your first message to diagnostic)
nope. We wanted to be backward compatible. And this problem is fore sure a general one from base.py line 597. This one is straightforward to fix (return None instead of raising an exception). I am therefore waiting on your feedback for the first one before making a PR to correct all of it. Cheers, |
Hi, I think it is just that there is no 'bounds' in many of the opencage json responses. I am not even trying to use the bbox attribute, I think it is something to do with the:
One of the lookups that provides the error is: 'AirportClinic M - MediCare Flughafen München Medizinisches Zentrum'. It returns a value, but it is the wrong location (it doesn't really find it). Some of the json responses returns the 'bounds' if it is an exact lookup and then there is no error. |
Should be fixed with PR #293. Could you check that it solves all your issues ? (with the branch fix_opencage) |
Thanks for the effort. It unfortunately still has an error:
|
I should have added a test case for this call ... it now passes on my side. Could you check again ? |
Merged into master by Denis 👍 |
Thanks, tested this morning and all seems to be working again! |
Hi,
The Opencage lookup seems to be broken again. I get the following error:
I can solve it by putting a try, except around the bit:
but I'm not sure that that is the best solution... :)
I'm not sure how the new multiple search results have changed things and if it will be a general error, or only an error with opencage.
The text was updated successfully, but these errors were encountered: