Google Earth Engine ——数据全解析专辑(COPERNICUS/S5P/OFFL/L3_AER_AI和LH)气溶胶指数数据集

本文涉及的产品
公共DNS(含HTTPDNS解析),每月1000万次HTTP解析
全局流量管理 GTM,标准版 1个月
云解析 DNS,旗舰版 1个月
简介: Google Earth Engine ——数据全解析专辑(COPERNICUS/S5P/OFFL/L3_AER_AI和LH)气溶胶指数数据集

OFFL/L3_AER_AI

This dataset provides offline high-resolution imagery of the UV Aerosol Index (UVAI), also called the Absorbing Aerosol Index (AAI).


The AAI is based on wavelength-dependent changes in Rayleigh scattering in the UV spectral range for a pair of wavelengths. The difference between observed and modelled reflectance results in the AAI. When the AAI is positive, it indicates the presence of UV-absorbing aerosols like dust and smoke. It is useful for tracking the evolution of episodic aerosol plumes from dust outbreaks, volcanic ash, and biomass burning.


The wavelengths used have very low ozone absorption, so unlike aerosol optical thickness measurements, AAI can be calculated in the presence of clouds. Daily global coverage is therefore possible.


For this L3 AER_AI product, the absorbing_aerosol_index is calculated with a pair of measurements at the 354 nm and 388 nm wavelengths. The COPERNICUS/S5P/OFFL/L3_SO2 product has the absorbing_aerosol_index calculated using the 340 nm and 380 nm wavelengths.

OFFL/L3_AER_AI


该数据集提供了紫外线气溶胶指数 (UVAI) 的离线高分辨率图像,也称为吸收气溶胶指数 (AAI)。


AAI 基于一对波长的 UV 光谱范围内瑞利散射的波长相关变化。观察到的和模拟的反射率之间的差异导致了 AAI。当 AAI 为正值时,表明存在吸收紫外线的气溶胶,如灰尘和烟雾。它可用于跟踪粉尘爆发、火山灰和生物质燃烧引起的偶发气溶胶羽流的演变。


所使用的波长对臭氧的吸收非常低,因此与气溶胶光学厚度测量不同,AAI 可以在有云的情况下计算。因此,每日全球报道是可能的。


对于此 L3 AER_AI 产品,吸收气溶胶指数是通过在 354 nm 和 388 nm 波长处进行的一对测量计算得出的。 COPERNICUS/S5P/OFFL/L3_SO2 产品具有使用 340 nm 和 380 nm 波长计算的吸收气溶胶指数。


OFFL L3 Product

To make our OFFL L3 products, we find areas within the product's bounding box with data using a command like this:

harpconvert --format hdf5 --hdf5-compression 9
-a 'absorbing_aerosol_index_validity>50;derive(datetime_stop {time})'
S5P_OFFL_L2__AER_AI_20181030T213916_20181030T232046_05427_01_010200_20181105T210529.nc
grid_info.h5


We then merge all the data into one large mosaic (area-averaging values for pixels that may have different values for different times). From the mosaic, we create a set of tiles containing orthorectified raster data.

Example harpconvert invocation for one tile:

harpconvert --format hdf5 --hdf5-compression 9
-a 'absorbing_aerosol_index_validity>50;derive(datetime_stop {time});
bin_spatial(2001, 50.000000, 0.01, 2001, -120.000000, 0.01);
keep(absorbing_aerosol_index,sensor_altitude,sensor_azimuth_angle,
     sensor_zenith_angle,solar_azimuth_angle,solar_zenith_angle)'
S5P_OFFL_L2__AER_AI_20181030T213916_20181030T232046_05427_01_010200_20181105T210529.nc
output.h5


Dataset Availability

2018-07-04T13:34:21 - 2021-09-04T00:00:00

Dataset Provider

European Union/ESA/Copernicus

Collection Snippet

ee.ImageCollection("COPERNICUS/S5P/OFFL/L3_AER_AI")

Resolution

0.01 degrees

Bands Table

Name Description Min* Max* Units
absorbing_aerosol_index A measure of the prevalence of aerosols in the atmosphere, calculated by [this equation](https://earth.esa.int/web/sentinel/technical-guides/sentinel-5p/level-2/aerosol-index) using the 354/388 wavelength pair. -21 39
sensor_altitude Altitude of the satellite with respect to the geodetic sub-satellite point (WGS84). 828543 856078 m
sensor_azimuth_angle Azimuth angle of the satellite at the ground pixel location (WGS84); angle measured East-of-North. -180 180 degrees
sensor_zenith_angle Zenith angle of the satellite at the ground pixel location (WGS84); angle measured away from the vertical. 0.098 66.87 degrees
solar_azimuth_angle Azimuth angle of the Sun at the ground pixel location (WGS84); angle measured East-of-North. -180 180 degrees
solar_zenith_angle Zenith angle of the satellite at the ground pixel location (WGS84); angle measured away from the vertical. 8 88 degrees


* = Values are estimated

影像属性:

Name Type Description
ALGORITHM_VERSION String The algorithm version used in L2 processing. It's separate from the processor (framework) version, to accommodate different release schedules for different products.
BUILD_DATE String The date, expressed as milliseconds since 1 Jan 1970, when the software used to perform L2 processing was built.
HARP_VERSION Int The version of the HARP tool used to grid the L2 data into an L3 product.
INSTITUTION String The institution where data processing from L1 to L2 was performed.
L3_PROCESSING_TIME Int The date, expressed as milliseconds since 1 Jan 1970, when Google processed the L2 data into L3 using harpconvert.
LAT_MAX Double The maximum latitude of the asset (degrees).
LAT_MIN Double The minimum latitude of the asset (degrees).
LON_MAX Double The maximum longitude of the asset (degrees).
LON_MIN Double The minimum longitude of the asset (degrees).
ORBIT Int The orbit number of the satellite when the data was acquired.
PLATFORM String Name of the platform which acquired the data.
PROCESSING_STATUS String The processing status of the product on a global level, mainly based on the availability of auxiliary input data. Possible values are "Nominal" and "Degraded".
PROCESSOR_VERSION String The version of the software used for L2 processing, as a string of the form "major.minor.patch".
PRODUCT_ID String Id of the L2 product used to generate this asset.
PRODUCT_QUALITY String Indicator that specifies whether the product quality is degraded or not. Allowed values are "Degraded" and "Nominal".
SENSOR String Name of the sensor which acquired the data.
SPATIAL_RESOLUTION String Spatial resolution at nadir. For most products this is `3.5x7km2`, except for `L2__O3__PR`, which uses `28x21km2`, and `L2__CO____` and `L2__CH4___`, which both use `7x7km2`. This attribute originates from the CCI standard.
TIME_REFERENCE_DAYS_SINCE_1950 Int Days from 1 Jan 1950 to when the data was acquired.
TIME_REFERENCE_JULIAN_DAY Double The Julian day number when the data was acquired.
TRACKING_ID String UUID for the L2 product file.


代码:

var collection = ee.ImageCollection('COPERNICUS/S5P/OFFL/L3_AER_AI')
  .select('absorbing_aerosol_index')
  .filterDate('2019-06-01', '2019-06-06');
var band_viz = {
  min: -1,
  max: 2.0,
  palette: ['black', 'blue', 'purple', 'cyan', 'green', 'yellow', 'red']
};
Map.addLayer(collection.mean(), band_viz, 'S5P Aerosol');
Map.setCenter(-118.82, 36.1, 5);


相关文章
|
2天前
|
机器学习/深度学习 人工智能 编解码
深入探索AI文生语音技术的奥秘:从文本输入到逼真语音输出的全链条语音合成过程解析
【9月更文挑战第2天】深入探索AI文生语音技术的奥秘:从文本输入到逼真语音输出的全链条语音合成过程解析
 深入探索AI文生语音技术的奥秘:从文本输入到逼真语音输出的全链条语音合成过程解析
|
27天前
|
人工智能 PyTorch 算法框架/工具
Xinference实战指南:全面解析LLM大模型部署流程,携手Dify打造高效AI应用实践案例,加速AI项目落地进程
【8月更文挑战第6天】Xinference实战指南:全面解析LLM大模型部署流程,携手Dify打造高效AI应用实践案例,加速AI项目落地进程
Xinference实战指南:全面解析LLM大模型部署流程,携手Dify打造高效AI应用实践案例,加速AI项目落地进程
|
22天前
|
机器学习/深度学习 人工智能 自然语言处理
HuggingGPT解析:使用 ChatGPT及HuggingFace上的族系解决AI问题
HuggingGPT是一个框架,它使用大型语言模型(如ChatGPT)作为控制器来管理和协调Hugging Face上的AI模型,以语言作为通用接口解决多模态和领域的复杂AI任务。
25 0
HuggingGPT解析:使用 ChatGPT及HuggingFace上的族系解决AI问题
|
25天前
|
机器学习/深度学习 人工智能 算法
【人工智能】人工智能与传统美工结合,AI美工的详细解析
AI美工是一个结合了人工智能技术与美工设计的岗位,它利用AI工具和技术来辅助或完成美工设计的各项工作。以下是对AI美工的详细解析
39 2
|
28天前
|
人工智能 算法
AI 0基础学习,数学名词解析
AI 0基础学习,数学名词解析
12 2
|
11天前
|
Java 数据库连接 数据库
AI 时代风起云涌,Hibernate 实体映射引领数据库高效之路,最佳实践与陷阱全解析!
【8月更文挑战第31天】Hibernate 是一款强大的 Java 持久化框架,可将 Java 对象映射到关系数据库表中。本文通过代码示例详细介绍了 Hibernate 实体映射的最佳实践,包括合理使用关联映射(如 `@OneToMany` 和 `@ManyToOne`)以及正确处理继承关系(如单表继承)。此外,还探讨了常见陷阱,例如循环依赖可能导致的无限递归问题,并提供了使用 `@JsonIgnore` 等注解来避免此类问题的方法。通过遵循这些最佳实践,可以显著提升开发效率和数据库操作性能。
29 0
|
1月前
|
机器学习/深度学习 人工智能 TensorFlow
|
1月前
|
机器学习/深度学习 人工智能 自然语言处理
🔬技术宅必看!AI Prompt深度解析,商业数据分析的科学魔法
【8月更文挑战第1天】在快速发展的科技领域中, AI Prompt 正革新商业数据分析方式。它通过自然语言指令, 驱动 AI 模型实现数据洞察。本文探讨 AI Prompt 的定义、原理及其在商业分析中的应用。**最佳实践包括**: 精准设计 Prompt 以确保清晰具体的指令; 结合领域知识优化 Prompt, 提升分析准确性; 采用迭代法, 根据反馈持续改进模型性能。掌握 AI Prompt 技术, 不仅提高效率, 更能洞察商机, 创造价值。
62 0
|
2月前
|
人工智能 自然语言处理 搜索推荐
阿里云搜索开发工作台:快速搭建AI语义搜索与RAG链路的深度解析
阿里云搜索开发工作台凭借其丰富的组件化服务和强大的模型能力,为企业快速搭建AI语义搜索及RAG链路提供了有力支持。通过该平台,企业可以灵活调用各种服务,实现高效的数据处理、查询分析、索引构建和文本生成等操作,从而大幅提升信息获取与处理能力。随着AI技术的不断发展,阿里云搜索开发工作台将继续优化和完善其服务,为企业数字化转型和智能化升级注入更强动力。
73 0
|
2月前
|
人工智能 搜索推荐 计算机视觉
[AI Perplexica] 深入解析,AI 架构揭秘
了解 Perplexica 的核心架构,探索其用户界面、代理链、大型语言模型、嵌入模型等关键组件的运作方式,揭秘 AI 如何高效处理复杂查询任务。

热门文章

最新文章

推荐镜像

更多