Google Earth Engine(GEE)——sentinel2数据介绍

简介: Google Earth Engine(GEE)——sentinel2数据介绍

之前有粉丝在公众号问我,对于sentinel2是否需要进行去云的问题,这里就简单写一下关于这个数据的问题:

现在回答是因为所有光学影像都是需要去云的,因为遇到没有云的影像概率太小了,况且数据预处理阶段的去云是必不可少的一个关键环节,一般在GEE平台需要的处理就是去云处理,而很多modis数据和Landsat8数据,以及sentinel数据都是通过QA波段的位掩技术实现的。所以一般无论做反演还是监测都需要进行这一步修正。

现在先给大家推荐一个官方的文档介绍的链接:


哨兵-2是一项宽幅、高分辨率、多光谱成像任务,支持哥白尼土地监测研究,包括监测植被、土壤和水覆盖,以及观测内陆水道和沿海地区。

哨兵-2的数据包含13个UINT16光谱带,代表TOA反射率,以10000米为尺度。详见Sentinel-2用户手册。此外,还有三个QA波段,其中一个(QA60)是一个带有云层遮蔽信息的比特掩码波段。

每个Sentinel-2产品(压缩档案)可能包含多个产品。每个产品成为一个单独的地球引擎资产。Sentinel-2资产的EE资产ID有以下格式。COPERNICUS/S2/20151128T002653_20151128T102149_T56MNN. 这里第一个数字部分代表传感日期和时间,第二个数字部分代表产品生成日期和时间,最后一个6个字符的字符串是唯一的颗粒标识符,表示其UTM网格参考(见MGRS)。

GEE上的波段介绍:

Dataset Availability

2015-06-23T00:00:00 - 2021-11-23T00:00:00

Dataset Provider

European Union/ESA/Copernicus

Collection Snippet

ee.ImageCollection("COPERNICUS/S2")

Bands Table

Name Description Resolution Wavelength Scale
B1 Aerosols 60 meters 443.9nm (S2A) / 442.3nm (S2B) 0.0001
B2 Blue 10 meters 496.6nm (S2A) / 492.1nm (S2B) 0.0001
B3 Green 10 meters 560nm (S2A) / 559nm (S2B) 0.0001
B4 Red 10 meters 664.5nm (S2A) / 665nm (S2B) 0.0001
B5 Red Edge 1 20 meters 703.9nm (S2A) / 703.8nm (S2B) 0.0001
B6 Red Edge 2 20 meters 740.2nm (S2A) / 739.1nm (S2B) 0.0001
B7 Red Edge 3 20 meters 782.5nm (S2A) / 779.7nm (S2B) 0.0001
B8 NIR 10 meters 835.1nm (S2A) / 833nm (S2B) 0.0001
B8A Red Edge 4 20 meters 864.8nm (S2A) / 864nm (S2B) 0.0001
B9 Water vapor 60 meters 945nm (S2A) / 943.2nm (S2B) 0.0001
B10 Cirrus 60 meters 1373.5nm (S2A) / 1376.9nm (S2B) 0.0001
B11 SWIR 1 20 meters 1613.7nm (S2A) / 1610.4nm (S2B) 0.0001
B12 SWIR 2 20 meters 2202.4nm (S2A) / 2185.7nm (S2B) 0.0001
QA10 Always empty 10 meters 0
QA20 Always empty 20 meters 0
QA60 Cloud mask 60 meters 0
QA60 Bitmask
  • Bit 10: Opaque clouds
    • 0: No opaque clouds
    • 1: Opaque clouds present
  • Bit 11: Cirrus clouds
    • 0: No cirrus clouds
    • 1: Cirrus clouds present

以下是官网给出的去云的内容介绍:


Cloud Masks

The Level-1C products embed:

  • Vector mask (GML format)
  • cloud mask including an indicator specifying cloud type:
  • dense cloud
  • cirrus cloud
  • statistical information: percentage of cloudy pixels and of cirrus pixels in the cloud mask.


Cloud Mask (Dense/Cirrus)

The cloud mask enables cloudy and cloud-free pixels to be identified. The mask includes both dense clouds and cirrus clouds with an indicator specifying the cloud type.

Processing is performed with data sampled at 60 m spatial resolution for all spectral bands.

Identification of Dense Clouds

The dense clouds, also called opaque clouds, are characterised by a high reflectance in the blue spectral region (B2).

The method used to identify dense cloud pixels is based on B2 reflectance threshold. To avoid false detection, mainly due to snow/cloud confusion, SWIR reflectance in B11 and B12 are also used. Snow and clouds both have a high reflectance in the blue. Cloud reflectance is high in the SWIR, whereas snow presents a low reflectance.

Additional criteria based on B10 reflectance are added to avoid high altitude ice cloud and snow confusion (both having a low reflectance in the SWIR bands B11 and B12). At B10, there is a high atmospheric absorption band and only high altitude clouds are detected. However, this last criterion is only applied after a first detection of cloud pixel in the blue band where cirrus is transparent.

