Hi,
we were running into the same issues and solved it by this workaround: use
Windows 8.3 filenames and paths for ECW files:
// WORKAROUND for either a GDAL issue or an issue within the ECW
library used by GDAL:
// when opening ECW files with unicode chars in the filename or
p
Hi all,
what is the current state of the adoption and implementation of RFC #26
(http://trac.osgeo.org/gdal/wiki/rfc26_blockcache)? Are there any plans to
finalize the development for it?
-Konstantin
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
Hi Etienne,
maybe you could also use the ESRI WKTs from: http://spatialreference.org/
e.g.: http://spatialreference.org/ref/epsg/4326/esriwkt/
Kosta
> -Original Message-
> From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-
> boun...@lists.osgeo.org] On Behalf Of Etienne Tourigny
>
And add x64 support to that list, too...
Kosta
-Original Message-
From: gdal-dev-boun...@lists.osgeo.org
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Christopher Barker
Sent: Wednesday, January 05, 2011 5:49 PM
To: gdal-dev@lists.osgeo.org
Subject: Re: Fwd: Re: [gdal-dev] FWToo
Hi Even,
the fallback to double/real does only help if the integer could be stored in 52
bits, since the rest of the bits are reserved for the mantissa and sign =>
exact up to ~15 decimal digits.
I proposed a fix 3 years ago to change the data type to string in order to not
loose data:
Hi,
what benefit/improvement would the OpenCL integration bring to GDAL? Additional
functionality or a speedup of existing functions? Probably only operations on
images and/or rasters are supported; reprojection/warping and filtering would
be good candidates, right? What concrete operations wou
> -Original Message-
> From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-
> boun...@lists.osgeo.org] On Behalf Of Daniel Morissette
> Sent: Tuesday, April 27, 2010 17:28
> To: gdal-dev
> Subject: Re: [gdal-dev] Motion: Promote GDAL/OGR 1.7.2 RC3 to Final
> Release
>
> Frank Warmerdam
Hi!
There are two RFCs regarding the Unicode issues:
RFC #5: http://trac.osgeo.org/gdal/wiki/rfc5_unicode
RFC #23: http://trac.osgeo.org/gdal/wiki/rfc23_ogr_unicode
RFC #23 seems to be adopted for GDAL 1.6. But to me it is not that clear,
which functions/me