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.
Greetings! So I replied on Gitter, but capturing here just as well. MetPy has azimuth_range_to_lat_lon--you only need to convert the x/y values to az/range values: https://unidata.github.io/MetPy/latest/api/generated/metpy.calc.azimuth_range_to_lat_lon.html?highlight=azimuth#metpy.calc.azimuth_range_to_lat_lon It would also be a good idea for us to do this work for the user when we improve the interface for the NEXRAD code. If you're interested, feel free to open a feature request: https://github.com/Unidata/MetPy/issues/new?assignees=&labels=Type%3A+Feature&template=feature_request.md Hope that helps, Ryan > Hello, > > I have a question regarding the storm tracking information within MetPy. I > have it returning information, but does MetPy convert the coordinates of > each storm to correct lat, lons? Right now all it’s returning is x and y > coordinates. > > If not, do you know of a way to possibly convert these to lat lons? I’ve > done research online but can’t seem to come to a conclusion. Ticket Details =================== Ticket ID: WCJ-104515 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.