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

Historical data response without duplicate validity times #116

Open
cwasicki opened this issue May 29, 2024 · 1 comment
Open

Historical data response without duplicate validity times #116

cwasicki opened this issue May 29, 2024 · 1 comment
Assignees
Labels
part:❓ We need to figure out which part is affected priority:❓ We need to figure out how soon this should be addressed type:enhancement New feature or enhancement visitble to users
Milestone

Comments

@cwasicki
Copy link
Contributor

What's needed?

There are multiple forecasts for the same validity time with different creation times. Usually users only need a single forecast for each validity time.

Proposed solution

There should be an option to remove all duplicate forecasts with the same validity time based on their relation to the creation time. For instance usually forecasts are only available some hours after they were created. This means, when requesting the data, we would only return the validity time with creation time closest to the validity time, but ignoring those where creation time is below a certain user-defined time difference.

Use cases

No response

Alternatives and workarounds

Currently the user has to do the de-duplication.

Additional context

No response

@cwasicki cwasicki added part:❓ We need to figure out which part is affected priority:❓ We need to figure out how soon this should be addressed type:enhancement New feature or enhancement visitble to users labels May 29, 2024
@cwasicki cwasicki added this to the v1.0.0 milestone Sep 10, 2024
@TalweSingh
Copy link
Contributor

@cwasicki will provide the interface

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:❓ We need to figure out which part is affected priority:❓ We need to figure out how soon this should be addressed type:enhancement New feature or enhancement visitble to users
Projects
None yet
Development

No branches or pull requests

3 participants