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
Unless Unidata decides to forward requests from the former URL to the latter, it'd likely be good to update the link, which would be relatively straightforward. However, I'm not sure how your internal processes for backporting link fixes to documents takes place, as the same link exists in the current draft version as well as a number of other older versions of the standard.
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out. As far as I can see, there isn't a reference to the NUG in section 4.4, but there is a reference to UDUNITS, which takes you to the list of references at the end of the document. In that list, the link to NUG is given as http://www.unidata.ucar.edu/software/netcdf/docs/user_guide.html, which doesn't work, as you say. Is this what you mean?
We should fix it, so I'll change this to a defect issue. As far as I know, we don't attempt to fix previous versions.
In attempting to research what the exact allowable format for relative time units for CF section 4.4 for ioos/compliance-checker#947, I found a broken link referenced for the NetCDF Users Guide at http://www.unidata.ucar.edu/software/netcdf/docs/user_guide.html
It seems the NUG now resides at https://docs.unidata.ucar.edu/nug/current/index.html .
Unless Unidata decides to forward requests from the former URL to the latter, it'd likely be good to update the link, which would be relatively straightforward. However, I'm not sure how your internal processes for backporting link fixes to documents takes place, as the same link exists in the current draft version as well as a number of other older versions of the standard.
The text was updated successfully, but these errors were encountered: