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

[netCDF #AMK-356058]: NetCDF with all leap years -- how's that done?

Did the answers to the stackoverflow question provide you
with an idea how to do this?

> 
> Please refer to the updated StackOverflow question here:
> https://stackoverflow.com/questions/49185907/netcdf-how-to-create-list-of-time-values-for-years-with-366-days-all-leap-or-3
> 
> If I can fill Feb 29th's time value with the time value from Feb 28th
> during non-leap years then this shouldn't be an issue for me when I read
> the data myself later in my processing. However, I'd like to make sure I
> can also use visualization tools such as Panoply and see the actual time
> step I think I'm seeing, and not face a compounding off-by-one problem that
> I'm not aware of due to an inability of the software to interpret the dates
> as intended. This has probably already been worked out, but I've not found
> good/conclusive documentation on this and I'm trying to clarify before I
> get too far into weeds.
> ?
> --James?
> 
> 
> address@hidden> wrote:
> 
> >
> > James Adams - NOAA Affiliate,
> >
> > Your Ticket has been received, and a Unidata staff member will review it
> > and reply accordingly. Listed below are details of this new Ticket. Please
> > make sure the Ticket ID remains in the Subject: line on all correspondence
> > related to this Ticket.
> >
> > NOTE: All email exchanges with Unidata User Support are recorded in the
> > Unidata inquiry tracking system and then made publicly available through
> > the web.  If you do not want to have your interactions made available in
> > this way, you must let us know in each email you send to us.
> >
> >     Ticket ID: AMK-356058
> >     Subject: NetCDF with all leap years -- how's that done?
> >     Department: Support netCDF
> >     Priority: Normal
> >     Status: Open
> >
> >
> >
> > The NetCDF libraries are developed at the Unidata Program Center,
> > in Boulder, Colorado, funded primarily by the National Science Foundation .
> >
> > All support requests are handled by the development team. No dedicated
> > support staff are funded at this time. For this reason we cannot guarantee
> > response times, nor that we can resolve every support issue, although we
> > do our best to respond within 72 hours.
> >
> > It is in the nature of support requests that the same question is asked
> > many
> > times. We urge you to search the support archives for material relating to
> > your support request:
> >
> > http://www.unidata.ucar.edu/search.jsp?support&netcdf
> >
> > If you are having trouble building netCDF, please take a look at the
> > "Building NetCDF" page:
> >
> > http://www.unidata.ucar.edu/software/netcdf/docs/building.html
> >
> > or the (unfortunately somewhat out-of-date) NetCDF Build Troubleshooter
> > page:
> >
> > http://www.unidata.ucar.edu/software/netcdf/docs/troubleshoot.html
> >
> > Windows users should see the FAQ list:
> >
> > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#
> > windows_netcdf4_2
> >
> > Complete documentation (including a tutorial, and sample programs in C,
> > Fortran,
> > Java, and other programming languages) can be found on the netCDF
> > Documentation page:
> >
> > http://www.unidata.ucar.edu/software/netcdf/docs/
> > http://www.unidata.ucar.edu/software/netcdf/examples/programs/
> >
> > If you resolve your issue through one of these methods, please send a
> > reply to
> > this email, letting us know that you no longer need support. This will help
> > us spend more time on netCDF development.
> >
> > Best regards,
> >
> > Unidata User Support
> >
> >
> 
> 
> --
> ?
> James Adams
> Scientific Programmer, Government Contractor, ERT, Inc.
> ?
> Center for Weather and Climate (CWC)
> ?
> NOAA's National Centers for Environmental Information (NCEI)
> address@hidden
> 
> 

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: AMK-356058
Department: Support netCDF
Priority: Emergency
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.