Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
nns@xxxxxxxxxxxx (Nancy Soreide) write: > ... our EPS I/O library always returns to the > calling routines a two-integer array in which the first integer is the > "true Julian Day Number" with units of days, and the second integer is > the number of milliseconds since midnight of the true Julian Day.... We too use the two-integer approach to time. We assign two separate integer variables "time_day(time)" and "time_msec(time)" that have the Julian Day and millisecond of day as used above. We too use the millisecond of day from midnight. Maintaining milliseconds as an integer maps directly to our satellite data. Our data can cover many years as well. Using integers means we are assured that all bits of the original information are preserved.
netcdfgroup archives: