When loading in Sentinel-1 data, users can use the STAC property filters to select their desired sat:orbit_state, which is either DESCENDING or ASCENDING. However, for a given spatio-temporal extent it's currently still the user's responsibility to determine what the optimal/pre-dominant orbit state is for their extent.
Many projects currently do an offline CDSE STAC query to determine the best orbit state. See for example: https://github.com/Open-EO/openeo-gfmap/blob/maintenance/0.4.x/src/openeo_gfmap/utils/catalogue.py#L332
Given that openEO anyway queries the STAC API as well, it would be a nice quality of life improvement for users, if openEO could determine the optimal sat:orbit_state on the fly.
Users would then still be able to select their desired orbit state themselves using STAC property filters. With an additional AUTO option that would let openEO select the orbit state for them.
It's a request we have received from multiple users already. GEE apparently has a similar feature.
When loading in Sentinel-1 data, users can use the STAC property filters to select their desired
sat:orbit_state, which is eitherDESCENDINGorASCENDING. However, for a given spatio-temporal extent it's currently still the user's responsibility to determine what the optimal/pre-dominant orbit state is for their extent.Many projects currently do an offline CDSE STAC query to determine the best orbit state. See for example: https://github.com/Open-EO/openeo-gfmap/blob/maintenance/0.4.x/src/openeo_gfmap/utils/catalogue.py#L332
Given that openEO anyway queries the STAC API as well, it would be a nice quality of life improvement for users, if openEO could determine the optimal
sat:orbit_stateon the fly.Users would then still be able to select their desired orbit state themselves using STAC property filters. With an additional
AUTOoption that would let openEO select the orbit state for them.It's a request we have received from multiple users already. GEE apparently has a similar feature.