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

area type: "snow" #63

Open
taylor13 opened this issue Mar 26, 2022 · 9 comments
Open

area type: "snow" #63

taylor13 opened this issue Mar 26, 2022 · 9 comments
Labels
accepted Agreed for inclusion in the next release of the standard name table or other controlled vocabulary standard name (added by template) Requests and discussions for standard names and other controlled vocabulary

Comments

@taylor13
Copy link

taylor13 commented Mar 26, 2022

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:

The surface called "surface" means the lower boundary of the atmosphere. The surface temperature 
is the temperature at the interface, not the bulk temperature of the medium above or below. Unless
 indicated in the cell_methods attribute, a quantity is assumed to apply to the whole area of each 
horizontal grid box. Previously, the qualifier where_type was used to specify that the quantity applies 
only to the part of the grid box of the named type. Names containing the where_type qualifier are 
deprecated and newly created data should use the cell_methods attribute to indicate the horizontal 
area to which the quantity applies.

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").

@taylor13 taylor13 added the question Further information is requested label Mar 26, 2022
@DanHollis
Copy link

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 surface_snow_binary_mask with surface_snow_area_fraction: 0.5.

However I agree that the meaning of area type snow should be clarified. I see that there are a couple of related area types - ice_and_snow_on_land and snow_free_land. In these two examples the word 'snow' is being used to mean surface snow. Following this pattern, another option would be to add snow_on_land. Having said that, there are quite a few existing standard names that include 'surface_snow' in the name, but also some that refer to just 'snow'. I haven't attempted to work out whether the latter refer to falling snow or lying snow. My vote would be to define the existing snow area type as falling snow (to match rain) and add either surface_snow or snow_on_land.

@taylor13
Copy link
Author

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.

@taylor13
Copy link
Author

taylor13 commented Apr 21, 2022

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")?

@JonathanGregory
Copy link
Contributor

JonathanGregory commented Apr 21, 2022 via email

@taylor13
Copy link
Author

Yes, probably should be. So "snow lying on the surface or collected by the canopy"

@davidhassell
Copy link
Collaborator

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!).

@taylor13
Copy link
Author

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.

@taylor13
Copy link
Author

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"?

@feggleton feggleton added the standard name (added by template) Requests and discussions for standard names and other controlled vocabulary label Nov 3, 2022
@github-actions
Copy link

github-actions bot commented Apr 6, 2023

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

@github-actions github-actions bot added the moderator attention (added by GitHub action) Moderators are requested to consider this issue label Apr 6, 2023
@JonathanGregory JonathanGregory added add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor and removed question Further information is requested labels Apr 12, 2023
@github-actions github-actions bot removed the moderator attention (added by GitHub action) Moderators are requested to consider this issue label Apr 12, 2023
@feggleton feggleton added accepted Agreed for inclusion in the next release of the standard name table or other controlled vocabulary and removed add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor labels Apr 21, 2023
@efisher008 efisher008 transferred this issue from cf-convention/discuss Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Agreed for inclusion in the next release of the standard name table or other controlled vocabulary standard name (added by template) Requests and discussions for standard names and other controlled vocabulary
Projects
None yet
Development

No branches or pull requests

5 participants