Prados, Ana | Engineering Papers

NASA NTRS2010

Applications of OMI Tropospheric NO(Sub 2) Data: Air Quality Trends in the US and Lightning NO(x) Source Strength

This talk will be presented in two parts: 1) an analysis of tropospheric column NO2 trends in the eastern half of the United States over the period 2005 to 2009 and 2) estimation of lightning NO(x) production rates based on OMI observations and lightning flash rate data. The air quality trends in the eastern US will be determined for specific subregions using tropospheric column NO2 data from OMI for 2005 through 2008 and from GOME-2 for 2007 through 2009. This period is characterized by significant NO(x) emission reductions at power plants within most of this region. The air quality trends will be compared with those estimated from continuous emission monitoring data from the power plants compiled by the US Environmental Protection Agency. OMI NO2 data have also been used to estimate lightning NOx production per flash in selected storms near Costa Rica and Panama during the 2007 NASA TC4 field campaign and over the continental US, Gulf of Mexico, and western Atlantic during the summers of 2005 and 2006. The lightning signal is extracted from the OMI data through a custom retrieval in which an NO2 profile representative of convective outflow is used in the airmass factor calculation and the background NO2 column is subtracted from the tropospheric column. When combined with NO(x)/NO2 ratios from the NASA GMT model and observed flash rates, the resulting estimates of NO(x) production per flash are comparable to those estimated obtained from analyses of aircraft data and cloud-resolving modeling.

Pickering, Kenneth↗

NASA NTRS2008

Provenance in Data Interoperability for Multi-Sensor Intercomparison

As our inventory of Earth science data sets grows, the ability to compare, merge and fuse multiple datasets grows in importance. This requires a deeper data interoperability than we have now. Efforts such as Open Geospatial Consortium and OPeNDAP (Open-source Project for a Network Data Access Protocol) have broken down format barriers to interoperability; the next challenge is the semantic aspects of the data. Consider the issues when satellite data are merged, cross-calibrated, validated, inter-compared and fused. We must match up data sets that are related, yet different in significant ways: the phenomenon being measured, measurement technique, location in space-time or quality of the measurements. If subtle distinctions between similar measurements are not clear to the user, results can be meaningless or lead to an incorrect interpretation of the data. Most of these distinctions trace to how the data came to be: sensors, processing and quality assessment. For example, monthly averages of satellite-based aerosol measurements often show significant discrepancies, which might be due to differences in spatio- temporal aggregation, sampling issues, sensor biases, algorithm differences or calibration issues. Provenance information must be captured in a semantic framework that allows data inter-use tools to incorporate it and aid in the intervention of comparison or merged products. Semantic web technology allows us to encode our knowledge of measurement characteristics, phenomena measured, space-time representation, and data quality attributes in a well-structured, machine-readable ontology and rulesets. An analysis tool can use this knowledge to show users the provenance-related distrintions between two variables, advising on options for further data processing and analysis. An additional problem for workflows distributed across heterogeneous systems is retrieval and transport of provenance. Provenance may be either embedded within the data payload, or transmitted from server to client in an out-of-band mechanism. The out of band mechanism is more flexible in the richness of provenance information that can be accomodated, but it relies on a persistent framework and can be difficult for legacy clients to use. We are prototyping the embedded model, incorporating provenance within metadata objects in the data payload. Thus, it always remains with the data. The downside is a limit to the size of provenance metadata that we can include, an issue that will eventually need resolution to encompass the richness of provenance information required for daata intercomparison and merging.

Lynnes, Chris↗