SEARCH · Engineering Papers

Results for “date warehouse”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

3 records

All sources NASA NTRS DOE OSTI

NASA NTRS2021

Dendroarchaeological Analysis of the Terminal Warehouse in New York City Reveals A History of Long-Distance Timber Transport During the Gilded Age

The Gilded Age of the late 19th century marked a period of rapid development and urbanization in New York City, U.S. To accommodate the high demand in wood products during that time, the timbers used for development of the city were increasingly sourced from locations distant from the northeastern United States. The Terminal Warehouse in the Chelsea neighborhood of New York City was one of many large buildings erected during this period of city expansion, and is an important symbol of New York City commerce during the late 1800s. To determine the history and provenance of timbers used in the construction of the Terminal Warehouse, we used tree-ring analysis on longleaf pine (Pinus palustris Mill.) joists that were original to the building. The ring-width patterns on the joists cross dated well internally, suggesting a common origin of the sampled lumber. Further, our Terminal Warehouse tree-ring chronology (1512–1891 C.E.) correlated strongly with existing tree-ring chronologies from western/central Georgia and eastern Alabama, indicating that the timbers were extracted from this region of the southeastern United States. The provenancing and dating of the Terminal Warehouse timbers underscores the important role that southern pines played in the expansion and development of New York City during the Gilded Age.

Dendroprovenance↗

NASA NTRS2014

Complete Decoding and Reporting of Aviation Routine Weather Reports (METARs)

Aviation Routine Weather Report (METAR) provides surface weather information at and around observation stations, including airport terminals. These weather observations are used by pilots for flight planning and by air traffic service providers for managing departure and arrival flights. The METARs are also an important source of weather data for Air Traffic Management (ATM) analysts and researchers at NASA and elsewhere. These researchers use METAR to correlate severe weather events with local or national air traffic actions that restrict air traffic, as one example. A METAR is made up of multiple groups of coded text, each with a specific standard coding format. These groups of coded text are located in two sections of a report: Body and Remarks. The coded text groups in a U.S. METAR are intended to follow the coding standards set by National Oceanic and Atmospheric Administration (NOAA). However, manual data entry and edits made by a human report observer may result in coded text elements that do not follow the standards, especially in the Remarks section. And contrary to the standards, some significant weather observations are noted only in the Remarks section and not in the Body section of the reports. While human readers can infer the intended meaning of non-standard coding of weather conditions, doing so with a computer program is far more challenging. However such programmatic pre-processing is necessary to enable efficient and faster database query when researchers need to perform any significant historical weather analysis. Therefore, to support such analysis, a computer algorithm was developed to identify groups of coded text anywhere in a report and to perform subsequent decoding in software. The algorithm considers common deviations from the standards and data entry mistakes made by observers. The implemented software code was tested to decode 12 million reports and the decoding process was able to completely interpret 99.93 of the reports. This document presents the deviations from the standards and the decoding algorithm. Storing all decoded data in a database allows users to quickly query a large amount of data and to perform data mining on the data. Users can specify complex query criteria not only on date or airport but also on weather condition. This document also describes the design of a database schema for storing the decoded data, and a Data Warehouse web application that allows users to perform reporting and analysis on the decoded data. Finally, this document presents a case study correlating dust storms reported in METARs from the Phoenix International airport with Ground Stops issued by Air Route Traffic Control Centers (ATCSCC). Blowing widespread dust is one of the weather conditions when dust storm occurs. By querying the database, 294 METARs were found to report blowing widespread dust at the Phoenix airport and 41 of them reported such condition only in the Remarks section of the reports. When METAR is a data source for an ATM research, it is important to include weather conditions not only from the Body section but also from the Remarks section of METARs.

METAR Decoder/Parser↗

NASA NTRS2016

Supply Warehouse#3, SWMU 088 Operations, Maintenance, and Monitoring Report Kennedy Space Center, Florida

This document presents the findings, observations, and results associated with Operations, Maintenance, and Monitoring (OM&M) activities of Corrective Measures Implementation (CMI) activities conducted at Supply Warehouse #3 (SW3) located at John F. Kennedy Space Center (KSC), Florida from October 8, 2015, to September 12, 2016, and performance monitoring results for semi-annual sampling events conducted in March and September 2016. The primary objective of SW3 CMI is to actively decrease concentrations of trichloroethene (TCE) and vinyl chloride (VC) to less than Florida Department of Environmental Protection (FDEP) Natural Attenuation Default Concentrations (NADCs), and the secondary objective is to reduce TCE, cis-1,2-dichloroethene (cDCE), trans-1,2-dichloroethene (tDCE), 1,1-dichloroethene (11DCE), and VC concentrations to less than FDEP Groundwater Cleanup Target Levels (GCTLs). The SW3 facility has been designated Solid Waste Management Unit (SWMU) 088 under KSC's Resource Conservation and Recovery Act (RCRA) Corrective Action Program. Based on the results to date, the SW3 air sparging (AS) system is operating at or below the performance criteria as presented in the 2008 SW3 Corrective Measures Implementation (CMI) Work Plan and 2009 and 2012 CMI Work Plan Addenda. Since the start of AS system operations on December 19, 2012, through the September 2016 groundwater sampling event, TCE concentrations have decreased to less than the GCTL in all wells within the Active Remediation Zone (ARZ), and VC results remain less than NADC but greater than GCTL. Based on these results, team consensus was reached at the October 2016 KSC Remediation Team (KSCRT) meeting to continue AS system operations and semi-annual performance monitoring of volatile organic compounds in March 2017 at ten monitoring wells at select locations, and in September 2017 at four monitoring wells at select locations to reduce VC concentrations to below GCTL. Additionally, surface water samples will be collected at locations SW0001, SW0002, and SW0003 during both the March and September 2017 events. Team consensus was also reached at the October 2017 KSCRT meeting to continue with operation and maintenance (O&M) of the AS system at SW3.

REPORT↗