Using CALIOP to estimate cloud-field base height and its uncertainty: the Cloud Base Altitude Spatial Extrapolator (cbase) algorithm and dataset
Open data API in a single place
Provided by Bundesamt für Kartographie und Geodäsie
Get early access to Using CALIOP to estimate cloud-field base height and its uncertainty: the Cloud Base Altitude Spatial Extrapolator (cbase) algorithm and dataset API!
Attenuated backscatter profiles from the CALIOP satellite lidar are used to estimate cloud base heights of lower-troposphere liquid clouds (cloud base height below approximately 3 km). Even when clouds are thick enough to attenuate the lidar beam (optical thickness > 5), the technique provides cloud base heights by treating the cloud base height of nearby thinner clouds as representative of the surrounding cloud field. Using ground-based ceilometer data, uncertainty estimates for the cloud base height product at retrieval resolution are derived as a function of various properties of the CALIOP lidar profiles. Evaluation of the predicted cloud base heights and their predicted uncertainty using a second, statistically independent, ceilometer dataset shows that cloud base heights and uncertainties are biased by less than 10 %.
Cbase provides two files for each CALIOP VFM input file: one using a 40 km window to detect the cloud field base height, and one using a 100 km window. (The input CALIOP VFM dataset is organised by the daytime/nighttime half of each orbit.) The file name pattern is
Cbase<resolution>_T<time><day/night>.nc (identical to the input)
Caliop VFM file name with the exception of the product name). Files are organised into subdirectories by half-orbit start date.
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.