Difference between revisions of "Standards Implementation Virtual Workshops"

From Earth Science Information Partners (ESIP)
Line 46: Line 46:
 
=====Types of web services implemented/Formats returned=====
 
=====Types of web services implemented/Formats returned=====
  
* REST services: xml, csv, kml, json, netCDF (future)
+
'''REST services - in production:'''
* OGC WCS for point, time-point, and grid (future)
+
'''Data/Forecasts'''
 +
ForecastByZIPCode - json, csv, xml
 +
ObservedByZIPCode - json, csv, xml
 +
ForecastsByIssueDate - csv, xml
 +
ActionDaysByDate - csv, xml
 +
Ozone24HourAQI - csv, xml
 +
PM25Mid24HrAQI - csv, xml
 +
ReportingAreaMaxAverageAQI - csv, xml
 +
SiteMaxAverageAQI 
 +
'''Agency/Site Information'''
 +
SiteInfoByAQSCode - csv, xml
 +
AgencyGetSites - csv, xml
 +
GetReportingAreas - csv, xml
 +
 
 +
'''OGC WCS, REST format - on staging server:'''
 +
Point - csv, aqcsv, kml
 +
TimePoint - csv, aqcsv, kml
 +
Future: Grid - kml, NetCDF
  
 
=====Access to web services=====
 
=====Access to web services=====

Revision as of 15:54, March 3, 2010

Main ESIP page >> Main AQ Work Group page

Welcome to the Standards Implementation Virtual Workshops Workspace


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.



What's New


See all news

Background on Interoperability of Data Systems

Virtual Workshop 1

March 5, 2010

AIRNow

Data being served

Real-time air quality observations and forecasts.

Types of web services implemented/Formats returned

REST services - in production: Data/Forecasts ForecastByZIPCode - json, csv, xml ObservedByZIPCode - json, csv, xml ForecastsByIssueDate - csv, xml ActionDaysByDate - csv, xml Ozone24HourAQI - csv, xml PM25Mid24HrAQI - csv, xml ReportingAreaMaxAverageAQI - csv, xml SiteMaxAverageAQI Agency/Site Information SiteInfoByAQSCode - csv, xml AgencyGetSites - csv, xml GetReportingAreas - csv, xml

OGC WCS, REST format - on staging server: Point - csv, aqcsv, kml TimePoint - csv, aqcsv, kml Future: Grid - kml, NetCDF

Access to web services

List of Web Services: This page lists web services operated at the AIRNow DMC. The page includes sample URL strings, example output files, and describes all inputs and outputs: http://staging.sonomatech.com/airnow_ws/

Demonstration Form for WCS: Allows building URLs and running the Web Coverage Services (Point and TimePoint): http://staging.sonomatech.com/airnowi/wcs_demowebpage/wcs_point.aspx

The demo page includes documentation of inputs and outputs, and inlcudes links to GetCapabilities and DescribeCoverage documents (drafts). The URL string is visually assembled when form selections are made. This form will be used in the virtual workshop.

These WCS services are currently operating on staging servers. An API Key from the staged AIRNow database will required to run the services. Email steve@sonomatech.com for a temporary key.

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;





Questions, comments, feedback - leave a comment on the discussion page.

People This is an open project and if you are interested in contributing to the technical . Register on this ESIP wiki to contribute content, discussions, or modify the page and click the "watch" tab.


Standards_Implementation_Virtual_Workshops