Difference between revisions of "Air Quality Breakout, ESIP 2013 Winter Meeting"

From Earth Science Information Partners (ESIP)
Line 13: Line 13:
  
 
'''SESSION 1 PARTICIPANTS'''
 
'''SESSION 1 PARTICIPANTS'''
 +
 
''In-person'': Richard Eckman, Stefan Falke, Greg Frost, Rudy Husar, Ann Keane, Terry Keating, Chris Lynnes, Kelly Monteleone, Erin Robinson
 
''In-person'': Richard Eckman, Stefan Falke, Greg Frost, Rudy Husar, Ann Keane, Terry Keating, Chris Lynnes, Kelly Monteleone, Erin Robinson
  
Line 19: Line 20:
  
 
'''SESSION 2 PARTICIPANTS'''
 
'''SESSION 2 PARTICIPANTS'''
 +
 
''In Person'': Richard Eckman, Stefan Falke, Greg Frost, Rudy Husar, Ann Keane, Terry Keating, Ken Keiser
 
''In Person'': Richard Eckman, Stefan Falke, Greg Frost, Rudy Husar, Ann Keane, Terry Keating, Ken Keiser
  
Line 37: Line 39:
  
 
*History and Work of ESIP AQ Cluster/WG, Connections to GEO AQCoP:
 
*History and Work of ESIP AQ Cluster/WG, Connections to GEO AQCoP:
AQ Cluster has connected lots of data systems and programs, through efforts like DataFed
+
**AQ Cluster has connected lots of data systems and programs, through efforts like DataFed
Need to figure out what’s still operational in this network
+
**Need to figure out what’s still operational in this network
Timeline of AQ Cluster, AQWG, GEO AQCoP activity
+
**Timeline of AQ Cluster, AQWG, GEO AQCoP activity
ESIP Clusters meant to be short term. As interest and goals become longer term, AQ Cluster became AQWG
+
**ESIP Clusters meant to be short term. As interest and goals become longer term, AQ Cluster became AQWG
As AQWG, group involved with ESIP activities, governance, eligible for support, etc
+
**As AQWG, group involved with ESIP activities, governance, eligible for support, etc
Stefan ran logistics for AQWG during much of its history
+
**Stefan ran logistics for AQWG during much of its history
AQWG presented themselves to GEOSS as self-organized grouping
+
**AQWG presented themselves to GEOSS as self-organized grouping
AQWG loaded in AQ datasets, built interoperable systems, contributed to best practices collection
+
**AQWG loaded in AQ datasets, built interoperable systems, contributed to best practices collection
AQCoP Regional Clusters for North America, Europe, India
+
**AQCoP Regional Clusters for North America, Europe, India
ESIP wiki provides workspace for AQWG & AQCoP
+
**ESIP wiki provides workspace for AQWG & AQCoP
Goal is an interoperable AQ Data Network (ADN)
+
**Goal is an interoperable AQ Data Network (ADN)
Tour of ESIP GEO AQCoP workspace
+
**Tour of ESIP GEO AQCoP workspace
ADN Solta 2011 Meeting: connect the connectors to create a network
+
**ADN Solta 2011 Meeting: connect the connectors to create a network
  
  
Line 55: Line 57:
 
(See Schultz presentation file)
 
(See Schultz presentation file)
  
1. AQCoP/ADN issues:
+
*AQCoP/ADN issues:
1st meeting - Solta  
+
**1st meeting - Solta  
2nd meeting - Dublin
+
**2nd meeting - Dublin
AQCoP mailing list – need to increase usage
+
**AQCoP mailing list – need to increase usage
Confusion on the European side about GEO AQCoP  
+
**Confusion on the European side about GEO AQCoP  
Delineate better who is doing what, try to make that clear to EU folks
+
**Delineate better who is doing what, try to make that clear to EU folks
Continue series of workshops
+
**Continue series of workshops
Propose next workshop in Boulder this fall
+
**Propose next workshop in Boulder this fall
  
2. JOIN – Jülich OWS Interface
+
*JOIN – Jülich OWS Interface
ECCAD data served up – example overlay ACCMP and PAN data from model
+
**ECCAD data served up – example overlay ACCMP and PAN data from model
JOIN is ready for users as of last week
+
**JOIN is ready for users as of week of January 7
Jülich test system still available until end of month
+
**Jülich test system still available until end of month
Next steps for JOIN:
+
**Next steps for JOIN:
Restructuring and public release of core code – preparing for public release of the code, can port to ECCAD, IAGOS groups, CIERA  
+
***Restructuring and public release of core code – can port to ECCAD, IAGOS groups, CIERA  
Support: MACC, IGAS (Toulouse IAGOS data), EPA, FZ Jülich, EU, HTAP
+
**Support: MACC, IGAS (Toulouse IAGOS data), EPA, FZ Jülich, EU, HTAP
  
3. MACC requests of AQCoP:
+
*MACC requests of AQCoP (MACC = EU’s chemical forecasting effort):
(MACC = EU’s chemical forecasting effort)
+
**Better user management
Better user management
+
**Direct linking to specific data sets and views
Direct linking to specific data sets and views
+
**Consolidate metadata profile and publish metadata records – still working on best practice recommendations
Consolidate metadata profile and publish metadata records – still working on best practice recommendations
 
  
4. HTAP requests of AQCoP:
+
*HTAP requests of AQCoP (HTAP = intercontinental pollutant transport model intercomparison exercise):
(HTAP = intercontinental pollutant transport model intercomparison exercise)
+
**Geneva meeting in mid-March
Geneva meeting in mid-March
+
**Linkage to met.no server (new HTAP archive)
Linkage to met.no server (new HTAP archive)
+
**More model and data comparison tools
More model and data comparison tools
 
  
  
 
'''Claire Granier''' – ''ECCAD''
 
'''Claire Granier''' – ''ECCAD''
  
ECCAD delivers emission inventories and ancillary data
+
*ECCAD delivers emission inventories and ancillary data
Ether – European Earth Science network
+
*Ether – European Earth Science network
Links to Julich server
+
*Links to Julich server
Making the data useful to a broad community, simple to use tools
+
*Making the data useful to a broad community, simple to use tools
Next steps: Include more GHGs, toxics
+
*Next steps:  
 +
**Include more GHGs, toxics
  
  
Line 97: Line 98:
 
(See Frost presentation file)
 
(See Frost presentation file)
  
Motivation for improving emissions data
+
*Motivation for improving emissions data
Overview of GEIA’s mission and goals
+
*Overview of GEIA’s mission and goals
Examples of GEIA activities, including ECCAD and CIERA portals
+
*Examples of GEIA activities, including ECCAD and CIERA portals
GEIA relies heavily on its partnership with AQCoP
+
*GEIA relies heavily on its partnership with AQCoP
Scientific and technical needs for improving access and analysis of emissions data
+
*Scientific and technical needs for improving access and analysis of emissions data
Suggest changing name of GEO AQCoP to “Air Quality and Atmospheric Composition CoP”
+
*Suggest changing name of GEO AQCoP to “Air Quality and Atmospheric Composition CoP”
  
  
Line 108: Line 109:
 
(See Shankar presentation file)
 
(See Shankar presentation file)
  
Support EPA capabilities for regional chemical transport modeling and emissions
+
*Support EPA capabilities for regional chemical transport modeling and emissions
Perspective and needs for delivering data to EPA and other US regulatory entities
+
*Perspective and needs for delivering data to EPA and other US regulatory entities
Engage groups who provide various data sets for emission modeling (land cover, etc) in AQCoP – data are distributed all over the place, but not connected right now
+
*Engage groups who provide various data sets for emission modeling (land cover, etc) in AQCoP
 
+
**Data are distributed all over the place, but not connected right now
CMAS carries out its efforts through work assignments
+
*CMAS carries out its efforts through work assignments
 +
*Modeling platforms from OAQPS and what’s being done in ORD are not well connected
  
Modeling platforms from OAQPS and what’s being done in ORD are not well connected
+
*Emission Modeling Framework database – Zac Adelman, Uma
 +
**EPA’s data could be made available through this database
  
Emission Modeling Framework database – Zac Adelman, Uma
+
*Recommends not duplicating efforts, and keeping CMAS involved, especially due to limited resources on US side
EPA’s data could be made available through this database
 
Recommends not duplicating efforts, and keeping CMAS involved, especially due to limited resources on US side
 
  
  
 
'''Terry Keating''' – ''Issues of interest to AQWG/AQCoP''
 
'''Terry Keating''' – ''Issues of interest to AQWG/AQCoP''
  
1. Bringing satellite data into AirNow
+
*Bringing satellite data into AirNow
  
2. HTAP
+
*HTAP
Example of why we need a GEOSS
+
**Example of why we need a GEOSS
Next meeting in Geneva, March 18-22, in conjunction with WMO’s 2013 conference
+
**Next meeting in Geneva, March 18-22, in conjunction with WMO’s 2013 conference
Details at http://www.htap.org/
+
**Details at http://www.htap.org/
Objectives:
+
**Objectives:
Establish science, evaluations, analyses to be done in HTAP
+
***Establish science, evaluations, analyses to be done in HTAP
Status of information infrastructure that’s been created for HTAP
+
***Status of information infrastructure that’s been created for HTAP
  
Could expand Martin Schultz group’s system built for HTAP Phase 1
+
**Could expand Martin Schultz group’s system built for HTAP Phase 1
  
Modeling resources:
+
**Modeling resources:
Data at Julich and met.no (AeroCom)
+
***Data at Julich and met.no (AeroCom)
Ensemble system at JRC
+
***Ensemble system at JRC
Atmospheric Brown Cloud Asia
+
***Atmospheric Brown Cloud Asia
MICS Asia (Tokyo, China) – Asian modeling
+
***MICS Asia (Tokyo, China) – Asian modeling
RSIG – regional modeling exercises
+
***RSIG – regional modeling exercises
  
Observations:
+
**Observations:
Surface – NILU (EBAS)
+
***Surface – NILU (EBAS)
Aircraft – ATOM (NASA Langley)
+
***Aircraft – ATOM (NASA Langley)
Satellite – NASA GIOVANNI, Atmos Comp Portal
+
***Satellite – NASA GIOVANNI, Atmos Comp Portal
  
Emissions:
+
**Emissions:
GEIA/CIERA – one platform to deliver HTAP emissions
+
***GEIA/CIERA – one platform to deliver HTAP emissions
ECCAD – another platform to deliver HTAP emissions; in process of modifying to accept information at higher resolution
+
***ECCAD – another platform to deliver HTAP emissions; in process of modifying to accept information at higher resolution
  
Development of analysis tools that draw on these databases
+
**Development of analysis tools that draw on these databases
Some work at DataFed, MACC to develop tools: this effort could be expanded
+
**Some work at DataFed, MACC to develop tools: this effort could be expanded
  
3. North American Commission on Environmental Cooperation
+
*North American Commission on Environmental Cooperation Climate Information System
Climate Information System
+
**CEC involves US, Canada, Mexico
CEC had a scoping project about this – decided to focus on emissions; identified need for web services approach to delivering these data
+
**CEC had a scoping project about this – decided to focus on emissions
3 countries working on online database of GHG and BC emissions
+
***identified need for web services approach to delivering these data
Proposals due next week, select contractor by end of January, work done by end of July
+
**3 countries working on online database of GHG and BC emissions
Tri-national national-level database focused on GHGs, BC, and related emissions
+
**Proposals due next week, select contractor by end of January, work done by end of July
Terry will connect contractor to AQCoP
+
**Tri-national national-level database focused on GHGs, BC, and related emissions
 +
**Terry will connect contractor to AQCoP
  
4. AQCoP Governance
+
*AQCoP Governance
Wiki discussion initiated
+
**Wiki discussion initiated
Recommend defining co-chairs, secretariat, steering body
+
**Recommend defining co-chairs, secretariat, steering body
  
  
Line 171: Line 173:
  
 
''1. Name of AQCoP''
 
''1. Name of AQCoP''
Recommend that we include “Atmospheric Composition” in name
+
*Recommend that we include “Atmospheric Composition” in name
Need to let GEO know about this change
+
*Need to let GEO know about this change
Alert ESIP?
+
*Alert ESIP?
  
  
 
''2. AQ Governance''
 
''2. AQ Governance''
Telecon to formalize the governance - Beginning of February?
+
*Telecon to formalize the governance - Beginning of February?
Need some governance in place before we call another meeting of the CoP  
+
*Need some governance in place before we call another meeting of the CoP  
In addition to “top-down” structure, need “bottom up” governance
+
*In addition to “top-down” structure, need “bottom up” governance
Need technical committee to deal with network issues: data catalog, metadata…
+
*Need technical committee to deal with network issues: data catalog, metadata…
Perhaps defining these tasks as working groups?
+
*Perhaps defining these tasks as working groups?
High-level umbrella steering group necessary for strategic planning and to secure resources
+
*High-level umbrella steering group necessary for strategic planning and to secure resources
Need improved forum for communication and coordination
+
*Need improved forum for communication and coordination
Suggestion to nominate 2 interim chairs or conveners to help organize meetings and coordinate efforts
+
*Suggestion to nominate 2 interim chairs or conveners to help organize meetings and coordinate efforts
  
  

