The initial files that have been mirrored over and are under going testing have resulted in creation of the 2 emails below. The non CF "standard_name =" "profile_time" was used in two files. The files already include "Profile Time" as a "long_name -" which complies with CF.
My opinion as that we should go ahead and archive these data but that this issue will be resolved in new files.
Regards,
Tom
1
The IOOS National Glider Data Assembly Center Submission
/nodc/data/IOOS-GDAC/SIP/SG609-20140719T1700.ncCF.nc3.nc cannot be processed.
CF Standard Name "profile_time" not found in Climate and Forecast standard names to NODC data types cross walk
2
The IOOS National Glider Data Assembly Center Submission
/nodc/data/IOOS-GDAC/SIP/SG610-20150206T1750.ncCF.nc3.nc cannot be processed.
SG610-20150206T1750.ncCF.nc3.nc: time_qc:standard_name "profile_time status_flag" not found in CF Standard Names Mapping Table
Implemented compliance checker on incoming data sets. Notification of invalid/missing standard_name values on the deployment registration page and data provider will be notified by @kerfoot