HLS eo:common_name near infrared mismatch

未关闭
#506 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
领域
data

调研方向

首先，将 hls2-l30 和 hls2-s30 的 HLS STAC item 和 item-asset 元数据与 HLS v2 User Guide 以及 EO STAC common-band-name crosswalk 进行比较。当受影响的元数据中 B05 标记为 nir08、B08 标记为 nir 且 B8A 标记为 nir，并考虑了上游 NASA 源时，即视为完成。

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
46
派生
22
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/PlanetaryComputerDataCatalog 的其他 Issue

查看 microsoft/PlanetaryComputerDataCatalog 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。