Open karlmsmith opened 6 years ago
Comment by @AnsleyManke on 10 Dec 2010 23:56 UTC This is actually a behavior we put in when adding CF bounds to files, which behaves really badly in this instance, where we are using SAVE/APPEND to write out every Nth timestep to a dataset.
The bahavior is described in the Ferret v5.7 release notes: http://ferret.pmel.noaa.gov/FERRET_17sep07/Documentation/Release_Notes/v57.html#nc_bounds where it says,
"If there is a gap between time steps in the file and the first time step being appended, Ferret inserts a void point whose bounds are the upper bound of the last time in the file, and the lower bound of the first time step being appended."
We could allow the user to work around this with, perhaps, a new qualifier
SAVE/APPEND=discontiguous
or some such thing.
Comment by @AnsleyManke on 14 Dec 2010 00:34 UTC Or, SAVE/NOBOUNDS which has been requested elsewhere. Possibly a range of behaviors.
Reported by @AnsleyManke on 10 Dec 2010 00:25 UTC
The resulting file has a point at the midpoint between the upper bound of the grid cell of the first point and the lower bound of the cell of the second point
Possible solution: write discontinuous bounds, and on reading a file with discontinuous bounds, create new bounds between the coordinate locations.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1772