Search NASA⌕ Search

SEARCH · Search NASA

Results for “data standard”

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 109 records · Page 6

Standardization of computer compatible tape formats for remote sensing data

Standards and guidelines being developed for future CCT formats for use in Landsat receiving stations are presented, in order to solve the data compatability problem, and to consider user community requirements. Data exchange at the local, regional, national, or international level is an important user requirement, and data integration from various sources should be possible. The tape super structure allows various formats to be implemented. A volume directory identifies the volume, and a file descriptor confirms it. The data is then filed, and it is determined whether the data files are appropriate to already defined file classes. If not, a new class is established. Applications of this format are in three areas: satellite imagery, geocoded polygon data, and airborne remote sensing data.

Thomas, V. L.↗

Standard formatted data units-control authority procedures

The purpose of this document is to establish a set of minimum and optional requirements for the implementation of Control Authority (CA) organizations within and among the Agencies participating in the Consultative Committee for Space Data Systems (CCSDS). By satisfying these requirements, the resultant cooperating set of CA organizations will produce a global CA service supporting information transfer with digital data under the Standard Formatted Data Unit (SFDU) concept. This service is primarily accomplished through the registration, permanent archiving, and dissemination of metadata in the form of Metadata Objects (MDO) that assist in the interpretation of data objects received in SFDU form. This Recommendation addresses the responsibilities, services, and interface protocols for a hierarchy of CA organizations. The top level, consisting of the CCSDS Secretariat and its operational agent, is unique and primarily provides a global coordination function. The lower levels are Agency CA organizations that have primary responsibility for the registration, archiving, and dissemination of MDOs. As experience is gained and technology evolves, the CA Procedures will be extended to include enhanced services and their supporting protocols. In particular, it is anticipated that eventually CA organizations will be linked via networks on a global basis, and will provide requestors with online automated access to CA services. While this Recommendation does not preclude such operations, it also does not recommend the specific protocols to be used to ensure global compatibility of these services. These recommendations will be generated as experience is gained.

Source record↗

Data File Standard for Flow Cytometry, Version FCS 3.1

