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

VRADH and DBZH moments may be loaded from different sweeps, and DBZH-only sweeps dropped #132

Open
adokter opened this issue Oct 10, 2019 · 0 comments
Milestone

Comments

@adokter
Copy link
Owner

adokter commented Oct 10, 2019

Certain older NEXRAD data has different range resolution for lowest three (250 m) and highest two (500 m) elevation scans, as well as different resolutions for different moments, e.g.
https://noaa-nexrad-level2.s3.amazonaws.com/2010/09/11/KBGM/KBGM20100911_012056_V03.gz:

moment range azim elev
R 1000 1 3.5, 4.5
R_HI 250 0.5 0.5, 0.5, 1.5, 1.5, 2.5, 2.5
V 250 1 3.5, 4.5
V_HI 250 0.5 0.5, 1.5, 2.5
  • When multiple scans at same elevation are available, WSRLIB uses largest PRF sweep for radial velocity and spectrum with, and lowest PRF for reflectivity. I think a better approach would be to keep the reflectivity scan acquired simultaneously with reflectivity, so largest PRF sweep in all cases. However, currently the behaviour is unclear, because unclear which of two sweeps at identical elevation is returned by RSL_get_sweep(sweep, elev). Have to add control over this in vol2bird.
  • Related: the above file includes multiple reflectivity scans that do not have associated radial velocity. These are currently not used or stored in converted ODIM output. Add access to these
@adokter adokter added this to the 1.0 milestone Oct 10, 2019
@adokter adokter changed the title sweeps loaded from RSL may have VRADH and DBZH from different sweeps VRADH and DBZH moments may be loaded from different sweeps, and DBZH-only sweeps dropped Oct 10, 2019
@adokter adokter modified the milestones: 1.0, 0.6 Nov 6, 2019
@adokter adokter modified the milestones: 0.6, 0.7 Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant