Nick Savage
Nick Savage
this is still important but I don't have any time to fix it myself
taking this back to basics. The problem is that the orginal UMDP F3 which was the basis of the pp load and save rules was somewhat lose in its teminology...
assuming a round trip with pp data is unchanged, then there are two other cases: 1. loading from pp and saving to some other format e.g. netCDF - this will...
What I could probably do is make the above changes (except the conversion of standard calendar) and then see which, if any, of the tests break
it sounds like this is an issue we will have to live with. Trying to make this backward compatible seems very hard but there is no consensus to make it...
No one ever looks at warnings.
I have to admit, I am now getting a bit lost with all of this. It came about because I needed to convert some netCDF data from the ACCESS model...
proposal in pp.py change calendar = cf_units.CALENDAR_STANDARD to calendar = cf_units.CALENDAR_PROLEPTIC_GREGORIAN and in pp_save_rules.py change elif time_coord.units.calendar == 'standard': to elif time_coord.units.calendar == 'proleptic_gregorian': then we have to decide how...
> option 2: convert calendar to proleptic greogrian before saving. Will only affect results for dates before 1582 I think this is the best solution here.
for now it would be worth this staying open as #5138 is close to being ready