Dennis Heimbigner

Ok. I will put it on my stack.

No, see : https://github.com/Unidata/netcdf-fortran/issues/72 Passing a single string could be done, but there are a number of cases where we need to pass an array of strings (roughtly C char**)...

From the point of view of the Unidata netcdf group, named dimensions (shared dimensions in netcdf parlance) is essential for managing coordinate variables. So the netcdf extension to Zarr (or...

>NetCDF doesn't have explicit support for coordinates at all I do not believe this is completely correct; there is no syntactic support, but if you look at the netcdf 3...

WRT to things like units, you need to be very careful about embedding domain specific semantics into the data model. Our experience is that this is best left to metadata...

Remember that the same dimension may be used in multiple variables, so it is probably not a good idea to attach dimension information (other than the name) to a variable.

BTW, one common example of multidimensional coordinate variables is when defining a trajectory data set.

I stand corrected. One discussion of coordinate variables is here as a convention. https://www.unidata.ucar.edu/software/netcdf/docs/netcdf_data_set_components.html#coordinate_variables That reference says that it is a convention, but the source code does take them into...

A couple of other things. 1. I think Stephan two point are correct as guiding principles. 2. I think the simplest solution is to just implement simple named dimensions and...

I am aware of the problem, although it dropped off my radar recently. The problem is that it requires some significant re-factoring of the code to work with a NetcdfFIle...