Search NASA⌕ Search

SEARCH · Search NASA

Results for “data requests”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

NASA’s Human Data Repositories: An In Depth Look at the New Data Request Process

As NASA transitions its focus to travel back to the moon and on to new destinations, the need to ensure the capture, analysis, and application of research and medical data is of greater urgency than at any other previous time. In this era of limited resources and challenging schedules, the Human Research Program (HRP), based at NASA’s Johnson Space Center (JSC), recognizes the need to extract the greatest possible amount of information from the data already captured. To this end, the HRP Chief Scientist Office (CSO), HRP Program Planning and Control (PP&C) Office, and the Space Medicine Operations Division have been working together to make reuse of both research data and medical monitoring data more accessible to the user community through the Life Science Data Archive (LSDA) and the Lifetime Surveillance of Astronaut Health (LSAH) Repositories. The task of both LSDA and LSAH repositories is to acquire, preserve, and distribute retrospective research (LSDA) and medical (LSAH) data and information both within the NASA community and to the science community at large, for knowledge discovery, retrospective analysis, and planning of future research studies. An additional goal is to encourage collaboration with non-NASA institutions also faced with enhancing human performance in extreme environments. In September 2022, the LSDA website and its contents transitioned to a new NASA Life Sciences Portal (https://nlsp.nasa.gov/explore/lsdahome). This site continues to feature publicly releasable information such as non-attributable datasets, experiment descriptions (from Project Mercury to ISS, as well as from multiple flight analog missions), descriptions of medical monitoring data, and LSAH newsletters (1992 - 2022). The website also provides an updated portal to request additional research and medical data not accessible from the public website. This presentation will provide an in-depth look at the new system as it relates to finding and requesting retrospective data. We will also detail processes from making a request to delivering data for different types of data requests (i.e., attributable, or non-attributable). This includes descriptions of various approval boards, what information and actions the requestor is responsible for, and key milestones in making data available for reuse.

D. M. Thomas↗
NASA NTRS2000

The SHADOZ Data Base: History, Archive Web Guide, and Sample Climatologies

SHADOZ (Southern Hemisphere Additional Ozonesonde) is a project to augment and archive ozonesonde data from ten tropical and subtropical ozone stations. Started in 1998 by NASA's Goddard Space Flight Center and other US and international co-investigators, SHADOZ is an important tool for tropospheric ozone research in the equatorial region. The rationale for SHADOZ is to: (1) validate and improve remote sensing techniques (e.g., the Total Ozone Mapping Spectrometer (TOMS) satellite) for estimating tropical ozone, (2) contribute to climatology and trend analyses of tropical ozone and (3) provide research topics to scientists and educate students, especially in participating countries. SHADOZ is envisioned as a data service to the global scientific community by providing a central public archive location via the internet: http://code9l6.gsfc.nasa.gov/Data_services/shadoz. While the SHADOZ website maintains a standard data format for the archive, it also informs the data users on the differing stations' preparation techniques and data treatment. The presentation navigates through the SHADOZ website to access each station's sounding data and summarize each station's characteristics. Since the start of the project in 1998, the SHADOZ archive has accumulated over 600 ozonesonde profiles and received over 30,000 outside data requests. Data also includes launches from various SHADOZ supported field campaigns, such as, the Indian Ocean Experiment (INDOEX), Sounding of Ozone and Water in the Equatorial Region (SOWER) and Aerosols99 Atlantic Cruise. Using data from the archive, sample climatologies and profiles from selected stations and campaigns will be shown.

White, J. C.↗
NASA NTRS2008

The NPOESS Preparatory Project (NPP) Science Data Segment (SDS) Data Depository and Distribution Element (SD3E) System Architecture

The National Polar-orbiting Operational Environmental Satellite System (NPOESS), the U.S. Government's future low-Earth orbiting satellite system, will monitor global weather and environmental conditions. Serving as a risk reduction for NPOESS, the NPOESS Preparatory Project (NPP) will provide remotely sensed atmospheric, land, ocean, ozone, and sounder data that will serve the meteorological and global climate change scientific communities. The National Aeronautics and Space Administration (NASA) NPP Science Data Segment's (SDS) primary role is to independently assess the quality of the NPP science and environmental data records for their ability to support climate research. The SDS is composed of nine elements; an input element that receives data from the operational agencies and acts as a buffer, a calibration analysis element, five elements devoted to measurement based quality assessment, an element used to test algorithmic improvements, and an element that provides overall science direction. Each element requires a set of sensor specific science data products for their evaluation. There are four NPP sensors that will be flown on the NPP observatory. They are the Visible Infrared Imagining Radiometer Suite (VIIRS), the Advanced Technology Microwave Sounder (ATMS), the Cross-Track Infrared Sounder (CrIS), and the Ozone Mapper/Profiler Suite (OMPS). It is estimated that these four sensors combined will make daily data requests for approximately six terabytes of NPP science products from the operational data providers. As a result, issues associated with duplicate data requests, data transfers of large volumes of diverse products, and data transfer failures raised concerns with respect to the network traffic and bandwidth consumption. Therefore, a central data broker system for receiving and buffering data requests and data products for the SDS was developed. The data element for this system is called the SDS Data Depository and Distribution Element (SD3E). It supports science mission data assessment by assuring the timely and validated acquisition and subsequent transfer of the NPP Science Mission data to the SDS Elements and NPP Science Team. The six science elements that interface with the SD3E span across the NASA Goddard Space Flight Center (GSFC), the NASA Jet Propulsion Laboratory (JPL), and the University of Wisconsin. As the primary communication vehicle for the science elements and science team, the SD3E has an interface to the operational data providers: National Environment Satellite, Data, and Information Service (NESDIS) Interface Data Processing System (IDPS) and the National Oceanic Atmospheric Administration's (NOAA) Comprehensive Large Array-data Stewardship system (CLASS) Archive Data System (ADS), that are responsible for product generation and archive and distribution respectively. The SD3E is designed to be a semi-customizable and semi-automated system. This system is designed to provide flexibility and ease of use for the science users in accessing the latest data products by creating a rolling data cache that temporarily stores the products locally before transferring the data to the SDS Measurement based elements for the land, ocean, atmosphere, sounder, and ozone. This paper describes the design and architecture of one of the nine SDS elements, the SD3E, and how this system has provided a mechanism for efficient data exchange, how it has helped in alleviating some of the network traffic and usage, and how it has contributed to reducing operational costs.

Ho, Evelyn L.↗
NASA NTRS2008

The NPOESS Preparatory Project Science Data Segment (SDS) Data Depository and Distribution Element (SD3E) System Architecture

The National Polar-orbiting Operational Environmental Satellite System (NPOESS) Preparatory Project (NPP) Science Data Segment (SDS) will make daily data requests for approximately six terabytes of NPP science products for each of its six environmental assessment elements from the operational data providers. As a result, issues associated with duplicate data requests, data transfers of large volumes of diverse products, and data transfer failures raised concerns with respect to the network traffic and bandwidth consumption. The NPP SDS Data Depository and Distribution Element (SD3E) was developed to provide a mechanism for efficient data exchange, alleviate duplicate network traffic, and reduce operational costs.

Ho, Evelyn L.↗
NASA NTRS1974

Status of availability of Mariner 9 (1971-051A) TV picture data

Request procedures are described for Mariner 9 TV picture data. Image processing laboratory, user's guides, mosaics, catalogues, and microfiches are briefly discussed. Samples of the limb picture microfiche index and catalogue are presented.

Source record↗
NASA NTRS2013

Dynamic Server-Based KML Code Generator Method for Level-of-Detail Traversal of Geospatial Data

Web-based geospatial client applications such as Google Earth and NASA World Wind must listen to data requests, access appropriate stored data, and compile a data response to the requesting client application. This process occurs repeatedly to support multiple client requests and application instances. Newer Web-based geospatial clients also provide user-interactive functionality that is dependent on fast and efficient server responses. With massively large datasets, server-client interaction can become severely impeded because the server must determine the best way to assemble data to meet the client applications request. In client applications such as Google Earth, the user interactively wanders through the data using visually guided panning and zooming actions. With these actions, the client application is continually issuing data requests to the server without knowledge of the server s data structure or extraction/assembly paradigm. A method for efficiently controlling the networked access of a Web-based geospatial browser to server-based datasets in particular, massively sized datasets has been developed. The method specifically uses the Keyhole Markup Language (KML), an Open Geospatial Consortium (OGS) standard used by Google Earth and other KML-compliant geospatial client applications. The innovation is based on establishing a dynamic cascading KML strategy that is initiated by a KML launch file provided by a data server host to a Google Earth or similar KMLcompliant geospatial client application user. Upon execution, the launch KML code issues a request for image data covering an initial geographic region. The server responds with the requested data along with subsequent dynamically generated KML code that directs the client application to make follow-on requests for higher level of detail (LOD) imagery to replace the initial imagery as the user navigates into the dataset. The approach provides an efficient data traversal path and mechanism that can be flexibly established for any dataset regardless of size or other characteristics. The method yields significant improvements in userinteractive geospatial client and data server interaction and associated network bandwidth requirements. The innovation uses a C- or PHP-code-like grammar that provides a high degree of processing flexibility. A set of language lexer and parser elements is provided that offers a complete language grammar for writing and executing language directives. A script is wrapped and passed to the geospatial data server by a client application as a component of a standard KML-compliant statement. The approach provides an efficient means for a geospatial client application to request server preprocessing of data prior to client delivery. Data is structured in a quadtree format. As the user zooms into the dataset, geographic regions are subdivided into four child regions. Conversely, as the user zooms out, four child regions collapse into a single, lower-LOD region. The approach provides an efficient data traversal path and mechanism that can be flexibly established for any dataset regardless of size or other characteristics.

Baxes, Gregory↗
NASA NTRS1989

Space data management at the NSSDC (National Space Sciences Data Center): Applications for data compression

The National Space Science Data Center (NSSDC), established in 1966, is the largest archive for processed data from NASA's space and Earth science missions. The NSSDC manages over 120,000 data tapes with over 4,000 data sets. The size of the digital archive is approximately 6,000 gigabytes with all of this data in its original uncompressed form. By 1995 the NSSDC digital archive is expected to more than quadruple in size reaching over 28,000 gigabytes. The NSSDC digital archive is expected to more than quadruple in size reaching over 28,000 gigabytes. The NSSDC is beginning several thrusts allowing it to better serve the scientific community and keep up with managing the ever increasing volumes of data. These thrusts involve managing larger and larger amounts of information and data online, employing mass storage techniques, and the use of low rate communications networks to move requested data to remote sites in the United States, Europe and Canada. The success of these thrusts, combined with the tremendous volume of data expected to be archived at the NSSDC, clearly indicates that innovative storage and data management solutions must be sought and implemented. Although not presently used, data compression techniques may be a very important tool for managing a large fraction or all of the NSSDC archive in the future. Some future applications would consist of compressing online data in order to have more data readily available, compress requested data that must be moved over low rate ground networks, and compress all the digital data in the NSSDC archive for a cost effective backup that would be used only in the event of a disaster.

Green, James L.↗
NASA NTRS1997

CINTEX: International Interoperability Extensions to EOSDIS

A large part of the research under this cooperative agreement involved working with representatives of the DLR, NASDA, EDC, and NOAA-SAA data centers to propose a set of enhancements and additions to the EOSDIS Version 0 Information Management System (V0 IMS) Client/Server Message Protocol. Helen Conover of ITSL led this effort to provide for an additional geographic search specification (WRS Path/Row), data set- and data center-specific search criteria, search by granule ID, specification of data granule subsetting requests, data set-based ordering, and the addition of URLs to result messages. The V0 IMS Server Cookbook is an evolving document, providing resources and information to data centers setting up a VO IMS Server. Under this Cooperative Agreement, Helen Conover revised, reorganized, and expanded this document, and converted it to HTML. Ms. Conover has also worked extensively with the IRE RAS data center, CPSSI, in Russia. She served as the primary IMS contact for IRE-CPSSI and as IRE-CPSSI's liaison to other members of IMS and Web Gateway (WG) development teams. Her documentation of IMS problems in the IRE environment (Sun servers and low network bandwidth) led to a general restructuring of the V0 IMS Client message polling system. to the benefit of all IMS participants. In addition to the IMS server software and documentation. which are generally available to CINTEX sites, Ms. Conover also provided database design documentation and consulting, order tracking software, and hands-on testing and debug assistance to IRE. In the final pre-operational phase of IRE-CPSSI development, she also supplied information on configuration management, including ideas and processes in place at the Global Hydrology Resource Center (GHRC), an EOSDIS data center operated by ITSL.

Graves, Sara J.↗
NASA NTRS2018

Predicting the Operational Acceptance of Airborne Flight Reroute Requests Using Data Mining

For tools that generate more efficient flight routes or reroute advisories, it is important to ensure compatibility of automation and autonomy decisions with human objectives so as to ensure acceptability by the human operators. In this paper, the authors developed a proof of concept predictor of operational acceptability for route changes during a flight. Such a capability could have applications in automation tools that identify more efficient routes around airspace impacted by weather or congestion and that better meet airline preferences. The predictor is based on applying data mining techniques, including logistic regression, a decision tree, a support vector machine, a random forest and Adaptive Boost, to historical flight plan amendment data reported during operations and field experiments. Cross validation was used for model development, while nested cross validation was used to validate the models. The model found to have the best performance in predicting air traffic controller acceptance or rejection of a route change, using the available data from Fort Worth Air Traffic Control Center and its adjacent Centers, was the random forest, with an F-score of 0.77. This result indicates that the operational acceptance of reroute requests does indeed have some level of predictability, and that, with suitable data, models can be trained to predict the operational acceptability of reroute requests. Such models may ultimately be used to inform route selection by decision support tools, contributing to the development of increasingly autonomous systems that are capable of routing aircraft with less human input than is currently the case.

Operational Acceptability↗
NASA NTRSDate not supplied

Increasing Accessibility of the Runs-on-Request Metadata, Data, and Services at the Community Coordinated Modeling Center

Space weather models are essential to our ability to understand and predict space weather events. For over 20 years, the Community Coordinated Modeling Center (CCMC, https://ccmc.gsfc.nasa.gov) has been providing transformative tools and platforms for hosting space weather models and associated services, free and open to anyone interested in studying space weather. Runs-on-Request system (ROR) is one of the popular services at CCMC that permits researchers and other end-users to exercise cutting-edge hosted heliophysics and space weather models using a simple web interface, as well as collaborate on an extensive and continuously growing archive of over 28,000 model run results. Similar to other projects at CCMC, ROR has grown as a community project that strives to be open and transparent to its users. In this poster, we discuss some of our recent efforts to further expose ROR data, metadata, and services to the end users through both custom and community-developed access protocols. We also discuss how in-house science support provided by the CCMC team plays a paramount role in making ROR data and services truly accessible by the community.

Maksym Petrenko↗
NASA NTRS1997

Requesting AVIRIS Data: A Guide for Principal Investigators

This guide serves as a brief overview of the AVIRIS instrument and its role in the field of imaging spectrometry. Mission planning and flight operations are discussed, and recommendations are given regarding the deployment of ground truth experiments.

VISIBLE SPECTRA↗
NASA NTRSDate not supplied

Standard Measures During Spaceflight

The key goal of the Spaceflight Standard Measures project is to ensure that a set of measures, representing the Human Research Program’s key risks and acquired with minimal impact on time and resources, is consistently captured from crewmembers through the end of the International Space Station (ISS) Program. Data collected under the Spaceflight Standard Measures project include assessments of sleep/wake cycles, cognition, immune status and function, general blood and urine chemistry (urine is collected only before flight and after landing), microbiome composition (gastrointestinal tract, saliva, and body surface), cardiovascular structure and function (carotid intima-media thickness, orthostatic responses), sensorimotor function, and team processes. Data is collected once or twice before the flight (180 and 90 days before launch), twice during the 6-month missions (fight day 30 and 30 days before return to Earth) with the exception of actigraphy, which is recorded continuously during the mission, and during two-week periods before and after the mission. In this presentation, we will review the data collected to date on twelve ISS crew members. These data are placed in the NASA Life Sciences Data Archive and are available for occupational surveillance (using non-identifiable data) Institutional Review Board-approved data sharing requests, and retrospective data requests. This data repository enables high-level monitoring of the effectiveness of countermeasures and meaningful interpretation of health and performance outcomes for various mission durations. The knowledge gained from this project informs and supports future hypothesis-driven research that will enable the success of planetary missions.

G R Clement↗
NASA NTRSDate not supplied

Standard Measures During Spaceflight

The goal of the Spaceflight Standard Measures project is to ensure that a set of measures, representing the Human Research Program’s key risks and acquired with minimal impact on time and resources, is consistently captured from crewmembers through the end of the International Space Station (ISS) Program. Data collected under the Spaceflight Standard Measures project include assessments of sleep/wake cycles, cognition, immune status and function, general blood and urine chemistry (urine is collected only before flight and after landing), microbiome composition (gastrointestinal tract, saliva, and body surface), cardiovascular structure and function (carotid intima-media thickness, orthostatic responses), sensorimotor function, sleep quality, and team processes. Data is collected once or twice before the flight (180 and 90 days before launch), twice during the 6-month missions (flight day 30 and 30 days before return to Earth) with the exception of actigraphy, which is recorded during two-week periods before, during, and after the mission. In this presentation, we will review the data collected to date on 31 ISS crewmembers. These data are placed in the NASA Life Sciences Portal (NLSP) and are available for occupational surveillance (using non-identifiable data), Institutional Review Board-approved data sharing requests, and retrospective data requests. This data repository enables high-level monitoring of the effectiveness of countermeasures and meaningful interpretation of health and performance outcomes for various mission durations. The knowledge gained from this project informs and supports future hypothesis-driven research that will enable the success of planetary missions.

G R Clement↗
NASA NTRS2003

Automating the Processing of Earth Observation Data

NASA s vision for Earth science is to build a "sensor web": an adaptive array of heterogeneous satellites and other sensors that will track important events, such as storms, and provide real-time information about the state of the Earth to a wide variety of customers. Achieving this vision will require automation not only in the scheduling of the observations but also in the processing of the resulting data. To address this need, we are developing a planner-based agent to automatically generate and execute data-flow programs to produce the requested data products.

Golden, Keith↗
NASA NTRS2003

Automated Data Processing as an AI Planning Problem

NASA s vision for Earth Science is to build a "sensor web"; an adaptive array of heterogeneous satellites and other sensors that will track important events, such as storms, and provide real-time information about the state of the Earth to a wide variety of customers. Achieving his vision will require automation not only in the scheduling of the observations but also in the processing af tee resulting data. Ta address this need, we have developed a planner-based agent to automatically generate and execute data-flow programs to produce the requested data products. Data processing domains are substantially different from other planning domains that have been explored, and this has led us to substantially different choices in terms of representation and algorithms. We discuss some of these differences and discuss the approach we have adopted.

Golden, Keith↗