insarlab
Issue after ISCE2 Stitching of HyP3 Sentinel-1 Burst Products
Description of the problem Recently, HyP3 started providing Sentinel-1 Burst InSAR products, and MintPy has updated support for Multi-Burst products. However, HyP3 currently only supports up to 15 bursts per Multi-Burst product. To process more than 15 bursts, I downloaded multiple individual burst products (not Multi-Burst) from HyP3 and stitched them using ISCE2, which is capable of handling a larger number of bursts. The stitching process completed successfully, and the merged products are shown below.
However, when I tried to run smallbaselineApp.py in MintPy, I encountered a few issues:
- MintPy could not recognize the ISCE2-stitched product names.
******************** step - load_data ********************
load_data.py --template /home/jianbo/hyp3/test/burst_data/SBAS/smallbaselineApp.cfg processor : hyp3 SAR platform/sensor : unknown from project name "None"
prepare metadata files for hyp3 products
prep_hyp3.py "./data//unw_phase.tif"
/home/jianbo/anaconda3/envs/InSAR/lib/python3.11/site-packages/osgeo/gdal.py:311: FutureWarning: Neither gdal.UseExceptions() nor gdal.DontUseExceptions() has been explicitly called. In GDAL 4.0, exceptions will be enabled by default.
warnings.warn(
Traceback (most recent call last):
File "/home/jianbo/anaconda3/envs/InSAR/bin/smallbaselineApp.py", line 8, in
The naming convention did not match MintPy’s expected format. The format of ISCE stitched products and txt file as follows:
I fixed this by:
Renaming the product files to match the HyP3 SLC InSAR naming convention.
Editing the associated .txt files to update the "Reference Granule" and "Secondary Granule" fields. Since ISCE2's merged .txt contains multiple burst timestamps, I extracted and retained the earliest and latest timestamps.The file name and txt file after editing as follows:
After renaming and editing, MintPy was able to recognize and load the data.
- However, in the final velocity map, the individual bursts were not stitched together — there were visible gaps between the bursts (as shown in the attached figure).
Interestingly, this issue does not occur in the
timeseries.h5 file.The time-series outputs show properly connected bursts, indicating that the spatial stitching worked correctly at the time series level.
Although the time series file appears to be connected across bursts, it still shows unusual behavior, with deformation values from different dates being nearly identical in some cases.
System information
- Operating system: Ubuntu 22.04 LTS
- Python environment: conda
- MintPy version: MintPy version 1.6.1.post26, date 2025-04-01
- InSAR processor/product: hyp3, isce2
- Your custom / default template file (if the bug is related to a specific dataset):
Verify the hd5 files meta data and paste it here.
you can use command h5ls
https://mintpy.readthedocs.io/en/latest/api/data_structure/
The detail information of hd5 file by h5ls as follows:
~/hyp3/test/burst_data/SBAS$ h5ls velocity.h5
intercept Dataset {2805, 2688}
interceptStd Dataset {2805, 2688}
residue Dataset {2805, 2688}
velocity Dataset {2805, 2688}
velocityStd Dataset {2805, 2688}
~/hyp3/test/burst_data/SBAS$ h5ls velocity.h5 timeseries.h5
intercept Dataset {2805, 2688}
interceptStd Dataset {2805, 2688}
residue Dataset {2805, 2688}
velocity Dataset {2805, 2688}
velocityStd Dataset {2805, 2688}
bperp Dataset {22}
date Dataset {22}
timeseries Dataset {22/Inf, 2805, 2688}