Revision as of 14:35, January 16, 2013

Winter 2013 Meeting Schedule | < Back to the AQ Workspace

Notes from Breakout Sessions

ESIP Air Quality Working Group (AQWG) and GEO Air Quality Community of Practice (AQCoP)

Thursday, January 10, 2013

SESSION 1 8:30-10:00 GMT-5

SESSION 2 10:30-12:00 GMT-5

SESSION LEAD: Ann Keane (NOAA)

SESSION 1 PARTICIPANTS

In-person: Richard Eckman, Stefan Falke, Greg Frost, Rudy Husar, Ann Keane, Terry Keating, Chris Lynnes, Kelly Monteleone, Erin Robinson

Remote: Jennifer Davis, Claire Granier, Praveen Noojipady, Martin Schultz, Uma Shankar, Wenli Yang


SESSION 2 PARTICIPANTS

In Person: Richard Eckman, Stefan Falke, Greg Frost, Rudy Husar, Ann Keane, Terry Keating, Ken Keiser

Remote: Zac Adelman, Sarav Arunachalam, Steve Keppler, Martin Schultz, Uma Shankar


INDIVIDUAL PRESENTATIONS

Rudy Husar, Erin Robinson, Stefan FalkeOverview of AQWG and AQCoP (See Falke and Husar presentation files)

  • Role of ESIP in AQCoP:
    • Neutral space for coordination and interaction
    • Bringing together people at technical practitioner level
    • Support technical infrastructure for science applications
    • Provide virtual interaction as well as human interaction
    • ESIP critical to AQCoP functions
  • History and Work of ESIP AQ Cluster/WG, Connections to GEO AQCoP:
    • AQ Cluster has connected lots of data systems and programs, through efforts like DataFed
    • Need to figure out what’s still operational in this network
    • Timeline of AQ Cluster, AQWG, GEO AQCoP activity
    • ESIP Clusters meant to be short term. As interest and goals become longer term, AQ Cluster became AQWG
    • As AQWG, group involved with ESIP activities, governance, eligible for support, etc
    • Stefan ran logistics for AQWG during much of its history
    • AQWG presented themselves to GEOSS as self-organized grouping
    • AQWG loaded in AQ datasets, built interoperable systems, contributed to best practices collection
    • AQCoP Regional Clusters for North America, Europe, India
    • ESIP wiki provides workspace for AQWG & AQCoP
    • Goal is an interoperable AQ Data Network (ADN)
    • Tour of ESIP GEO AQCoP workspace
    • ADN Solta 2011 Meeting: connect the connectors to create a network


Martin SchultzEuropean Perspectives on AQCoP; JOIN (See Schultz presentation file)

  • AQCoP/ADN issues:
    • 1st meeting - Solta
    • 2nd meeting - Dublin
    • AQCoP mailing list – need to increase usage
    • Confusion on the European side about GEO AQCoP
    • Delineate better who is doing what, try to make that clear to EU folks
    • Continue series of workshops
    • Propose next workshop in Boulder this fall
  • JOIN – Jülich OWS Interface
    • ECCAD data served up – example overlay ACCMP and PAN data from model
    • JOIN is ready for users as of week of January 7
    • Jülich test system still available until end of month
    • Next steps for JOIN:
      • Restructuring and public release of core code – can port to ECCAD, IAGOS groups, CIERA
    • Support: MACC, IGAS (Toulouse IAGOS data), EPA, FZ Jülich, EU, HTAP
  • MACC requests of AQCoP (MACC = EU’s chemical forecasting effort):
    • Better user management
    • Direct linking to specific data sets and views
    • Consolidate metadata profile and publish metadata records – still working on best practice recommendations
  • HTAP requests of AQCoP (HTAP = intercontinental pollutant transport model intercomparison exercise):
    • Geneva meeting in mid-March
    • Linkage to met.no server (new HTAP archive)
    • More model and data comparison tools


Claire GranierECCAD

  • ECCAD delivers emission inventories and ancillary data
  • Ether – European Earth Science network
  • Links to Julich server
  • Making the data useful to a broad community, simple to use tools
  • Next steps:
    • Include more GHGs, toxics


Greg FrostEmissions Data Needs, Issues, and Interoperability from the GEIA Perspective (See Frost presentation file)

  • Motivation for improving emissions data
  • Overview of GEIA’s mission and goals
  • Examples of GEIA activities, including ECCAD and CIERA portals
  • GEIA relies heavily on its partnership with AQCoP
  • Scientific and technical needs for improving access and analysis of emissions data
  • Suggest changing name of GEO AQCoP to “Air Quality and Atmospheric Composition CoP”


