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

[python #UMK-725743]: nexrad level III plotting with Metpy

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 #UMK-725743]: nexrad level III plotting with Metpy
  • Date: Thu, 15 Jul 2021 16:34:44 -0600
Greetings!

I'm glad you figured it out. That sounds like really poor behavior by 
`azimuth_range_to_lat_lon`, and I've opened an issue to remind us to improve it 
at some point:

https://github.com/Unidata/MetPy/issues/1970

Cheers!

Ryan

> Well, I figured out the main issue.  The range (rng) is in KM, but the
> metpy function  metpy.calc.azimuth_range_to_lat_lon expects meters.  So I
> multiplied range by 1000 and I get this:
> http://www.met.sjsu.edu/weather/radartest/demo-9.png
> 
> I ultimately figured it out by finding the range of lat and lon and seeing
> they were tiny, then it clicked it needed to convert range  to meters.


Ticket Details
===================
Ticket ID: UMK-725743
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.