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

Nexrad Level2 different range resolution not taken into account #263

Open
kmuehlbauer opened this issue Feb 4, 2025 · 0 comments
Open
Labels
bug Something isn't working

Comments

@kmuehlbauer
Copy link
Collaborator

See #259 for an example case.

For sweep number 4, 5, 6 REF is 1000m range resolution whereas VEL and SW is 250m resolution. In the pyart reader the lower resolution data is interpolated to the higher resolution data to fit into the radar object.

Unfortunately this was overlooked on implementation time that this not only happens between sweeps (which would not be a problem here) but also within a certain sweep. So how to resolve this issue for xradar?

I'd really like to avoid this interpolation/upsampling, to not change the source data. We could just add another sweep/group in these cases. WDYT @openradar/xradar?

@kmuehlbauer kmuehlbauer added the bug Something isn't working label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant