Skip to content
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

incorrect read of nyquist velocity and range resolution for specific NEXRAD files #166

Closed
adokter opened this issue Nov 23, 2020 · 1 comment
Assignees
Labels
Milestone

Comments

@adokter
Copy link
Owner

adokter commented Nov 23, 2020

Two related problems, exemplified in certain NEXRAD files, e.g. file KLOT20080905_002257_V03.gz:

  • Range resolution is read from the ray information provided by RSL_get_first_ray_of_volume() using the reflectivity volume, such that the range resolution is always taken from the first lowest-elevation reflectivity sweep. As a result, the range resolution is read incorrectly if there is a change in range resolution at higher elevation scans. Higher elevation sweeps may have larger range bins, causing these higher elevations scans to projected incorrectly (at too close range / too low altitude). The range resolution should be read for each sweep individually.
  • Nyquist velocity is always taken from the reflectivity data of a given sweep. As a result, incorrect Nyquist velocity might be read, because Nyquist velocity of the reflectivity sweep can differ from the radial velocity sweep. Older NEXRAD files may have reflectivity sweeps collected with different PRFs, one short-range matching the radial velocity sweep, and one additional long-range. RSL reads only the long-range sweep, causing a mismatch in PRF and Nyquist velocity between the radial velocity and reflectivity scan parameter collected at the same elevation. A solution to this problem is to take the Nyquist velocity from the radial velocity data.
@adokter adokter added the bug label Nov 23, 2020
@adokter adokter self-assigned this Nov 23, 2020
adokter added a commit that referenced this issue Nov 23, 2020
@adokter
Copy link
Owner Author

adokter commented Nov 23, 2020

fixed by #167

@adokter adokter closed this as completed Nov 23, 2020
@adokter adokter added this to the 0.6 milestone Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant