Search NASA⌕ Search

SEARCH · Search NASA

Results for “data formats”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2017

Meteorological Support Interface Control Working Group (MSICWG) Instrumentation, Data Format, and Networks Document

The purpose of this document is to provide an overview of instrumentation discussed at the Meteorological Interface Control Working Group (MSICWG), a reference for data formats currently used by members of the group, a summary of proposed formats for future use by the group, an overview of the data networks of the group's members. This document will be updated as new systems are introduced, old systems are retired, and when the MSICWG community necessitates a change to the formats. The MSICWG consists of personnel from the National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC), NASA Marshall Space Flight Center (MSFC), NASA Johnson Space Center (JSC), National Oceanic and Atmospheric Administration National Weather Service Spaceflight Meteorology Group (SMG), and the United States Air Force (USAF) 45th Space Wing and Weather Squadron. The purpose of the group is to coordinate the distribution of weather related data to support NASA space launch related activities.

Brenton, James↗
NASA NTRS1988

Common Data Format (CDF) to store images

The original goal of this study was to allow free interchange of images between the HGS and other analytical tools available to NASA. Originally conceived as a collection of individual computer programs that could individually convert any format image to any other format and transfer images via several routes, NASA elected to adopt a Common Data Format (CDF) to store images. This allowed the storage of all images in one format on the NASA EADS. Most of the individual programs were then combined and placed in a user friendly menu-driven system that allows free interchange of image formats within EADS (Sun Workstation), HGS, and Omnicon systems. Additional software and hardware was supplied that allows physical transfer of the formatted images throughout these systems and to external systems.

Shreve, Loy W., II↗
DOE OSTI2025

Electric Vehicle Charging Analytics and Reporting Tool (EV-ChART): Data Format and Preparation Guidance (V.5.0)

The Joint Office of Energy and Transportation maintains the Electric Vehicle Charging Analytics and Reporting Tool (EV-ChART), which provides a centralized hub for submitting electric vehicle (EV) charging infrastructure data directed by the Federal Highway Administration (23 CFR 680.112(a)-(c)). EV-ChART provides a streamlined data submission process and an integrated set of analytic tools, connects to other data sources, and empowers data sharing and access across stakeholders, including the public. Any data shared publicly will be aggregated and anonymized to stay in accordance with 23 CFR 680. This EV-ChART Data Format and Preparation Guidance provides a comprehensive overview of the data reporting requirements as authorized under 23 CFR 680.112(a)-(c)). The guidance is intended to be used alongside the EV-ChART Data Input Template, which defines the tabular data structure that these data submissions must follow. Per 23 CFR 680.112(a)-(c), the annual and quarterly data submissions are required of all National Electric Vehicle Infrastructure (NEVI) Formula Program projects, as well as projects for the construction of publicly accessible EV chargers that are funded with funds made available under Title 23, United States Code, including any EV charging infrastructure project funded with federal funds that is treated as a project on a federal-aid highway. One-time data submissions are required of both the NEVI Formula Program projects and grants awarded under 23 U.S.C. 151(f) for projects that are for EV charging stations located along and designed to serve the users of designated Alternative Fuel Corridors (AFCs). Other information and data required in 23 CFR 680, such as 23 CFR 680.112(d), 23 CFR 680.116(c), and 23 CFR 680.106(a), are not discussed in this guidance.

33 ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2023

Electric Vehicle Charging Analytics and Reporting Tool (EV-ChART): Data Format and Preparation Guidance, Version 2.0

The Joint Office of Energy and Transportation maintains the Electric Vehicle Charging Analytics and Reporting Tool (EV-ChART), which provides a centralized hub for submitting electric vehicle (EV) charging infrastructure data directed by the Federal Highway Administration (23 CFR 680.112) EV-ChART will provide a streamlined data submission process and an integrated set of analytic tools, connect to other data sources, and empower data sharing and access across stakeholders, including the public. Any data shared publicly will be aggregated and anonymized to stay in accordance with 23 CFR 680. This EV-ChART Data Format and Preparation Guidance provides a comprehensive overview of the data reporting requirements as authorized under 23 CFR 680.112. The guidance is intended to be used alongside the EV-ChART Data Input Template, which defines the tabular data structure that these data submissions must follow.

ADVANCED PROPULSION SYSTEMS,MATHEMATICS AND COMPUT↗
NASA NTRS1998

Advanced Data Format (ADF) Software Library and Users Guide

