Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Add earliest/first to dateTimeSchema #64

Closed
SpeckiJ opened this issue Aug 5, 2024 · 2 comments
Closed

[Feature Request] Add earliest/first to dateTimeSchema #64

SpeckiJ opened this issue Aug 5, 2024 · 2 comments
Assignees
Labels
ready Was discussed during a telecon and a decision was made review

Comments

@SpeckiJ
Copy link
Collaborator

SpeckiJ commented Aug 5, 2024

Currently the special keywords: "now" and "latest" are supported for querying via time:

For clients it would be nice to also have earliest/first as a reference point. Without this there is no real straightforward way to get the earliest observation in a datastream. Especially for giving an overview of the data this is often required.

While the Datastream itself also has a phenomenonTime, this is often only a very broad timeframe (e.g. the length of the overall measurement campaign) and not necessarily the actual timeframe of the first observation.

@alexrobin
Copy link
Collaborator

alexrobin commented Sep 19, 2024

Discussed during 09/19 telecon.
Ok to add earliest. (mandatory like other options in the enum)

@alexrobin alexrobin added the ready Was discussed during a telecon and a decision was made label Oct 3, 2024
@autermann
Copy link
Member

autermann commented Jan 23, 2025

Discussed 01/23: remove the now keyword and just keep latest.

Finding out the earliest values is trivial, as the DataStream has temporal extents for result and phenomenon times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Was discussed during a telecon and a decision was made review
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants