Closed richardsc closed 9 months ago
I just noticed that I messed up my fork/edit/PR and did it on the main
branch instead of develop
. @dankelley let me know if you want me to do it again.
Thanks. I'll propagate it into the develop etc.
PS. no, I didn't get a notification. I can't for the life of me figure out what setting controls that. I do pay for GH, and wish there were some way to get help on such things.
Thanks for your help on this, folks. Your package has been very useful in getting Sentinel V data into a usable .nc state!
This PR arose from a recent issue noted by @kurtisanstey where the netCDF file creation fails if the variables are "too big" (I put this in quotes because I don't actually know what the limit is). This appears to be a limitation of the netCDF v3 file, which is what
ncdf4::nc_create()
defaults to, by way of theforce_v4=FALSE
argument.All I've done here is to add the
force_v4
argument tooce2ncdf()
(and each of the sub-functions, e.g.adp2ncdf()
), but with a default value ofTRUE
. Considering netCDF v4 was released in 2008, I think we're safe to assume that most people creating new nc files are fine with using version 4.