Hi Chris,
> I'm going to venture a guess that the netcdf Java libs can [handle the
> "T"] (anyone know for sure?)
Yes, the netCDF-Java library can parse date/time strings with the "T".
Ethan
On Fri, Sep 23, 2016 at 1:26 PM, Chris Barker wrote:
> On Thu, Sep 22, 2016
I totally agree. Don't deprecate anything but definitely encourage ISO
8601:2004(E) with the caveat of requiring an offset-from-Z indicator.
Cheers,
Ethan
On Fri, Sep 23, 2016 at 9:38 AM, Bob Simons - NOAA Federal <
bob.sim...@noaa.gov> wrote:
> Seth McGinnis said:
> "I hesitate to support
Hi all,
NetCDF-Java has no issues with T or no T in an ISO time string.
Sean
On Friday, September 23, 2016, Ethan Davis wrote:
> Hi Chris,
>
>
>> I'm going to venture a guess that the netcdf Java libs can [handle the
>> "T"] (anyone know for sure?)
>
>
> Yes, the netCDF-Java
Picking this up again after a long silence.
I have been discussing this with my colleagues at KNMI and have gotten some
comments from Alison Pamment (thanks). The conclusion is that we would like
to revise the suggestion somewhat.
The proposal for the wind stress divergence is essentially
Seth McGinnis said:
"I hesitate to support encouraging the use of the T because in my
experience, approximately 0% of existing NetCDF files have it."
a) We aren't advocating forbidding the older formats / saying that files
with those time formats will become invalid. This is a question of what we
For LUMIP we would like to propose several new variables, listed in the
attached excel spreadsheet, to the list.
Thanks,
Dave Lawrence and Elena Shevliakova
CMIP6DataRequest_LUMIP_propose_to_list.xlsx
Description: MS-Excel 2007 spreadsheet
___
On Thu, Sep 22, 2016 at 2:11 PM, Aaron Sweeney - NOAA Affiliate <
aaron.swee...@noaa.gov> wrote:
> In case you and others are not already aware the Internet Engineering
> Task Force (IETF) RFC 3339: "Date and Time on the Internet: Timestamps,"
> circa 2002, (see