-
Notifications
You must be signed in to change notification settings - Fork 17
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
Nicer error reporting when geocoder fails #55
Comments
I tried a simple fix for this
but getting issues with the
@felix-schott can you try reproducing please? |
Hi @mtravis - not on my laptop at the moment, so can't reproduce but I'm guessing it might be because the programme is not exiting and because the geocoding is unsuccessful, the programme continues and expects a geometry instead of None where it raises the error. try-except is the right approach to suppress the long error message, but we need to exit the programme immediately afterwards. A similar thing happens here - maybe copy that approach? The empty return terminates the programme. (On Linux, it would be better to use sys.exit(1) instead of an empty return but I'm not sure how that behaves on other platforms, so just use the empty return.) |
I'd also print a more meaningful error message: "No results found for {location} - please try a different search term." Otherwise users don't know what's happening. |
Actually, sorry, you will have to use sys.exit or raise an exception since return will only exit the helper function, not the whole programme. It might be cleaner to return None from the geocoding function if no result could be found, and then use the empty return approach in the calling function |
I've got it working with sys.exit but will try implementing the return None and updating the calling function later. My error message is sensible looking once it calls the internal message from the event. |
@felix-schott I'm struggling a bit with to get the script to exit fully without sys.exit(1). I agree it would be cleaner not to use this method but can't get download_buildings to work. |
When I request a location with
--location
and it doesn't have results I get a barfed stack trace:It'd be better to catch the error and just inform users that their location string didn't work - they can get the geojson on their own or try a more common string.
The text was updated successfully, but these errors were encountered: