Zhang Yunjun

I agree with you, that's the timing difference along the orbit! If it's not accounted for, this timing variation will introduce a small ramp along the azimuth direction for a...

> And also, how would this work if the specified step_size = 1? You wouldn't have a coarse grid, but would still shift the starting lat/lon by a pixel, unless...

> To clarify though, how do you envision this `swath` mode? Would you increment through multiple frames individually? From what I understand, merged products passed either through ISCE or ARIA...

> As far as commits to pysolid, I will issue a PR capturing your most recent suggestions regarding adjustments to the number of steps. Perhaps from there we could perhaps...

> Great, but to clarify I meant to stitch the downsampled products intentionally for the sake of efficiency/speed. I.e. current interpolation procedure takes ~a few secs or so depending on...

Thank you @scottstanie for the info and forwarding. Could you update the notes regarding the `--no-binary` and `-std=legacy` options? The long-term solution would be to translate the fotran code to...

Either `CMake` or `Meson` sounds good to me. I don't have a preference. Tagging @scottstanie for discussion.

The issue I had is not finding the orbit file. After downloading it manually using isce2, the error is gone.

We should print out a warning msg or raise error if `s1reader.get_orbit_file_from_dir()` returns empty.

Adding the `os.path.isfile(orbit_file)` sounds good to me. Since `load_bursts()` will be frequently used, I like the current passing of orbit_file, instead of an XML or list object. To be fair,...