NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi ESIP, NetCDF, and THREDDS folks - First, I'm sorry for the cross posting. I have a hard time figuring out which NetCDF list does what; there are 'best practices' threads on several lists, interspersed with install and development threads. The OceanSITES project would like to find the most useful way to provide a link within a NetCDF file to an external dataset. > Another piece I am missing ... is an optional field, that link to a > data DOI. Why? Here's an example: We operate an OceanSITES site off > the Cape Verdes and the sediment trap data is ... not included in an > netcdf file but processed and stored elsewhere > https://doi.pangaea.de/10.1594/PANGAEA.863969 Does THREDDS have a standard way to provide links to related or co-located data? Is this something we discussed as part of ESIP's ACDD recommendations? I've been searching through my store of old messages, and haven't come up with anything. Thanks very much for any advice on this! - Nan Galbraith -- ******************************************************* * Nan Galbraith Information Systems Specialist * * Upper Ocean Processes Group Mail Stop 29 * * Woods Hole Oceanographic Institution * * Woods Hole, MA 02543 (508) 289-2444 * *******************************************************
netcdfgroup archives: