Checked for duplicates
Yes - I've already checked
Describe the bug
PR #348 added convexHull to bounding_polygon creation for the DISP metadata. This introduced changes in displaying (also potential spatial querying?) DISP footprints on ASF Vertex portal (Example, Frame F33039 over Hawaii) of some products produced before September 16, 2025.
The footprint of the bounding_polygon looks incorrect even before the PR, picking small polygon instead of capturing full data extent due to disconnected CSLC bursts (expected due to water between big and small islands).
What did you expect?
The quick solution for the ASF portal could be to use /identification/product_bounding_box instead of /identification/bounding_polygon to display product. This layer comes in UTM coordinates so would require transformation of corner coordinates to WGS to display in the portal. Also, corner coordinates do not reflect real squinted data extent, rather straight rectangular box.
The solution would be to issue the patch to update /identification/bounding_polygon` by adding this after L203 src/disp_s1/_utils.py.
footprint_geom = shapely.from_wkt(footprint_wkt).minimum_rotated_rectangle
return split_on_antimeridian(footprint_geom)
Result would be green polygon.
Reproducible steps
Environment
Please paste the output of the following:
`python -c "import dolphin; print(dolphin.show_versions())"`
...
Checked for duplicates
Yes - I've already checked
Describe the bug
PR #348 added convexHull to bounding_polygon creation for the DISP metadata. This introduced changes in displaying (also potential spatial querying?) DISP footprints on ASF Vertex portal (Example, Frame F33039 over Hawaii) of some products produced before September 16, 2025.
The footprint of the bounding_polygon looks incorrect even before the PR, picking small polygon instead of capturing full data extent due to disconnected CSLC bursts (expected due to water between big and small islands).
What did you expect?
The quick solution for the ASF portal could be to use
/identification/product_bounding_boxinstead of/identification/bounding_polygonto display product. This layer comes in UTM coordinates so would require transformation of corner coordinates to WGS to display in the portal. Also, corner coordinates do not reflect real squinted data extent, rather straight rectangular box.The solution would be to issue the patch to update /identification/bounding_polygon` by adding this after L203 src/disp_s1/_utils.py.
Result would be green polygon.
Reproducible steps
Environment
Please paste the output of the following: `python -c "import dolphin; print(dolphin.show_versions())"` ...