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

evapotranspiration subClassOf thickness? #227

Open
cmungall opened this issue Oct 14, 2020 · 2 comments
Open

evapotranspiration subClassOf thickness? #227

cmungall opened this issue Oct 14, 2020 · 2 comments
Labels

Comments

@cmungall
Copy link
Collaborator

Aligning concepts like evapotranspiration in SWEET with the concept with the same name in ENVO (which is a process)

Trying to make sense of:

image

Is it really correct to say that potential evapotranspiration is a thickness?

I suppose according to WP, PET
https://en.wikipedia.org/wiki/Potential_evaporation
can be measured in mm/month, so it is in some sense a kind of thickness. So it seems the SWEET conception of properties like thickness is very inclusive? I think I would make sense to document and articulate the definitions here so that consistent classification decisions can be made here, and we could determine if things like evapotranspiration subClassOf thickness is intended or a mistake

@cmungall cmungall added the bug label Oct 14, 2020
@graybeal
Copy link
Collaborator

So I think in English the usage could go either way: something was caused by evapotranspiration, or there were 3mm of evapotranspiration. (No idea if scientists reject one of those sentences.)

SWEET has this kind of thing throughout, where the choice made is not consistent with my expectations and definitions, but I couldn't argue it was technically wrong. And without definitions, who's to say?

From a modeling perspective, though, wouldn't it be more sensible if it were a process, the result of which was a thickness of fluid? (Like we don't say "snow" is a thickness, we say "snow cover" is a thickness.) I'd vote for that. So that would remove all the subclass declarations about it (default unit, measure of, has unit, quantity, and quantitative property) and leave 'study of' some physics.

@r0sek
Copy link
Collaborator

r0sek commented Aug 17, 2023

I think Evapotranspiration and Potential Evapotranspiration are classified incorrectly.

Evapotranspiration is a process and is expressed as the rate of some depth of water loss over time, eg. mm per unit time. The depth or thickness is a measurement of the amount of water (in the substrate) that is transformed into water vapor by the evapotranspiration process, not the thickness of the resulting water vapor; see the Units section of the FAO chapter on evapotranspiration https://www.fao.org/3/X0490E/x0490e04.htm for further explanation. The same is true for potential evapotranspiration.

I searched for "evapotranspiration boundary layer", which I was imagining could be a boundary layer of water vapor that occurs over crops or forests, etc. and is specifically attributed to evapotranspiration, and would then be a type of thickness, but couldn't find anything. Most scholarly articles describing that phenomena appear to simply use the term "boundary layer".

SWEET currently has phenomena > biological phenomena > transpiration and physical process > state change > vaporization > evaporation. Evapotranspiration is a combination of the two, but I think should be considered a biological process as "transpiration" occurs in plants but is only combined with "evaporation" in situations where the two cannot be quantifiably distinguished.

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

No branches or pull requests

3 participants