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

From Earth Science Information Partners (ESIP)
Line 34: Line 34:
  
 
== GEO-ESIP Community Activities  - 5 min each max? ==  
 
== GEO-ESIP Community Activities  - 5 min each max? ==  
[[Image:2010-07_AQInfrastructure.ppt|AQ Infrastructure ppt]] | [http://capita.wustl.edu/dataSpaceMetadata_trial/2010-07AQInfrastructure_files/slide0003.htm Clickable AQ Infrastructure]
 
 
=== GEO AQ Community of Practice ===
 
=== GEO AQ Community of Practice ===
 
* [http://geo-aq-cop.org/ GEO AQ CoP Collaborative Website]
 
* [http://geo-aq-cop.org/ GEO AQ CoP Collaborative Website]
Line 41: Line 40:
  
 
=== AQ GEOSS Community Infrastructure ===
 
=== AQ GEOSS Community Infrastructure ===
 +
[[Image:2010-07_AQInfrastructure.ppt|AQ Infrastructure ppt]] | [http://capita.wustl.edu/dataSpaceMetadata_trial/2010-07AQInfrastructure_files/slide0003.htm Clickable AQ Infrastructure]
 
==== AQ Earth Observation Requirements; User Requirements Registry ====
 
==== AQ Earth Observation Requirements; User Requirements Registry ====
 
* [http://datafedwiki.wustl.edu/index.php/2010-05-28:_GEO_URR_AQ_Framework GEO URR AQ Framework]
 
* [http://datafedwiki.wustl.edu/index.php/2010-05-28:_GEO_URR_AQ_Framework GEO URR AQ Framework]
 
* [http://www.earthobservations.org/documents/committees/uic/200909_12thUIC/17%20GEOSS%20User%20Requirements%20Registry.pdf GEO URR Brochure]
 
* [http://www.earthobservations.org/documents/committees/uic/200909_12thUIC/17%20GEOSS%20User%20Requirements%20Registry.pdf GEO URR Brochure]
 +
 +
==== WCS/WMS/WFS for Accessing data ====
 +
* [http://wiki.esipfed.org/index.php/WMS_GetCapabilities WMS Documentation]
 +
* [http://wiki.esipfed.org/index.php/WCS_Access_to_netCDF_Files WCS Access to netCDF files]
  
 
==== ISO metadata for finding data  ====
 
==== ISO metadata for finding data  ====
Line 49: Line 53:
 
* [http://geo-aq-cop.org/isodiscussion ISO 19115/19115 AQ Community Record Documentation]
 
* [http://geo-aq-cop.org/isodiscussion ISO 19115/19115 AQ Community Record Documentation]
  
==== WCS/WMS/WFS for Accessing data ====
+
==== GEOSS Architecture Implementation Pilot AIP-3 ====
* [http://wiki.esipfed.org/index.php/WMS_GetCapabilities WMS Documentation]
 
* [http://wiki.esipfed.org/index.php/WCS_Access_to_netCDF_Files WCS Access to netCDF files]
 
 
 
=== GEOSS Architecture Implementation Pilot AIP-3 ===
 
 
* [http://sites.aip3.ogcnetwork.net/home/home/air-quality-health AIP-3 AQ Collaboration Workspace]
 
* [http://sites.aip3.ogcnetwork.net/home/home/air-quality-health AIP-3 AQ Collaboration Workspace]
 
'''(scheduled break from 2:45-3:15)'''
 
'''(scheduled break from 2:45-3:15)'''

Revision as of 12:00, July 20, 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)


New Projects 20-minutes

CyAir - Cyberinfrastructure for Air Quality Management

Funded Networking Projects Updates, 5-min each

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)

GEO-ESIP Community Activities - 5 min each max?

GEO AQ Community of Practice

AQ GEOSS Community Infrastructure

File:2010-07 AQInfrastructure.ppt | Clickable AQ Infrastructure

AQ Earth Observation Requirements; User Requirements Registry

WCS/WMS/WFS for Accessing data

ISO metadata for finding data

GEOSS Architecture Implementation Pilot AIP-3

(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
    • Listing of current connected datasets (with monitoring of service performance)
    • Example of health performance on AQ uFIND - shows status of server (how many layers returned) and status of indiv. layer
  • 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..