Add option to high level API to allow arbitrary dap2 style query constraints

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api

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.

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.

Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lasp/latis-python-client

All issues in lasp/latis-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.