Skip to content

ISCE output - MiaplPy input #130

Description

@Basin-Ir

I am a beginner in using MiaplPy, but I managed to run it successfully using the sample data. The sample file and example provided with the package are as follows:

wget https://zenodo.org/record/6539952/files/PichinchaSenDT142.zip
unzip PichinchaSenDT142.zip
cd PichinchaSenDT142
miaplpyApp.py PichinchaSenDT142.txt --dir ./miaplpy

Now, I have tried to create new input data for MiaplPy using ISCE2 based on my own Sentinel-1 images. My goal is to later use the MiaplPy output in the SARvey package. According to the documentation, the input for MiaplPy should have the following structure:

ISCE_processed_data
├─ reference
│ ├─ IW*.xml
│ └─ ...
├─ merged
│ ├─ SLC
│ │ ├─ YYYYMMDD
│ │ │ ├─ YYYYMMDD.slc.full
│ │ │ └─ ...
│ │ ├─ YYYYMMDD
│ │ ├─ YYYYMMDD
│ ├─ geom_reference
│ │ ├─ hgt.rdr.full
│ │ ├─ lat.rdr.full
│ │ ├─ lon.rdr.full
│ │ ├─ los.rdr.full
│ │ └─ ...
└─ baselines
└─ YYYYMMDD_YYYYMMDD
└─ YYYYMMDD_YYYYMMDD.txt

And this input should correspond to the output of ISCE2. After running ISCE2 for about five hours, a large number of massive files were generated on my system, and the processing completed successfully. However, I cannot find the files that MiaplPy requires as input among the ISCE2 outputs!

I used the following command and the output is very large. I expected it to only output for the defined BBox which is a small range!

python /home/behzadsarhadi/tools/isce/applications/topsApp.py --steps /mnt/c/WSLData/SARvey_Rey/topsApp.xml

Image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions