NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Jennifer Adams wrote:
Hi, Dennis -- I'm sorry to pepper you with questions, but I think this is really important and I'm eager for the DAP interface in netcdf-4 to work well with GrADS and the GDS.
No problem; I need all the feedback and bug reports and opinions I can get :-) I want to get this right.
Requiring prefixes on OPeNDAP URLs is inconsistent with libnc-dap and a pretty significant change to the OPeNDAP user interface.
Actually, libnc-dap has always supported the prefixes, although you probably never used them. I too would like to get rid of them and hopefully the defaults will be such that user rarely need them.
Can configuration options such as [fetchlimit=1] be parsed from the user's .dodsrc file instead?
This is an open issue here in the netcdf group. Historically, the use of environment variables or .rc files has been avoided in favor of various flag setting extensions to the interface.
Also, if client-side cacheing is disabled, will that append the '?varname[constraints]' syntax to requests like 'GET model.dods'? --Jennifer
Yes, it will ask for a specific variable only and will do so using dap projection constraints. =Dennis Heimbigner
netcdfgroup archives: