-
Notifications
You must be signed in to change notification settings - Fork 2
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
Agree with each GAW SAG on level 0 data #23
Comments
Here is the definition WDCA and WDCRG are using: This table is in fact valid for all types of data we are handling. There are adaptations possible for data types where the raw data stream has a very large volume, where some pre-compression is allowed. |
Definitions for WOUDC: https://guide.woudc.org/en/#chapter-3-standard-data-format |
From May 2024 @wmo-im/wmds/issues/477 "Status update from May 2024: Proposed definitions for Level 0 data: |
The ICOS definition of Level 0 is: Level 0=Raw data are information or objects directly obtained from human measurements or automated sensors that have not undergone any transformation. They may provide quantitative or qualitative information about physical variables of the environment and may be of various forms, such as images, text files or physical samples. Level 0 data are data in physical units either directly provided by instruments or converted from engineering units (for example, mV, mA, Ω) to physical units. All ICOS raw data that is collected automatically from instruments is gathered into daily (compressed) archives per instrument that is sent without delay to the repository and minted a PID (based on the AES256 checksum) and linked to the metadata system. All data pipelines build on the full cycle from processing this raw data up to the NRT and final quality controlled data, fully reproducible and transparent. |
to review the discussion about 'level 0 data' in GitHub (wmo-im/wmds#477) and agree with each GAW domain (SAGs) what would be level 0 data, whether and where they need to be archived.
The text was updated successfully, but these errors were encountered: