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

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

Ok, with ncss, what I suggested will not work.
At the bottom of the ncss page you fill in, there should be
a box labeled "NCSS Request URL". Please post the contents of
that box.

> ...hmmm just shows that the page won't open when I try the log option you 
> suggested?
> 
> Thanks again!
> Kristi
> 
> 
> 
> Kristin Burkholder, Ph.D.
> 
> Assistant Professor of Environmental Science
> 
> Stonehill College
> 
> ________________________________
> From: Burkholder, Kristin C.
> Sent: Thursday, May 23, 2019 3:41 PM
> To: address@hidden
> Subject: Re: [EXT]: [THREDDS #LSJ-656413]: Thredds Data Access Issue- Advice?
> 
> Great, thanks for the suggestions. Here is the link that I'm using:
> 
> http://oceanus.meas.ncsu.edu:8080/thredds/ncss/grid/useast/roms/2007-2017_hindcast.nc/dataset.html
> 
> And yes, I was trying to extract .nc files, so I will give that fetch option 
> a try.
> 
> Does the link give you any more hints as to what might be happening?
> 
> Thanks so much for your help- I'm right at the edge of my knowledge here so I 
> appreciate it!
> 
> Kristi
> 
> 
> 
> Kristin Burkholder, Ph.D.
> 
> Assistant Professor of Environmental Science
> 
> Stonehill College
> 
> ________________________________
> From: Unidata THREDDS Support <address@hidden>
> Sent: Thursday, May 23, 2019 3:33 PM
> To: Burkholder, Kristin C.
> Cc: address@hidden
> Subject: [EXT]: [THREDDS #LSJ-656413]: Thredds Data Access Issue- Advice?
> 
> 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.
> 
> 
> 
> 

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