Patrick

This is going to be a bit more complicated than it may appear at first. Variables (and dimensions) have a unique name in a NetCDF file; the same is not...

How about this: ``` > library(ncdfCF) > netcdf_file data subset(data[["TEMP"]], list(PRES = c(10, 20)), rightmost.closed = TRUE) 10 11 12 13 14 15 16 17 18 19 20 3.738 3.783...

Hi Milton, package `ncdfCF` will use whatever `netcdf` functionality is exposed to R through `RNetCDF`. I'll reach out if I find any issues. Working on reading groups and UDTs now....

Hi Dave @dblodgett-usgs, the focus of `ncdfCF` is two-fold. First is to provide easy access to NetCDF data using familiar R vocabulary, including basics like `dim()`, `dimnames()`, and `[` and...

**First the good bits:** `CFtime` already has function `CFtimestamp()` to produce `POSIXct` values. `as.POSIXct.stars()` would look like this: ``` as.POSIXct.stars = function(x, ...) { d = st_dimensions(x) for (i in...

I'm not sure that datum transformations would compare, unless people start producing their own transformation parameters. MAUP is a better analogue in my opinion, in that people may combine or...

This file contains climatology data which is why the year seems to be off (in fact it is off, it should be year 0 according to the COARDS convention which...

The [inverse situation](https://github.com/pvanlaake/CFtime/issues/9#issue-2509455047) also happens...

Hi Jintao, From the print of the file contents it is clear that the axes of the data sets are reversed from the recommendations in the CF Metadata Conventions. While...

On 28 March, @rhijmans wrote: > I need to investigate this a bit more, but this is probably because the file does not follow the CF standard. The NO2 file...