microsoft / microsoft/PlanetaryComputerDataCatalog
HLS eo:common_name near infrared mismatch
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the HLS STAC item and item-asset metadata for hls2-l30 and hls2-s30 with the HLS v2 User Guide and the EO STAC common-band-name crosswalk. Done means B05 is labeled nir08, B08 is labeled nir, and B8A is labeled nir in the affected metadata, with the upstream NASA source considered.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100