This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Tim, I can't verify that using spaces conforms to the CF standard because I don't know that standard. I can verify, however, that units like "meters per second" are perfectly acceptible to the UDUNITS package. > Hello, > > I'm looking at syntax for units here: > > http://www.unidata.ucar.edu/software/udunits/udunits-2.2.12/doc/udunits/udunits2lib.html#Syntax > > From the examples, it looks like I don't need to convert spaces to > underscores in my units attribute in a netCDF file. For example, I > could have: > > variable_name:units = "meters per second" ; > > (instead of variable_name:units = "meters_per_second" ;) > > However, I'm having trouble finding anything definitive in the > documentation. Will you please verify if I can have a CF-compliant netCDF > file with a units attribute with spaces in the value? > > Thanks, > > Tim Whiteaker > Research Scientist > The University of Texas at Austin Regards, Steve Emmerson Ticket Details =================== Ticket ID: SPR-727026 Department: Support UDUNITS Priority: Normal Status: Closed