Closed pmar closed 11 years ago
The problem is NEST-core libraries that are used for handling DEM in jLinda functionality. The issue is being investigated by @lveci of NEST team.
Partially resolved with https://github.com/ppolabs/jlinda/commit/a43a827bfe7f3fdf2a64f765235f7ab8037498d2
Resolved with commit to NEST core https://github.com/pmar/nest/commit/f94f9efa7f2d670db1aa25df2b41e17bcbb6fe09 . See this pull request for details: https://github.com/lveci/nest/pull/14
Currently InSAR operators that in their processing require height information (eg. Subtraction of Topography, Coherence, DEM Assisted Coregistration etc.), are allowed to use as input only the 'official' DEMs (e.g., SRTM, ASTER, etc).
The support of type and formats of DEMs that are available for InSAR processing, should be extended for external and/or user-prepared DEMs.
(reported by @AndreaMinchella )