search

asfadmin / Discovery-asf_search

BSD 3-Clause "New" or "Revised" License
131 stars 45 forks source link

[Bug]Searching the burst stack based on asf_search is much less compared to the ASF site. #244

Closed ZGHHGZ closed 10 months ago

ZGHHGZ commented 10 months ago

Taking 'S1_303069_IW3_20231004T101321_VV_AF9D-BURST' as an example, only 5 images can be searched using python, and 15 images can be searched on the asf website.

8ade62d29618330b075cd7c6a5f3c96

68581427d92b29e8521aa527eaced11

SpicyGarlicAlbacoreRoll commented 10 months ago

Thank you for filing a bug report!

This issue stems from how Vertex failing to handle null perpendicular values as expected. The BURST products missing from the asf-search based stack are actually missing state vectors in CMR. By default asf-search removes these products from the stack while the SearchAPI keeps them in and assigns a null value to their perpendicular baselines. Consequently, the ASF Data Search website (which depends on SearchAPI) interprets these null perpendicular baseline values as being 0, whereas they should be marked as non-existent instead.

asf-search will be changed to keep these products with missing state vectors in the stack while raising a warning in the near future with this pull request #248, and we're looking into ways for the website to show which products are missing state vectors in baseline and sbas searches.