issue_comments: 489164504

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/1849#issuecomment-489164504 https://api.github.com/repos/pydata/xarray/issues/1849 489164504 MDEyOklzc3VlQ29tbWVudDQ4OTE2NDUwNA== 2448579 2019-05-03T16:51:40Z 2019-05-03T16:51:40Z MEMBER

Because it's set in your input file. Both example files in this thread have _Storage = 'contiguous' set on all variables but the dimensions are not unlimited, so these files are compliant. Here's the output of ncdump -sh sample.nc (second comment in this thread)

``` netcdf sample { dimensions: y = 6 ; variables: float x(y) ; x:_FillValue = NaNf ; x:_Storage = "contiguous" ; x:_Endianness = "little" ; int64 y(y) ; y:_Storage = "contiguous" ; y:_Endianness = "little" ;

// global attributes: :_NCProperties = "version=1,netcdflibversion=4.4.1.1,hdf5libversion=1.8.18" ; :_SuperblockVersion = 0 ; :_IsNetcdf4 = 1 ; :_Format = "netCDF-4" ; ```

When you ask xarray to write out an unlimited dimension, it doesn't delete encoding['contiguous'] and then netCDF4 raises an error (I think).

It's probable that the underlying software you're using to write has probably changed versions and is setting it by default. You can check this by comparing the output of ncdump -sh file.nc on cheyenne and your local machine

If this is right, the solution would be either a) delete encoding['contiguous'] if it is True when asked to write out an unlimited dimension. b) raise a warning and ask the user to do the deletion before writing.

My preference is for (a).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   290572700