You're currently viewing an old version of this dataset. To see the current version, click here.
ABoVE Science Cloud
Data and Resources
Additional Info
Field | Value |
---|---|
Source | https://above.nasa.gov/profiles_/above_products.html |
Last Updated | May 26, 2021, 02:25 (UTC) |
Created | November 9, 2020, 07:03 (UTC) |
Country | USA |
Data Management | Data management based on standard metadata and data product formats International metadata standards (e.g., ISO19115) should be used to facilitate discovery, sharing, and understanding data products among the diverse investigators within ABoVE. In addition, standard file format, parameter names, and units are encouraged. Community-of-practice standards should be used when these exist (e.g. AmeriFlux, GTN-P, CF Conventions). Geospatial data products should at a minimum be produced using the ABoVE Standard Projection (vector and raster) and Reference Grid (raster). Archive ABoVE metadata and data products, including value-added products and model input and output generated by the program, need to be archived when the data sets are finalized for publication or at the completion of the investigator’s funding. The process and timeline for archiving ABoVE data will be based on each project’s data management plan, modified collaboratively by the investigators, the NASA HQ program manager, the CCE Office and the appropriate archive. Most data products generated during ABoVE with NASA funding will be archived at the ORNL DAAC, and cross-referenced with the archive centers of Partner Programs (DOE NGEE-Arctic, Polar Knowledge Canada) where appropriate. |
Data Policy | NASA Data Policy This policy states that there can be no period of exclusive access to the data or data products generated during the project by either an individual scientist or a science team. A short period of time for calibration, correction, and quality assessment prior to public release is permissible. Some exceptions regarding full public access may need to be established for data obtained from sources that bind users to more restrictive data policies or that are inherently sensitive in nature (e.g., commercial satellite data or confidential human-subjects data). See more on the NASA Earth Science Data and Information Policy. ABoVE Data For the purposes of this Policy, the term "ABoVE data" shall mean the primary observations, monitoring data, site characterization information, model output, remotely sensed products, and ancillary data specifically supported by NASA and its partner agencies to meet the goals outlined in the ABoVE Concise Experiment Plan (link). All data must be accompanied by quantified estimates of uncertainty. ABoVE data includes metadata, which are defined as the descriptive information such as content, quality, and conditions that characterize a set of measurements. Data sets from other sources (e.g., forest inventory data, satellite products, global meteorological analysis, etc.) may be needed to meet the goals of ABoVE, but were not funded specifically for ABoVE. There may also be data from other programs (e.g. DOE NGEE-Arctic, Polar Knowledge Canada) that are partners with ABoVE, but fall under other management. The ABoVE Leadership Team will help broker agreements with officials and institutions in order to obtain such data sets for use by ABoVE science team members. Resolving conflicts over data and the data policy. Conflicts over the interpretation of this Data Policy, or its implementation, will be resolved at the lowest level possible within the science team, who should refer to the American Geophysical Union Policy for Scientific Integrity and Professional Ethics. Direct resolution of issues between investigators is preferred; the CCE Office and or sponsoring agencies may become involved if resolution cannot be reached. |
Data Sharing Principle | Full, open, and timely sharing of the full suite of data sets for all ABoVE science team members is a fundamental objective. All data and associated metadata produced by NASA-funded projects should be made available to every ABoVE investigator as soon as feasible but no later than 12 months after acquisition. The leaders of Partner Projects and Affiliated Projects should identify data that they intend to share when they join the ABoVE Science Team. They should provide data and metadata as soon as feasible following data collection. The agency sponsoring their data collection should define the duration of any exclusive use period. In the case of Indigenous Knowledge (IK, section 6) obtained from community stakeholders, IK data will be shared pending review and approval by the local community, tribal council, or group who participated in ABoVE research and outreach activities. Certain data products provisioned for the Science Team in the ABoVE Science Cloud (ASC) have conditions for use and/or restrictions on redistribution. Users of the ASC must acknowledge and follow these conditions and restrictions. Data will be analyzed cooperatively by all scientists involved in obtaining them, with the caveat that if IK is involved, knowledge holders must be involved in the analysis and must first provide consent before IK data are disseminated to other ABoVE investigators. In addition, ABoVE data will be made available in preliminary form to ABoVE investigators to enable quality assurance through preliminary analysis and intercomparison with other data sets. Corrections and refinements to data products will be made as the analysis proceeds. Revisions will be noted, and investigators and the ABoVE Science Cloud data system will maintain version control. The ABoVE Science Cloud is provided as a resource for data processing and sharing among the ABoVE Science team during the course of the campaign. Long-term archival and stewardship, including issuing of citations and DOIs, will be accomplished as described in section 7. Sharing Models Model source code, when made publicly available, can be used to understand the uncertainty of model results relative to results from other models or observations, enable others to see how models treat individual processes, and ultimately serve to improve models. ABoVE investigators will make numerical models and key algorithms used in publications available to program participants and the broader user community no later than upon publication. As a model evolves during ABoVE, newer model versions associated with publications will also be made available to the research community upon publication. Each model submitted should include model source code along with version number, documentation in terms of a technical note or carefully documented code, example input and output, and a history of changes. Model archiving will follow the best-practice requirements and recommendations proposed in Thornton et al. (2005). Credit will be given to model developers through citation when information from archived models is used in publications. Certain model codes may be subject to copyright or international agreements that are more restrictive. The CCE Office will be responsible for brokering agreements with officials and institutions in order to obtain specific models required for use by ABoVE scientists. |