lasp / lasp/latis-python-client
Add option to high level API to allow arbitrary dap2 style query constraints
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In the interest of not limiting LaTiS features through the read_data interface and avoiding the release cycle for critical new features, add an option to add any dap2 style constraint expression after the time selections to the read_data API.
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 at the high-level read_data API and trace how time selections are assembled. Determine where an arbitrary DAP2-style constraint expression can be accepted after those selections; done means callers can pass such a constraint without waiting for a new dedicated high-level option for each feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100