Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross InSAR functionality #8

Closed
pmar opened this issue Jun 12, 2013 · 5 comments
Closed

Cross InSAR functionality #8

pmar opened this issue Jun 12, 2013 · 5 comments

Comments

@pmar
Copy link
Collaborator

pmar commented Jun 12, 2013

No description provided.

@ghost ghost assigned pmar Jun 12, 2013
@pmar
Copy link
Collaborator Author

pmar commented Jun 13, 2013

Core class and functionality implemented and committed. Operator needs to be profiled and further tested.

@pmar
Copy link
Collaborator Author

pmar commented Jun 27, 2013

80% work finished with: 3bfe2dd . There is still functionality for updating of metadata to be merged from non-public branches, and issues with random crashing to be resolved.

Still, I will not continue building this operator on top of NEST/JAI functionality. Will come back to it after new coregistration is being released. I need new resampling for this.

@pmar
Copy link
Collaborator Author

pmar commented Aug 17, 2013

Closed with: 3bfe2dd + 129f109

@pmar pmar closed this as completed Aug 17, 2013
@pmar
Copy link
Collaborator Author

pmar commented Nov 4, 2013

Operator UI still needs some work. CrossResampling has an Action missing (see disussion at #21). This is developed in some of local branches - integrate and publish.

@pmar pmar reopened this Nov 4, 2013
@pmar
Copy link
Collaborator Author

pmar commented Mar 4, 2014

Major rework of Cross Intereferometry functionality

Ref. commit: 76a942d .

Summary:

The fnc is now more generic - instead of working on the stack of coarse coregistered SLC's the operator is re-worked to resample an image from the input geometry into the other one, that is selected by the user. In this case from ERS/ASAR geometry to ASAR/ERS respectively.

The idea behind this rework is that the operator can be reused - by plug in of the other deterministic relationships between other SAR geometries - for other cases that are similar to resampling needed for optimal Cross-InSAR. For example Deskewing of 'Actual Doppler' acquired ALOS data.

Workflow example: cross_insar_workflow

Testing

Operator/fnc tested on South Holland ERS/Envisat pairs. Coherence is there, but very likely something is going wrong with orbit handling. See Examples.

Example 1: Result of Cross Interferogram using annotated orbits.

cross_insar_results_2

Example 2: Result of Cross Interferogram using DORIS orbits for ASAR and annotated for ERS2. Changes in the fringe pattern suggest that ERS2 orbits are not reliable for InSAR. Unfortunately, NEST cannot 'ApplyOrbit' for ERS2 using EIGEN-GRACE01S. Issue is communicated to @lveci - the main developer of NEST.

cross_insar_results_1

Known Issues:

  • Issues with orbital trends under investigation. Most likely will be resolved using Eigen-Grace01s orbits for ERS2 acquisitions.

pmar added a commit that referenced this issue Mar 18, 2014
@pmar pmar closed this as completed in 0abcec2 Mar 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant