Sounds like we've converged and can CLOSE this. And, yes, this doesn't actually require `nsigma` be a saved parameter - though it's useful supporting metadata.
My remarks on "w" grid vertical coordinates is not a bounds issue. It's another coordinate for variables defined at a different location, as in the vertical velocity in this ROMS model dataset https://urldefense.us/v3/__http://tds.marine.rutgers.edu/thredds/dodsC/roms/doppio/2017_da/avg/Averages_Best.html__;!!G2kpM7uM-TzIFchu!geKEgrES2bG0xXvKVDsP3lMXQ3fK-tkNmLVXZgpemTj78lQotcBxpE2QPclTfoWSWAf-Vf_vx6I$ that uses `ocean_s_coordinate_g2` ``` s_rho long_name: S-coordinate at RHO-points valid_min: -1.0 valid_max: 0.0 positive: up standard_name: ocean_s_coordinate_g2 formula_terms: s: s_rho C: Cs_r eta: zeta depth: h depth_c: hc ``` and ```s_w long_name: S-coordinate at W-points ... formula_terms: s: s_w C: Cs_w eta: zeta depth: h depth_c: hc` ``` u velocity data are dimensioned on s_rho. w velocity data are dimensioned on s_w. For ocean_sigma_over_z_coordinate **IF** the file contains w data, THEN we would need another dimension (length nlayers+1) and coordinate. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/314*issuecomment-825699395__;Iw!!G2kpM7uM-TzIFchu!geKEgrES2bG0xXvKVDsP3lMXQ3fK-tkNmLVXZgpemTj78lQotcBxpE2QPclTfoWSWAf-Gc-0z0U$ This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
