You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only single ip1 values are decoded by fstd2nc.mixins.decode_ip1. This should be extended to properly decode the triplets rp1, rp2, rp3 and handle possible ranges encoded in those elements. Probably this logic should be moved outside of vcoords and put in another mixin, since both forecasts and vertical levels can encode this range information.
This is needed in order to support certain accumulated fields like precipitation.
The text was updated successfully, but these errors were encountered:
neishm
changed the title
Support level time ranges with (ip1,ip2,ip3) triplets.
Support level / time ranges with (ip1,ip2,ip3) triplets.
Oct 11, 2023
I originally thought it would be a straightforward case of passing ip1,ip2,ip3 through the rpnpy function DecodeIp, but after some testing it appears that function doesn't always give the appropriate ranges? May need to settle for patching in support piecemeal for each case based on what end users are expecting the ranges to be.
Currently, only single ip1 values are decoded by
fstd2nc.mixins.decode_ip1
. This should be extended to properly decode the triplets rp1, rp2, rp3 and handle possible ranges encoded in those elements. Probably this logic should be moved outside of vcoords and put in another mixin, since both forecasts and vertical levels can encode this range information.This is needed in order to support certain accumulated fields like precipitation.
The text was updated successfully, but these errors were encountered: