Closed lbesnard closed 7 years ago
According to v1.3 of the IMOS conventions, pressure is supposed to be converted into depth in metres to provide a vertical coordinate, but this is not stated in the new version (1.4). However both versions do say you can't label a pressure as "depth" or "height". Either way this needs some work.
@lbesnard Have you made any changes to this kind of file? There may be a few things we can improve in the checker, but I think the file is technically not IMOS-1.3 compliant. We may need to have a chat with @ggalibert and @smancini to decide what we want to insist on.
@lbesnard Have you made any changes to this kind of file?
No I haven't. happy to have a chat
Just a note, the message about geospatial_vertical_min/max
being numeric type is a separate issue. (The offending file has these attributes as integers, and the checker is currently expecting a float.)
After further discussions we've decided to leave these checks unchanged in the checker, and instead look into the possibility of adding a DEPTH variable to these files.
@lbesnard What's the status of these files? Is this still an issue or have you found a way around it? If we need to keep tracking this issue, please move it to the content repo. Otherwise please close it. Thanks.
This issue has been moved to https://github.com/aodn/data-services/issues/652
Not having a
DEPTH
dimension, and using aPRES
one instead triggers a series of issues with the IMOS checker, while the file is CF compliant.Example file : IMOS_AATAMS-SATTAG_TSP_20130302T012000Z_Q9900562_FV00.nc.zip