Cirrus Cloud

Cirrus clouds are thin, transparent or semi-transparent clouds, forming at high altitudes, approximately 6-7 km above the Earth's surface.

The method of identifying cirrus cloud pixels from dense cloud pixel is based on two spectral criteria:

  • B10 corresponds to a high atmospheric absorption band: only high altitude clouds can be detected
  • cirrus cloud, being semi-transparent, cannot be detected in the B2 blue band.

A pixel with low reflectance in the B2 band and high reflectance in the B10 band has a good probability of being cirrus cloud but this is not a certainty. Some opaque clouds have a low reflectance in the blue and can be identified as cirrus cloud.

To limit false detections (due to high reflectance in the blue or due to the fact that clouds are not spectrally registered), a filter using morphology-based operations is applied on both dense and cirrus masks performing:

  • erosion, to remove isolated pixels
  • dilatation, to fill the gap and extend clouds.

If after morphology operations, a pixel is both dense and cirrus, the dense cloud mask prevails.

The cloud mask can be set to three values:

  • 0 is a cloud-free pixel
  • 1 is a dense cloud pixel
  • 2 is a cirrus cloud pixel.

If measurements are not available in one or several bands needed to calculate the cloud mask, the mask value is set to NODATA.

After all filtering steps, the cloud mask is available at a spatial resolution of 60 m. It is then re-sampled at spatial resolutions of 10 m and 20 m for each corresponding spectral band. The re-sampling is not a geometric transformation but a radiometric interpolation.

All these processing steps ensure that a pixel identified as cloud-free is actually cloud-free.


相关文章
|
4月前
|
数据可视化 定位技术 Sentinel
如何用Google Earth Engine快速、大量下载遥感影像数据?
【2月更文挑战第9天】本文介绍在谷歌地球引擎(Google Earth Engine,GEE)中,批量下载指定时间范围、空间范围的遥感影像数据(包括Landsat、Sentinel等)的方法~
1983 1
如何用Google Earth Engine快速、大量下载遥感影像数据?
|
4月前
|
编解码 算法 定位技术
GEE时序——利用sentinel-2(哨兵-2)数据进行地表物候学分析(时间序列平滑法估算和非平滑算法代码)
GEE时序——利用sentinel-2(哨兵-2)数据进行地表物候学分析(时间序列平滑法估算和非平滑算法代码)
326 3
|
4月前
|
机器学习/深度学习 算法 数据可视化
基于Google Earth Engine云平台构建的多源遥感数据森林地上生物量AGB估算模型含生物量模型应用APP
基于Google Earth Engine云平台构建的多源遥感数据森林地上生物量AGB估算模型含生物量模型应用APP
196 0
|
4月前
|
Java 测试技术 Nacos
|
4月前
|
存储 编解码 数据可视化
Google Earth Engine获取随机抽样点并均匀分布在栅格的不同数值区中
【2月更文挑战第14天】本文介绍在谷歌地球引擎(Google Earth Engine,GEE)中,按照给定的地表分类数据,对每一种不同的地物类型,分别加以全球范围内随机抽样点自动批量选取的方法~
427 1
Google Earth Engine获取随机抽样点并均匀分布在栅格的不同数值区中
|
4月前
|
算法 数据挖掘 定位技术
GEE 案例——如何计算sentinel-2中每一个单景影像的波段的DN值并绘制直方图
GEE 案例——如何计算sentinel-2中每一个单景影像的波段的DN值并绘制直方图
95 5
|
4月前
|
存储 编解码 人工智能
GEE数据集——哨兵2号Sentinel-2 云概率数据集
GEE数据集——哨兵2号Sentinel-2 云概率数据集
324 2
|
21天前
|
Java UED Sentinel
微服务守护神:Spring Cloud Sentinel,让你的系统在流量洪峰中稳如磐石!
【8月更文挑战第29天】Spring Cloud Sentinel结合了阿里巴巴Sentinel的流控、降级、熔断和热点规则等特性,为微服务架构下的应用提供了一套完整的流量控制解决方案。它能够有效应对突发流量,保护服务稳定性,避免雪崩效应,确保系统在高并发下健康运行。通过简单的配置和注解即可实现高效流量控制,适用于高并发场景、依赖服务不稳定及资源保护等多种情况,显著提升系统健壮性和用户体验。
47 1
|
3月前
|
监控 Java Sentinel
使用Sentinel进行服务调用的熔断和限流管理(SpringCloud2023实战)
Sentinel是面向分布式、多语言异构化服务架构的流量治理组件,主要以流量为切入点,从流量路由、流量控制、流量整形、熔断降级、系统自适应过载保护、热点流量防护等多个维度来帮助开发者保障微服务的稳定性。
105 3
|
6天前
|
监控 Java Nacos
SpringCloud基础5——微服务保护、Sentinel
sentinel、雪崩问题、流量控制、隔离和降级、授权规则、规则持久化
SpringCloud基础5——微服务保护、Sentinel