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

Standard names: iceberg_transport_across_line #235

Open
mankoff opened this issue Nov 8, 2024 · 6 comments
Open

Standard names: iceberg_transport_across_line #235

mankoff opened this issue Nov 8, 2024 · 6 comments
Labels
accept within 7 days Starts 7 day countdown to accept a change to standard names or other controlled vocabulary standard name (added by template) Requests and discussions for standard names and other controlled vocabulary

Comments

@mankoff
Copy link

mankoff commented Nov 8, 2024

Proposer's name Ken Mankoff

Date 2024-11-07

iceberg_transport_across_line

Description: Transport across_line means that which crosses a particular line on the Earth's surface; formally this means the integral along the line of the normal component of the transport. "Iceberg" means all ice floating in the sea which has formed from calving of land ice, rather than by other processes such as freezing sea water.

Units: kg s-1

From: https://github.com/orgs/cf-convention/discussions/388 except that upon further reflection of that discussion, I believe that land_ice_transport_across_line and land_ice_transport_across_grounding_line are not needed due to tendency_of_land_ice_mass.

Furthermore, the original request was for icebergs at their calving location, which I now find is handled by tendency_of_land_ice_mass_due_to_calving. Therefore, the above new name is not needed by me. It may be useful to others for icebergs crossing some arbitrary line in the ocean - that is, a term similar to sea_ice_transport_across_line.

@mankoff mankoff added add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor standard name (added by template) Requests and discussions for standard names and other controlled vocabulary labels Nov 8, 2024
Copy link

github-actions bot commented Nov 8, 2024

Thank you for your proposal. These terms will be added to the cfeditor (http://cfeditor.ceda.ac.uk/proposals/1) shortly. Your proposal will then be reviewed and commented on by the community and Standard Names moderator.

@JonathanGregory
Copy link
Contributor

Thanks for helping CF, Ken @mankoff! Since you almost have a use-case for this quantity, and it seems likely that it will be needed by someone, and it follows an existing pattern, and you've gone to the effort of making the proposal, I think we should add it.

@taylor13
Copy link

taylor13 commented Nov 8, 2024

I too support the proposal, but was wondering why we shouldn't be more specific and include "mass" in the definition, that is iceberg_mass_transport_across_line.

I noticed that we haven't been completely consistent in whether we should use "mass_transport" or "transport" alone when we mean "mass transport". When it isn't mass transport, I think we state what type of transport we're talking about (e.g., volume transport or heat transport). Otherwise, we typically presume the term "transport" means "mass transport" (e.g., eastward_atmosphere_water_vapor_transport_across_unit_distance). If that's the case why do the following names include "mass"?

upward_ocean_mass_transport
carbon_mass_transport_in_river_channel
nitrogen_mass_transport_in_river_channel
phosphorus_mass_transport_in_river_channel
silicate_mass_transport_in_river_channel
square_of_upward_ocean_mass_transport
ocean_mass_x_transport_due_to_advection
ocean_mass_x_transport_due_to_advection_and_parameterized_eddy_advection
ocean_mass_y_transport_due_to_advection
ocean_mass_y_transport_due_to_advection_and_parameterized_eddy_advection

Despite these inconsistencies I'm o.k. with omitting "mass" if we include in the description (of all such variables) a sentence something like: "Transport", as used here, means "mass transport".

@mankoff
Copy link
Author

mankoff commented Nov 8, 2024

I based this name off of sea_ice_transport_across_line.

I note mass is in units so it might be redundant to have it in the name? Or if having it in units justifies having it in the name, then should "_per_unit_time" also be in the name?

@taylor13
Copy link

taylor13 commented Nov 8, 2024

Yes, you've been completely consistent with past practice. No need for you to do anything more.

I'm suggesting, however, that it would be good for us to include for all our existing "mass transport" names, when "mass" is omitted from the name, that "transport" means "mass transport" (and not something like "volume transport"). As you say, you can infer that from the units, but I think it would be helpful to point this out in the description of the variables too.

This is not your responsibility, since it applies to multiple existing standard names.

@efisher008
Copy link
Collaborator

Dear Ken @mankoff, Karl @taylor13,

Thank you for the discussion. The name has been kept as iceberg_transport_across_line and the following line added to the description: "Transport", as used here, means "mass transport". This can be added to the CF phraselist for terms which include "transport" without the qualifying "mass". I will start the countdown to acceptance, which is 7 days with no further changes.

It sounds like a new issue is needed to discuss the changes to the existing mass_transport names / transport names omitting mass. I am happy to open this if @taylor13 and @JonathanGregory have no objections.

Best wishes,
Ellie

@efisher008 efisher008 added accept within 7 days Starts 7 day countdown to accept a change to standard names or other controlled vocabulary and removed add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accept within 7 days Starts 7 day countdown to accept a change to standard names 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

4 participants