NatLabRockies / NatLabRockies/gradeit
USGS web API rate limiting
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Query rate limiting by the usgs web api is the likely cause of intermittent and unpredictable errors when using the web api data source. This could be solved with a wait command in the loop when querying the api for every points. Additionally, could email usgs elevation point query service help to determine the precise rate limit.
This is lower priority since any highly performant application of GradeIT will require a local verison of the USGS DEM database.
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
Locate the loop that queries the USGS web API for each point and inspect how the web API data source handles intermittent errors. Determine the service's precise rate limit, including by contacting the USGS elevation point query service help if needed, then define completion as preventing rate-limit failures without disrupting point processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100