Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “API,”

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 NTRS1981

Correlation of spacecraft passive microwave system data with soil moisture indices (API)

Electrical scanning microwave radiometer brightness temperature, meteorological data, climatological data, and winter wheat crop information were used to estimate that soil moisture content in the Great Plains region. Results over the predominant winter wheat areas indicate that the best potential to infer soil moisture occurs during fall and spring. These periods encompass the growth stages when soil moisture is most important to winter wheat yield. Other significant results are reported.

Blanchard, B. J.↗
NASA NTRS1994

Integrating UniTree with the data migration API

The Data Migration Application Programming Interface (DMAPI) has the potential to allow developers of open systems Hierarchical Storage Management (HSM) products to virtualize native file systems without the requirement to make changes to the underlying operating system. This paper describes advantages of virtualizing native file systems in hierarchical storage management systems, the DMAPI at a high level, what the goals are for the interface, and the integration of the Convex UniTree+HSM with DMAPI along with some of the benefits derived in the resulting product.

Schrodel, David G.↗
NASA NTRS2017

Task 28: Web Accessible APIs in the Cloud Trade Study

This study explored three candidate architectures for serving NASA Earth Science Hierarchical Data Format Version 5 (HDF5) data via Hyrax running on Amazon Web Services (AWS). We studied the cost and performance for each architecture using several representative Use-Cases. The objectives of the project are: Conduct a trade study to identify one or more high performance integrated solutions for storing and retrieving NASA HDF5 and Network Common Data Format Version 4 (netCDF4) data in a cloud (web object store) environment. The target environment is Amazon Web Services (AWS) Simple Storage Service (S3).Conduct needed level of software development to properly evaluate solutions in the trade study and to obtain required benchmarking metrics for input into government decision of potential follow-on prototyping. Develop a cloud cost model for the preferred data storage solution (or solutions) that accounts for different granulation and aggregation schemes as well as cost and performance trades.

cost model↗
NASA NTRS2021

HAPI: An API Standard for Accessing Heliophysics Time Series Data

Heliophysics data analysis often involves combining diverse science measurements, many of them captured as time series. Although there are now only a few commonly used data file formats, the diversity in mechanisms for automated access to and aggregation of such data holdings can make analysis that requires intercomparison of data from multiple data providers difficult. The Heliophysics Application Programmer's Interface (HAPI) is a recently developed standard for accessing distributed time series data to increase interoperability. The HAPI specification is based on the common elements of existing data services, and it standardizes the two main parts of a data service: the request interface and the response data structures. The interface is based on the REpresentational State Transfer (REST) or RESTful architecture style, and the HAPI specification defines five required REST endpoints. Data are returned via a streaming format that hides file boundaries; the metadata is detailed enough for the content to be scientifically useful, e.g., plotted with appropriate axes layout, units, and labels. Multiple mature HAPI-related open-source projects offer server-side implementation tools and client-side libraries for reading HAPI data in multiple languages (IDL, Java, MATLAB, and Python). Multiple data providers in the US and Europe have added HAPI access alongside their existing interfaces. Based on this experience, data can be served via HAPI with little or no information loss compared to similar existing web interfaces. Finally, HAPI has been recommended as a COSPAR standard for time series data delivery.

Robert S. Weigel↗
NASA NTRSDate not supplied

InVEST Urban Development: Incorporating Earth Observation Data into the Integrated Valuation of Ecosystem Services and Tradeoffs (InVEST) Urban Flood Risk Mitigation Model Python API

Urban flooding poses as one of the biggest issues for cities today, as its impacts are amplified by both climate change and urbanization. The Natural Capital Project’s Integrated Valuation of Ecosystem Services and Tradeoffs (InVEST) Urban Flood Risk Mitigation (UFRM) model, which benefits from its simplicity and robustness, is commonly used in NASA DEVELOP projects for disaster mitigation, urban planning, and environmental justice issues. While InVEST UFRM model was able to produce the surface water runoff and retention map sufficient for the scopes of past projects, the model accuracy and spatial variability need improvement. Since the current InVEST UFRM model employs constant rainfall depth for all pixels in the area of interest (AOI), the model suffers from inaccurately estimating rainfall depth, runoff volume, and flood depth. Therefore, we adapted the model so that satellite-based precipitation raster datasets (i.e., Integrated Multi-satellitE Retrievals for Global Precipitation Measurement [GPM IMERG]) can be used instead of a single constant value. We simulated the flood events on August 21st and August 22nd, 2017 in Wyandotte County, Kansas using both our modified and the original InVEST UFRM model and then compared the results after incorporating the rainfall raster into the model. Areas with developed land on the land use map predicted moderate to high flood volume in the original volume regardless of the actual amount of precipitation. The modified model considered the rainfall depth’s spatial variation achieving less overestimation of flood runoff and volume at low-to-moderate rainfall area.

Son Do↗
NASA NTRS2023

InVEST Urban Development: Incorporating Earth Observation Data into the Integrated Valuation of Ecosystem Services and Tradeoffs (InVEST) Urban Flood Risk Mitigation Model Python API

Urban flooding poses as one of the biggest issues for cities today as its impacts are amplified by both climate change and urbanization. The Natural Capital Project’s Integrated Valuation of Ecosystem Services and Tradeoffs (InVEST) Urban Flood Risk Mitigation (UFRM) model, which benefits from its simplicity and robustness, is commonly used in NASA DEVELOP projects for disaster mitigation, urban planning, and environmental justice issues. While the InVEST UFRM model was able to produce the surface water runoff and retention map sufficient for the scopes of past projects, the model’s accuracy and spatial variability need improvement. Since the current InVEST UFRM model employs constant rainfall depth for all pixels in the area of interest (AOI), the model suffers from inaccurately estimating rainfall depth, runoff volume, and flood depth. Therefore, we adapted the model so that satellite-based precipitation raster datasets (i.e., Integrated Multi-satellitE Retrievals for Global Precipitation Measurement [GPM IMERG]) can be used instead of a single constant value. We simulated the flood events on August 21st and August 22nd, 2017, in Wyandotte County, Kansas using both our modified and the original InVEST UFRM model and then compared the results after incorporating rainfall raster into the model. Areas with developed land on the land use map predicted moderate to high flood volume in the original volume regardless of the actual amount of precipitation. The modified model considered the rainfall depth’s spatial variation achieving less overestimation of flood runoff and volume at low-to-moderate rainfall area.

Urban flooding↗