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

[python #XSV-292843]: MetPy Cross Section issue

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: [python #XSV-292843]: MetPy Cross Section issue
  • Date: Wed, 12 Jun 2019 14:15:24 -0600
Hi Kyle,

I've played around with your data for awhile and was able to recreate your 
issue, but I can't seem to find a way around it. What's odd is that the example 
dataset that we use for testing also has both data types ('int64' and 
'datetime64[ns]) in it that are reportedly causing this issue, so I don't 
believe that it's explicitly the nanoseconds that's the problem here (see 
example here: 
https://unidata.github.io/MetPy/latest/examples/cross_section.html). That being 
said, I don't know what is causing this issue. Hopefully future data you have 
works with our cross-section code. I apologize for not having a quick solution 
for you!

Best regards,
Zach Bruick

 

Hey Ryan,

https://www.dropbox.com/sh/m8i1fphge73fxsc/AABJl5ezvyPzrkZHEtnd4pJEa?dl=0 
<https://www.dropbox.com/sh/m8i1fphge73fxsc/AABJl5ezvyPzrkZHEtnd4pJEa?dl=0>

Above is the link to the directory with the WRF-ARW data. Let me know if you 
have troubles getting it or anything. I have also attached one of my 
cross-sections that I made from the same file with wrf-python for reference. 
Thanks again for doing this! 



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