-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bugs in NEXRAD L2 reader #180
Comments
@ghiggi might be my fault. Could you please create a minimal example without |
Just use
|
@ghiggi The first one is most likely an issue with not taking the 1-based day count into account here: xradar/xradar/io/backends/nexrad_level2.py Line 1336 in 2d266bb
So we would need to subtract 1 day on that line, before transforming to milliseconds. Feel free to send in a PR to correct this. For the second issue I'll need a deeper look into next week. |
Ahhh okay - that makes sense... agreed, I can dig into this a bit more next week as well. |
Description
I identified two bugs affecting the NEXRAD L2 reader.
time
coordinates andtime_coverage
variables to be shifted by 1 day compared to the actual time. This impacts all NEXRAD L2 files.Can someone have a look at it ? Maybe @mgrover1 who implemented the reader?
Here below I provide MCVE and error logs.
MCVE - Time is shifted by 1 day
MCVE -
IndexError: list index out of range
Error log:
The text was updated successfully, but these errors were encountered: