topsApp: Add ability to select specific bursts for processing

[forrestfwilliams]

As organizations such as JPL, ASF, and ESA move towards burst-centric Sentinel-1 IW processing, it would be great to add a more intuitive way to select specific burst for processing via topsApp. Right now, it's possible to select specific burst for processing via carefully selecting a region of interest, but this method can be error prone when trying to select a single burst due to the way that bounding boxes for neighboring bursts overlap.

I'd like to propose adding an optional burst number property to the reference and secondary xmls that would behave in a similar way to the swath number and would allow a user to select specific bursts that they want to process.

For example:

<?xml version="1.0" encoding="UTF-8"?>
<component name="reference">
  <property name="safe">S1A_IW_SLC__1SSV_20150119T135944_20150119T140004_004241_005286_4271.SAFE</property>
  <property name="swath number">2</property>
  <!-- proposed addition below-->
  <property name="burst number">7</property>
</component>

My initial investigation suggests that changes would need to be made to the preprocessor step, and the crop method of the Sentinel1 class.

I'm happy devote a significant amount of work to this effort, but would like to have buy-in from ISCE2 team as well as some guidance on the best way to proceed.

[forrestfwilliams]

@yunjunz, any chance you'd be interested in this effort?

[yunjunz]

@yunjunz, any chance you'd be interested in this effort?

Hi @forrestfwilliams, I am not super interested in this, since ISCE3 and OPERA had done it and hopefully be ready in the very near future, so I would just wait for that. On the other hand, I am not a heavy user of topsApp (more into topsStack).

[forrestfwilliams]

Sounds good! We need this for our HyP3 burst products so I'll keep working on this, but I understand where you're coming from.