[Gdal-dev] Re: gdalwarp -tps weirdness

[Hamish]

> > I'm trying to use gdalwarp's new thin plate spline warping but it is
> > doing funny things. Seems like a memory stomping problem but I'm not
> > sure. Doing things like changing the order of GCPs (dozen placed by
> > hand with gdal_translate) or the length of the output filename makes
> > it either work or have the output go haywire.
> > 
> > anybody come across this before?
> 
> I had a problem much like this some time ago. Maybe you are
> experiencing something similar? Anyway here is an excerpt of the
> original correspondence with Frank:
> 
> My question: 
> ---
> > I grew some gray hair finding out, that you can´t have a numeric
> > filename when you use gcps with gdal_translate.
[...]
> Franks answer:
> ----
> Asger, 
> The problem is that there is an optional elevation argument in the
> -gcp switch.  The usage message should look like this (now updated):
> 
>    [-gcp pixel line easting northing [elevation]]*
> 
> In order to determine if an elevation is supplied, the program tries
> to read a numeric value from the argument.  If it gets a non-zero
> value it treats it as elevation. ---


Yes, I found that one too. Filed it as bug # 863 (gdal_translate).
:)
My work-around was to put something after the -gcp entries and before
the input source name.  "-co compress=lzw" does the trick.


This doesn't solve bug # 864 though (gdalwarp).
:(



thanks,
Hamish