Public-Environmental-Data-Partners / Public-Environmental-Data-Partners/EJAM-API
manage large requests
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 1
- Forks
- 1
- Avg merge
- 38m
- Merged PRs (30d)
- 1
Description
Currently, the API will try to make a report for anything, even a point with a 1000 mile buffer.
Contributor guide
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 tracing the API path that creates a report for a point with a large buffer. Determine how request size is currently handled and what limit or response is expected for oversized requests. Done means large requests are handled predictably without attempting an unbounded report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- api, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100