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.
Rosalyn, > Whilst moving from udunits1 to udunits2 I have found some units which > were valid in udunits1 are not valid with udunits2 like M/S and W/M2. I > completely agree that units like these, in uppercase, should be invalid. Whilst? :-) I believe yours is the first email I've received to use that word. Thank you. > However, I've found a couple of units like K/DAY, METRES and DAY that > were invalid with udunits1 but are now accepted by udunits2. I and > others here think that these should also be invalid and only the > lowercase k/day, metres and day should be valid. Is this a mistake? > > I had a quick look but couldn't see anything that indicated criteria > about when a unit is allowed to be in uppercase and/or lowercase. > > I'd be grateful for some clarification. Unit symbol comparisons are case-sensitive but unit name comparisons are not. Thus, "M" and "S" are not allowed but "DAY" and "METRES" are. Will that be a problem? > Regards, > Rosalyn. > > -- > ------------------------------------------------------------------------ > Rosalyn Hatcher > NCAS Computational Modelling Services > Dept. of Meteorology, University of Reading, > Earley Gate, Reading. RG6 6BB > Email: address@hidden Tel: +44 (0) 118 378 6016 Regards, Steve Emmerson Ticket Details =================== Ticket ID: RIM-618234 Department: Support UDUNITS Priority: Normal Status: Closed