-
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
Standard names: *Micronekton* #212
Comments
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. |
Dear Aurore Thanks for your engagement with and contributions to CF! Perhaps @roy-lowry might comment on the biology of these proposed names. Regarding the physical aspects, a couple of things occur to me:
Best wishes Jonathan |
Dear Jonathan, These are morphological groups of organisms (size based), not taxa, so a specific standard name for each group is the correct way to go. The descriptive terms such as epipelagic describe where abouts in the water column the organisms are to be found. These are commonly used in biological oceanography, but obviously need to be defined in the description. In particular, the difference between migrant and highly migrant needs to be clarified. These do describe data z co-ordinates, but I think they should be considered equivalent to atmospheric terms like 'troposphere' rather than '2m air temperature' and therefore be allowed. 'Wet weight' is the term commonly used to describe the mass of a sample - say the catch from a net trawl - as soon as it is caught. 'Dry weight' is also commonly used for the mass of that sample after all water has been removed by processing like freeze drying. The dried samples can then be analysed to give the amount of carbon or nitrogen giving rise to Standard Names like 'mole_concentration_of_miscellaneous_zooplankton_expressed_as_carbon_in_sea_water' which have been used as the model for 'expressed_as_wet_weight' Possible alternatives that come to mind: wet_mass_content_of_epipelagic_micronekton_in_sea_water mass_content_of_epipelagic_micronekton_expressed_as_wet_in_sea_water mass_content_of_epipelagic_micronekton_expressed_as_wet_mass_in_sea_water Do any of these get around your issue? If so, any preference? Cheers, Roy. |
Dear Roy Thanks for explaining. From what you say, I understand that "epipelagic" identifies both a layer of the ocean, like troposphere, and the species which are found in it. We still wouldn't need But without If these layers are actually defined by depth, as you suggest, could we have just Thanks for your help Jonathan |
Thanks Jonathan, First, these layers are defined through parameters that are related to depth rather than depth ranges in metres. For example, epipelagic is the layer at the top of the ocean where there is sufficient light for photosynthesis. Its physical thickness in metres varies as a function of water clarity. Consequently, I would strongly advise against using bounds, especially when vertical migration comes into consideration. Might have misled you. The terms like "epipelagic" are describing a subset of micronekton population in the water column rather than specifying where in the water column a measurement was made (these are modelling parameters rather than measurements). So "epipelagic micronekton" should be thought of as "micronekton that always live in the epipelagic layer" and "migrant lower mesopelagic micronekton" should be thought of as "micronekton that live mostly in the lower mesopelagic layer but regularly move into another layer". So, how about? mass_wet_content_of_epipelagic_micronekton_in_ocean Roy. |
Dear Roy Thanks, I see. Since Best wishes Jonathan |
Dear Jonathon, wet_mass_content was my preference and certainly not a green dog issue. I thought you preferred mass_wet_content and decided I could live with it. So, having taken a look at the ocean_etc. precedents I think your suggestion of: ocean_wet_mass_content_of_epipelagic_micronekton etc. works for me. Regards, Roy. |
Dear Roy Thanks a lot. I'm glad we're both happy with that. Is that all right for you, Aurore? Jonathan |
Dear @roy-lowry and @JonathanGregory Thank you so much for advising us on Micronekton. Your final suggestions are perfectly fine for us as well :
Aurore |
Thanks Aurore, Could you now prepare some draft descriptions? Roy. |
Hi Aurore @abiardeau, Thank you for working with @roy-lowry to revise this proposal. I have modified the names in the CF editor, and as a remember the entries can be found here:
I will wait for further input from you on the descriptions. Best wishes, |
Hi Aurore @abiardeau, Perhaps I could suggest the following text to add to your term descriptions? I am wondering if the description of 'ocean content' is appropriate for your suggested names: a vertical integral "from the surface to the bottom of the ocean", for epipelagic / mesopelagic terms which specify a measurement depth interval? Perhaps @JonathanGregory and @roy-lowry could comment on this also. Best regards, |
I agree that it ought to say "within the specified vertical bounds" in this case, rather that "from the surface to the bottom". |
Hi Ellie and Jonathan, Thanks for your first definitions of ocean wet mass content.
If needed : Aurore |
22/08/2024
Hello, I am Aurore BIARDEAU (me again :) ) from Mercator Ocean international.
We are enriching the Copernicus Marine service with micronekton parameters.
Micronekton is classically defined by a size range of 2cm-20 cm. It contains a large diversity of fish, crustacean, squid, and gelatinous species. It can be only a temporary stage for species with large growth potential. Micronekton biomass content (primary dataset) is delivered at the three pelagic levels (namely epipelagic, upper and lower mesopelagic levels).
Here are the standard_names we propose for micronekton :
Micronekton is expressed in wet weight (g/m2).
With regards to your feedback on the issue #29 , the functional groups are expressed here.
Before getting into the descriptions, I would like to know your thoughts those standard_names ?
Thanks very much !
Aurore
The text was updated successfully, but these errors were encountered: