Closed wildintellect closed 11 months ago
I've checked the DOI has not changed, the versions being requested are accurate.
@jjfrench found at least one major cause, we're releasing a new version of GEDI Subsetter 0.6.2 that updates the maap-py
version. In testing this is working to solve MAAP API timeout errors. We haven't hit the 403 error yet, so we'll need user help to find some jobs that reliably trigger that issue. See more https://github.com/MAAP-Project/gedi-subsetter/pull/55
New version should be registered in the MAAP ADE soon.
Interesting - I ran
inputs = dict(
aoi="https://maap-ops-workspace.s3.amazonaws.com/shared/pbasak/Peru/Ecoregions/Central_Andean_puna.gpkg",
doi="L4A",
lat="lat_lowestmode",
lon="lon_lowestmode",
beams="all",
columns="agbd, agbd_se, sensitivity, geolocation/sensitivity_a2",
query="l2_quality_flag == 1 and l4_quality_flag == 1 and sensitivity > 0.95 and `geolocation/sensitivity_a2` > 0.95",
limit=0,
temporal="-",
output="gedi_subset"
)
Locally in the ADE, worked just fine
Most recent run in the DPS job returns 500 though 🤔 Different error code though, so progress?
Just ran it again... no error. Intermittent erroring out, that doesn't sound fun.
Closing - it looks as if this was the majority fix. Will open another ticket if we continue to encounter 500's for a different related issue.
Describe the bug GEDI Subsetter is failing to access L4A data from ORNL with 403 forbidden. Reported by user @pbasak
To Reproduce Run a GEDI subsetter job
example aoi
https://maap-ops-workspace.s3.amazonaws.com/shared/pbasak/Peru/Ecoregions/Bolivian_Yungas.gpkg
Additional context See also recent issue
874