Uma ShankarUNC/CMAS Efforts (See Shankar presentation file)

  • Support EPA capabilities for regional chemical transport modeling and emissions
  • Perspective and needs for delivering data to EPA and other US regulatory entities
  • Engage groups who provide various data sets for emission modeling (land cover, etc) in AQCoP
    • Data are distributed all over the place, but not connected right now
  • CMAS carries out its efforts through work assignments
  • Modeling platforms from OAQPS and what’s being done in ORD are not well connected
  • Emission Modeling Framework database – Zac Adelman, Uma
    • EPA’s data could be made available through this database
  • Recommends not duplicating efforts, and keeping CMAS involved, especially due to limited resources on US side


Terry KeatingIssues of interest to AQWG/AQCoP

  • Bringing satellite data into AirNow
  • HTAP
    • Example of why we need a GEOSS
    • Next meeting in Geneva, March 18-22, in conjunction with WMO’s 2013 conference
    • Details at http://www.htap.org/
    • Objectives:
      • Establish science, evaluations, analyses to be done in HTAP
      • Status of information infrastructure that’s been created for HTAP
    • Could expand Martin Schultz group’s system built for HTAP Phase 1
    • Modeling resources:
      • Data at Julich and met.no (AeroCom)
      • Ensemble system at JRC
      • Atmospheric Brown Cloud Asia
      • MICS Asia (Tokyo, China) – Asian modeling
      • RSIG – regional modeling exercises
    • Observations:
      • Surface – NILU (EBAS)
      • Aircraft – ATOM (NASA Langley)
      • Satellite – NASA GIOVANNI, Atmos Comp Portal
    • Emissions:
      • GEIA/CIERA – one platform to deliver HTAP emissions
      • ECCAD – another platform to deliver HTAP emissions; in process of modifying to accept information at higher resolution
    • Development of analysis tools that draw on these databases
    • Some work at DataFed, MACC to develop tools: this effort could be expanded
  • North American Commission on Environmental Cooperation Climate Information System
    • CEC involves US, Canada, Mexico
    • CEC had a scoping project about this – decided to focus on emissions
      • identified need for web services approach to delivering these data
    • 3 countries working on online database of GHG and BC emissions
    • Proposals due next week, select contractor by end of January, work done by end of July
    • Tri-national national-level database focused on GHGs, BC, and related emissions
    • Terry will connect contractor to AQCoP
  • AQCoP Governance
    • Wiki discussion initiated
    • Recommend defining co-chairs, secretariat, steering body


GROUP DISCUSSION

1. Name of AQCoP

  • Recommend that we include “Atmospheric Composition” in name
  • Need to let GEO know about this change
  • Alert ESIP?


2. AQ Governance

  • Telecon to formalize the governance - Beginning of February?
  • Need some governance in place before we call another meeting of the CoP
  • In addition to “top-down” structure, need “bottom up” governance
  • Need technical committee to deal with network issues: data catalog, metadata…
  • Perhaps defining these tasks as working groups?
  • High-level umbrella steering group necessary for strategic planning and to secure resources
  • Need improved forum for communication and coordination
  • Suggestion to nominate 2 interim chairs or conveners to help organize meetings and coordinate efforts



Proposed Agenda

January 10 8:30-10:00 GMT-5

  • Introduction to the GEO AQ CoP - Rudy Husar
  • Discussion of CoP Governance and issues raised during the session. To be continued in the second session.

Some of topics to cover might be:

  • what data is provided
  • what technologies are used
  • who is using the data for what
  • what difficulties have you encountered
  • what is needed for future development

January 10 10:30-12:00 GMT-5

This session will cover issues raised in the first session. Some potential topics:

  • Issues faced by modelers in accessing data services.
  • Issues of accessing data services
  • Issues of publishing data services
  • Existing metadata standards and conventions
  • Use cases for the existing services
  • Discussion of technologies for access to large data for various types of post-processing web services. The IRODS group may be presenting at ESIP as well.
  • How to proceed with metadata data developments started in Dublin.
  • Discussion of the next versions of WCS and DAP.
  • Data conventions for distributing point data.
  • Data catalog registration and search access. Does AQCoP need a faceted search i.e. [1]?

The goal of these two sessions will be to gain a better understanding of how the community is working and what work needs to be done to meet the broader scientific priorities.