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

[python #NMJ-899116]: Metpy/Cartopy Issues



Hi!

Your code looks like it should work. We just had someone else report this same 
error on StackOverflow, so we're going to dig in more to see what's going on. 
The only other version item I didn't get from you is what version of Python 
you're using. We will work on this and let you know when we figure out what's 
going on. 

Thanks,
Zach

> I have tried import metpy but it is still giving me the (ÂAttributeError: 
> 'Dataset' object has no attribute 'metpy' ) error. I am curious if you could 
> show me what you did on your end to get it working so I could see what my 
> difference is. I have attached my current form fo the code including the 
> import metpy.Â
> 
> On Friday, September 20, 2019, 12:38:58 PM PDT, wrote:
> 
> I think in the code I sent I had it in thereÂ
> 
> 
> Sent from Yahoo Mail for iPhone
> 
> 
> On Friday, September 20, 2019, 10:21 AM, Unidata Python Support 
> <address@hidden> wrote:
> 
> Thank you for providing the data! That was very helpful. However, I was able 
> to plug it into the code you provided. The only way I was able to recreate 
> your problem is if I didn't import anything from MetPy. Then the code 
> returned the same error you provided. As long as you import something from 
> MetPy, the xarray accessor should work.
> 
> Zach
> 
> > Here is the link to the nc 
> > fileÂhttps://drive.google.com/open?id=1xS_u7hFgLXGVEDCvvWfkrWQiG9fDGfoV
> >
> > On Wednesday, September 18, 2019, 12:28:12 PM PDT,
> > What email can i use to send it.
> >
> > On Wednesday, September 18, 2019, 09:08:51 AM PDT, Unidata Python Support 
> > <address@hidden> wrote:
> >
> > > Ok, it shouldn't be xarray, as we test for compatibility, so we'll move 
> > > past that for now. Is there a way to subset this file and provide it via 
> > > dropbox/drive/or some other method? Until we're able to recreate it on 
> > > our side, I'm not sure what's going on here, as the same script with a 
> > > different netCDF file works for me.
> >
> > Thanks,
> > Zach
> > >
> > >
> > > On Monday, September 16, 2019, 10:44:14 AM PDT,
> > >
> > > I just tried the pip install upgrade but it says that the 0.11.3 is the 
> > > current one on Canopy.Â
> > >
> > > On Monday, September 16, 2019, 10:38:03 AM PDT, Unidata Python Support 
> > > <address@hidden> wrote:
> > >
> > > Thanks for the version information. Could you update xarray to the 
> > > current version (v0.12.3) with pip install --upgrade xarray, and then 
> > > rerun the script? Just trying to see if some kind of incompatibility 
> > > error has crept up here.
> > >
> > > Thanks,
> > > Zach
> > > >
> > > >
> > > > On Monday, September 16, 2019, 10:32:51 AM PDT,
> > > >
> > > > I'm using the metpy that's available by the pip install metpy. Xarray 
> > > > is currently at 0.11.3-4
> > > >
> > > > On Monday, September 16, 2019, 10:28:09 AM PDT, Unidata Python Support 
> > > > <address@hidden> wrote:
> > > >
> > > > Thanks for sending that. This looks identical to the tutorial script 
> > > > (which works for me), at least through line 15. What version of MetPy 
> > > > are you using? Have you tried running the lines in order? If you run 
> > > > either line 7 or 9 (the MetPy import statements), then line 15 should 
> > > > work. If you run lines 1 to 15 and still get this problem, and are 
> > > > using MetPy v0.10.2, then we'll work to get a subset of your data 
> > > > maybe. Also knowing the version of Xarray that you're using may be 
> > > > helpful too.
> > > >
> > > > Thanks,
> > > > Zach
> > > >
> > > > > Here is the code as the nc/grib2files are so big.Â
> > > > >
> > > > > On Monday, September 16, 2019, 09:44:57 AM PDT, Unidata Python 
> > > > > Support <address@hidden> wrote:
> > > > >
> > > > > Hi!
> > > > >
> > > > > Can you send your script (if you've modified it from the tutorial 
> > > > > posted online) and data (if it's not too big)? Theoretically, the 
> > > > > MetPy Xarray accessor should be registered once you import anything 
> > > > > from MetPy (like the script does in line 9). So if you run this 
> > > > > script from top to bottom and you still get this error, that's 
> > > > > definitely an issue we need to investigate .
> > > > >
> > > > > Zach
> > > > >
> > > > > > I found the cartopy package after I had sent the email. However, a 
> > > > > > new problem has came upÂ
> > > > > >
> > > > > > Even though I have pip installed metpy.
> > > > > >
> > > > > > |
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thursday, September 12, 2019, 10:27 AM, Unidata Python Support 
> > > > > > <address@hidden> wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > So the error is complaining about not being able to find the GEOS 
> > > > > > library on your system when it's trying to build CartoPy from 
> > > > > > source. Looking at CartoPy's install instructions:
> > > > > >
> > > > > > https://scitools.org.uk/cartopy/docs/latest/installing.html#installing
> > > > > >
> > > > > > It appears that Canopy should have packages for CartoPy available, 
> > > > > > which I also see in the official Canopy package list:
> > > > > >
> > > > > > https://www.enthought.com/product/canopy/#/package-index
> > > > > >
> > > > > > So my advice would be to use Canopy's installer to install a 
> > > > > > prebuilt CartoPy package.
> > > > > >
> > > > > > Ryan
> > > > > >
> > > > > > > Hi there,ÂI am trying to follow theÂxarray with MetPy Tutorial 
> > > > > > > â MetPy 0.10Âtutorial. However, I am getting an error about 
> > > > > > > cartopy (Picture attached). I googled and I tried to do pip 
> > > > > > > install cartopy but I got another error (Picture also attached). 
> > > > > > > I am curious if there is a way to fix this?
> > > > > > >
> > > > > > > |
> > > > > > > |
> > > > > > > |Â |
> > > > > > > xarray with MetPy Tutorial â MetPy 0.10
> > > > > > >
> > > > > >
> > > > > > Ticket Details
> > > > > > ===================
> > > > > > Ticket ID: NMJ-899116
> > > > > > Department: Support Python
> > > > > > Priority: Low
> > > > > > 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.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > Ticket Details
> > > > > ===================
> > > > > Ticket ID: NMJ-899116
> > > > > Department: Support Python
> > > > > Priority: Low
> > > > > 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.
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > Ticket Details
> > > > ===================
> > > > Ticket ID: NMJ-899116
> > > > Department: Support Python
> > > > Priority: Low
> > > > 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.
> > > >
> > > >
> > > >
> > > >
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: NMJ-899116
> > > Department: Support Python
> > > Priority: Low
> > > 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.
> > >
> > >
> > >
> > >
> >
> > Ticket Details
> > ===================
> > Ticket ID: NMJ-899116
> > Department: Support Python
> > Priority: Low
> > 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.
> >
> >
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: NMJ-899116
> Department: Support Python
> Priority: Low
> 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.
> 
> 
> 
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: NMJ-899116
Department: Support Python
Priority: Low
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.