Open falkamelung opened 1 year ago
Hi Unavco team,
When I run ssara_federated_query.py for TSX without --asfResponseTimeout option it works fine. It finds 5 scenes:
--asfResponseTimeout
ssara_federated_query.py --relativeOrbit=36 --intersectsWith='Polygon((-80.41 25.52, -80.41 26.00, -80.12 26.00, -80.12 25.52, -80.41 25.52))' --collectionName='TSX ARC_famelung_COA3837' --beamSwath=strip_014 --start=2017-09-01 --end=2017-10-31 --parallel=5 SSARA API query: 2.669125 seconds Found 5 scenes
However, when I run the same command with the --asfResponseTimeout=60 option it does not return anything:
--asfResponseTimeout=60
ssara_federated_query.py --relativeOrbit=36 --intersectsWith='Polygon((-80.41 25.52, -80.41 26.00, -80.12 26.00, -80.12 25.52, -80.41 25.52))' --collectionName='TSX ARC_famelung_COA3837' --beamSwath=strip_014 --start=2017-09-01 --end=2017-10-31 --parallel=5 --asfResponseTimeout=60 SSARA API query: 2.538935 seconds Found 0 scenes
This looks like a bug to me. In contrast, when I search for Sentinel-1 data it returns the same number of data, independent of this option:
ssara_federated_query.py --relativeOrbit=48 --intersectsWith='Polygon((-80.45 25.60, -80.45 26.20, -80.11 26.20, -80.11 25.60, -80.45 25.60))' --platform=SENTINEL-1A,SENTINEL-1B --parallel=5 --start=2023-06-01 SSARA API query: 7.788151 seconds Found 4 scenes ssara_federated_query.py --relativeOrbit=48 --intersectsWith='Polygon((-80.45 25.60, -80.45 26.20, -80.11 26.20, -80.11 25.60, -80.45 25.60))' --platform=SENTINEL-1A,SENTINEL-1B --parallel=5 --start=2023-06-01 --asfResponseTimeout=50 SSARA API query: 5.437817 seconds Found 4 scenes
I am routinely using the --asfResponseTimeout only recently, which might be why this arose only now.
Hi Unavco team,
When I run ssara_federated_query.py for TSX without
--asfResponseTimeout
option it works fine. It finds 5 scenes:However, when I run the same command with the
--asfResponseTimeout=60
option it does not return anything:This looks like a bug to me. In contrast, when I search for Sentinel-1 data it returns the same number of data, independent of this option:
I am routinely using the
--asfResponseTimeout
only recently, which might be why this arose only now.