The "CFD General Notation System" (CGNS) consists of a collection of conventions, and conforming software, for the storage and retrieval of Computational Fluid Dynamics (CFD) data. It facilitates the exchange of data between sites and applications, and helps stabilize the archiving of aerodynamic data. This effort was initiated in order to streamline the procedures in exchanging data and software between NASA and its customers, but the goal is to develop CGNS into a National Standard for the exchange of aerodynamic data. The CGNS development team is comprised of members from Boeing Commercial. Airplane Group, NASA-Ames, NASA-Langley, NASA-Lewis, McDonnell-Douglas Corporation (now Boeing-St. Louis), Air Force-Wright Lab., and ICEM-CFD Engineering. The elements of CGNS address all activities associated with the storage of data on external media and its movement to and from application programs. These elements include: 1) The Advanced Data Format (ADF) Database manager, consisting of both a file format specification and its 1/0 software, which handles the actual reading and writing of data from and to external storage media; 2) The Standard Interface Data Structures (SIDS), which specify the intellectual content of CFD data and the conventions governing naming and terminology; 3) The SIDS-to-ADF File Mapping conventions, which specify the exact location where the CFD data defined by the SIDS is to be stored within the ADF file(s); and 4) The CGNS Mid-level Library, which provides CFD-knowledgeable routines suitable for direct installation into application codes. The ADF is a generic database manager with minimal intrinsic capability. It was written for the purpose of storing large numerical datasets in an efficient, platform independent manner. To be effective, it must be used in conjunction with external agreements on how the data will be organized within the ADF database such defined by the SIDS. There are currently 34 user callable functions that comprise the ADF Core library and are described in the Users Guide. The library is written in C, but each function has a FORTRAN counterpart.

Smith, Matthew↗
NASA NTRS1993

The df: A proposed data format standard

A standard is proposed describing a portable format for electronic exchange of data in the physical sciences. Writing scientific data in a standard format has three basic advantages: portability; the ability to use metadata to aid in interpretation of the data (understandability); and reusability. An improperly formulated standard format tends towards four disadvantages: (1) it can be inflexible and fail to allow the user to express his data as needed; (2) reading and writing such datasets can involve high overhead in computing time and storage space; (3) the format may be accessible only on certain machines using certain languages; and (4) under some circumstances it may be uncertain whether a given dataset actually conforms to the standard. A format was designed which enhances these advantages and lessens the disadvantages. The fundamental approach is to allow the user to make her own choices regarding strategic tradeoffs to achieve the performance desired in her local environment. The choices made are encoded in a specific and portable way in a set of records. A fully detailed description and specification of the format is given, and examples are used to illustrate various concepts. Implementation is discussed.

Lait, Leslie R.↗
NASA NTRSDate not supplied

Cloud Optimized Data Formats

Cloud computing offers the promise of being able to analyze Big Data earth Observations at scale, by allowing scientists to deploy many nodes at once to analyze the data. However, in order to take full advantage of cloud scalability, it is often necessary to reorganize and reformat the data to enable fine-grained, parallel access to the data in Web Object Storage. NASA recently conducted a study of several formats that are optimized for analysis in the cloud: Parquet, zarr, HDF (Hierarchical Data Format) in the Cloud, and Cloud-Optimized GeoTIFF (Tagged Image File Format). They were compared against non-cloud-optimized formats, netCDF (network Common Data Form) and GeoTIFF, with criteria based both on stewardship and analysis performance.

Christopher Lynnes↗
DOE OSTI2024

PHYSLITE - A new reduced common data format for ATLAS

The High Luminosity LHC (HL-LHC) era brings unprecedented computing challenges that call for novel approaches to reduce the amount of real and Monte Carlo-simulated data that is stored, while continuing to support the rich physics program of the ATLAS experiment. With the beginning of LHC Run 3, ATLAS introduced a new common data format, PHYS, that replaces most of the analysis-specific formats that were used in Run 2, and therefore reduces the disk storage significantly. ATLAS also launched the prototype of another common format, PHYSLITE, that is about a third of the size of PHYS. PHYSLITE will be the main format for ATLAS at the HL-LHC and aims to serve 80% of all physics analyses. To simplify analysis workloads and further reduce disk usage it is designed to largely replace user-defined analysis n-tuples and consequently contains pre-calibrated objects. Various forms of validations are in place to ensure correct functionality for users. Developments continue towards HL-LHC to improve the PHYSLITE format further.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
NASA NTRS1981

Two-channel Costas loop tracking performance for UQPSK signals with arbitrary data formats

Previous results on the tracking performance of two-channel Costas-type carrier synchronization loops are generalized and corrected, in order that they may be applied to several mixed-format cases. In particular, the mean-square phase jitter performance of these loops with active arm filters, synchronous or asynchronous symbol clocks, and arbitrary data formats on the two channels is examined. It is demonstrated that for each case, selection of the channel gain ratio, as motivated by the MAP estimation theory, does not guarantee optimum loop tracking performance: in some instances, a conventional single-channel Costas loop would outperform the two-channel version with the MAP choice of gain ratio. It is suggested that the gain ratio be chosen to directly minimize the mean-square phase tracking jitter which is equivalent to minimizing the loop's 'squaring loss'. This can, in some cases, improve the performance measure, although in all cases, the two-channel loop will still outperform the single-channel version.

Simon, M. K.↗
NASA NTRS1972

Carpet plot data format

Analysis and interpretation of data is the crucial phase of the decision making process. The interplay between variables must be considered as to their relative significance upon the final result, and sometimes time-sensitive decisions must be made when actual events deviate from predicted information, such as Apollo 13. As the number of variables increases past say four, the traditional method of cross-plotting tends to break down, and digital/analog results cannot present a sharply defined method of analysis. A graphical system, the carpet plot, is presented in which an unlimited number of complicated relationships of variables can be evaluated.

Byrne, J. M.↗
NASA NTRS1992

ROSAT implementation of a proposed multi-mission x ray data format

Until recently little effort has been made to ensure that data from X-ray telescopes are delivered in a format that reflects the common characteristics that most X-ray datasets share. Instrument-specific data-product design hampers the comparison of X-ray measurements made by different detectors and should be avoided whenever possible. The ROSAT project and the High Energy Astrophysics Science Archive Research Center (HEASARC) have defined a set of X-ray data products ('rationalized files') for ROSAT data that can be used for distribution and archiving of data from other X-ray missions. This set of 'rationalized files' has been defined to isolate instrument-independent and instrument-specific quantities using standards FITS constructs to ensure portability. We discuss the usage of the 'rationalized files' by ROSAT for data distribution and archiving, with particular emphasis on discrimination between instrument-independent and instrument-specific quantities, and discuss application of this format to data from other X-ray missions.

Corcoran, M.↗
NASA NTRS2005

The Hierarchical Data Format for EOS (HDF-EOS)

HDF is a file format and a software library for data storage, management, exchange, and archiving. It is written and maintained by the National Center for Supercomputing Applications (NCSA). HDF5 has a very simple but versatile data model which is compatible with most competing formats. Through its grouping and linking mechanisms, the HDF5 data model enables complex data relationships and dependencies. HDF5 accommodates the inclusion of many common types of metadata and arbitrary types and quantities of user-defined metadata.

Ullman, Richard↗
NASA NTRS1982

LANDSAT-D data format control book. Volume 2: Telemetry

The formats used for the transmission of LANDSAT-D and LANDSAT-D Prime spacecraft telemetry data through either the TDRS/GSTDN via the NASCOM Network to the CSF are described as well as the telemetry flow from the command and data handling subsystem, a telemetry list and telemetry matrix assignment for the mission and engineering formats. The on-board computer (OBC) controlled format and the dwell format are also discussed. The OBCs contribution to telemetry, and the format of the reports, are covered. The high rate data channel includes the payload correction data format, the narrowband tape recorder and the OBC dump formats.

Talipsky, R.↗
DOE OSTI2025

mzPeak: Designing a Scalable, Interoperable, and Future-Ready Mass Spectrometry Data Format

Advances in mass spectrometry (MS) instrumentation, such as higher resolution, faster scan speeds, and improved sensitivity, have significantly increased the volume and complexity of data. The growing adoption of imaging and ion mobility further amplifies these challenges across MS-based omics fields, including proteomics, metabolomics, and lipidomics. While these technologies unlock new possibilities, they also present significant challenges in data management, storage, and accessibility. Existing open formats, such as the XML-based community standards mzML and imzML, struggle to meet the demands of modern MS workflows due to their large file sizes, slow data access, and limited metadata support. Vendor-specific formats, while optimized for proprietary instruments, lack interoperability, comprehensive metadata support and long-term archival reliability. This white paper lays the groundwork for mzPeak, a next-generation community data format designed to address these challenges and support high-throughput, multi-dimensional MS workflows. By adopting a hybrid model that combines efficient binary storage for numerical data and both human and machine-readable metadata storage, mzPeak will reduce file sizes, accelerate data access, and offer a scalable, adaptable solution for evolving MS technologies. For researchers, mzPeak will enable enhanced interoperability across platforms, seamless support for complex workflows including ion mobility and MS imaging, and faster data access compared to existing community formats such as mzML. Its design will ensure data is managed in compliance with regulatory standards, essential for applications such as precision medicine and chemical safety, where long-term data integrity and accessibility are critical. For vendors, mzPeak provides a streamlined, open alternative to proprietary formats, reducing the burden of regulatory compliance while aligning with the industry's push for transparency and standardization. By offering a high-performance, interoperable solution, mzPeak positions vendors to meet customer demands for sustainable data management tools which will be able to handle emerging and future data types and workflows. mzPeak aspires to become the cornerstone of MS data management, empowering researchers, vendors, and developers to innovate and collaborate more effectively.

data formats↗
NASA NTRS1995

Exchange, interpretation, and database-search of ion mobility spectra supported by data format JCAMP-DX

To assist peak assignment in ion mobility spectrometry it is important to have quality reference data. The reference collection should be stored in a database system which is capable of being searched using spectral or substance information. We propose to build such a database customized for ion mobility spectra. To start off with it is important to quickly reach a critical mass of data in the collection. We wish to obtain as many spectra combined with their IMS parameters as possible. Spectra suppliers will be rewarded for their participation with access to the database. To make the data exchange between users and system administration possible, it is important to define a file format specially made for the requirements of ion mobility spectra. The format should be computer readable and flexible enough for extensive comments to be included. In this document we propose a data exchange format, and we would like you to give comments on it. For the international data exchange it is important, to have a standard data exchange format. We propose to base the definition of this format on the JCAMP-DX protocol, which was developed for the exchange of infrared spectra. This standard made by the Joint Committee on Atomic and Molecular Physical Data is of a flexible design. The aim of this paper is to adopt JCAMP-DX to the special requirements of ion mobility spectra.

Baumback, J. I.↗