Replies: 1 comment 1 reply
-
Interesting, I remember the antimeridian being a problem with some datasets. Let us take a look and see if a) the metadata is wrong, or b) the code should split queries that cross the anteimeridian into 2 bboxes. Thanks for reporting this @danbroman |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using earthaccess to find and download VIIRS snow data (see the call above). This search returns the h10v03 graticule (VIIRS uses the MODIS tile grid) which is what I want. It also returns the h20v01 graticule which I don't want. I suspect it's because the second graticule crosses the antimeridian:
Minimum Longitude: -128.8568
Maximum Longitude: 95.6578
Minimum Latitude: 39.828
Maximum Latitude: 79.533
This graticule does not fall within my bounding box. Have others had this issue, and is there a workaround?
Beta Was this translation helpful? Give feedback.
All reactions