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.
Can you post an example URL using thredds-jetstream for me to investigate? > On second thought perhaps I was not using the correct server, thredds-jumbo > seems to work fine while thredds-jetstream is still giving me fits. > > address@hidden> wrote: > > > First, see if the data is accessible thru your web browser. > > Take the URL and add .dds to the end of the path (but before any ?....). > > e.g. http://x.y/a/b/c -> http://x.y/a/b/c.dds > > Stick this into your browser and see what you get. > > > > > > > > I was writing to check to see if there were any issues regarding the > > > OPENDAP access for the model data housed on Thredds Server. It seems that > > > if I try to access the data either through the Access Form on the server > > or > > > via a request from some python code (utilizing PyDAP) that I get an HTTP > > > 400 Error returned. The data is obviously available as I can see it is > > > there by looking at WMS link and downloading the grib file directly from > > > the server so I just wanted to write to check to see if access via > > OPENDAP > > > has been removed or if there is another Error going on. I attempted to > > > access the RAP, GFS, HRRR and NAM models with the same experience with > > > each. Thanks in advance for any insight or help you can provide. > > > > > > Kind Regards, > > > > > > Geoffrey Baum > > > > > > > > > > =Dennis Heimbigner > > Unidata > > > > > > Ticket Details > > =================== > > Ticket ID: JQR-339682 > > 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: JQR-339682 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.