-
Notifications
You must be signed in to change notification settings - Fork 39
Description
Hi there datacube-ows team,
I've been making use of the data_available_for_dates property that comes back back via a GetFeatureInfo request.
One of the things I've been noticing is that I'm getting way more dates, than what there is available for the specific bbox I've provided. Specifically I'm using the ga_s2m_ard_3 layer provided by https://ows.dea.ga.gov.au.
What that means in practical terms is that I'm showing a bunch of dates on my UI, to my users, they are selecting one, and blank tiles are coming back. FWIW I'm operating on a farm-scale.
I think there are 2 causes for the blank tiles
- cloud cover
- The actual area covered by the image doesn't cover the area requested in the
bbox
If I was going to guestimate things I'd say
- 25% of the times I'm impacted by significant cloud cover
- 25% of the times I'm impacted by coverage mismatch
- 50% of the times I get the expected image
I'm wondering if there is a place for somehow refining requests for data_available_for_dates, perhaps by passing some extra parameters, a bit like cql_filter or filter within the Geoserver WMS?
cql_filter: item_cloud_cover < 20 AND INTERSECTS(item_geom, POINT(45, -135))
I appreciate this is probably non-trivial, and is possibly also constrained by ODC itself, but I thought I'd create an issue
Regards,
Rowan