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

[THREDDS #LSJ-656413]: Thredds Data Access Issue- Advice?

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: [THREDDS #LSJ-656413]: Thredds Data Access Issue- Advice?
  • Date: Thu, 23 May 2019 13:33:00 -0600
Seeing the exact URL you used would be helpful.
But my guess is that you are using OPeNDAP protocol
(which means that the URL has the substring "/dodsc/").
There is a default size limit for opendap requests, but
the thredds server owner can change it.
If you are using the netcdf-c library to access the thredds server, then
you can try the following:
1. prefix the URL with the string "[log][show=fetch]" so you
   get something like this: "[log][show=fetch]https://...";
2. Using that URL should produce some extra debug output
   that might tell you something.

> 
> I’m having trouble grabbing data from a Thredds Server set up by a 
> collaborator.  The first time I requested data, the server returned it within 
> about 2 minutes (the size of the output file was ~1.7GB).  However, the 
> second call that I submitted (for the same size file, just a different time 
> period) yielded no results- I just received an empty file immediately upon 
> return (size ~5 MB)… it seems as though the server became non-functional.
> 
> Could you please tell me what is going on?  Can you also let me know if there 
> is a size limit beyond which this issue occurs?  Is there a way I can correct 
> things once this issue has occurred?
> 
> 

=Dennis Heimbigner
  Unidata


Ticket Details
===================
Ticket ID: LSJ-656413
Department: Support THREDDS
Priority: Normal
Status: Open
===================
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.