Gdalwarp speed comparison

3 messages Options Options
Embed this Post
Permalink
Rahkonen Jukka

Gdalwarp speed comparison

Reply Threaded MoreMore options
Print post
Permalink
Hi,

I made some time ago a few measurements about the speed in of reprojecting
images with gdalwarp and and another software.  Results can be found from here:
http://forums.ermapper.com/viewtopic.php?t=2889

Another software had an option to use an option called "Speed optimization"
which had a big effect on speed. It believe it relates somehow to warping either
in bigger blocks or pixel-by-pixel. I wonder if gdalwarp is utilising something
similar because it tends to be so fast?

-Jukka Rahkonen-

_______________________________________________
gdal-dev mailing list
gdal-dev@...
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Frank Warmerdam

Re: Gdalwarp speed comparison

Reply Threaded MoreMore options
Print post
Permalink
Jukka Rahkonen wrote:

> Hi,
>
> I made some time ago a few measurements about the speed in of reprojecting
> images with gdalwarp and and another software.  Results can be found from here:
> http://forums.ermapper.com/viewtopic.php?t=2889
>
> Another software had an option to use an option called "Speed optimization"
> which had a big effect on speed. It believe it relates somehow to warping either
> in bigger blocks or pixel-by-pixel. I wonder if gdalwarp is utilising something
> similar because it tends to be so fast?

Jukka,

By default gdalwarp uses a linear approximator for the transformations with
a permitted error of (I think) a quarter pixel.  This basically transforms
three points on a scanline.  The start, end and middle.  Then it compares the
linear approximation of the center based on the end points to the real thing
and checks the error.  If the error is less than the error threshold then
the remaining points are approximated (in two chunks utilizing the center
point).  The error threshold (in pixels) can be controlled with the
gdalwarp -te switch.

So if you want to compare a true pixel-by-pixel reprojection you should
use "-te 0" which disables this approximator entirely.

I assume the speed optimization techniques in the ERMapper tool are in some
fashion similar.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@...
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org

_______________________________________________
gdal-dev mailing list
gdal-dev@...
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Matt Wilkie-2

Re: Gdalwarp speed comparison

Reply Threaded MoreMore options
Print post
Permalink
Thank you for the explanation Frank. I'd wondered about that switch.
Recorded for posterity at
http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp#Howdoes-etErrorThresholdwork
as always please check for accuracy or faithfulness.

> The error threshold (in pixels) can be controlled with the gdalwarp
> -te switch.

typo: that should be '-et', as written is Target Extent.


cheers,

matt wilkie
--------------------------------------------
Geographic Information,
Information Management and Technology,
Yukon Department of Environment
10 Burns Road * Whitehorse, Yukon * Y1A 4Y9
867-667-8133 Tel * 867-393-7003 Fax
http://environmentyukon.gov.yk.ca/geomatics/
--------------------------------------------



_______________________________________________
gdal-dev mailing list
gdal-dev@...
http://lists.osgeo.org/mailman/listinfo/gdal-dev