Rafael Schouten

The dimension name difference is because Rasters switches some common x/y/z names into explicit X/Y/Z to standardize algorithms (e.g. rasterize knows to automatically rasterize polygons into X/Y dimensions and not...

Missing values in the dimensions may be a CommonDataModel/NCDatsets bug, I think its forbidden in the CF standard too. Rasters would not introduce that. Rasters will only give you Intervals...

Oh right my issue for the missing values was closed: https://github.com/Alexander-Barth/NCDatasets.jl/issues/185 We could just run `map(identity, lookup)` over the vectors before using them to remove `Missing`. @Alexander-Barth I think we...

#655 fixes the missing problem on the Rasters side for now

Ok in that case we really need a way to stop CommonDataModel from replacing the FillValue with missing at all. I'm going to overhaul `missing` handling and CF standards application...

> You can ignore the defined FillValue by setting it to nothing: We really need this at the point of loading the file or when getting a specific variable, for...

A right I have to stop reading these on mobile. We can allow setting that from Rasters fairly easily.

Great! If also added fixes to Rasters to avoid Missing in lookups

Ok its always assumed to be the center in CF standards, but I guess when a bounds matrix is provided we need to actually check that (and currently we dont)....

~~Oh that's the same with netcdf, bounds matrix is optional.~~ Oops I misread `now` for `not`. That is a pain, but we do try and check is `Regular` is ok...