The flow cytometry data file standard provides the specifications needed to completely describe flow cytometry data sets within the confines of the file containing the experimental data. In 1984, the first Flow Cytometry Standard format for data files was adopted as FCS 1.0. This standard was modified in 1990 as FCS 2.0 and again in 1997 as FCS 3.0. We report here on the next generation flow cytometry standard data file format. FCS 3.1 is a minor revision based on suggested improvements from the community. The unchanged goal of the standard is to provide a uniform file format that allows files created by one type of acquisition hardware and software to be analyzed by any other type. The FCS 3.1 standard retains the basic FCS file structure and most features of previous versions of the standard. Changes included in FCS 3.1 address potential ambiguities in the previous versions and provide a more robust standard. The major changes include simplified support for international characters and improved support for storing compensation. The major additions are support for preferred display scale, a standardized way of capturing the sample volume, information about originality of the data file, and support for plate and well identification in high throughput, plate based experiments. Please see the normative version of the FCS 3.1 specification in Supporting Information for this manuscript (or at http://www.isac-net.org/ in the Current standards section) for a complete list of changes.

59 BASIC BIOLOGICAL SCIENCES↗

Standard services for the capture, processing, and distribution of packetized telemetry data

Standard functional services for the capture, processing, and distribution of packetized data are discussed with particular reference to the future implementation of packet processing systems, such as those for the Space Station Freedom. The major functions are listed under the following major categories: input processing, packet processing, and output processing. A functional block diagram of a packet data processing facility is presented, showing the distribution of the various processing functions as well as the primary data flow through the facility.

Stallings, William H.↗

Solar Bankability Data to Advance Transactions and Access (SB-DATA) Final Technical Report

The DOE project “Solar Bankability Data to Advance Transactions and Access”, known in the solar industry and referred to in this report as “Orange Button”, had project objectives of convening key stakeholder participants in the solar project lifecycle to develop a data taxonomy that meets to the solar industry’s needs for standardized data types for use in solar projects. Additional Orange Button deliverables included the development of an online data exchange to act as a clearinghouse of data that conformed to the data standard and additional solar industry data, and a Solar Data Translation Platform that could transform legacy solar project data to conform to the Orange Button data standard. All of these objectives were achieved. The Smart Electric Power Alliance (SEPA) provided program management, industry participant recruiting and convening, worked with the solar industry to define the scope of the Orange Button data taxonomy, and documented and delivered the taxonomy data requirements to funded project partners to develop both the taxonomy and the data conversion tools. Further efforts included performing extensive industry outreach and awareness to encourage adoption of the Orange Button taxonomy by the solar industry by enumerating the cost saving benefits of using the taxonomy and the public benefit of the increased use of solar energy due to increased bankability and viability of solar development projects. Solar PV panel and component prices have fallen in the last decade, while soft costs have remained stubbornly high and can account for as much as 64% of the total cost of a new solar system. Part of the U.S. Department of Energy SunShot Initiative, Orange Button enabled the creation and adoption of industry-led open data standards for rapid and seamless information exchange across the solar value chain, from origination to decommissioning. Standardizing data will reduce soft costs by making it easier to share solar data and speeding up processes. The taxonomy is a product of solar industry participants convening to identify the pain points caused by incompatible data, and to agree on and standardize data types to be used by the actors in the solar project lifecycle. This report focuses on the SEPA led first phase of Orange Button project that included industry outreach and recruiting participants for five industry working groups, widespread industry outreach to increase awareness and encourage eventual adoption of the taxonomy, and the definition of the scope, use cases, and supporting data types of the Orange Button taxonomy. The solar industry has been receptive of the completed Orange Button taxonomy. In SEPA’s work, 401 solar industry participants facilitated by SEPA defined the scope, use cases, and requirements for the taxonomy leading to over 150 taxonomy early adopters incorporating the taxonomy into their software products serving the solar industry, and several large investors and banks have started projects to enable them to utilize the taxonomy to gain back-office efficiencies. Moving forward, as the solar industry more widely embraces the Orange Button taxonomy and begins realizing the tangible benefits of adoption at scale, we expect further pressure on solar soft costs and increases in the bankability of solar projects.

14 SOLAR ENERGY↗

Standardizing Navigation Data: A Status Update

This paper presents the work of the Navigation Working Group of the Consultative Committee for Space Data Systems (CCSDS) on development of standards addressing the transfer of orbit, attitude and tracking data for space objects. Much progress has been made since the initial presentation of the standards in 2004, including the progression of the orbit data standard to an accepted standard, and the near completion of the attitude and tracking data standards. The orbit, attitude and tracking standards attempt to address predominant parameterizations for their respective data, and create a message format that enables communication of the data across space agencies and other entities. The messages detailed in each standard are built upon a keyword = value paradigm, where a fixed list of keywords is provided in the standard where users specify information about their data, and also use keywords to encapsulate their data. The paper presents a primer on the CCSDS standardization process to put in context the state of the message standards, and the parameterizations supported in each standard, then shows examples of these standards for orbit, attitude and tracking data. Finalization of the standards is expected by the end of calendar year 2007.

VanEepoel, John M.↗

NASA data system standards

The NASA approach to data systems standardization is described. The major thrust of this activity is to assure effective use of NASA resources. The process by which standards are written, who writes them, and what subjects are covered, is briefly examined.

Byers, R. A.↗

Collaborative Data Publication Utilizing the Open Data Repository's (ODR) Data Publisher

Introduction: For small communities in diverse fields such as astrobiology, publishing and sharing data can be a difficult challenge. While large, homogenous fields often have repositories and existing data standards, small groups of independent researchers have few options for publishing standards and data that can be utilized within their community. In conjunction with teams at NASA Ames and the University of Arizona, the Open Data Repository's (ODR) Data Publisher has been conducting ongoing pilots to assess the needs of diverse research groups and to develop software to allow them to publish and share their data collaboratively. Objectives: The ODR's Data Publisher aims to provide an easy-to-use and implement software tool that will allow researchers to create and publish database templates and related data. The end product will facilitate both human-readable interfaces (web-based with embedded images, files, and charts) and machine-readable interfaces utilizing semantic standards. Characteristics: The Data Publisher software runs on the standard LAMP (Linux, Apache, MySQL, PHP) stack to provide the widest server base available. The software is based on Symfony (www.symfony.com) which provides a robust framework for creating extensible, object-oriented software in PHP. The software interface consists of a template designer where individual or master database templates can be created. A master database template can be shared by many researchers to provide a common metadata standard that will set a compatibility standard for all derivative databases. Individual researchers can then extend their instance of the template with custom fields, file storage, or visualizations that may be unique to their studies. This allows groups to create compatible databases for data discovery and sharing purposes while still providing the flexibility needed to meet the needs of scientists in rapidly evolving areas of research. Research: As part of this effort, a number of ongoing pilot and test projects are currently in progress. The Astrobiology Habitable Environments Database Working Group is developing a shared database standard using the ODR's Data Publisher and has a number of example databases where astrobiology data are shared. Soon these databases will be integrated via the template-based standard. Work with this group helps determine what data researchers in these diverse fields need to share and archive. Additionally, this pilot helps determine what standards are viable for sharing these types of data from internally developed standards to existing open standards such as the Dublin Core (http://dublincore.org) and Darwin Core (http://rs.twdg.org) metadata standards. Further studies are ongoing with the University of Arizona Department of Geosciences where a number of mineralogy databases are being constructed within the ODR Data Publisher system. Conclusions: Through the ongoing pilots and discussions with individual researchers and small research teams, a definition of the tools desired by these groups is coming into focus. As the software development moves forward, the goal is to meet the publication and collaboration needs of these scientists in an unobtrusive and functional way.

easy to use and implement software tool↗

TDA Assessment of Recommendations for Space Data System Standards

NASA is participating in the development of international standards for space data systems. Recommendations for standards thus far developed are assessed. The proposed standards for telemetry coding and packet telemetry provide worthwhile benefit to the DSN; their cost impact to the DSN should be small. Because of their advantage to the NASA space exploration program, their adoption should be supported by TDA, JPL, and OSTDS.

Posner, E. C.↗

Practices and Standards for Data and Processing at the APS

The handling of datasets at scientific user facilities is becoming progressively more challenging as advances in sources and detectors drive increasingly aggressive data acquisition rates. The ability to share and process these data depends on the ability of the originator of the data and the persons making use of that data to unequivocally agree on what these data mean. This understanding is driven by use of standardized data formats.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Consultative Committee for Space Data Systems recommendation for space data system standards: Telecommand. Part 2.1: Command operation procedures

This recommendation contains the detailed specification of the logic required to carry out the Command Operations Procedures of the Transfer Layer. The Recommendation for Telecommand--Part 2, Data Routing Service contains the standard data structures and data communication procedures used by the intermediate telecommand system layers (the Transfer and Segmentation Layers). In particular, it contains a brief description of the Command Operations Procedures (COP) within the Transfer Layer. This recommendation contains the detailed definition of the COP's in the form of state tables, along with definitions of the terms used. It is assumed that the reader of this document is familiar with the data structures and terminology of part 2. In case of conflict between the description of the COP's in part 2 and in this recommendation, the definition in this recommendation will take precedence. In particular, this document supersedes section 4.3.3.1 through 4.3.3.4 of part 2.

Source record↗

Towards standards for data exchange and integration and their impact on a public database such as CEBS (Chemical Effects in Biological Systems)

Integration, re-use and meta-analysis of high content study data, typical of DNA microarray studies, can increase its scientific utility. Access to study data and design parameters would enhance the mining of data integrated across studies. However, without standards for which data to include in exchange, and common exchange formats, publication of high content data is time-consuming and often prohibitive. The MGED Society ( (www.mged.org)) was formed in response to the widespread publication of microarray data, and the recognition of the utility of data re-use for meta-analysis. The NIEHS has developed the Chemical Effects in Biological Systems (CEBS) database, which can manage and integrate study data and design from biological and biomedical studies. As community standards are developed for study data and metadata it will become increasingly straightforward to publish high content data in CEBS, where they will be available for meta-analysis. Different exchange formats for study data are being developed: Standard for Exchange of Nonclinical Data (SEND; (www.cdisc.org)); Tox-ML ( (www.Leadscope.com)) and Simple Investigation Formatted Text (SIFT) from the NIEHS. Data integration can be done at the level of conclusions about responsive genes and phenotypes, and this workflow is supported by CEBS. CEBS also integrates raw and preprocessed data within a given platform. The utility and a method for integrating data within and across DNA microarray studies is shown in an example analysis using DrugMatrix data deposited in CEBS by Iconix Pharmaceuticals.

60 APPLIED LIFE SCIENCES↗

Planetary program data systems standards

Stages in the development of planetary program data system standards since the inception of program standards in 1969 are identified as a review of the then existing data system element designs, the selection of canditate elements for additional standards, and the formation in 1972 of a Telecommunication Standards Committee for fulltime work in the final preparation of the standards. Further efforts in developing and implementing a complete set of standards within the possibly shortest time are planned.

Glahn, E. W.↗

ARM Data File Standards Version 1.2

The U.S. Department of Energy (DOE)’s Atmospheric Radiation Measurement (ARM) Climate Research Facility performs routine in situ and remote-sensing observations to provide a detailed and accurate description of the Earth atmosphere in diverse climate regimes. The result is a huge archive of diverse data sets containing observational and derived data, currently accumulating at a rate of 30 terabytes (TB) of data and 150,000 different files per month (http://www.archive.arm.gov/stats/). Continuing the current processing while scaling this to even larger sizes is extremely important to the ARM Facility and requires consistent metadata and data standards. The standards described in this document will enable development of automated analysis and discovery tools for the ever growing data volumes. It will enable consistent analysis of the multiyear data, allow for development of automated monitoring and data health status tools, and allow future capabilities of delivering data on demand that can be tailored explicitly for the user needs. This analysis ability will only be possible if the data follows a minimum set of standards. This document proposes a hierarchy of required and recommended standards.

54 ENVIRONMENTAL SCIENCES↗

ARM Data File Standards Version: 1.0

The Atmospheric Radiation Measurement (ARM) Climate Research Facility performs routine in situ and remote-sensing observations to provide a detailed and accurate description of the Earth atmosphere in diverse climate regimes. The result is a diverse data sets containing observational and derived data, currently accumulating at a rate of 30 TB of data and 150,000 different files per month (http://www.archive.arm.gov/stats/storage2.html). Continuing the current processing while scaling this to even larger sizes is extremely important to the ARM Facility and requires consistent metadata and data standards. The standards described in this document will enable development of automated analysis and discovery tools for the ever-growing volumes of data. It also will enable consistent analysis of the multiyear data, allow for development of automated monitoring and data health status tools, and facilitate development of future capabilities for delivering data on demand that can be tailored explicitly to user needs. This analysis ability will only be possible if the data follows a minimum set of standards. This document proposes a hierarchy that includes required and recommended standards.

Kehoe, Kenneth↗