Skip to content
Prev 23956 / 29559 Next

raster pkg: overwriting the dimensions detected by netcdf4 (PERSIANN-CDR)

On Thu, 4 Feb 2016 at 02:20 MAURICIO ZAMBRANO BIGIARINI <
mauricio.zambrano at ufrontera.cl> wrote:

            
In addition, while reading the file with the latest version of GRASS
I wouldn't bother with the conversation if I were you. Just get your
toolkit in order and make sure you know what it's doing and why.  If you
explore their tools you might quickly understand why they're so adamant,
but it's not worth the time IMO.

library(fortunes)
fortune("illogical")

If there's a predictable pattern in the file you might explore a patch for
raster to auto-detect and handle it? I'd be happy to do that - if you
provide the data and as much information about it and its kind as you can
find.  If you want to know more I would start with ncdf4 directly, so you
see what raster has to do down there.

BTW, there's nothing strange about the way raster handles this in general,
if you peek under the hood in many software packages they all have the same
zoo of exceptions and special cases. NetCDF is incredibly general and that
flexibility gets pretty thoroughly abused. I have no patience for talk of
standards and conventions when it comes to this format, the data that
floods in just has to be dealt with, and that means your toolkit is full of
special cases (raster the details exceptionally well for its portion of
file variants).

Cheers, Mike.