en Rouault wrote:
James,
ok, I confirm the bug. This was indeed specific to the new implementation of the
PCIDSK driver that came in 1.7.0.
See http://trac.osgeo.org/gdal/ticket/3755 for the fix
Le jeudi 16 septembre 2010 20:57:51, James Meyer a écrit :
Hi Even
Thanks for the reply. I ran you
ng ? which GDAL version ? Which GDAL driver is
used by your dataset ? etc etc ? If you run it under gdb, what is the stack
trace when it is blocked ?
Even
Le jeudi 16 septembre 2010 10:23:27, James Meyer a écrit :
Hi
I am opening a GDALDataset in my main thread which I then pass to a
secon
Hi
I am opening a GDALDataset in my main thread which I then pass to a
second thread for processing. Only the second thread accesses the dataset.
As soon as the thread makes a call to GDALRasterBand::RasterIO() the
thread blocks indefinitely.
Could you please explain to me why this is happe
Ah yes that's it.
Thanks a lot!
On 7/13/2010 2:33 PM, Frank Warmerdam wrote:
James Meyer wrote:
Hi
Actually I did call it.
Sorry I just didn't include it in the code because it was much
earlier in the program.
However after some playing around, it seems that the error only
o
t;);
printf("Releasing Resources\n");
GDALClose(dst);
free(data);
free(buffer);
//**
On 13/07/2010 13:37, Chaitanya kumar CH wrote:
James,
You forgot to call GDALAllRegister() before opening the dataset. Then
you will not get a NULL with GDALOp
Hi
I am trying to use MEM (In-memory) datasets with GDAL.
However, on trying to close the dataset I get a segmentation fault.
The dataset is created successfully. The handle returned is valid and I
am able to read and write to it.
Am I not supposed to try and close the handle or am I doing som
Hi
I am a new user of GDAL. I have a need for creating small image datasets
in memory without the use of physical files on disk.
So is it possible to open such a GDALDataset in-memory, and if it is, how?
Thanks,
James
___
gdal-dev mailing list
gdal-
