Hi,
we seem to have problems accessing global vegetation data (https://lpdaac.usgs.gov/products/mod13a3v061/) using the AppEEARS Cloud API according to https://lpdaac.usgs.gov/news/a%CF%81%CF%81eears-is-in-the-cloud-now/.
Using the previous ("non-cloud") approach, we used to request the dataset mod13a3v061 successfully for the whole possible area (the entire globe) as one single dataset (using "coordinates": [[[-180.0, -90.0], [-180.0, 90.0], [180.0, 90.0], [180.0, -90.0], [-180.0, -90.0]]]).
We are noticing that for such a request, the task now ends as successfully completed, but no dataset/file is returned anymore (neither geotiff nor netcdf4). However, areas smaller than the entire globe do return a correct dataset for download.
Can anyone confirm this issue? Is this a data size challenge, and what would be the best approach for the requirement to access global data? Many thanks in advance.
Unsuccessful attempts to download global vegetation data mod13a3v061 using Cloud API
-
- User Services
- Posts: 345
- Joined: Mon Sep 30, 2019 12:39 pm America/New_York
- Has thanked: 10 times
Re: Unsuccessful attempts to download global vegetation data mod13a3v061 using Cloud API
We apologize for the delayed response. We have forwarded your inquiry to our Subject Matter Expert for assistance.
-
- Subject Matter Expert
- Posts: 71
- Joined: Tue Nov 12, 2019 4:02 pm America/New_York
- Been thanked: 3 times
Re: Unsuccessful attempts to download global vegetation data mod13a3v061 using Cloud API
@sclare ,
Thank you for reaching out, and we apologize for the inconvenience. The behavior you described appears to be a bug, and it looks like it has existed since before our cloud deployment. We’ve recorded the problem and will be looking into a solution. In the meantime, you can break up your single request into two requests. We’ve had success with submitting a request for the eastern and western hemispheres. Thank you for your patience.
Thank you for reaching out, and we apologize for the inconvenience. The behavior you described appears to be a bug, and it looks like it has existed since before our cloud deployment. We’ve recorded the problem and will be looking into a solution. In the meantime, you can break up your single request into two requests. We’ve had success with submitting a request for the eastern and western hemispheres. Thank you for your patience.