Difference between revisions of "Standards Implementation Virtual Workshops"

From Earth Science Information Partners (ESIP)
Line 1: Line 1:
 +
[[Air Quality Work Group| Back to Air Quality Work Group]]
 +
 
A series of "[[Virtual Meetings|virtual workshops]]" are being organized in order to help the air quality community establish best practices and conventions for implementing data format and exchange standards (e.g., netCDF-CF and OGC WCS)in order to advance the level of interoperability among air quality information systems and projects.  
 
A series of "[[Virtual Meetings|virtual workshops]]" are being organized in order to help the air quality community establish best practices and conventions for implementing data format and exchange standards (e.g., netCDF-CF and OGC WCS)in order to advance the level of interoperability among air quality information systems and projects.  
  

Revision as of 11:08, February 26, 2010

Back to Air Quality Work Group

A series of "virtual workshops" are being organized in order to help the air quality community establish best practices and conventions for implementing data format and exchange standards (e.g., netCDF-CF and OGC WCS)in order to advance the level of interoperability among air quality information systems and projects.

The objectives of the virtual workshops are to

  • publish and expose existing services from multiple providers,
  • compare standards implementations, explore differences, address challenges and reconcile differences in implementations
  • agree on 'AQ Community' conventions and define guidance that harmonize the implementation of standards-based services

The concept of the virtual workshops is to foster interaction among the air quality community through semi-formal workshops that take advantage of remote meeting technologies and allow productive exchanges among the participants while residing in distributed physical locations.

Interoperability of Data Systems

Virtual Workshop 1

March 5, 2010

AIRNow

Data being served
Data formats used
Types of web services implemented
  • REST services: xml, csv, kml, json, netCDF
  • OGC WCS for point data, returns AQI surrogate data
  • OGC WCS for point, time-point, and grid


Access to web services

include access points such as GetCapabilities or example data access requests (e.g., GetCoverage)

Issues and questions
  • web services require authentication (using API key)
  • payload options and formats (netCDF is evolving)
  • need to make things uniform
AIP Description of Services
  • Relationship of the components and services to the [architecture of your project?]
  • Does your service support of open standards? Is there multiple-use potential outside of a single project?
  • Performance capability of the components including typical traffic (hits per hour) that the components support, and
  • Availability of the components for participation in the Pilot activities including persistence.
  • Identify how your components and services will be used in the GEOSS Common Infrastructure (GCI). If you will provide client application capabilities, identify how this may also exploit the GCI in the proposed project. Comments to support the refinement of the AIP Architecture are encouraged,
AIP Description of Projects Involved with (How do the services fit into existing projects already?)
  • Describe participation and/or membership of the responding organization in Air Quality activities;