[GRASS-dev] New georectifying module in TclTk

[Michael Barton]

Hamish,

It sounds like most of the issues can be avoided by using i.rectify -c. What
are the disadvantages of using the -c switch? It is not very clear (to me)
in the docs.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Hamish <hamish_nospam at yahoo.com>
> Date: Tue, 6 Jun 2006 22:35:32 +1200
> To: Maciek Sieczka <werchowyna at epf.pl>
> Cc: <michael.barton at asu.edu>, <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] New georectifying module in TclTk
> 
> Michael:
>>> (Is 3rd order georectification still broken?)
> Maciek:
>> Broken?! Can you elaborate on it? The last time I used i.rectify few
>> mnonths ago I only noticed that 2nd order output is somewhat strange
>> (map borders became convex, in general rectification result worse
>> than 1st and 3rd order), but 1st and 3rd produced a reasonable
>> output...
> 
> see
>  https://intevation.de/rt/webrt?serial_num=3166
> related ?
>  https://intevation.de/rt/webrt?serial_num=3052
> 
> also
>  https://intevation.de/rt/webrt?serial_num=3296
> 
> I think GDAL order=3 will have the same problems, as both started from
> the same code.
> 
> I didn't know order=2 had problems..?
> 
> 
> 
> Michael:
>>> There has been some discussion about dropping i.rectify for
>>> gdalwarp. I¹ve used i.rectify here, but it is probably possible to
>>> rewrite this to use gdalwarp in the future.
> 
> I think we should keep i.rectify but use GDAL's warp API for the heavy
> lifting. (as opposed to the "gdalwarp" program)
> 
> see
>  https://intevation.de/rt/webrt?serial_num=2952
>  http://www.gdal.org/warptut.html
> 
> 
> Hamish