Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.
"Robert E. McGrath" <mcgrath@xxxxxxxxxxxxx> writes: > Yes, we made a deliberate design decision to not require dimension > scale datasets to be the same size as the dimension. > > There are use cases where you might not want this, e.g., the > scale values are every 5th tick mark. > > Also, it is not clear what the semantics should be if a dataset > is extended: what should happen to an associated dimension scale > dataset? What if it is shared by several datasets? > > As to the interpretation: that is entirely up to the application. > > In the case of NC4, you should define some constraints, perhaps > as conventions. If necessary, you could put an additional > attribute on the scale dataset, to indicate that this should > be interpreted according to NC4 conventions. > OK, thanks! Ed -- Ed Hartnett -- ed@xxxxxxxxxxxxxxxx
netcdf-hdf archives: