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

Problem on Longitude #21

Open
ditafaith opened this issue Nov 7, 2024 · 9 comments
Open

Problem on Longitude #21

ditafaith opened this issue Nov 7, 2024 · 9 comments

Comments

@ditafaith
Copy link

Notebook name
MintPy_Time_Series.ipynb

Describe the bug
There was a problem with the longitude label.

Expected behavior
It should read 122 degrees

Screenshots
Selection_020

Are you running locally or in OpenSARLab?
Yes

System Info (If not working in OpenSARLab):

  • OS: Ubuntu
  • JupyterLab version 4.2.1
  • opensarlab_MintPy_Recipe_Book Version 1.0.1
  • Browser Chrome

Additional context
If possible, I request to enable unwrapping error (at least one method that available on MintPy).

@Alex-Lewandowski
Copy link
Contributor

Hi @ditafaith,

The longitude values are being displayed in scientific notation:
image

This is not something we can adjust in the notebook. It would have to be updated in MintPy itself.

Step 6 of the https://github.com/ASFOpenSARlab/opensarlab_MintPy_Recipe_Book/blob/main/c_MintPy_Time_Series.ipynb notebook performs optional unwrapping error correction. To run that step, you must first have enabled it in the https://github.com/ASFOpenSARlab/opensarlab_MintPy_Recipe_Book/blob/main/b_Update_Configuration.ipynb notebook.

@ditafaith
Copy link
Author

Thanks @Alex-Lewandowski for the feedback.
I understood the situation and expect the notebook in the future can accommodate this thing.

Since I use hyp3-gamma, it is still not possible to apply any unwrapping correction methods.

@Alex-Lewandowski
Copy link
Contributor

Hi @ditafaith,

Unfortunetly, the Minimum Cost Flow (MCF) program that GAMMA uses for phase unwrapping does not provide the option for outputting connected components data, which are required for both MintPy's unwrapping error correction methods.

@ditafaith
Copy link
Author

Hi @Alex-Lewandowski,

Glad to see that ASF provide ISCE-burst and make it possible to apply both corrections.

Do you know where is the file output in mintpy if we want to get coordinate (geo/UTM), velocity rate, and its error, such as a grid file. Not only an extracted point.

@Alex-Lewandowski
Copy link
Contributor

Alex-Lewandowski commented Nov 15, 2024

Hi @ditafaith MintPy saves output data to a MintPy directory, located in the directory containing the input data.

These are all saved as HDF5 files. You can find the geometry data in the MintPy/inputs directory.

image

@ditafaith
Copy link
Author

Thanks @Alex-Lewandowski

I understood that there is no single file containing coordinate and velocity together. Thus, these values should be extracted from velocity.h5 and geoGeometry.h5.

@ditafaith
Copy link
Author

Hi @Alex-Lewandowski
I still encounter problems to apply deramp using c_MintPy_Time_series.ipynb.
Will you plan to apply this feature to the notebook?

@Alex-Lewandowski
Copy link
Contributor

Alex-Lewandowski commented Feb 7, 2025

Hi @ditafaith, We have heard from several people recently who would like the notebook to support deramping. I have added this to our backlog, and we intend to add that support soon (weeks not months). I'll leave this issue open until that has been done.

This issue relates to #14

@ditafaith
Copy link
Author

Thanks @Alex-Lewandowski, glad to hear this response.
Also, will you consider enabling unwrapping correction on the notebook of MintPy, particularly for users who use ifgs from burst data?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants