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.
Steve, > I was recently looking at udunits and experimenting with the library > interface and wondered about one of the unit alias names. > > In udunits version 1, the symbol 'lbf' was associated with a > force_pound and a kip was defined as 1000 lbf. So in interactive mode: > > You have: kip > You want: > Definition: "4448.2216152605 kilogram meter second-2" > > However, in udunits 2, I see that lbf is now the symbol for force_ton, > although kip is still defined as 1000 lbf. So in interactive mode: > > udunits2: Using default XML database > You have: kip > You want: > 8896443.230521 m.kg.s-2 > You have: > > I was only really interested in lbf as I haven't seen this used as a > symbol for force_ton, and other units utilities on various unices > all report lbf as 4.448222e +00 m-kg/sec2 > > I just wondered if there a particular reason for the changed definition > of lbf in version 2? When searching for a reason, never overlook stupidity. :-) I've made a new release (v2.7.8) with "lbf" equal to "force_pound". Thanks for sending this in. > Steve > -- > ---------------------------------------------------------- > Yow! of the hour: > "The C Programming Language -- A language which combines the > flexibility of assembly language with the power of assembly > language." > ---------------------------------------------------------- Regards, Steve Emmerson Ticket Details =================== Ticket ID: AXH-450115 Department: Support UDUNITS Priority: Normal Status: Closed