GDAL cannot be used to manipulate the netcdf dimension definitions.
You should use something specialized in dealing with netcdf dimensions such
as cdo [1] or nco [2].
[1] https://code.zmaw.de/projects/cdo
[2] http://nco.sourceforge.net/
On Tue, Apr 14, 2015 at 2:46 AM, Dominik Schneider <
domini
Sorry, edit - the setZ line should be:
r <- setZ(r, dt0)
On Wed, 15 Apr 2015 at 00:40 Michael Sumner wrote:
> Well, FWIW -
>
> Here the CRS doesn't round-trip properly, partly as the PROJ.4 string in R
> is not sufficient, and the date type gets recorded as raw integer (that's
> ok depending
Well, FWIW -
Here the CRS doesn't round-trip properly, partly as the PROJ.4 string in R
is not sufficient, and the date type gets recorded as raw integer (that's
ok depending what your target environment will need). Using gdal_translate
you could augment the netcdf created here with a proper WKT
Hi Mike - Thanks for the response and sorry this wasn’t quite clear. IDL
data cubes are of the ENVI format and thus also have an associated ascii
.hdr file. A dataset with 10 bands is here:
https://dl.dropboxusercontent.com/u/5962491/IDLENVIswe.zip
There is no time data in the .mdl file, but I know
On Tue, 14 Apr 2015 at 05:46 Dominik Schneider <
dominik.schnei...@colorado.edu> wrote:
> Hi -
>
> I have some .mdl files from IDL with .hdr header files that I’d like to
> convert to netcdf.
> The following code produces a netcdf file with a subdataset for each band
> in the mdl file. Is there an
Hi -
I have some .mdl files from IDL with .hdr header files that I’d like to
convert to netcdf.
The following code produces a netcdf file with a subdataset for each band
in the mdl file. Is there any way to define the bands as the time
dimension, in this case 4416 hourly timesteps?
Or is there an
