pyart

pyart copied to clipboard

In Solox, there is a correction that can be made to airborne radar data to correct for aircraft motion in order to get ground relative velocities. I can't for the life of me find the metadata to fix this manually, so I'm not sure where to start on implementing a pull request, but I think this would be a very valuable feature to have in pyart.

Hello @aschueth ! Just one question, is solox another package I assume? What could always happen, if so, it can be made an optional dependency. With implementing a PR, I think in corrections in pyart.corrections would work. Depending on how the code is I can try to help guide this more.

Whoops, sorry @zssherman, I meant solox as soloii/solo3, the old NCAR c++ radar editor. Again I have no idea how it is written or what metadata it looks at, but hopefully someone in this community might have some knowledge?

Ah gotcha, makes sense. Yeah, I can ask around to see. I'll also labels to this Issue tracker. I agree, I think this would be a valuable feature to have in pyart as well. Trying to think on how to approach this.

It's been a long time since I looked at this code. Maybe @dstex knows how this is done?

FYI, the airborned specific variables are stored in the radar object and if memory serves me correctly, this either cfradial defined OR NOAA P-3 specific.

If it's a NOAA P-3 sigmet file, it looks like you might need to modify this function to include store one or all of the various ground speeds found in the header. Again don't recall which ground speed order or anything. But hope this helps to start.

This is something that is/was considered in the ongoing development of HawkEdit (the forthcoming solo replacement). They note the applicable corrections needed in these meeting notes.

As far as I can tell, the aircraft motion variables are included in both the P-3 sigmet files and the cfradials.

I'd be happy to look at working this into Py-ART in the near future (and/or testing any implementation against the solo-based correction).