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

Air daily maximum temperature #13

Open
mabablue opened this issue Nov 1, 2024 · 2 comments
Open

Air daily maximum temperature #13

mabablue opened this issue Nov 1, 2024 · 2 comments

Comments

@mabablue
Copy link
Member

mabablue commented Nov 1, 2024

Variable Description: Temperature of the air in a height of 1.7 meter, daily maximum
(group A: Daily maximum temperature of the air at a specified distance from a specified reference surface)

Reasoning as provided by group A: The variable name highlights the fact that this is a statistics (daily maximum) of a property (temperature) of an object of interest with given constraints (distance from reference surface, type of reference surface).

Let's discuss about different implementations:

https://i-adopt.github.io/examples/Challenge/A/A_2.ttl.html as provided by group A
and: https://i-adopt.github.io/examples/Challenge/2.ttl.html as provided by the core group

Property (label): temperature vs extreme temperature

Object of Interest (label): air vs atmosphere

Matrix (label): atmosphere vs atmospheric state

Context Object(s) (label): none vs atmosphere

Constraint(s) (label) and which Entity it constraints: 1,7 meter above ground vs distance from reference surface
in addition as proposed by group A: daily maximum, reference surface type

Dimension Information: temperature

Applicable Unit(s): Celsius Degree

Link to a Publication of the Variable or Method:

Link to Turtle File (ttl) in this Repository (optional):

@mabablue
Copy link
Member Author

mabablue commented Nov 1, 2024

Re property: I think both are possible as extreme temperature would be a specialization of temperature; we need to consider that statistical measures are not part of the variable description in I-ADOPT and should be addressed in the protocol instead
Re object of interest: I think air is the colloquial term for atmosphere (in the sense of mixture of gases)
Re matrix: the core group had atmosphere (in the sense of a layer), group A atmospheric state. I try to better understand what is meant with state - these are conditions but not the material that embeds the object of interest (definition of matrix), so it could be modelled as constraint then; in our logic, if we use atmosphere as object of interest, the matrix should then be troposphere (as the layer in which the mixture of gas is embedded)
Re context object: I think we need atmosphere only once in the description
Re constraints: all what is related to a protocol or method (like reference surface type, daily maximum) should be kept outside the core variable description also because it would constrain the whole variable which would violate the ontology logic. It needs to be addressed separately. But see here how we could extent the variable description as a proposal.

@KathiSchleidt
Copy link

To my view, atmospheric state is not an entity, thus does not fit for Matrix

In addition, I believe you're measuring the temperature at a specific point in the atmosphere, not the atmosphere in its entirety. I'm wondering if this shouldn't be indicated

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

No branches or pull requests

2 participants