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

Decide what date columns are deemed necessary for the data processing pipeline #34

Open
JulianBiesheuvel opened this issue Jul 4, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@JulianBiesheuvel
Copy link
Collaborator

For now a hard constraint on FROM and TO DATE in the dataset. But what if only one of the two is available? We have to think about this. For now, if either of the two dates is in invalid or not provided, the data recorded is deleted from the dataset.

@khsjursen
Copy link
Collaborator

Right now MBM removes data containing 99 in TO_DATE and FROM_DATE. In the WGMS dataset 99 is used not only for missing day of month (YYYYMM99), but missing month (YYYY9999). For some glaciers this removes a lot of data.

If YEAR is provided then a possibility here is to give the user the option of filling start and end dates of the hydrological year (or winter/summer period). But this is quite a strong assumption such that it should be flagged somehow..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants