2010-03-05: Airnow - Virtual Workshop 1

From Earth Science Information Partners (ESIP)

Standards Implementation Virtual Workshops

March 5, 2010


Data being served

Real-time air quality observations and forecasts.

Types of web services implemented/Formats returned

REST services - in production:
ForecastByZIPCode - json, csv, xml
ObservedByZIPCode - json, csv, xml
ForecastsByIssueDate - csv, xml
ActionDaysByDate - csv, xml
Ozone24HourAQI - csv, xml
PM25Mid24HrAQI - csv, xml
ReportingAreaMaxAverageAQI - csv, xml
SiteMaxAverageAQI - csv, xml


Agency/Site Information
SiteInfoByAQSCode - csv, xml
AgencyGetSites - csv, xml
GetReportingAreas - csv, xml

OGC WCS, REST - on staging server:
Point - csv, aqcsv, kml
TimePoint - csv, aqcsv, kml
Grid - kml, NetCDF (not yet implemented)

Access to web services

Web Service Details:
This page lists web services operated at the AIRNow DMC with sample URLs, example output files, and inputs and outputs:

List of Services

Demonstration Form for WCS Services:
Allows building URLs and running the Web Coverage Services (Point and TimePoint):

WCS Demo Form

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 is required to run the services. Email steve@sonomatech.com for a temporary key.

Issues and questions
  • WCS arguments; Questions about how to handle coverage argument to accommodate parameters/duration/POC.
  • 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;