【记录】CALIPSO Lidar Level 1B产品介绍

2023-11-11 15:20

本文主要是介绍【记录】CALIPSO Lidar Level 1B产品介绍,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

目录

CALIPSO Quality Statements Lidar Level 1B Profile Products Version Releases: 3.01, 3.02, 3.30

Attenuated Backscatter Profiles

Total Attenuated Backscatter 532

Perpendicular Attenuated Backscatter 532

Attenuated Backscatter 1064

Calibration Coefficients and Uncertainties

Column Reflectance

Geolocation and Altitude Registration

Latitude

Longitude

Lidar Data Altitude

Number Bins Shift

Surface Altitude Shift

Orbit Number

Path Number

Meteorological Data

Time Parameters

Profile Identification

Ancillary Data

Day Night Flag

IGBP Surface Type

Land Water Mask

NSIDC Surface Type

Surface Elevation

CALIPSO Quality Statements Lidar Level 1B Profile Products Version Releases: 2.01, 2.02


CALIPSO Quality Statements Lidar Level 1B Profile Products Version Releases: 3.01, 3.02, 3.30

CALIOP_L1ProfileProducts_3-01-v02.pdf

Attenuated Backscatter Profiles

Total Attenuated Backscatter 532

The total attenuated backscatter at 532 nm,β’532n Section 6.2.2 of the Lidar Level I ATBD (PDF),是主要的激光雷达一级数据产品之一。β’532是是532nm体积后向散射系数和532nm处的双向光学透射的乘积。Lidar Level I ATBD (PDF)第6节详细描述了来自两个组成偏振分量的532nm总衰减后向散射的构造。衰减的反向散射剖面是从校准的(除以校准常数)、距离校正的、激光能量归一化的、基线减去激光雷达返回信号中得到的。

532nm衰减后向散射系数被记录在每个激光脉冲的对应的583个元素的阵列中,对应于由激光雷达数据高度字段定义的恒定高度网格(元数据中Lidar Data Altitudes字段中记录)。(https://blog.csdn.net/wokaowokaowokao12345/article/details/79790675)

为了减少下行链路数据量,对不同的高度范围使用不同的水平和垂直分辨率,如下表所示。

The total attenuated backscatter at 532 nm, β'532 in Section 6.2.2 of the Lidar Level I ATBD (PDF), is one of the primary lidar Level 1 data products. β'532 is the product of the 532 nm volume backscatter coefficient and the two-way optical transmission at 532 nm from the lidar to the sample volume. The construction of the 532 nm total attenuated backscatter from the two constituent polarization components is described in detail in Section 6 of the Lidar Level I ATBD (PDF). The attenuated backscatter profiles are derived from the calibrated (divided by calibration constant), range-corrected, laser energy normalized, baseline subtracted lidar return signal.

The 532 nm attenuated backscatter coefficients are reported for each laser pulse as an array of 583 elements that have been registered to a constant altitude grid defined by the Lidar Data Altitude field.

Note that to reduce the downlink data volume, an on-board averaging scheme is applied using different horizontal and vertical resolutions for different altitude regimes, as shown in the following table.

Uncertainties for the attenuated backscatter are not explicitly reported in the CALIOP Level 1 data products to save data volume, which would otherwise approximately double the Level 1 data volume. If needed, users can compute random errors for the attenuated backscatter products as described in Uncertainties for Attenuated Backscatter (PDF). IDL code for computing the attenuated backscatter uncertainties is contained in IDL Code for Uncertainty Calculations (PDF).

Perpendicular Attenuated Backscatter 532

532nm总衰减后向散射的垂直分量。垂直通道532nm衰减后向散射的轮廓以与532nm总后向散射的轮廓相同的方式记录。反向散射的平行分量的轮廓可以通过从总量中简单地减去垂直分量来获得。

This field reports the perpendicular component of the 532 nm total attenuated backscatter, as described in section 6 of the CALIPSO Lidar Level I ATBD (PDF). Profiles of the perpendicular channel 532 nm attenuated backscatter are reported in the same manner as are profiles of the 532 nm total backscatter. Profiles of the parallel component of the backscatter can be obtained by simple subtraction of the perpendicular component from the total.

Attenuated Backscatter 1064

The attenuated backscatter at 1064 nm, β'1064, is computed according to equation 7.23 in section 7.2 of the Lidar Level I ATBD (PDF). Like β'532, β'1064 is one of the primary lidar Level 1 data products. β'1064 is the product of the 1064 nm volume backscatter coefficient and the two-way optical transmission at 1064 nm from the lidar to the sample volume. Profiles of the 1064 nm attenuated backscatter are reported in the same manner as are profiles of the 532 nm total backscatter. However, the first 34 bins of each profile contain fill values (-9999), because no 1064 nm data is downlinked from the 30.1 - 40 km altitude range.

Calibration Coefficients and Uncertainties

Column Reflectance

Geolocation and Altitude Registration

Latitude

Geodetic latitude, in degrees, of the laser footprint on the Earth's surface.

Longitude

Longitude, in degrees, of the laser footprint on the Earth's surface.

Lidar Data Altitude

这是一个HDF元数据字段,定义激光雷达1级剖面产品注册到的583个距离仓的高度(请参考表1:下行链路数据的不同高度范围的距离分辨率)。

This is an HDF metadata field that defines the altitudes of the 583 range bins (refer to Table 1: Range Resolutions of Different Altitude Ranges for Downlinked Data) to which lidar Level 1 profile products are registered.

Number Bins Shift

Number bins shift contains the number of 30 meter bins the profile specific 30 meter array elements are shifted to match the lowest altitude bin of the fixed 30 meter altitude array. Profile specific altitude arrays are computed as a function of the actual spacecraft offnadir angle, which varies slightly from the commanded spacecraft off-nadir angle. The fixed altitude array is computed using the commanded spacecraft off-nadir angle (0.3 or 3.0 degrees). The profile specific array elements may be shifted up or down.

Surface Altitude Shift

Surface altitude shift contains the altitude difference between the profile specific 30 meter altitude array and the fixed 30 meter altitude array at the array element that includes mean sea level. Profile specific altitude arrays are computed as a function of the actual spacecraft off-nadir angle, which varies slightly from the commanded spacecraft off-nadir angle. The fixed altitude array is computed using the commanded spacecraft off-nadir angle (0.3 or 3.0 degrees). The units are in kilometers and the values may be positive or negative. The difference is calculated as: Surface_Altitude_Shift = altitude (profile specific 30 meter mean sea level bin) - altitude (fixed 30 meter mean sea level bin).

Orbit Number

Orbit Number consists of three HDF metadata fields that define the number of revolutions by the CALIPSO spacecraft around the Earth and is incremented as the spacecraft passes the equator at the ascending node. To maintain consistency between the CALIPSO and CloudSat orbit parameters, the Orbit Number is keyed to the Cloudsat orbit 2121 at 23:00:47 on 2006/09/20. Because the CALIPSO data granules are organized according to day and night conditions, day/night boundaries do not coincide with transition points for defining orbit number. As such, three parameters are needed to describe the orbit number for each granule as:

  • Orbit Number at Granule Start: orbit number at the granule start time
  • Orbit Number at Granule End: orbit number at the granule stop time
  • Orbit Number Change Time: time at which the orbit number changes in the granule

Path Number

Orbit Number Path Number consists of three HDF metadata fields that define an index ranging from 1-233 that references orbits to the Worldwide Reference System (WRS). This global grid system was developed to support scene identification for LandSat imagery. Since the A-Train is maintained to the WRS grid within +/- 10 km, the Path Number provides a convenient index to support data searches, instead of having to define complex latitude and longitude regions along the orbit track. The Path Number is incremented after the maximum latitude in the orbit is realized and changes by a value of 16 between successive orbits. Because the CALIPSO data granules are organized according to day and night conditions, day/night boundaries do not coincide with transition points for defining path number. As such, three parameters are needed to describe the path number for each granule as:

  • Path Number at Granule Start: path number at the granule start time
  • Path Number at Granule End: path number at the granule stop time
  • Path Number Change Time: time at which the path number changes in the granule

Meteorological Data

Time Parameters

Profile Identification

Ancillary Data

Day Night Flag

This field indicates the lighting conditions at an altitude of ~24 km above mean sea level;

0 = day,

1 = night.

IGBP Surface Type

International Geosphere/Biosphere Programme (IGBP) classification of the surface type at the laser footprint. The IGBP surface types reported by CALIPSO are the same as those used in the CERES/SARB surface map.

Land Water Mask

This is an 8-bit integer indicating the surface type at the laser footprint, with

  • 0 = shallow ocean;
  • 1 = land;
  • 2 = coastlines;
  • 3 = shallow inland water;
  • 4 = intermittent water;
  • 5 = deep inland water;
  • 6 = continental ocean;
  • 7 = deep ocean.

NSIDC Surface Type

Snow and ice coverage for the surface at the laser footprint; data obtained from the National Snow and Ice Data Center (NSIDC).

Surface Elevation

这是从GTOPO30数字高程图(DEM)获得的激光足迹的表面高程,以高于当地平均海平面的公里为单位。

This is the surface elevation at the laser footprint, in kilometers above local mean sea level, obtained from the GTOPO30 digital elevation map (DEM).

CALIPSO Quality Statements Lidar Level 1B Profile Products Version Releases: 2.01, 2.02

CALIOP_L1ProfileProducts_2.01.pdf

这篇关于【记录】CALIPSO Lidar Level 1B产品介绍的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/390988

相关文章

redis过期key的删除策略介绍

《redis过期key的删除策略介绍》:本文主要介绍redis过期key的删除策略,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录第一种策略:被动删除第二种策略:定期删除第三种策略:强制删除关于big key的清理UNLINK命令FLUSHALL/FLUSHDB命

Java使用SLF4J记录不同级别日志的示例详解

《Java使用SLF4J记录不同级别日志的示例详解》SLF4J是一个简单的日志门面,它允许在运行时选择不同的日志实现,这篇文章主要为大家详细介绍了如何使用SLF4J记录不同级别日志,感兴趣的可以了解下... 目录一、SLF4J简介二、添加依赖三、配置Logback四、记录不同级别的日志五、总结一、SLF4J

在Spring Boot中浅尝内存泄漏的实战记录

《在SpringBoot中浅尝内存泄漏的实战记录》本文给大家分享在SpringBoot中浅尝内存泄漏的实战记录,结合实例代码给大家介绍的非常详细,感兴趣的朋友一起看看吧... 目录使用静态集合持有对象引用,阻止GC回收关键点:可执行代码:验证:1,运行程序(启动时添加JVM参数限制堆大小):2,访问 htt

MySQL 中查询 VARCHAR 类型 JSON 数据的问题记录

《MySQL中查询VARCHAR类型JSON数据的问题记录》在数据库设计中,有时我们会将JSON数据存储在VARCHAR或TEXT类型字段中,本文将详细介绍如何在MySQL中有效查询存储为V... 目录一、问题背景二、mysql jsON 函数2.1 常用 JSON 函数三、查询示例3.1 基本查询3.2

Pytest多环境切换的常见方法介绍

《Pytest多环境切换的常见方法介绍》Pytest作为自动化测试的主力框架,如何实现本地、测试、预发、生产环境的灵活切换,本文总结了通过pytest框架实现自由环境切换的几种方法,大家可以根据需要进... 目录1.pytest-base-url2.hooks函数3.yml和fixture结论你是否也遇到过

Python获取中国节假日数据记录入JSON文件

《Python获取中国节假日数据记录入JSON文件》项目系统内置的日历应用为了提升用户体验,特别设置了在调休日期显示“休”的UI图标功能,那么问题是这些调休数据从哪里来呢?我尝试一种更为智能的方法:P... 目录节假日数据获取存入jsON文件节假日数据读取封装完整代码项目系统内置的日历应用为了提升用户体验,

Spring Boot 配置文件之类型、加载顺序与最佳实践记录

《SpringBoot配置文件之类型、加载顺序与最佳实践记录》SpringBoot的配置文件是灵活且强大的工具,通过合理的配置管理,可以让应用开发和部署更加高效,无论是简单的属性配置,还是复杂... 目录Spring Boot 配置文件详解一、Spring Boot 配置文件类型1.1 applicatio

MySQL INSERT语句实现当记录不存在时插入的几种方法

《MySQLINSERT语句实现当记录不存在时插入的几种方法》MySQL的INSERT语句是用于向数据库表中插入新记录的关键命令,下面:本文主要介绍MySQLINSERT语句实现当记录不存在时... 目录使用 INSERT IGNORE使用 ON DUPLICATE KEY UPDATE使用 REPLACE

Python 中的异步与同步深度解析(实践记录)

《Python中的异步与同步深度解析(实践记录)》在Python编程世界里,异步和同步的概念是理解程序执行流程和性能优化的关键,这篇文章将带你深入了解它们的差异,以及阻塞和非阻塞的特性,同时通过实际... 目录python中的异步与同步:深度解析与实践异步与同步的定义异步同步阻塞与非阻塞的概念阻塞非阻塞同步

Python Dash框架在数据可视化仪表板中的应用与实践记录

《PythonDash框架在数据可视化仪表板中的应用与实践记录》Python的PlotlyDash库提供了一种简便且强大的方式来构建和展示互动式数据仪表板,本篇文章将深入探讨如何使用Dash设计一... 目录python Dash框架在数据可视化仪表板中的应用与实践1. 什么是Plotly Dash?1.1