-
Notifications
You must be signed in to change notification settings - Fork 101
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
Invalid longitude error if bounding box contains a zero #325
Comments
Hello @dbaston! Thanks for reporting this. We're actually in the process of improving our spatial input handling (#322) to address #321 and several other issues (e.g. for inputs that cross the dateline). @sjh1024, perhaps we could add this as a test case? I'd have to dig in a bit more to try and figure out why the NSIDC API doesn't like the submitted query - it may be that their API cannot handle the scientific notation for coordinate input. I will investigate this more next week after I return from a conference this week. |
Thank you for reporting this! I will add this test case + discuss a potential fix with Jessica this week. |
Trying to query with the bounding box
(0, 0, 1, 1)
throws the following error:This is apparently because
np.sign(0) != np.sign(1)
. If I try to nudge the bounding box to avoid the error, with(1e-6, 1e-6, 1, 1)
I get:The text was updated successfully, but these errors were encountered: