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

[Support #ZKC-478244]: Python Siphon Thredds issue



Based on the error messages you sent, I agree that it looks like a problem with 
the GRIB file.

Did you clear out the data on the server? I don't see the data for 11-09-2017 
listed any more.

Ryan

> The more I look at this, I wonder if it is a bad grib file issue. I grabbed 
> the GFS 0.25 deg data from the DS84.1 on RDA instead of DS83.3 and the file 
> size is a bit different. Now I get an error of
> 
> 
> HTTPError                                 Traceback (most recent call last)
> <ipython-input-5-8551a4b29a20> in <module>()
> 2 gfsdata.variables('Pressure_reduced_to_MSL_msl').add_lonlat()
> 3 gfsdata.lonlat_box(60, 300, 10, 80)
> ----> 4 data = ncss.get_data(gfsdata)
> 
> /opt/conda/lib/python3.6/site-packages/siphon/ncss.py in get_data(self, query)
> 112
> 113         """
> --> 114         resp = self.get_query(query)
> 115         return response_handlers(resp, self.unit_handler)
> 116
> 
> /opt/conda/lib/python3.6/site-packages/siphon/http_util.py in get_query(self, 
> query)
> 377         """
> 378         url = self._base[:-1] if self._base[-1] == '/' else self._base
> --> 379         return self.get(url, query)
> 380
> 381     def url_path(self, path):
> 
> /opt/conda/lib/python3.6/site-packages/siphon/http_util.py in get(self, path, 
> params)
> 461             raise requests.HTTPError('Error accessing {0}: {1:d} 
> {2}'.format(resp.request.url,
> 462                                                                           
>    resp.status_code,
> --> 463                                                                       
>        text))
> 464         return resp
> 465
> 
> HTTPError: Error accessing 
> http://weather.aos.wisc.edu:8080/thredds/ncss/grib/NCEP/GFS/Global_0p25deg_ana/GFS_Global_0p25deg_ana_20171109_1800.grib2?var=Pressure_reduced_to_MSL_msl&time=2017-11-09T18%3A00%3A00&west=60&east=300&south=10&north=80&accept=netcdf4&addLatLon=True:
>  500 Not a GRIB-2 Data representation section
> 
> 
> I'm going to try to strip out just the MSLP record to a file of its own and 
> see what happens with that.
> 
> FWIW..
> 
> 
> Pete
> 
> 
> 
> <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
> Pete Pokrandt - Systems Programmer
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086  - address@hidden
> 
> 
> ________________________________
> From: Unidata User Support <address@hidden>
> Sent: Wednesday, November 29, 2017 2:10 PM
> To: Pete Pokrandt
> Subject: [Support #ZKC-478244]: Python Siphon Thredds issue
> 
> 
> Pete Pokrandt,
> 
> Your Ticket has been received, and a Unidata staff member will review it and 
> reply accordingly. Listed below are details of this new Ticket. Please make 
> sure the Ticket ID remains in the Subject: line on all correspondence related 
> to this Ticket.
> 
> 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.
> 
> Ticket ID: ZKC-478244
> Subject: Python Siphon Thredds issue
> Department: Support
> 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.
> 
> Please let us know how we can assist you further.
> 
> Unidata User Support
> 
> 
> 


Ticket Details
===================
Ticket ID: ZKC-478244
Department: Support Python
Priority: Normal
Status: Closed
===================
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.