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.

Re: [netcdfgroup] ncdump (snapshot2009102000) missing some coordinate variables for OPeNDAP data set

  • To: Jennifer Adams <jma@xxxxxxxxxxxxx>
  • Subject: Re: [netcdfgroup] ncdump (snapshot2009102000) missing some coordinate variables for OPeNDAP data set
  • From: John Caron <caron@xxxxxxxxxxxxxxxx>
  • Date: Tue, 27 Oct 2009 23:14:34 -0600
Jennifer Adams wrote:

I don't know about other OPeNDAP servers, but GDS won't allow a .dods request without any constraints.

the TDS doesnt care if there are constraints or not, but it will refuse requests larger than a configurable size. The default i think is 500 Mb for binary, and 50 Mb for ascii.

I guess I'm not happy about having to tell users they need to add something in order to use URL's which have worked for a number of years, or about having to change application code so it recognizes and passes a prefix on through to the open-nc routine.
I agree completely.

the netcdf-java opendap client doesnt support prefixes. in fact, it doesnt 
allow you to open a constrained dataset. you open the entire dataset, then send 
constraints to read the data. the idea is to treat a remote dataset the same as 
a local dataset. sometimes that doesnt work very well, but mostly it works ok, 
and its often a great advantage to the application who only sees the netcdf API.



  • 2009 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the netcdfgroup archives: