Closed laurenkwick closed 4 months ago
The issue seems to be on PC's side of things; for instance, here's a valid STAC item: https://planetarycomputer.microsoft.com/api/stac/v1/collections/alos-fnf-mosaic/items/N37W082_16_FNF
But if you scroll down to the "assets" and click the link for C, you get an error message: https://pceo.blob.core.windows.net/palsar/alos_fnf_mosaic/N37W082_16_C_F02DAR.tif
I opened a discussion on the Planetary Computer repo to see what's up, but I have no idea if/when those assets will get restored: https://github.com/microsoft/PlanetaryComputer/discussions/367
Now that said: rsi should give you the data that it could download anyway; that's why this is a warning and not an error in the code. I'll try and fix that issue.
Ah okay, that makes sense for why I was running into some trouble. Thank you for opening that discussion!
I'm marking this as closed because the rsi bit of the issue -- the entire download failing when only some assets couldn't be downloaded -- is now fixed in #75. Thank you so much for opening the issue -- your examples made this one pretty easy to debug!
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
Hello!
Everything with the package is amazing so far. I am having some trouble with accessing the ALOS FNF dataset using the
get_stac_data
function. I've spent some time debugging this, but am currently feeling stuck.To access ALOS FNF data from the planetary computer, I am running this code:
After attempting to run, I am seeing these errors:
I know that
rsi
uses somerstac
functionality to access the data, so I tried to download the ALOS FNF dataset using exclusivelyrstac
to make sure there wasn't something funky happening there:The
stars
package was able to read in and plot the data. I then looked into thersi
source code, found thedownload_function
which calls to the "Failed to download" error I was seeing:I manually replicated the
sf::gdal_utils
function outside of my script, using thefnf_urls
variable from before to see if the utility failed outside of the code. However, I was able to successfully run the gdal warps utility manually.I'm wondering if the
url
variable within the source code gets impacted in some way before thegdal_utils
function is called. Maybe it's something to do with the PC signing that is unique to the ALOS FNF dataset? I haven't had any other issues usingget_stac_data
for other PC datasets like ESA Worldcover, for example, so it's just a bit strange that it's happening with this dataset.Let me know if there is anything you would like for me to try, and thank you so much for all the work you've put into
rsi
!!!