Pleiades cloud coverage filtering and apparently missing products

Hi,
can you perhaps provide the AOI so that we can look into it?

In general however Airbus processes the data from the same acquisition to different what they called “processing levels” and we only ingest the products at processingLevel: SENSOR. This is because:

processingLevel This value could be equal to SENSOR (images which meet Living Library criteria) and ALBUM (images that do not meet Living Library criteria in terms of Incidence angle and Cloud cover. They can not be streamed on the fly but you will soon be able to order them for delivery in your private workspace)

So we only focus to SENSOR for the moment.
In addition to the above, I imagine that Airbus also exposes some data on GeoStore, that are not even available in Living library.

Ah, that could explain it, and that at least in this area, there is a ca. 20% cloud cover cut off for “Living Library” criteria…

AOI:
{‘type’: ‘Polygon’,
‘coordinates’: (((11.444931176639274, 47.27841015984613),
(11.455415837530495, 47.27841015984613),
(11.455415837530495, 47.28253076444111),
(11.444931176639274, 47.28253076444111),
(11.444931176639274, 47.27841015984613)),)}

Cheers
 

can you check the above area/time period in Airbus Living Library directly?

Hi,
I will check the Airbus Living Library as soon as possible. For now, the OneAtlas search service is unavailable.

I checked the Airbus Living Library for Pléiades products from 2019 and there is indeed only one dataset from 14 September 2019, which is the same one our API returns. The first and last results on the list are SPOT imagery.

That explains the difference in data availability between GeoStore and our API at the current stage.

Cheers