You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe that currently the _NC_GLOBAL:gts_ingest global attribute is the only one used by NCEI to determine this and it marks an entire data set that should or should not be released to GTS.
For example, we have a dataset in which we noticed that the conductivity went bad, resulting in bad salinity profiles. As far as we can tell, the temperature data is good and can be used in models without the salinity. So we would like to have the temperature data sent, but not the salinity.
Are there plans to implement variable based GTS release and have NCEI use the VARIABLE:gts_ingest attribute to determine what variables are released to GTS and what variables are not?
Reference
No response
The text was updated successfully, but these errors were encountered:
What should we add?
The IOOS Metadata Profile specification allows for the variable based gts_ingest attribute to mark a variable that should or should not be released to GTS.
I believe that currently the _NC_GLOBAL:gts_ingest global attribute is the only one used by NCEI to determine this and it marks an entire data set that should or should not be released to GTS.
For example, we have a dataset in which we noticed that the conductivity went bad, resulting in bad salinity profiles. As far as we can tell, the temperature data is good and can be used in models without the salinity. So we would like to have the temperature data sent, but not the salinity.
Are there plans to implement variable based GTS release and have NCEI use the VARIABLE:gts_ingest attribute to determine what variables are released to GTS and what variables are not?
Reference
No response
The text was updated successfully, but these errors were encountered: