developer.nrel.gov icon indicating copy to clipboard operation
developer.nrel.gov copied to clipboard

nsrdb-GOES-conus-v4-0-0 not working?

Open williamhobbs opened this issue 2 months ago • 7 comments

PSM4 CONUS (GOES CONUS v4) appears to not be working. E.g.,

https://developer.nrel.gov/api/nsrdb/v2/solar/nsrdb-GOES-conus-v4-0-0-download.csv?wkt=POINT(-80.00%2040.00)&attributes=ghi&names=2018&utc=false&leap_day=true&email=YOUR_EMAIL&api_key=DEMO_KEY

(after changing email and key)

returns

{
  "inputs": {
    "body": {

    },
    "params": {

    },
    "query": {
      "wkt": "POINT(-80.00 40.00)",
      "attributes": "ghi",
      "names": "2018",
      "utc": "false",
      "leap_day": "true",
      "email": "[email protected]"
    }
  },
  "metadata": {
    "version": "2.0.0"
  },
  "status": 400,
  "errors": [
    "Data processing failure."
  ]
}

See https://github.com/pvlib/pvlib-python/discussions/2587.

williamhobbs avatar Oct 31 '25 17:10 williamhobbs

cc @PjEdwards

kandersolar avatar Oct 31 '25 18:10 kandersolar

I am experiencing the same issue. Even using the provided example from the documentation, the request fails with error "Data processing failure".

jessemilam avatar Nov 03 '25 18:11 jessemilam

OK I see the problem. The years 2018, 2019, and 2020 are giving an authorization error in the AWS side of the stack. I'm working with the team that manages our data in AWS to get a resolution.

FWIW 2021-2024 are working fine.

I'll report back when we get this resolved.

PjEdwards avatar Nov 03 '25 19:11 PjEdwards

Thanks, @PjEdwards. Also FWIW, AWS was returning unexpected rate limit errors last week for ECMWF’s S3 bucket. I wonder if the issues are in some way related.

https://github.com/blaylockbk/Herbie/discussions/487

williamhobbs avatar Nov 03 '25 19:11 williamhobbs

I will say it is really weird that this issue would just show up on a Thursday afternoon. AFAIK we don't ever manipulate the permissions on those S3 buckets except when we're setting up new datasets the first time.

PjEdwards avatar Nov 03 '25 22:11 PjEdwards

The evidence of that is in the fact that to get these fixed we have to contact the special NREL representative who works with AWS to manage these public data buckets! That's why the fix is taking a non-trivial amount of time even though setting an ACL on the bucket is the work of seconds.

PjEdwards avatar Nov 03 '25 22:11 PjEdwards

Tuesday morning update... the permissions issue was a red herring. The underlying cause is some corrupt data in S3. Unfortunately this means re-uploading the entire dataset which is a multi-day process. I would guess we should have these up my Monday, but that isn't a guarantee.

PjEdwards avatar Nov 04 '25 14:11 PjEdwards

Friday morning update... 2018 - 2021 are working now. 2022 - 2024 are still reloading.

PjEdwards avatar Nov 07 '25 14:11 PjEdwards

Final reloading is complete. I had to manually clear some caches and now it looks to me like everything is back to nominal. Please let me know if you continue to have access issues! Otherwise I'll close the ticket after a day or so.

PjEdwards avatar Nov 13 '25 00:11 PjEdwards