[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: Sat, 10 Mar 2012 12:55:41 -0700
> Dear Russ and Dennis:
> 
> Thanks for your responses. Is Unidata considering to add this functionality 
> in a later version?

If by "this functionality" you mean providing some sort of transparent packing 
and unpacking as 
currently exists for compression with netCDF-4, then yes, that's on our list of 
features to add.  
However it's not clear that using an HDF5 filter is the way we would implement 
it.

--Russ

> Concerning development under Windows I appreciate if you would inform me of 
> new developments. Should you need help doing independent tests please don't 
> hesitate to contact me.

Thanks for the offer.  We'll keep everyone on the netcdfgroup mailing list 
apprised of new developments
that provide better support for the Windows platform.

--Russ

> -----Ursprüngliche Nachricht-----
> Von: Unidata netCDF Support [mailto:address@hidden]
> Gesendet: Freitag, 9. März 2012 22:53
> An: address@hidden
> Cc: address@hidden; address@hidden
> Betreff: [netCDF #VIG-404579]: caching
> 
> 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
> 
> 

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



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