Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “interoperability”

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 1,117 records · Page 62

Restructuring Big Data to Improve Data Access and Performance in Analytic Services Making Research More Efficient for the Study of Extreme Weather Events and Application User Communities

By developing and enhancing various services and tools, the GES DISC provides users with the capability to access and visualize data, and to make comparisons of data from multiple sensor and models via a number of cross-discipline projects. Discovering Data via Faceted Web Interface Web interface to data products and services Search and Download mechanisms Dataset Landing Pages Accessing Data through Interoperable Services: GDS – GrADS Data Server OPeNDAP - Open-source Project for a Network Data Access Protocol WMS – OGC service GIS connector – allowing IS tools to access data easier (coming soon) HTTPS -- direct online access Downloading Data Basics: Subset and egridding Service – Parameter, Spatial, Time, Vertical, Mean averaging, format conversion, and regridding for L3/L4 gridded data Swath Data Subsetter – Parameter, spatial subset of L2 /L1 data. Visualizing Data Online: Giovanni –Visualization and Analysis L3/L4 gridded data AIRS NRT Viewer – AIRS near-real-time DQVis – L2 data quality visualization

data cube↗

Simulation and Verification System and Method

A simulation and verification system and method. An interoperability server provides a communications hub for communications between communicating nodes. Nodes connected to a first protocol data bus communicate in a first protocol, e.g., a half-duplex bus protocol. Nodes connected to a second protocol data bus communicate in a second protocol, e.g., a full-duplex bus protocol. A time synchronization bus provides time-frames for synchronizing operation of connected nodes. Interceptors optionally intercept communications between nodes.

Seeger, Steven↗

NASA GES DISC Earth Science Data Support

It is the NASA Goddard Earth Sciences (GES) Data and Information Services Center (DISC) mission statement to facilitate data access and evaluation, as well as scientific exploration and discovery. Recently, GES DISC has been evolving and improving our data management and services in order to promote GES DISC data to be easily discovered, improve usage and made more interoperable with common tools. As a result, we will present a brief review of our recent data services at the GES DISC including our new science-data driven website, subsetting and resampling services across multitude of satellite processing levels, visualization services, and how we utilize social media tools to interact with user communities.

data support↗

Enabling Technologies for Deep Space Imaging

From the beginning of the Space Age, imagery, particularly motion imagery, has been a part of crewed and un-crewed missions. As technologies have evolved the imagery gets better, more compelling, and more useful for operations and monitoring of systems, crew, and spacecraft. As we look forward now to crewed missions beyond low-Earth orbit, such as the Lunar Orbiting Platform-Gateway being considered as a pre-cursor to future crewed Mars missions, there are both opportunities and challenges in implementing a multi-faceted imaging system that advances mission capabilities and technology. This paper will present a vision for an imaging system that is relevant for operations of the ISS and future crewed missions in deep space, with a detailed look at some of the key innovative technologies required to enable such a system. Specific enabling technologies included are: Innovative camera systems capable of providing a 360deg field-of-view without moving parts; Ultra-high Definition (or higher) resolution; High Efficiency Video Coding compression; Compatibility with Delay Tolerant Network protocols; and Intelligent systems capable of monitoring the field-of-view for un-crewed missions. Opportunities where Standardization can enable interoperability are also identified.

Grubbs, Rodney↗

Summary of the 1st AIAA Geometry and Mesh Generation Workshop (GMGW-1) and Future Plans

The 1st AIAA Geometry and Mesh Generation Workshop (GMGW-1) was held in conjunction with the AIAA Aviation Forum and Exposition 2017 and in collaboration with the 3rd AIAA Computational Fluid Dynamics (CFD) High Lift Prediction Workshop (HiLiftPW-3). As the first AIAA workshop on these topics, GMGW-1's broad objectives were to assess the current state-of-the art in geometry preprocessing and mesh generation technology as well as software as applied to aircraft and spacecraft systems. The workshop was intended to identify and develop understanding of areas of needed improvement in terms of performance, accuracy, and applicability. It was also to provide a foundation for documenting best practices for geometry preprocessing and mesh generation. The genesis of GMGW-1 is found in the indictments levied against geometry preprocessing and mesh generation - not undeservedly - by the NASA CFD Vision 2030 Study. In order to create a reference against which future progress in geometry preprocessing and mesh generation can be measured, the organizers of GMGW-1, with the assistance of the organizers of HiLiftPW- 3, focused GMGW-1 on generation of meshes of the NASA High Lift Common Research Model (HL-CRM). Some of the generated meshes were provided for use by the participants in HiLiftPW-3. All meshes and the processes by which they were generated were analyzed by GMGW-1 as a first assessment of state of the art practices. The results of GMGW-1 added quantitative detail to known problem areas including geometry modeling, data interoperability, and amount of human intervention. They do provide a clear path toward a vision of geometry preprocessing and mesh generation in the year 2030. The next milepost along this path will be a second workshop.

Chawner, John R.↗

Seven Keys for Practical Understanding and Use of CGNS

We present key features of the CGNS standard, focusing on its two main elements, the data model (CGNS/SIDS) and its implementations (CGNS/HDF5 and CGNS/Python). The data model is detailed to emphasize how the topological user oriented information, such as families, are separated from the actual meshing that could be split or modified during the CFD work flow, and how this topological information is traced during the meshing process. We also explain why the same information can be described in multiple ways and how to handle such alternatives in an application. Two implementations, using HDF5 and Python, are illustrated in several use examples, both for archival and interoperability purposes. The CPEX extension formalized process is explained to show how to add new features to the standard in a consensual way; we present some of the next extensions to come. Finally we conclude by showing how powerful a consensual public approach like CGNS can be, as opposed to a stand-alone private one. All throughout the paper, we demonstrate how the use of CGNS could be of great benefit for both the meshing and CFD solver communities.

Poinot, Marc↗

Unmanned Aerial Systems (UAS) Integration into the National Airspace System (NAS)

NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.

UAS↗

Detect and Avoid: Efforts from NASA's UAS Integration into the NAS Project

NASA's Unmanned Aerial Systems (UAS) integration into the National Air Space (NAS) project has been working closely with the FAA and RTCA Special Committee 228 to identify and break down barriers to UAS integration. A focus of this work is on detect and avoid (DAA) technologies. A pilot has responsibility to see and avoid other aircraft and to remain "well clear," using their best judgment (Federal Aviation Regulations (FAR) Sec. 91.113). For UAS to perform this function, the see function is replaced by sensors to detect the other aircraft. Secondly, the pilot judgment of well clear has to be replaced by a mathematical expression. For Phase 1 of this effort, a well clear violation was defined if all three of these conditions are true: a) the horizontal clearance is less than 4000 ft., and b) the vertical clearance is less than 450 ft., and c) the time to loss of well clear is less than 35 seconds. This definition was developed with a great deal of community input and testing to ensure interoperability with Air Traffic Control (ATC) and pilots of manned aircraft. Appropriate guidance, alerting and displays were developed to allow UAS, with the appropriate sensors, to effectively maintain well clear. This work contributed to FAA Technical Standard Orders: TSO-C211, Detect and Avoid and TSO-C212, ATAR for Traffic Surveillance. Phase 2 of this work extends the operational environment to include the terminal area and lesser capable aircraft that might not have the payload capability to carry the RADAR defined in Phase 1. This session reports on work from Phase 1 and initial work in Phase 2.

Detect and Avoid (DAA)↗

OMI/TROPOMI Data Support from GES DISC

The NASA GES DISC has been the official archive center for data from the Ozone Monitoring Instrument (OMI) aboard NASA's Aura mission since 2004. In recent years, the GES DISC has been evolving and improving its data management and services in order to promote its data to be easily discovered and accessed, as well as to facilitate data "interoperability". This presentation will summarize metrics collected of OMI data usage and GES DISC data services. In order to support the recently released Sentinel-5P/TROPOMI data from ESA at the NASA GES DISC, a new End User License Agreement (EULA) has been implemented for users accessing these data from the GES DISC.

Johnson, J.↗

UTM UAS Serivce Supplier Development: Sprint 1 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.

UAS service supplier↗

UTM UAS Service Supplier Development: Sprint 2 Toward Technical Capability Level 4

NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.

software engineering↗

Cultivating an Emergent Earth Observation Analytics Ecosystem in the Cloud

A diverse set of data analytics systems for Earth Observations are sprouting up in the Earth Science community, with a wealth of processing algorithms and analysis methods. There is a similar wealth of data resources available via myriad data providers and clearinghouses, including large institutional systems like the Earth Observing System Data and Information System, Comprehensive Large Scale Array-data Stewardship System, and Federated Earth Observation Missions gateway. With Earth system science driving a need to work with more datasets together, and the community developing more analysis tools (some of them dataset-specific), how can we develop analysis workflows that incorporate far-flung datasets and leverage analysis resources from multiple organizations? Cloud computing points the way toward a solution in two different respects. Firstly, the access to and abstraction of virtually unlimited storage and computing power provides an environment that enables more straightforward means of pulling datasets and analysis resources together. Just as importantly, however, cloud computing serves as an example of an "ecosystem" of interoperating services, since the essence of cloud computing is the presentation of all resources as a service, from hardware to infrastructure to platform to software. This enables the combination of off-the-shelf, diverse services to construct entire systems that emerge out of an equally diverse community of architects and developers. This approach can be similarly applied to the data and analysis resources in the Earth Observation community. By exposing these resources via well understood services, and consuming resources in the same way, different organizations can construct bespoke analysis workflows and systems for their own purposes. The key leap the community needs to make is to develop analysis systems in components that interact with other components via services. The result would be a rich ecosystem of analytics components that can be combined to analyze datasets at scale and in conjunction with other datasets from other sources.

chaos↗

Collaborative Data Curation to Support the Multi-Mission Algorithm and Analysis Platform (MAAP)

Upcoming space-borne missions will offer unprecedented data about Earth but will also feature exponentially high data volumes. These high data volumes will change the way the scientific community works with data and will also create a unique need for improved data sharing and collaboration. NASA and ESA are working together to address these issues by collaboratively developing the Multi-Mission Algorithm and Analysis Platform (MAAP) to improve the understanding of global aboveground terrestrial carbon dynamics. The MAAP will support ESA’s BIOMASS mission, NASA’s GEDI mission and NASA/ISRO’s NISAR mission. The MAAP will be developed in two phases: a pilot phase and a full production phase. The pilot phase will demonstrate collaboration and basic capabilities. The pilot phase will focus on biomass relevant airborne and field campaign data. Two NASA teams are supporting the development of the MAAP. The MAAP engineering team is responsible for the development, maintenance and operations of the MAAP system while the MAAP data team ensures the ongoing quality of the data, metadata and other information provided in the MAAP. The MAAP data team also supports the ingest and archive of identified data to the MAAP platform. This poster describes the use case development process for the pilot MAAP and the data curated in support of those use cases. Additionally, this presentation will outline the pilot MAAP data ingest process and metadata curation effort along with efforts to ensure interoperability between ESA and NASA data and metadata.

Bugbee, Kaylin↗

Exploring Synergistic Tools from NASA Satellite Data for Air Quality

Space-borne earth observation has been important to monitor the earth condition and played a critical role in validating other instruments or modeling's outputs. However, the data from satellite earth observation are usually very complex in terms of science contents, formats, and spatiotemporal granularities, making them difficult to use from many aspects. NASA Goddard Earth Sciences Data and Information Services Center (GES DISC), one of the 12 official NASA data centers, archives and distributes rich collections of data from multiple satellite missions and model results. The GES DISC is also the official archive center for data from the Ozone Monitoring Instrument (OMI) aboard NASA's Aura mission since 2004. Recently, the GES DISC has been evolving and improving its data management and services in order to promote NASA data to be easily discovered and accessed, as well as to facilitate interoperability. We'll show in this presentation how to explore and analyze NASA earth observation data for air quality through a suite of user-friendly tools - from Worldview to Giovanni, demonstrating in using this set of tools prepares us to serve the Sentinel 5P TROPOMI to the community.

air quality↗

CEOS Virtual Data Repositories for WGISS Data Assets

The Committee on Earth Observation Satellites (CEOS), established in 1984 to coordinate civil space-borne observations of the Earth, through its Working Group on Information Systems and Services (WGISS) has been working towards aligning data repositories held by each of the member international agencies. The CEOS agencies hold a vast amount of earth observation data across science domains. WGISS has been working to agree on community standards for data and information discovery and to increase the interoperability and alignment among the member data repositories.

Enloe, Yonsook↗

OPeNDAP and HDF5 in the Cloud: Techniques and Best Practices for Serving HDF5 Data

In our talk we will discuss considerations and best practices for organizing data and metadata in HDF5 files when serving ESDIS products in S3 with OPeNDAP. The first part of the talk will be devoted to the best practices for organizing data and user-defined metadata including CF conventions in HDF5. We will also address interoperability with netCDF-4 and its role in accessing data in HDF5. In the second part of the talk we will go over OPeNDAP considerations for S3 access to HDF5 data.

HDF5↗

Ontologies for Aviation Data Management

Managing complex aviation data can be a significant challenge for any enterprise – whether a government agency, airline, airframe manufacturer, or aviation service provider. To handle this challenge, data models are typically developed to characterize and manage the data generated, used, and stored by a given enterprise. Unfortunately, different data providers employ qualitatively different data models, and this gives rise to problems exchanging data across organizational boundaries. Over the past decade, these problems have motivated data producers and consumers to look toward standardized data exchange models to address data interoperability. In this paper we examine some of these standardized data exchange models and compare them with a new type of data model based on ontologies. Ontology models have emerged in recent years from a confluence of research in the artificial intelligence, semantic web, and information science communities. This paper introduces ontology models, provides several use cases for ontologies relevant to aviation data management, and summarizes state of the art aviation prototype applications that utilize ontologies.

artificial intelligence↗

Collaborations and Partnerships in NASA’s Earth Science Data Systems

NASA has been collecting Earth observation data from spaceborne instruments since 1960. Today, there are tens of satellites orbiting the Earth and collecting frequent global observations for the benefit of mankind. Collaboration between NASA and organizations in the US and other countries has been extremely important in maintaining the Earth observation capabilities as well as collecting, organizing and managing the data. These collaborations have occurred in the form of: 1. NASA’s developing and launching spacecraft and instruments for operation by other agencies; 2. Instruments from collaborating organizations being flown on NASA satellites; and 3. Instruments from NASA being flown on satellites from collaborating organizations. In addition, there are collaborations such as joint science teams, data exchanges, and participation in international organizations to promote interoperability of various data systems. The purpose of this paper is to describe some of the Earth science data-related collaborative efforts in which NASA participates, and highlight a few results relevant to Earth system science research obtained through such collaborations.

Ramapriyan, Hampapuram K.↗