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.
>From: uhlman_w <address@hidden> >Organization: Regional Municipality of Durham, Ontario, Canada >Keywords: 199907211238.GAA20972 netCDF Y2K William, >My name is William Uhlman and I am the Y2K documentation coordinator for >the Regional Municipality of Durham, Ontario, Canada. We are a >registered user of your netCDF software and WHIPS software and would >like to request information regarding the Y2K status of your products. We now include in our netCDF Frequently Asked Questions list at http://www.unidata.ucar.edu/packages/netcdf/faq.html#y2k Is netCDF year 2000 compliant? All versions and releases of netCDF are year 2000 compliant, because none of the netCDF libraries or utilities deal in any special way with dates as a data type. If users want to represent date or time data in a netCDF file, they may choose their own convention for such representation in terms of basic data types such as integers, floating point numbers, or character strings. Use of the recommended units conventions supported by the udunits library for time assures year-2000 compliance, because the udunits package was designed to handle arbitrary times. This answer also indicates that the udunits package is Y2K compliant. We don't have any kind of certification, however. >Thank you in advance for your time. You are welcome. >Sincerely, >William Uhlman >-- >William Uhlman, M. Sc. >Y2K Documentation Coordinator >Durham Region >105 Consumers Drive Road >Whitby, ON, L1N 6A3 > >(905) 668-7725 ext. 5201 >Fax (905) 668-2051 >Email: address@hidden Tom Yoksas