On Tue, May 21, 2013 at 7:30 AM, Jose Gomez-Dans wrote:
> Hi Frank,
>
>
>
> On 21 May 2013 00:02, Frank Warmerdam wrote:
>
>> If you write a small part of an image, GDAL is likely to read a larger
>> area, update that and write it back. If other programs happen to try and
>> update the same larg
Hi Frank,
On 21 May 2013 00:02, Frank Warmerdam wrote:
> If you write a small part of an image, GDAL is likely to read a larger
> area, update that and write it back. If other programs happen to try and
> update the same larger area at the same time some data is likely to be
> lost.
>
Thanks
Jose,
I'm sorry, but I don't think this will work trivially.
If you write a small part of an image, GDAL is likely to read a larger
area, update that and write it back. If other programs happen to try and
update the same larger area at the same time some data is likely to be
lost.
If you are ca
Hi,
I have a rather demanding processing scheme (read data from files, and
process pixel per pixel). It's trivial to parallelise (just do pixels in
different machines/cores), and I intend to run this on several machines on
our cluster.
I'm unsure whether I can use GDAL (python bindings) like this.
