Difference between revisions of "Air Quality Break-out, ESIP 2010 Summer Meeting"

From Earth Science Information Partners (ESIP)
Line 5: Line 5:
 
''WebEx and dial-in will be available for remote participation. Details will be posted here prior to the meeting.''
 
''WebEx and dial-in will be available for remote participation. Details will be posted here prior to the meeting.''
  
===July 21, Wednesday ===
+
=July 21, Wednesday =
 
'''1:15-2:45'''
 
'''1:15-2:45'''
  
Line 15: Line 15:
  
  
* 5-minute Networking updates from ongoing projects
+
=== 5-minute Networking Projects Updates, 5-min each ===
** GEOSS AIP-3
+
==== GEOSS AIP-3 ====
** CEOS AC Portal
+
==== CEOS AC Portal====
** Giovanni
+
==== Giovanni====
** RSIG
+
==== RSIG====
** AIRNow
+
==== AIRNow====
** HTAP Network
+
==== HTAP Network====
** DataFed
+
==== DataFed====
  
 
** others (please add to this list)
 
** others (please add to this list)

Revision as of 09:07, July 19, 2010

back to full ESIP Summer Meeting agenda | Air Quality Main Page

The Air Quality Workgroup will be meeting on Wednesday and Thursday during the ESIP Summer Meeting.

WebEx and dial-in will be available for remote participation. Details will be posted here prior to the meeting.

July 21, Wednesday

1:15-2:45

  • Welcome, Introduction and Overview (5-minutes)


  • 20-minute presentations from new projects
    • CyAir - Cyberinfrastructure for Air Quality Management


5-minute Networking Projects Updates, 5-min each

GEOSS AIP-3

CEOS AC Portal

Giovanni

RSIG

AIRNow

HTAP Network

DataFed

    • others (please add to this list)
  • what is the state of the network connection Connectivity Matrix
    • Highlight nodes that are red that are high priority and aren't connected (outcome - critical systems need to be networked)


  • Community Topics (5 min each)
    • GEO AQ CoP
      • AQ Earth Observation Requirements
      • User Requirements Registry Update
    • AQ GEOSS Community Infrastructure


    • Using ISO metadata to catalog and find resources


(scheduled break from 2:45-3:15)


3:15-4:45


Discussion Focus Areas (20min each)

  • Institutional and human factors challenges and opportunities in interoperability
  • Interoperability successes among projects and use/planned use of GEOSS AQ Community Infrastructure
    • Lessons learned and guidance that can be formulated for others to use in their implementations
    • Challenges and new approaches to implementing interoperability
    • Define next steps for interoperability testing among projects
    • update interoperability matrix
  • Virtual AQ Interoperability Standards Implementation Workshops: making them work for you


  • CyAir Reflections: Given discussion above: What does this mean for CyAir?

July 22, Thursday

11:00-12:00

  • Outline next Interoperability Standards Implementation 'Virtual Workshops'
  • Define goals, scope and logistics for face-to-face/virtual AQ Interoperability Standards Implementation Workshop
  • Plans for GEO-VI Plenary Air Quality 'Showcase'



Ideas and Suggestions for Summer Meeting

  • Entire should be virtual - expect that more than half of participants might be remote.
  • Potential collaboration with the Tech workshops from Tuesday
  • Describe HTAP Network, ACP, other AQ projects by the way that they leverage AQ Community Infrastructure


  1. identifying and begin registering the emerging air quality data-as-services from the various projects e.g. (HTAP network; Atmp Comp Network, CyAir)
  2. using the ISO metadata for cataloging, discovery and finding the shared data resources
  3. agree on a few practical use cases for demonstrating interoperability and networking

We could also begin work on the

  • convention for metadata for understanding the observations (surface, satellite, model, emission...)
  • distributing the shared tools and methods (server, client, registration...)

A particular topic that would help GEOSS is a participatory discussion/feedback on the User Requirements Registry for air quality. A possible way to approach this is to ask the project representatives to identify their respective user requirements. I can provide more later..