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

[netCDF #VIG-404579]: caching

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: [netCDF #VIG-404579]: caching
  • Date: Fri, 09 Mar 2012 14:52:33 -0700
Russ is correct, there is currently no obvious
way to get a meaningful time of last modification.
You may be able to get some useful information
from whatever catalog service is available on
the server you are using.

Let me add that there is a limited form of caching
already in the dap code in the netcdf library.
It does not, however, live across sessions.
If you put the tag "[cache]" in front of the URL
before passing it to nc_open, then the whole dataset
will be retrieved and will be used in subsequence calls
to e.g. nc_get_vara. The cache entry goes away
upon calling nc_close.




=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: VIG-404579
Department: Support netCDF
Priority: High
Status: Closed