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

FIX: Elevation Angle for some products #925

Merged
merged 1 commit into from
Apr 3, 2020

Conversation

dcedgren
Copy link
Contributor

@dcedgren dcedgren commented Apr 1, 2020

Many Nexrad Level 3 files have elevation angle defined by Halfword 30 of the product description block, but not all. (Elevation angle is not relevant for all products.)

Added a list of products for which elevation angle is defined by Halfword 30 per Table V of the ICD. For products for which it is not defined added logic to return data as None.

Many Nexrad Level 3 files have elevation angle defined by Halfword 30 of the product description block, but not all. (Elevation angle is not relevant for all products.)

Added a list of products for which elevation angle is defined by Halfword 30 per Table V of the ICD. For products for which it is not defined added logic to return data as None.
@dcedgren
Copy link
Contributor Author

dcedgren commented Apr 1, 2020

Addresses Issue #923.

@zssherman
Copy link
Collaborator

@dcedgren Thanks again for another change. The only thing is the data too None. I wonder if there should be a warning of some sort. Without elevation data, plotting etc I don't think will no longer work. So I'm having a think on that one.

@dcedgren
Copy link
Contributor Author

dcedgren commented Apr 3, 2020

@zssherman, I don't know what the trickle-down might be. Products without elevation angle should be able to be plotted as a PPI but would be undefined to be plotted as an RHI. None makes more sense to me, but if we need to change it to zero to avoid compatibility issues with other modules that seems ok, too.

@zssherman
Copy link
Collaborator

@dcedgren I also think None would be the way to go. Only thing I would suggest is when elevation data is set to None a user warning stating that some functionality will be limited such as rhi plotting. @scollis are you good with this route?

@scollis
Copy link
Member

scollis commented Apr 3, 2020

Yep! And thanks for the initiative!

@dcedgren
Copy link
Contributor Author

dcedgren commented Apr 3, 2020

@zssherman this is something you can work on, right? Can you add a separate commit to this pull request?

@zssherman
Copy link
Collaborator

@dcedgren ofcourse, I'll except the PR and submit a separate commit. Thanks again for the PR!

@zssherman zssherman merged commit 5689a32 into ARM-DOE:master Apr 3, 2020
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

Successfully merging this pull request may close these issues.

3 participants