search

oceandatainterop / nc-eTAG

NetCDF file, metadata & data standards for electronic tagging datasets (nc-eTAG)
2 stars 0 forks source link

coordinates attribute #2

Open lesserwhirls opened 4 years ago

lesserwhirls commented 4 years ago

In the coordinates attribute of a variable, is trajectory necessary if just one tag/deployment? For example:

https://github.com/oceandatainterop/nc-eTAG/blob/2d7de81fd79e4ffc70dbdc62da8a47c4100aa3eb/nc-eTAG_Archival_Template.cdl#L90

lesserwhirls commented 4 years ago

CF does not really say one way or the other, from what I can tell. For example, the coordinates attribute of the humidity and temperature variables in the single time series example include the feature identity variable station_name, but the coordinates attribute on the O3 and NO3 variables in the single trajectory example does not include the feature identity variable trajectory.

oceandatainterop commented 4 years ago

Thanks. Sounds like one could go either way. Certainly it is not a mistake to include it, and in fact may be better to be more explicit/general, especially for the purposes of this nc-eTAG template specification where potentially multiple features could be included/supported.

lesserwhirls commented 4 years ago

When I made the choice for Rosetta, I went with clarity and included it, but it could go either way.