microsoft
HLS eo:common_name near infrared mismatch
I have been working with the new HLS collections recently and I came across a quirk in the STAC metadata for the HLS items. The eo:common_name field in the asset/item-asset metadata is meant to make it possible to easily understand the correct interpretation of each asset's bands.
The issue I found is concerns the near-infrared bands for both the Landsat and Sentinel collections. Here is how the bands are currently labeled:
| collection id | asset key | eo:common_name |
|---|---|---|
| hls2-l30 | B05 | nir |
| hls2-s30 | B08 | nir |
| hls2-s30 | B8A | - |
The correct interpretation would be like this:
| collection id | asset key | eo:common_name |
|---|---|---|
| hls2-l30 | B05 | nir08 |
| hls2-s30 | B08 | nir |
| hls2-s30 | B8A | nir08 |
Here is a link to the HLS v2 User Guide where there is a table that shows the proper crosswalk of bands between collections: https://lpdaac.usgs.gov/documents/1698/HLS_User_Guide_V2.pdf
After doing a little more digging I have discovered that this is not strictly an issue with the Planetary Computer collection - the issue is present in STAC items produced by NASA.
The EO STAC extension page has a nice crosswalk table for common name x band for many sensors including Landsat 8/9 and Sentinel 2.
