lveci/nest — pull request #14 by pmar (2013-06-27 18:40:03+00:00)
Title: Fix for correct handling of ASTER in InSAR modules and for Delaunay interpolation

Luis, here's the fix for correct ASTER handling - summary below. Please have a look.

The issue for InSAR and Delaunay was that I am using getGeoPos to define the interpolation space, and compute interpolation extent. This getGeoPos call was returning completely wrong values (was dividing instead of multiplying!), and when converting geo to radar coordinates something would shoot-off to infinity, and hence the reported error "radians only" would get triggered.

All InSAR tests pass now. I haven't tested non-InSAR Delaunay interpolation since it is skipped for this release.

-----

Fix for getGeoPos() of AsterElevationModel

AsterElevationModel.getGeoPos() now correctly computes Geographic
coordinates as a function of pixel index for ASTER DEM. This bug was
effecting correct use of ASTER DEM in InSAR modules, and modules
using Delaunay interpolation.

All InSAR tests passing.