Closed rzinke closed 5 months ago
Hi @rzinke, I think your solution sounds good to me. Just to put more details out, so that we could be more in sync on the design, here is what I am thinking:
one downloader & one reader for each GNSS solution / sources. This should give us the following variables:
other functions should be generic, including the search function given the SNWE and time period of interest, with an additional flag for the source/solution; and the analysis functions based on the above variables.
I would be more than happy to answer any questions if there is, please do not hesitate to let me know.
Hi @yunjunz, thanks for information--this is very helpful, and matches with what I deduced from the code. I'm definitely happy to hear thoughts and work with fellow developers on this.
Hello @yunjunz, @falkamelung, I have finalized pull request #1173 in which I have adapted mintpy/objects/gps to work with multiple GNSS data sources. I have tested the objects and functions in the gps module, as well as "downstream" routines such as view.py
, tsview.py
, plot.py
, and insar_vs_gps.py
. The pull request is waiting for at least one reviewer. What is the process for finding reviewers?
Thank you @rzinke for the PR! I will take a look at this later this week.
Description of the desired feature
Currently, MintPy only supports UNR solutions. It would be helpful for it to support multiple (or generic) solutions.
Describe the solution you'd like One flag to select among different supported solutions (e.g., 'UNR', 'ESESES', 'JPL'). And a generic file structure for less common velocity/displacement formats.
Additional context Especially useful for NISAR cal/val.
Are you willing to help implement and maintain this feature?
I (rzinke) will provide an initial pull request within 10 days of 27 March 2024.