On 12-06-25 1:44 PM, Etienne Tourigny wrote:
> There is no need for a workaround - Paolo simply did not configure
> gdal properly. Netcdf support in windows builds is a little different
> but is quite simple - just a few lines to edit in nmake.opt
>
Ah ok thanks Etienne, I was scared there for a
There is no need for a workaround - Paolo simply did not configure
gdal properly. Netcdf support in windows builds is a little different
but is quite simple - just a few lines to edit in nmake.opt
On Mon, Jun 25, 2012 at 12:45 PM, Jeff McKenna
wrote:
> On 12-06-25 12:25 PM, Paolo Corti wrote:
>>
Thanks again to Etienne for helping with this.
After closing the filed ticket [1] he has updated the wiki page [2] as
well with this, so most likely no one can be in my same shoes
p
[1] http://trac.osgeo.org/gdal/ticket/4717#comment:7
[2] http://trac.osgeo.org/gdal/wiki/NetCDF
Thanks for upda
On 12-06-25 12:25 PM, Paolo Corti wrote:
> On Mon, Jun 25, 2012 at 4:41 PM, Etienne Tourigny
> wrote:
>> For informatioon: the problem was that Paolo was using custom netcdf
>> libraries and did not add the proper option to configure
>>
>> --with-netcdf=/usr/local
>>
>
> Thanks again to Etienne f
On Mon, Jun 25, 2012 at 4:41 PM, Etienne Tourigny
wrote:
> For informatioon: the problem was that Paolo was using custom netcdf
> libraries and did not add the proper option to configure
>
> --with-netcdf=/usr/local
>
Thanks again to Etienne for helping with this.
After closing the filed ticket [
For informatioon: the problem was that Paolo was using custom netcdf
libraries and did not add the proper option to configure
--with-netcdf=/usr/local
Etienne
On Wed, Jun 20, 2012 at 5:47 AM, Paolo Corti wrote:
> On Tue, Jun 19, 2012 at 7:48 PM, Etienne Tourigny
> wrote:
>> no... unless your s
On Tue, Jun 19, 2012 at 7:48 PM, Etienne Tourigny
wrote:
> no... unless your system uses the hdf5 driver before the netcdf driver.
>
> If the netcdf driver detects a hdf5 file that ends with nc, nc2, nc4
> or cdf (the common extensions) then it opens it, else it passes it to
> the hdf5 driver.
> T
On Tue, Jun 19, 2012 at 2:25 PM, Paolo Corti wrote:
> Hi Etienne
>
>> I would guess your netcdf and gdal installation do not have netcdf-4 support.
>> And probably a 'gdalinfo ' shows the hdf5 driver picks it up, right?
>
> That was!
> I was missing out the --enable-netcdf-4 option: after recompil
Hi Etienne
> I would guess your netcdf and gdal installation do not have netcdf-4 support.
> And probably a 'gdalinfo ' shows the hdf5 driver picks it up, right?
That was!
I was missing out the --enable-netcdf-4 option: after recompiling
netcdf with that option option and then recompiling GDAL ev
That file does not use the "bigfile" flag, but it is probably a
netcdf-4 file (with hdf5 storage).
Regardless, "bigfiles" are supported since gdal-1.9.0 on 32-bit platforms.
I would guess your netcdf and gdal installation do not have netcdf-4 support.
And probably a 'gdalinfo ' shows the hdf5 dri
Paolo,
I had a similar issue with 32b system with some NetCDF files with "bigfile"
flag.
We should use (if I remember correctly) 64b system.
Regards,
Y.
Le vendredi 15 juin 2012 12:10:57 Paolo Corti a écrit :
> Hi all
>
> While I can succesfully read NetCDF in Mint 12 (my development
> enviro
Hi all
While I can succesfully read NetCDF in Mint 12 (my development
environment), I cannot manage to read the subdatasets in REL5 (the
production server).
In REL5 I can succesfully read the NetCDF dataset with gdalinfo:
gdalinfo /my/full/path/mydataset.nc4
But if I try reading a subdataset, I
12 matches
Mail list logo
