netCDF CF reader should be more lenient on time units.
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
In order to specify a dimension as time within the netCDF CF reader, there must be a dimension variable with a units properties containing a string of a known time unit (as per the CF specification). However, that check is currently only looking for the substrings " since " or " until " expecting the units to be in the form of "<time_unit> since " or "<time_unit> until ". However, the reader should also accept strings that match a valid <time_unit>.
The CF convention defines units as anything accepted by the udunits package (http://www.unidata.ucar.edu/software/udunits/). The attached udunits.dat (a text file) should contain a complete list of all time units that should be supported.