Air Quality Information System and GEOSS: India Air Quality and CATHALAC Applications
A Concept Proposal contains necessarily the following information to support the evaluation:
- project team leader’s name and contact information;
- implementing organizations and partners;
- initial description of project concept, including description of the decision or problem needing improvement and the application of Earth observations, data, or model products;
- intended beneficiaries and anticipated benefits and improvements;
- anticipated duration of project; and
- level of experience with Earth observations and type of assistance requested (if any).
These Concept Proposals are intended as a way to minimize initial efforts of project teams so that only projects of interest will prepare Full Proposals. However, the Concept Proposals need to contain sufficient information to enable the review panels’ evaluation and GEO support to the projects.
This section describes the main objectives of the project. It describes the proposed activities, technical approach, and methodology to apply Earth observations to improve the decision making. It describes efforts to transition results and ensure the sustained use of the Earth observations after the completion of the project.
Special focus on projects helping end users apply Earth observations, especially users in developing countries
Air quality data is normally created by a data provider for a particular mandated end user. The format of the data is specific to the use and the metadata that describe the data are focused on a certain application. More and more, the GEOSS idea is growing that ‘a single problem requires many datasets and a single dataset can serve many applications’ (Zhao, 2006). In order to access a dataset providers need to be able to publish and users need to be able to find and bind to a dataset of interest. Standardized data access services allow interoperability in binding to a dataset. However, the first two parts of publishing and finding a data access service are still problematic. In particular: (1) How does one describe the data access service so that it can be discovered by users? (2) Where does one publish their data access service so that it can be found?
Architecture Implementation and Reuse
PUBLISH-FIND-BIND FLOW THROUGH GCI
Publish: Initially it was thought that if one “published” data on the web in any format that was enough for sharing. Then it became obvious that if you wanted to integrate datasets that standard data access formats were useful and publication meant that one exposed a standard data access service available on the web. Through the Pilot it became apparent that just exposing the data access service with a GetCapabilities document doesn’t provide enough metadata for discovery and additional standard metadata needs to be published by the provider or distributor for discovery of the service, so the AQ metadata record and AQ Community Catalog was created.
The services we initially registered for the Pilot are OGC WMS and WCS services and they have a GetCapabilities document which has some metadata information included and can be mapped to ISO 19115 fields (Nativi, 2008). To further improve the use of GetCapabilities documents for metadata creation, we organized our data access services by dataset, so that the general metadata information was dataset specific and the coverages were each dataset parameter. Only a handful of additional fields are needed to create a valid metadata record and these can be hard coded or entered at the time or registration.
Find: In order to find the data access services in the clearinghouse one has to know what to search for. The clearinghouse queryable fields and metadata fields were mapped in a crosswalk to clarify how information was extracted from the harvested metadata records. The key queries we have been interested in so far are for finding our own records, through the parent identifier and searching for services by type and keyword.
The ESRI and USGS clearinghouses expose a search API which has enabled the AQ group to create a more customized search interfaces. One example interface that we have set up is using the USGS API and searching full text in order to find WMS or WCS services (Ref link).