-
Notifications
You must be signed in to change notification settings - Fork 22
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
6-01-02 Creation of a new code table RelativeHumidity #292
Comments
@fstuerzl @joergklausen -- who is the stakeholder or originator of this proposal? |
@markusfiebig was planning on proposing a a draft for this new table. |
Greetings from Canada. I was wondering if I could please get an update on this ticket. A few national operators would like to add relative humidity to their OSCAR/Surface record station and have requested and ETA when relative humidity will be available in the code list. Thank you |
@thineshsornalingam There is a misunderstanding here, presumably. This is not about the observed variable 'Relative humidity', it is about an additional code list on RH to specify other observed variables, specifically for aerosol observations, but perhaps others. |
Gao would like to know if this is about instrument or variable, water or ice? Joerg notes that there are open questions |
This may be a good case for tag. Thinking about a instrument RH tag which has at least two values (e.g., Dry and NotDryEnough) to indicate if the sample were dried under 40% or not. Possibly one may add the third value to denote the instrument RH under 20 or 15%. Is this Ok? @markusfiebig. |
@markusfiebig Please develop this issue into something more concrete (i.e., prvide summary and purpose). In my understanding, we're discussing a "constraint" (in the I-ADOPT lingo) and the question is whether a controlled vocabulary should exist to specify this constraint. If so, a controlled vocabulary should be proposed, .e.g.
alternatively:
If no such controlled vocab is needed, then we should close this issue. |
I consulted with a well-known aerosol measurement expert, Luke Ziemba: |
I support @gaochen-larc . @markusfiebig @ferrighi Could you please fill in the proposal and create a branch, so that it can be processed further? Thanks |
Please consult the Guidance and use the following structure for new issues.
Branch
[add branch when created]
Summary and Purpose
Stakeholder(s)
[include emails or handles as relevant]
Proposal
[your specific proposal to resolve the issue - update when decision on proposal is finalized]
Reason
[your reasoning why the proposal resolves the issue]
The text was updated successfully, but these errors were encountered: