Hi
Simultaneous writers would be a better long term solution as we often improve
the raster following initial creation. This improvement may well be a filter
run on a sub region ( eg a despeckle) or updating a piece of the dtm with
better information or even some manual edits as a last resort.
This is about the same acceleartion (2-3 times) as I got on jobs running
for a few days. My impression is that distributed tile processing would
give much more dramatic results.
On 01/12/2013 03:57 PM, Even Rouault wrote:
Le samedi 12 janvier 2013 15:08:55, Jan Hartmann a écrit :
You probabl
I would be interested in an implementation. I'm preparing a proposal to
georeference the complete cadastral map of the Netherlands in 1832 at a
10 cm/pixel scale with Cloud facilities. Gdalwarp is the central piece
of software, and distributed processing capabilities would be very
important. Co
> ex. convert
> multiple datasets to different output datasets in a parallel way.
As Frank underlined, there's currently an issue with the global block cache
regarding write support.
Imagine that you have 2 threads A and B.
Thread A deal with dataset A, and thread B deal with dataset .
Thread A
Le samedi 12 janvier 2013 02:38:55, Kennedy, Paul a écrit :
> Hi,
> Yes, we are pretty sure we will see a significant benefit. The processing
> algorithms are CPU bound not io bound. Our digital terrain model
> interpolations often run for many hours ( we do them overnight) but the
> underlying fi
Le samedi 12 janvier 2013 15:08:55, Jan Hartmann a écrit :
> You probably know this, but there is an option to let gdalwarp use more
> cores: -wo NUM_THREADS=ALL_CPUS. It gives some improvement, but not
> really staggering.
Do you use Proj 4.8.0 ? If not, that might explain why you don't see a
si
To add my 2cnts.
With MapWindow GIS we use TauDEM binaries to perform watershed delineations.
http://hydrology.usu.edu/taudem/taudem5.0/index.html
These TauDEM binaries are optimized to use MPI, but also work if you don't
have MPI installed.
I don't know in detail how it works but in general you
You probably know this, but there is an option to let gdalwarp use more
cores: -wo NUM_THREADS=ALL_CPUS. It gives some improvement, but not
really staggering. Splitting up operations over individual tiles would
really fasten up things. Even if I use only one VM, I can define 32
cores, and it wo
Hi Ivan
it seems to me like the GeoRasters is somewhat special, but I think it
warrants flagging it as supporting subdatasets regardless.
A generic example is the netcdf driver, which supports subdatasets
when a given netcdf file contains several variables, which can have
different CRSs. Each var
