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
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.