[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[UDUNITS #JLQ-522131]: udunits2 and utScan, utIsTime

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.

  • Subject: [UDUNITS #JLQ-522131]: udunits2 and utScan, utIsTime
  • Date: Fri, 19 Oct 2007 16:06:35 -0600
Sue,

> Well, any time within a couple of weeks should be fine.
> If it takes more I might revert back and try my luck with udunits.
> 
> Is it the intention of udunits2 to be able to parse and resolve
> all CF-1.0 compliant time strings? Or is the whole CF compliance
> issue not a goal or part of the package?

The UDUNITS-2 package is designed to be compatible with the 
original UDUNITS package at the  unit string level.  Therefore,
the UDUNITS-2 package should correctly parse every valid unit
specification that the UDUNITS package parses. This should 
include the CF conventions on unit strings.

> Also, is udunits2 meant to replace udunits? ie. best for
> developers to move on with the new stuff or are these really
> diff packages?

The API-s of the two packages have some overlap but are really
different API-s (the UDUNITS-2 API is larger).  The UDUNITS-2
package is meant to replace the UDUNITS package.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: JLQ-522131
Department: Support UDUNITS
Priority: Normal
Status: Closed