-
Notifications
You must be signed in to change notification settings - Fork 1
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
area type: "snow" #63
Comments
We don't have a need for the surface temperature of snow but we do create datasets of the number of days with snow lying on the ground. For this we use the standard name However I agree that the meaning of area type |
just to note: "snow_on_land" would not be the same as "surface_snow" because snow can lie on sea ice and land ice too, which are (in CF) not considered to be "land". Unless anyone knows that in the past "snow" has been interpreted as "falling_snow", as opposed to "surface_snow", we might prefer "snow" to mean "surface_snow", since I know for a fact that it has commonly been used to mean that in the past. |
Does anyone object to defining the standard_name for area_type "snow" as "snow lying on the surface" (not "snow residing or falling in the atmosphere")? |
Perhaps it's snow lying on the surface or the canopy?
|
Yes, probably should be. So "snow lying on the surface or collected by the canopy" |
I have no prior experience of using this area type, but having read this thread, I would have no objection to redefining area type "snow" to mean the suggested "snow lying on the surface or collected by the canopy" (although I'm not sure what is meant by the standard_name for area_type "snow" - was that intended? apologies if I'm missing something obvious!). |
Sorry, I think I misread something in one of the documents. As I now understand it, the area_type identifiers are not standard_names. Please note, I don't think we're really redefining area type "snow" since it was never precisely stated before how it should be interpreted; we're just clarifying. |
Dear Alison @japamment (or whoever might be able to implement this) There seems to be no objection and some support for clarifying the meaning of "snow" as an "area type" so in the drop down definition under "snow" in the table, could we replace "No help available" with "The portion of the surface covered by snow or with a canopy that hosts snow"? |
This issue has had no activity in the last 30 days. This is a reminder to please comment on standard name requests to assist with agreement and acceptance. Standard name moderators are also reminded to review @feggleton @japamment |
In the CF Area Type Table, "snow" is listed without any further explanation of its meaning. Also listed in the table is "rain", with the explanation that
An area_type of "rain" indicates that falling rain is present at some level in the atmospheric column above an area on the surface of the Earth.
My question is: are the "snow" and "rain" area types supposed to be interpreted similarly?If so, how would one record the surface temperature of the snow? I note that the standard names table describes surface_temperature as follows:
If we interpret the "snow" area type as the surface area covered by snow, then we could use surface_temperature with "where snow" in the
cell_methods
attribute, but if we interpret "snow" in the sense that "rain" is interpreted, then this would be incorrect.Perhaps, we should define another area type as "surface_snow", with an obvious interpretation, and also add an explanation of "snow" that is similar to the description of the "rain" area type.
An alternative would be to define a new area type, "falling_snow", which would be analogous to the "rain" area type (which really refers to a column in which there is falling rain), and reserve "snow" to refer to snow at the surface. A virtue of this alternative is that several variables (many megabytes of data) found in the CMIP6 archive have cell_methods with "where snow" meant to be interpreted as "where there is snow at the surface" (not "where this is snow falling in the column").
The text was updated successfully, but these errors were encountered: