-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: use max_num_gates for calculation of data shape #1337
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good @kmuehlbauer! Thanks for putting this together!
That works for reading the data, but it will crash during the plot (I am trying to plot the first elevation): File "dual_pol.py", line 15, in A sample file can be downloaded at: https://1drv.ms/u/s!AjzwFqty9OKPiPwNlxYAGzNyHDoLfQ?e=WUk03I |
Yes, what a pity, I've missed to fix the range as well. I'll add the needed changes. Thanks for the data file. I can confirm, that the range resolution changes in your file between sweeps. That contradicts the current Py-ART CfRadial1-based datamodel. @zssherman @mgrover what's the current workaround in that case? |
Yes, the range varies too. I've contacted the radar operator to change this because it doesn't make sense to me, but I've sent the file anyway as a good test file for reading a really bad-formatted file... |
I would not say it's bad formatted. It makes sense to increase the range resolution with increasing elevation which results in better height resolution for higher angles. That's one reason CfRadial2 was invented, a data model also Py-Art will switch to, with the help of Update: fix decrease -> increase |
Good to know about that improvement in CFRadial2. This file I've sent also changes the azimuth number between elevations (360/361). It's a good test file I guess. |
solves #1336
But only if range resolution is same for all sweeps.