Running ncks on the Canada Mosaic datasets fails because they are classic and not nc4. Add an nccopy step if the files are classic.
HINT: NC_EBADTYPE errors can occur when NCO tries to write netCDF4 features to a netCDF3 file, and, separately, when a variable's type conflicts with its _FillValue type.
1. netCDF4 features that cannot be defined in a netCDF3 file, and that thus will trigger this error, include groups and netCDF4 atomic types (e.g., NC_STRING, NC_UBYTE, NC_INT64).
To avoid this, remove all netCDF4 features before attempting to convert them to netCDF3 format, or write a netCDF4 output file instead of a netCDF3 output file.
2. The netCDF best practice is for _FillValue attributes to be the same numeric type as their host variables.
nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_put_vara()
Running ncks on the Canada Mosaic datasets fails because they are classic and not nc4. Add an nccopy step if the files are classic.