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: *Friction Velocity in Sea Water* #39

Closed
abiardeau opened this issue May 13, 2024 · 14 comments
Closed

Standard names: *Friction Velocity in Sea Water* #39

abiardeau opened this issue May 13, 2024 · 14 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

@abiardeau
Copy link

Hello,
I am Aurore BIARDEAU from Mercator Ocean international, working for Copernicus Marine service.
Date : 13-05-2024

We are in the process of implementing a new variable in the Copernicus Marine service and we would be happy to have your feedback on our proposal :

standard_name : eastward_friction_velocity_in_sea_water (same for northward)
(Inspired by existing standard_name eastward_friction_velocity_in_air)

unit : m s-1

I can provide more information from my expert colleagues if needed,
Kind regards,
Aurore

@abiardeau abiardeau 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 May 13, 2024
Copy link

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

Dear Aurore @abiardeau

For friction velocity in sea water, I suppose we ought to specify that it's a surface friction velocity, because the concept applies to the sea floor as well.

Best wishes

Jonathan

@abiardeau
Copy link
Author

Dear @JonathanGregory

Thanks for your answer. You're right, should we say : eastward_friction_velocity_at_sea_water_surface ?

@JonathanGregory
Copy link
Contributor

Yes, at_sea_water_surface is a phrase we've used before, so that would work. Another possibility is surface_eastward_friction_velocity_in_sea_water.

@abiardeau
Copy link
Author

Thanks, both would work for us. If there is any preference from your side we we'll go with it

@efisher008 efisher008 removed the add to cfeditor (added by template) Moderators are requested to add this proposal to the CF editor label May 24, 2024
@efisher008
Copy link
Collaborator

Dear Aurore,

I have added your proposed name eastward_friction_velocity_in_sea_water to the editor, and will wait for more discussion on the format before proceeding (including the change to one of the above suggestions). It would be useful to have a description for this name to help clarify its use.

Best regards,
Ellie

@efisher008
Copy link
Collaborator

Hello Aurore @abiardeau,

Looking back at this issue, I am wondering if it would be more descriptive to use the form eastward_friction_velocity_at_sea_water_surface/northward_friction_velocity_at_sea_water_surface for the names. This would specify that it is a surface quantity as @JonathanGregory had mentioned, and there is some precedent in the standard names table for using at_sea_water_surface.

If you could provide a description for the names, that would be very useful. I have added the description for eastward ("Eastward" indicates a vector component which is positive when directed eastward (negative westward).") and northward (""Northward" indicates a vector component which is positive when directed northward (negative southward).") to them as a starting point.

Best wishes,
Ellie

@efisher008 efisher008 added the moderator attention (added by GitHub action) Moderators are requested to consider this issue label Jul 22, 2024
@efisher008
Copy link
Collaborator

Hi Aurore @abiardeau,

I hope your summer is going well.
Now that your other batch of proposed standard names have been accepted, would you have any time to dedicate to progressing this proposal? It would be great to see it moving towards acceptance.

Best,
Ellie

@japamment japamment transferred this issue from cf-convention/discuss Jul 29, 2024
@github-actions github-actions bot removed the moderator attention (added by GitHub action) Moderators are requested to consider this issue label Jul 30, 2024
@abiardeau
Copy link
Author

Hello @efisher008
Thanks for your message.

I also prefer eastward_friction_velocity_at_sea_water_surface/northward_friction_velocity_at_sea_water_surface for the names.

About the definition, we propose this one, which is coherent with the definition of eastward_friction_velocity_in_air :

A velocity is a vector quantity.
"Eastward" indicates a vector component which is positive when directed eastward (negative westward).
Friction velocity is a reference ocean velocity derived from the relationship between ocean density and downward stress and is usually applied at a level close to the surface where stress is assumed to be independent of height and approximately proportional to the square of mean velocity.

@efisher008
Copy link
Collaborator

efisher008 commented Aug 15, 2024

Hello @abiardeau,

Yes, this sounds reasonable. I have added those descriptions and altered the names in the editor, visible here:
eastward_friction_velocity_at_sea_water_surface - https://cfeditor.ceda.ac.uk/proposal/5340
northward_friction_velocity_at_sea_water_surface - https://cfeditor.ceda.ac.uk/proposal/5419

I have also added the definition of friction velocity in the context of air and sea water as stated to the CF phrasebank.

Are there any further comments on this issue? Otherwise I think we can start the 7-day countdown period to acceptance.

Best wishes,
Ellie

@abiardeau
Copy link
Author

This is fine for me, thanks Ellie !

@efisher008 efisher008 added the accept within 7 days Starts 7 day countdown to accept a change to standard names or other controlled vocabulary label Aug 20, 2024
Copy link

This issue has had no activity in the last 30 days. Accordingly:

  • If you proposed this issue or have contributed to the
    discussion, please reply to any outstanding concerns.
  • If there has been little or no discussion, please comment
    on this issue, to assist with reaching a decision.
  • If the proposal seems to have come to a consensus, please
    wait for the moderators to take the next steps towards
    acceptance.

Standard name moderators are also reminded to review @feggleton @japamment @efisher008

@github-actions github-actions bot added the moderator attention (added by GitHub action) Moderators are requested to consider this issue label Sep 19, 2024
@efisher008
Copy link
Collaborator

Dear Aurore @abiardeau,

I apologise for not coming back to you, it seems as though I missed accepting this proposal! Your two new proposed names have now been accepted in the CF editor and will be published in the next standard names table version, v87, currently planned for release mid-late November this year.

Best wishes,
Ellie

@efisher008 efisher008 added accepted Agreed for inclusion in the next release of the standard name table or other controlled vocabulary and removed accept within 7 days Starts 7 day countdown to accept a change to standard names or other controlled vocabulary moderator attention (added by GitHub action) Moderators are requested to consider this issue labels Oct 21, 2024
@efisher008
Copy link
Collaborator

These names have been published in version 87 of the Standard Name table, dated 12 November 2024. I have now closed this issue as completed.

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

3 participants