Open aranas opened 1 year ago
Thanks for opening your first issue here at xarray! Be sure to follow the issue template! If you have an idea for a solution, we would really welcome a Pull Request with proposed changes. See the Contributing Guide for more. It may take us a while to respond here, but we really value your contribution. Contributors like you help make xarray better. Thank you!
What happened?
when converting calendar from a standard to a 360 calendar format on files with partial date spans (eg each file spanning one month), leap years will end up with 5 duplicate dates when later combining those partial files. Specifically, the dates that should be "dropped", end up being reassigned preceding dates which are covered already in a different partial file). This means that each partial/monthly file in a leap year, after conversion will have either 30 or 31 days, and after recombining those the full year will have 365 days.
(Partial files are needed for memory reason)
What did you expect to happen?
Instead we expect the total dates after recombining multiple files to amount to 360 days. We expect the dates that according to the documentation should be dropped for leap years, to be truly dropped, rather than reassigned a preceding date.
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
Anything else we need to know?
dates seem to be dropped fine when applying convert_calendar from standard to 360 to non-leap years
Environment