Update to gdal 1.9 and try again.
On Fri, May 31, 2013 at 2:36 AM, adi_khan adiba.niz...@gmail.com wrote:
I am using gdal 1.4.5 and wish to use gdal_merge to mosaic *.img images.
The command runs successfully (no error is reported) but the output file
contains the last input image and not
Hi,
GDAL 1.4.5 is ancient. Consider upgrading. The last release was 1.10.0.
Your commandline looks ok. Without knowing much about your input images or
what your output looks like it is hard to judge what went wrong.
Are img1.img, img2.img and img3.img spatially distinct? Is the produced
Am 31.05.2013 07:36, schrieb adi_khan:
I am using gdal 1.4.5 and wish to use gdal_merge to mosaic *.img images.
Please update to the current version. GDAL 1.10.0 is out now, available
for Windows via gisinternals.com.
Greetings,
André Joost
___
Thanks -- I did notice it was an earlier version (switching to the latest
OSGeo4W), I apologize for not checking the latest, but as Etienne
confirmed, the bug seems to be there in the latest as well. The HDF files
from various sources are so odd when it comes to naming layers, that this
SDS
Thanks for your reply frank.
I understand that the GDAL I am using is ancient, but considering 'upgrading
to other version' not an option could you tell me if there's a way I can
mosaic using 1.4.5 only?
Input images are spatially distinct. And the output image I.e. mosaic.img
was not already
On 31/05/2013 19:48, adi_khan wrote:
Thanks for your reply frank.
I understand that the GDAL I am using is ancient, but considering 'upgrading
to other version' not an option could you tell me if there's a way I can
mosaic using 1.4.5 only?
Another option is to use gdalwarp instead of
On Fri, May 31, 2013 at 7:47 PM, Jean-Claude Repetto jrepe...@free.frwrote:
On 31/05/2013 19:48, adi_khan wrote:
Thanks for your reply frank.
I understand that the GDAL I am using is ancient, but considering
'upgrading
to other version' not an option could you tell me if there's a way I can
David,
Note that the image cache will start discarding blocks on it's own when it
is full. I think the default cache is about 64MB.I don't think that
flushing the cache should be part of normal applications operations, though
if you are very tight on memory you might want to alter the
David,
I see I misunderstood about the free and it is already documented. So I
think the docs are good now and that most users should never even need to
think about the caching aspect.
Best regards,
Frank
On Fri, May 31, 2013 at 4:38 PM, Frank Warmerdam warmer...@pobox.comwrote:
David,
Hi everyone,
I am using below codes to try convert geometry from a Dgn file to Shape
file. But, I can't exit the FeatureReading loop:
void convert()
{
OGRRegisterAll();
OGRDataSource *poDS, *poSHPDS;
const char *pszDriverName = ESRI Shapefile;
OGRSFDriver *poDriver;
10 matches
Mail list logo
