[Feature Request] Usage Improvements for S1 Data

[dsherman-insar]

Hello all,

I am very interested in using this repo to download Sentinel-1 data with ESA. Would it be possible to add the following features:

1. filter queries by relative orbit number if provided all the time

• currently, in search.py > query_by_filter(), the relative_orbit_number is only checked if burst_mode is enabled. It would be useful to filter a query based on the relative_orbit_number and other parameters regardless if I am searching with bursts (via burst_mode) or for full scenes. Would this be possible to implement?

2. detect if a scene/group of bursts partially or fully covers my polygon query

• I do not know if there is a way currently to determine if a query or relative orbit partially or fully covers my polygon. In my application, it is very important that I have a fully covered polygon. Would it be possible to implement this functionality?

3. download and merge bursts covering my polygon

• if I understand properly, when downloading bursts I need to specify the file path for the burst in CopernicusDataSearcher.download_product(). It would be convenient to be able to download all bursts intersecting with my polygon and merge them all into the same manifest.safe. Would this be possible to implement if my second point is implemented?

Thank you very much, already this repo is very useful and helpful!

[sirbastiano]

Hi,
thanks for your patience and for the detailed suggestions — they are all valid points.

1. Relative orbit number filtering
Yes, it is possible to expose relative_orbit_number (and other metadata attributes) consistently in the search interface, independent of burst_mode. I will revise the documentation accordingly and provide a short tutorial so users can see how to use the extended filters.

2. Coverage of polygon by scene/bursts
I can add a column in the search results that reports the intersection/coverage between the user’s polygon and the sensor footprint. Full vs. partial vs. no-coverage checks are feasible, so this will be implemented.

3. Downloading multiple bursts vs. merging into a single SAFE
Automating multi-burst download is fine, and I can extend the API for that.
However, merging several bursts into a single manifest.safe is not implementable on this client side, because SAFE structure generation and product assembly are handled upstream by ESA’s MPC. The repository can automate the download of all relevant bursts, but not create a valid, merged SAFE product.

Let me know if there are other features you would find useful or if you have a specific workflow in mind — I can see what can be realistically added.

[dsherman-insar]

much appreciated I look forward to seeing these additions!

[sirbastiano]

Hi,

1. Documentation update
   The documentation has been updated to improve readability and to clarify how to filter by relative orbit number. Example:

# Search for relative orbit 87
results = searcher.search(
    collection_name="SENTINEL-1",
    attributes={"relativeOrbitNumber": 87}
)

2. Release information
   This functionality will be officially available starting from version v0.1.25.

[dsherman-insar]

thank you!