-
Notifications
You must be signed in to change notification settings - Fork 4
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
Dateline Unwrapping #81
Conversation
from shapely.geometry import box | ||
|
||
from isce2_topsapp.dateline import unwrap_geometry | ||
|
||
|
||
def test_wrapping(): | ||
bbox_unwrapped = box(-181, 51, -179, 53) | ||
bbox_wrapped = box(-179, 51, 179, 53) | ||
|
||
out_bbox_unwrapped = unwrap_geometry(bbox_wrapped) | ||
|
||
# Set equality is demonstrated by double containment | ||
bbox_unwrapped.contains(out_bbox_unwrapped) | ||
out_bbox_unwrapped.contains(bbox_unwrapped) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This summarizes what we are doing by unwrapping - maybe not a good idea to say "unwrapping" but the similarities were sort of similar to the phase scenario...
Let me know if there is a better term.
This will not pass until ACCESS-Cloud-Based-InSAR/dem-stitcher#50 is merged. |
|
It appears there is an issue with isce2 as well using the command above. When I ran with the appropriate version of dem-stitcher for staging the unwrapped DEM. ISCE2 is fitting the extents of the merged data within +/- 180 longitude as seen below.
And
The xml looks like:
|
I am going to close this for the time being. This is an ISCE2 issue and should be resolved there. |
Solves #78