NatLabRockies / NatLabRockies/developer.nlr.gov
API Rate Key Limits
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 60
- Forks
- 57
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
We are trying to access the BC-HRRR CONUS Wind Toolkit via HSDS using h5pyd/rex.
Dataset:
/nrel/wtk/bchrrr/v1.0.0/bchrrr_conus_2023.h5
Endpoint:
https://developer.nlr.gov/api/hsds
Observed behavior:
HSDS dataset open returns HTTP 429 Too Many Requests.
X-Ratelimit-Limit: 100000
X-Ratelimit-Remaining: 0
Retry-After: ~1900 seconds
Unexpected behavior:
A lightweight authenticated request to /api/hsds/about returns 200 and shows substantial X-Ratelimit-Remaining, but opening the actual BC-HRRR HSDS dataset returns 429. We also saw the same behavior after rotating to a fresh API key. When I tried to submit a comment through the Contact Us form in the NLR developer webpage, I also get a message that too many rate limits have been hit.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the authenticated request to /api/hsds/about and the BC-HRRR dataset open using h5pyd/rex, comparing their rate-limit headers and Retry-After responses. Determine why the dataset request and Contact Us form report exhausted limits despite the lightweight request showing remaining capacity; done means the cause and corrective action are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100