Search NASA⌕ Search

SEARCH · Search NASA

Results for “data archiving”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

GNSS-based Vegetation Optical Depth, Tree Sway, and Evapotranspiration data from the Niwot Ridge Subalpine Forest (US-NR1) AmeriFlux site

This data package contains data and information about Global Navigation Satellite System (GNSS)-based Vegetation Optical Depth (VOD), tree sway motion, and eddy-covariance evapotranspiration (ET) data collected at the Niwot Ridge Subalpine Forest AmeriFlux site (US-NR1). The raw GNSS data were collected between May 2022 and August 2023. Other processed datasets such as tree sway motion and ET data are also included. The goal was to study the water content within a subalpine forest and, more specifically, examine the canopy evaporation process. This data archive includes all data that were used within the following Biogeosciences discussion paper that further summarizes the research objectives and conclusions:Burns, S.P., V. Humphrey, E.D. Gutmann, M.S. Raleigh, D.R. Bowling, and P.D. Blanken, 2025: Using GNSS-based vegetation optical depth, tree sway motion, and eddy-covariance to examine evaporation of canopy-intercepted rainfall in a subalpine forest. EGUsphere [preprint],https://doi.org/10.5194/egusphere-2025-1755This data archive also supplements the 30-min Lawrence Berkeley National Laboratory (LBNL) AmeriFlux dataset for US-NR1 (i.e., https://doi.org/10.17190/AMF/1246088) and updates what was in the 2020 ESS-DIVE US-NR1 archive (https://doi.org/10.15485/1671825) to include data from the years 2020-2025. More specifically, the following updates are provided: (i) five-minute statistics (means, variances, covariances) of all data measured by the US-NR1 data system between Sep 2020 and Jun 2025 in netCDF format, (ii) the electronic logbook of US-NR1 site visits, (iii) a web calendar (in HTML format) documenting activity at the site (a replica of https://urquell.colorado.edu/calendar/), (iv) photos taken at the site between years 2020 and present day (Aug 2025), and (v) several auxiliary datasets, primary related to trees near the site, soil properties, soil moisture and soil temperature, and subcanopy radiation data. The data package is setup so that the web calendar, photos, and electronic logbook can be easily accessed on a local computer using a web browser. The provided data files are in either BINEX or SBF format (for the raw GNSS data), netCDF, CSV, ASCII, or MATLAB format. To obtain a better understanding about the archive, please start by reading the following PDF which is included within the data archive:README_ESS_DIVE_USNR1_2025_readme_first.pdf.

54 ENVIRONMENTAL SCIENCES↗

Archiving of Planetary Ring Data

Stellar occultation data provide our only Earth-based means of probing planetary rings at kilometer spatial resolution. The occultation data archive at MIT contains original data and analysis products of stellar occultations by the ring systems of the planets Jupiter, Saturn, Uranus, and Neptune observed by members of the group (and other groups) from 1977 to the present. During this time period, several media have been used to record and store the original and processed data: (1) chart records; (2) printed output, (3) audio reel tape; (4) audio cassette tape; (5) 7-track, 1/2-inch computer tape; (6) 9-track, 1/2-inch computer tape at 800, 1600, and 6250 bpi; (7) NOVA disk platters (2.5 and 5.0 Mbyte); (8) write once optical disks; (9) punched cards; and (10) read-write optical disks. With the rapid change of computer technology over this time period, some of these media have become not only obsolete, but nearly extinct. In particular, it has become nearly impossible to find any facilities that can still read 800 bpi tapes, which contain the only copies of several important data sets for the ring system of Uranus. In particular, we have an extensive ring data collection that includes data sets for the following Uranian ring occultations: U0, U11, U12, U13, U14, U25, U17, and U36.

Elliot, James L.↗

The Open Data Repositorys Data Publisher

Data management and data publication are becoming increasingly important components of researcher's workflows. The complexity of managing data, publishing data online, and archiving data has not decreased significantly even as computing access and power has greatly increased. The Open Data Repository's Data Publisher software strives to make data archiving, management, and publication a standard part of a researcher's workflow using simple, web-based tools and commodity server hardware. The publication engine allows for uploading, searching, and display of data with graphing capabilities and downloadable files. Access is controlled through a robust permissions system that can control publication at the field level and can be granted to the general public or protected so that only registered users at various permission levels receive access. Data Publisher also allows researchers to subscribe to meta-data standards through a plugin system, embargo data publication at their discretion, and collaborate with other researchers through various levels of data sharing. As the software matures, semantic data standards will be implemented to facilitate machine reading of data and each database will provide a REST application programming interface for programmatic access. Additionally, a citation system will allow snapshots of any data set to be archived and cited for publication while the data itself can remain living and continuously evolve beyond the snapshot date. The software runs on a traditional LAMP (Linux, Apache, MySQL, PHP) server and is available on GitHub (http://github.com/opendatarepository) under a GPLv2 open source license. The goal of the Open Data Repository is to lower the cost and training barrier to entry so that any researcher can easily publish their data and ensure it is archived for posterity.

Astrobiology data↗

Reusing Information Management Services for Recommended Decadal Study Missions to Facilitate Aerosol and Cloud Studies

NASA Earth Sciences Division (ESD) has made great investments in the development and maintenance of data management systems and information technologies, to maximize the use of NASA generated Earth science data. With information management system infrastructure in place, mature and operational, very small delta costs are required to fully support data archival, processing, and data support services required by the recommended Decadal Study missions. This presentation describes the services and capabilities of the Goddard Space Flight Center (GSFC) Earth Sciences Data and Information Services Center (GES DISC) and the reusability for these future missions. The GES DISC has developed a series of modular, reusable data management components currently in use. They include data archive and distribution (Simple, Scalable, Script-based, Science [S4] Product Archive aka S4PA), data processing (S4 Processor for Measurements aka S4PM), data search (Mirador), data browse, visualization, and analysis (Giovanni), and data mining services. Information management system components are based on atmospheric scientist inputs. Large development and maintenance cost savings can be realized through their reuse in future missions.

Kempler, Steve↗

HRP Data Management Plan

The purpose of Human Research Program Data Management Plan (DMP) is to define the processes and activities required for the overall management of the research data collected and managed by HRP throughout their life cycle. New updates to the Data Management Plan in 2023 include 1. CAPABILITIES AND SERVICES Data Repositories. Principal Investigators (PIs) funded by HRP may be asked to submit data to one of several NASA data repositories. HRP archives data in the NASA Life Sciences Portal (NLSP) that it considers to be unique and high value. This includes data from human subjects in space flight (ISS and commercial flights) and ground analogs to spaceflight; spaceflight tech demos involving humans; human omics data including the microbiome; parabolic flight studies; and the NASA Space Radiation Laboratory (NSRL). The Open Science Data Repository (OSDR) includes The Ames Life Sciences Data Archive (ALSDA), used to archive non-human biological data (e.g., animal) generated by the Human Research program, and GeneLab, available to HRP PIs to archive non-human omics data. Catalog for search and retrieval. A catalog of non-human HRP life science experiments, with all associated descriptions (mission, payload, hardware, and personnel related information), and biospecimens is provided on the NLSP public web site for search and retrieval. 2. IRB ROLE IN RETURN OF INDIVIDUAL RESEARCH RESULTS The NASA IRB manages the process for incidental findings and for returning results to subjects for studies for which NASA IRB is the IRB of record. Omics data, especially genomics data, may generate information significant to the health of or risk to a research subject. These data potentially hold the keys to understand lifetime risks of chronic diseases, such as cancer, as well as risks associated with exposures common in space flight. 3. UPDATE OF TERMS – IDENTIFIABLE AND ATTRIBUTABLE DATA HRP now follows Federal and NASA policy by using “identifiable” instead of “attributable” for Personally Identifiable Information (PII). 4. POLICY ABOUT INTERNAL NON-RESEARCH USE OF DATA The HRP Chief Scientist grants access to data from HRP-funded research for non-research internal use that includes program management, customer facilitation, strategic planning, and risk research planning. Typical HRP personnel granted access to HRP research data for internal use include the Element Scientist, Subject Matter Experts (SME), and Data/bioinformatics Scientists. If data accessed for Internal Use is provided to an intramural or extramural scientist for hypothesis driven research, all Federal and NASA regulations (e.g., IRB review) regarding human subject research apply.

Data Management Plan↗

Analysis of cloud characteristics derived from archived satellite data

The present investigation is concerned with the differing scientific user community requirements for cloud data and the nature of archived satellite data. It is concluded that information on cloud characteristics and cloud cover is of the utmost importance for at least three scientific research areas, viz. numerical weather forecasting, environmental remote sensing, and climatic monitoring and modelling. However, these three user groups require information at different levels of temporal and spatial resolution, and the nature of the comparison between surface and satellite assessment of cloud cover differs among the three groups. Taking into account the diverse requirements of the scientific community and difficulty of a mutually agreed definition of the cloud parameters, a number of recommendations are made. It is suggested that radiance data, not cloud data, should be archived directly from satellite observations, and that the highest spatial and temporal resolutions available should be retained in the archive.

Hughes, N. A.↗

Pooling the resources of the CMS Tier-1 sites

The CMS experiment at the LHC relies on 7 Tier-1 centres of the WLCG to perform the majority of its bulk processing activity, and to archive its data. During the first run of the LHC, these two functions were tightly coupled as each Tier-1 was constrained to process only the data archived on its hierarchical storage. This lack of flexibility in the assignment of processing workflows occasionally resulted in uneven resource utilisation and in an increased latency in the delivery of the results to the physics community.The long shutdown of the LHC in 2013-2014 was an opportunity to revisit this mode of operations, disentangling the processing and archive functionalities of the Tier-1 centres. The storage services at the Tier-1s were redeployed breaking the traditional hierarchical model: each site now provides a large disk storage to host input and output data for processing, and an independent tape storage used exclusively for archiving. Movement of data between the tape and disk endpoints is not automated, but triggered externally through the WLCG transfer management systems.With this new setup, CMS operations actively controls at any time which data is available on disk for processing and which data should be sent to archive. Thanks to the high-bandwidth connectivity guaranteed by the LHCOPN, input data can be freely transferred between disk endpoints as needed to take advantage of free CPU, turning the Tier-1s into a large pool of shared resources. The output data can be validated before archiving them permanently, and temporary data formats can be produced without wasting valuable tape resources. Lastly, the data hosted on disk at Tier-1s can now be made available also for user analysis since there is no risk any longer of triggering chaotic staging from tape.In this contribution, we describe the technical solutions adopted for the new disk and tape endpoints at the sites, and we report on the commissioning and scale testing of the service. We detail the procedures implemented by CMS computing operations to actively manage data on disk at Tier-1 sites, and we give examples of the benefits brought to CMS workflows by the additional flexibility of the new system.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

StarView: The object oriented design of the ST DADS user interface

StarView is the user interface being developed for the Hubble Space Telescope Data Archive and Distribution Service (ST DADS). ST DADS is the data archive for HST observations and a relational database catalog describing the archived data. Users will use StarView to query the catalog and select appropriate datasets for study. StarView sends requests for archived datasets to ST DADS which processes the requests and returns the database to the user. StarView is designed to be a powerful and extensible user interface. Unique features include an internal relational database to navigate query results, a form definition language that will work with both CRT and X interfaces, a data definition language that will allow StarView to work with any relational database, and the ability to generate adhoc queries without requiring the user to understand the structure of the ST DADS catalog. Ultimately, StarView will allow the user to refine queries in the local database for improved performance and merge in data from external sources for correlation with other query results. The user will be able to create a query from single or multiple forms, merging the selected attributes into a single query. Arbitrary selection of attributes for querying is supported. The user will be able to select how query results are viewed. A standard form or table-row format may be used. Navigation capabilities are provided to aid the user in viewing query results. Object oriented analysis and design techniques were used in the design of StarView to support the mechanisms and concepts required to implement these features. One such mechanism is the Model-View-Controller (MVC) paradigm. The MVC allows the user to have multiple views of the underlying database, while providing a consistent mechanism for interaction regardless of the view. This approach supports both CRT and X interfaces while providing a common mode of user interaction. Another powerful abstraction is the concept of a Query Model. This concept allows a single query to be built form a single or multiple forms before it is submitted to ST DADS. Supporting this concept is the adhoc query generator which allows the user to select and qualify an indeterminate number attributes from the database. The user does not need any knowledge of how the joins across various tables are to be resolved. The adhoc generator calculates the joins automatically and generates the correct SQL query.

Williams, J. D.↗

Atmospheric Radiation Measurement Climate Research Facility Operations Quarterly Report July 1-September 30, 2016

Individual datastreams from instrumentation at the Atmospheric Radiation Measurement (ARM) Climate Research Facility fixed and mobile research sites are collected and routed to the Data Management Facility (DMF) for processing in near-real time. Instrument and processed data are then delivered approximately daily to the ARM Data Archive, where they are made freely available to the research community. For each instrument, ARM calculates the ratio of the actual number of processed data records received daily at the ARM Data Archive to the expected number of data records. The results are tabulated by 1) individual datastream, site, and month for the current year, and 2) site and fiscal year dating back to 1998. The U.S. Department of Energy requires national user facilities to report time-based operating data. The requirements involve the: Actual hours of operation (ACTUAL) – 24 hours per day, 92 days or 2208 hours for this quarter Estimated maximum operation or uptime target (TARGET) Variance (VARIANCE), which is equal to (1 – [ACTUAL/TARGET]) TARGET and VARIANCE numbers account for unplanned downtime. Differences in TARGET performance reflect the complexity of local logistics and the frequency of extreme weather events. It is impractical to measure TARGET for each instrument or datastream. Data availability reported here refers to the average of the individual, continuous datastreams received by the ARM Data Archive. Therefore, data availability is directly related to individual instrument uptime expressed in hours. Data not at the ARM Data Archive are caused by downtime (scheduled or unplanned) of the individual instruments. Missing data caused by scheduled downtime are not included in the metrics. Thus, the average percentage of data in the ARM Data Archive represents the average percentage of the time the instruments were operating for the quarter.

Southern Great Plains, North Slope of Alaska, East↗

Atmospheric Radiation Measurement Climate Research Facility Operations Quarterly Report April 1-June 30, 2016

Individual datastreams from instrumentation at the Atmospheric Radiation Measurement (ARM) Climate Research Facility fixed and mobile research sites are collected and routed to the Data Management Facility (DMF) for processing in near-real time. Instrument and processed data are then delivered approximately daily to the ARM Data Archive, where they are made freely available to the research community. For each instrument, ARM calculates the ratio of the actual number of processed data records received daily at the ARM Data Archive to the expected number of data records. The results are tabulated by 1) individual datastream, site, and month for the current year, and 2) site and fiscal year dating back to 1998. The U.S. Department of Energy requires national user facilities to report time-based operating data. The requirements involve the: Actual hours of operation (ACTUAL) – 24 hours per day, 91 days or 2184 hours for this quarter Estimated maximum operation or uptime target (TARGET) Variance (VARIANCE), which is equal to (1 – [ACTUAL/TARGET]) TARGET and VARIANCE numbers account for unplanned downtime. Differences in TARGET performance reflect the complexity of local logistics and the frequency of extreme weather events. It is impractical to measure TARGET for each instrument or datastream. Data availability reported here refers to the average of the individual, continuous datastreams received by the ARM Data Archive. Therefore, data availability is directly related to individual instrument uptime expressed in hours. Data not at the ARM Data Archive are caused by downtime (scheduled or unplanned) of the individual instruments. Missing data caused by scheduled downtime are not included in the metrics. Thus, the average percentage of data in the ARM Data Archive represents the average percentage of the time the instruments were operating for the quarter.

North Slope of Alaska, Eastern North Atlantic, Sou↗

Contents of the NASA ocean data system archive, version 11-90

The National Aeronautics and Space Administration (NASA) Ocean Data System (NODS) archive at the Jet Propulsion Laboratory (JPL) includes satellite data sets for the ocean sciences and global-change research to facilitate multidisciplinary use of satellite ocean data. Parameters include sea-surface height, surface-wind vector, sea-surface temperature, atmospheric liquid water, and surface pigment concentration. NODS will become the Data Archive and Distribution Service of the JPL Distributed Active Archive Center for the Earth Observing System Data and Information System (EOSDIS) and will be the United States distribution site for Ocean Topography Experiment (TOPEX)/POSEIDON data and metadata.

Smith, Elizabeth A.↗

Atmospheric Radiation Measurement Climate Research Facility Operations Quarterly Report April 1-June 30, 2017

Individual datastreams from instrumentation at the U.S. Department of Energy (DOE) Atmospheric Radiation Measurement (ARM) Climate Research Facility fixed and mobile research observatories (sites) are collected and routed to the ARM Data Center (ADC). The Data Management Facility (DMF), a component of the ADC, executes datastream processing in near-real time. Processed data are then delivered approximately daily to the ARM Data Archive, also a component of the ADC, where they are made freely available to the research community. For each instrument, ARM calculates the ratio of the actual number of processed data records received daily at the ARM Data Archive to the expected number of data records. DOE requires national user facilities to report time-based operating data. The requirements involve: Actual hours of operation (ACTUAL)—24 hours per day, 91 days or 2184 hours for this quarter Estimated maximum operation or uptime target (TARGET) Variance (VARIANCE), which is equal to (1–[ACTUAL/TARGET]) TARGET and VARIANCE numbers account for unplanned downtime. Differences in TARGET performance reflect the complexity of local logistics and the frequency of extreme weather events. It is impractical to measure TARGET for each instrument or datastream. Data availability reported here refers to the average of the individual, continuous datastreams received by the ARM Data Archive. Therefore, data availability is directly related to individual instrument uptime expressed in hours. Data not at the ARM Data Archive are caused by downtime (scheduled or unplanned) of the individual instruments. Missing data caused by scheduled downtime are not included in the metrics. Thus, the average percentage of data in the ARM Data Archive represents the average percentage of the time the instruments were operating for the quarter.

Aerosol↗

Atmospheric Radiation Measurement Climate Research Facility Operations Quarterly Report January 1-March 31, 2017

Individual datastreams from instrumentation at the U.S. Department of Energy (DOE) Atmospheric Radiation Measurement (ARM) Climate Research Facility fixed and mobile research observatories (sites) are collected and routed to the ARM Data Center (ADC). The Data Management Facility (DMF), a component of the ADC, executes datastream processing in near-real time. Processed data are then delivered approximately daily to the ARM Data Archive, also a component of the ADC, where they are made freely available to the research community. For each instrument, ARM calculates the ratio of the actual number of processed data records received daily at the ARM Data Archive to the expected number of data records. DOE requires national user facilities to report time-based operating data. The requirements involve: Actual hours of operation (ACTUAL)—24 hours per day, 90 days or 2160 hours for this quarter Estimated maximum operation or uptime target (TARGET) Variance (VARIANCE), which is equal to (1–[ACTUAL/TARGET]) TARGET and VARIANCE numbers account for unplanned downtime. Differences in TARGET performance reflect the complexity of local logistics and the frequency of extreme weather events. It is impractical to measure TARGET for each instrument or datastream. Data availability reported here refers to the average of the individual, continuous datastreams received by the ARM Data Archive. Therefore, data availability is directly related to individual instrument uptime expressed in hours. Data not at the ARM Data Archive are caused by downtime (scheduled or unplanned) of the individual instruments. Missing data caused by scheduled downtime are not included in the metrics. Thus, the average percentage of data in the ARM Data Archive represents the average percentage of the time the instruments were operating for the quarter.

Eastern North Atlantic, Southern Great Plains, Nor↗

Restoration of Apollo Data by the Lunar Data Project/PDS Lunar Data Node: An Update

The Apollo 11, 12, and 14 through 17 missions orbited and landed on the Moon, carrying scientific instruments that returned data from all phases of the missions, included long-lived Apollo Lunar Surface Experiments Packages (ALSEPs) deployed by the astronauts on the lunar surface. Much of these data were never archived, and some of the archived data were on media and in formats that are outmoded, or were deposited with little or no useful documentation to aid outside users. This is particularly true of the ALSEP data returned autonomously for many years after the Apollo missions ended. The purpose of the Lunar Data Project and the Planetary Data System (PDS) Lunar Data Node is to take data collections already archived at the NASA Space Science Data Coordinated Archive (NSSDCA) and prepare them for archiving through PDS, and to locate lunar data that were never archived, bring them into NSSDCA, and then archive them through PDS. Preparing these data for archiving involves reading the data from the original media, be it magnetic tape, microfilm, microfiche, or hard-copy document, converting the outmoded, often binary, formats when necessary, putting them into a standard digital form accepted by PDS, collecting the necessary ancillary data and documentation (metadata) to ensure that the data are usable and well-described, summarizing the metadata in documentation to be included in the data set, adding other information such as references, mission and instrument descriptions, contact information, and related documentation, and packaging the results in a PDS-compliant data set. The data set is then validated and reviewed by a group of external scientists as part of the PDS final archive process. We present a status report on some of the data sets that we are processing.

Lunar↗

Policies and Procedures for Accessing Archived NASA Data via the Web

The National Space Science Data Center (NSSDC) was established by NASA to provide for the preservation and dissemination of scientific data from NASA missions. This white paper will address the NSSDC policies that govern data preservation and dissemination and the various methods of accessing NSSDC-archived data via the web.

James, Nathan↗

NASA biological and physical sciences databases: who’s the FAIRest of them all?

Conceptual models are a key part of the foundation of scientific study. Scientific data discovery and retrieval are often inaccurate and incomplete because these models are not sufficiently well-incorporated into data retrieval systems. Systems often don’t provide the necessary tools to those producing scientific data to fully and unambiguously annotate them and the result is consumers of the data cannot find them efficiently. The capability of data archives to provide these tools to link data to underlying conceptual models is one of dimensions of the recently developed “FAIR” principles (https://www.go-fair.org/fair-principles/ ), and is key to many automated processes being able to operate on these data, particularly analytics involving artificial intelligence. We used an open-source web service to measure the FAIR compliance of the three data archives operated by NASA for the biological and physical sciences: the Life Sciences Data Archive, the Physical Sciences Informatics database, and GeneLab. The service ingests references to data sets in these archives, and then executes domain-non-specific examinations of these data and metadata that test compliance to the FAIR principles. Of the 22 metrics tested, GeneLab passed 11 (50%), and PSI and LSDA each passed 7 (32%). These data were gathered using only one representative data set from each archive and we anticipate variability in results as we continue to apply these metrics to other data. A preliminary study of the failure traces for each metric suggests there is a wide range of effort and complexity in the enhancements required for each system to elevate FAIR compliance, and this is the subject of continued investigation. This information has been and will likely continue to be important information in planning these enhancements, with the goal of increased readiness of the data for automated processes.

database↗

Long-term archiving and data access: modelling and standardization

This paper reports on the multiple difficulties inherent in the long-term archiving of digital data, and in particular on the different possible causes of definitive data loss. It defines the basic principles which must be respected when creating long-term archives. Such principles concern both the archival systems and the data. The archival systems should have two primary qualities: independence of architecture with respect to technological evolution, and generic-ness, i.e., the capability of ensuring identical service for heterogeneous data. These characteristics are implicit in the Reference Model for Archival Services, currently being designed within an ISO-CCSDS framework. A system prototype has been developed at the French Space Agency (CNES) in conformance with these principles, and its main characteristics will be discussed in this paper. Moreover, the data archived should be capable of abstract representation regardless of the technology used, and should, to the extent that it is possible, be organized, structured and described with the help of existing standards. The immediate advantage of standardization is illustrated by several concrete examples. Both the positive facets and the limitations of this approach are analyzed. The advantages of developing an object-oriented data model within this contxt are then examined.

Hoc, Claude↗

ARM Climate Modeling Best Estimate Data - A new data product for climate modelers

This paper provides an overview of a new data product, named the Climate Modeling Best Estimate (CMBE) dataset, developed by the U.S. Department of Energy (DOE)’s Atmospheric Radiation Measurement (ARM) Program in order to better serve the need of climate model developers and encourage greater use of ARM data by modelers. The CMBE dataset contains those quantities that are often used in model evaluation and reflect unique ARM measurements of clouds and radiation (e.g., cloud occurrence, liquid water path, and surface radiative fluxes) from the highest quality data that ARM has for many years. The data are averaged over one hour period, which is comparable to a typical temporal resolution used in climate model output. They are currently available at five ARM Climate Research Facility (ACRF) sites located at the Southern Great Plains, North Slope of Alaska, and Tropic Western Pacific, and can be obtained from the ACRF data archive. The long-term continuous ARM data provide invaluable information to improve our understanding of the interaction between clouds and radiation and a solid observational basis for model validation and improvement. This paper shows some examples to demonstrate its unique values in studies of cloud processes, climate variability and change, and climate modeling. Plans for future enhancements of the CMBE product are also discussed.

54 ENVIRONMENTAL SCIENCES↗