【记录】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

相关文章

Spring Retry 实现乐观锁重试实践记录

《SpringRetry实现乐观锁重试实践记录》本文介绍了在秒杀商品SKU表中使用乐观锁和MybatisPlus配置乐观锁的方法,并分析了测试环境和生产环境的隔离级别对乐观锁的影响,通过简单验证,... 目录一、场景分析 二、简单验证 2.1、可重复读 2.2、读已提交 三、最佳实践 3.1、配置重试模板

在 Spring Boot 中使用异步线程时的 HttpServletRequest 复用问题记录

《在SpringBoot中使用异步线程时的HttpServletRequest复用问题记录》文章讨论了在SpringBoot中使用异步线程时,由于HttpServletRequest复用导致... 目录一、问题描述:异步线程操作导致请求复用时 Cookie 解析失败1. 场景背景2. 问题根源二、问题详细分

关于Spring @Bean 相同加载顺序不同结果不同的问题记录

《关于Spring@Bean相同加载顺序不同结果不同的问题记录》本文主要探讨了在Spring5.1.3.RELEASE版本下,当有两个全注解类定义相同类型的Bean时,由于加载顺序不同,最终生成的... 目录问题说明测试输出1测试输出2@Bean注解的BeanDefiChina编程nition加入时机总结问题说明

将sqlserver数据迁移到mysql的详细步骤记录

《将sqlserver数据迁移到mysql的详细步骤记录》:本文主要介绍将SQLServer数据迁移到MySQL的步骤,包括导出数据、转换数据格式和导入数据,通过示例和工具说明,帮助大家顺利完成... 目录前言一、导出SQL Server 数据二、转换数据格式为mysql兼容格式三、导入数据到MySQL数据

关于rpc长连接与短连接的思考记录

《关于rpc长连接与短连接的思考记录》文章总结了RPC项目中长连接和短连接的处理方式,包括RPC和HTTP的长连接与短连接的区别、TCP的保活机制、客户端与服务器的连接模式及其利弊分析,文章强调了在实... 目录rpc项目中的长连接与短连接的思考什么是rpc项目中的长连接和短连接与tcp和http的长连接短

四种Flutter子页面向父组件传递数据的方法介绍

《四种Flutter子页面向父组件传递数据的方法介绍》在Flutter中,如果父组件需要调用子组件的方法,可以通过常用的四种方式实现,文中的示例代码讲解详细,感兴趣的小伙伴可以跟随小编一起学习一下... 目录方法 1:使用 GlobalKey 和 State 调用子组件方法方法 2:通过回调函数(Callb

Oracle查询优化之高效实现仅查询前10条记录的方法与实践

《Oracle查询优化之高效实现仅查询前10条记录的方法与实践》:本文主要介绍Oracle查询优化之高效实现仅查询前10条记录的相关资料,包括使用ROWNUM、ROW_NUMBER()函数、FET... 目录1. 使用 ROWNUM 查询2. 使用 ROW_NUMBER() 函数3. 使用 FETCH FI

Python进阶之Excel基本操作介绍

《Python进阶之Excel基本操作介绍》在现实中,很多工作都需要与数据打交道,Excel作为常用的数据处理工具,一直备受人们的青睐,本文主要为大家介绍了一些Python中Excel的基本操作,希望... 目录概述写入使用 xlwt使用 XlsxWriter读取修改概述在现实中,很多工作都需要与数据打交

Python MySQL如何通过Binlog获取变更记录恢复数据

《PythonMySQL如何通过Binlog获取变更记录恢复数据》本文介绍了如何使用Python和pymysqlreplication库通过MySQL的二进制日志(Binlog)获取数据库的变更记录... 目录python mysql通过Binlog获取变更记录恢复数据1.安装pymysqlreplicat

java脚本使用不同版本jdk的说明介绍

《java脚本使用不同版本jdk的说明介绍》本文介绍了在Java中执行JavaScript脚本的几种方式,包括使用ScriptEngine、Nashorn和GraalVM,ScriptEngine适用... 目录Java脚本使用不同版本jdk的说明1.使用ScriptEngine执行javascript2.