# ODC STAC load Only Returns Last Slice with PlanetScope items (Others are Zeros)

**URL:** https://discourse.pangeo.io/t/odc-stac-load-only-returns-last-slice-with-planetscope-items-others-are-zeros/5355
**Category:** Data
**Created:** [August 18, 2025, 7:35pm UTC](https://discourse.pangeo.io/t/odc-stac-load-only-returns-last-slice-with-planetscope-items-others-are-zeros/5355 "2025-08-18T19:35:41Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![kirill.kzb](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/kirill.kzb/32/1276_2.png) [@kirill.kzb](https://discourse.pangeo.io/u/kirill.kzb)
#### Post date: [August 21, 2025, 3:52pm UTC](https://discourse.pangeo.io/t/odc-stac-load-only-returns-last-slice-with-planetscope-items-others-are-zeros/5355/15 "2025-08-21T15:52:15Z")

</div>

Yes that exists already `eo:bands.common_name` , and it is used by `odc.stac` , but only as an alias, so you can request `red` instead of `B3` for example. But it’s not guaranteed to be unique, so we can’t merge on that, and instead rely on the asset name. Landsat catalog for example has that issue, where `red`, `green` and `blue` appear as both independent 12bit bands and as 8bit bands within a `visual` asset. Also it’s and extension, so not guaranteed to be present at all.

Also there are only so many allowed names specific to CF needs.

---

_[View the full topic](https://discourse.pangeo.io/t/odc-stac-load-only-returns-last-slice-with-planetscope-items-others-are-zeros/5355)._