gdaltransform/gdalwarp -tps: incorrect results for some control point sets
For some sets of control points gdaltransform and gdalwarp give incorrect results when using the -tps option. Adding or removing a control point almost always gives correct results. AFAICS, when wrong, the transformed x-coordinate gets very big, or even overflows into a negative number. Gdalwarp shows this error sometimes at the beginning, while computing the boundaries of the output-file. It then gives messages like: output file > 4 G, or; negative output file boundaries.
Attached three almost identical gdaltransform scripts, with respectively 17, 18 and 19 control points. Only with 18 control point the transformed x-value leaps out of bounds
Change History
(4)
Keywords: |
gdaltransformer tps added
|
Milestone: |
→ 1.4.5
|
Resolution: |
→ duplicate
|
Status: |
new → closed
|
This bug is clearly a duplicate of #2300 and after updating to r14117, I confirm it is now fixed.