Difference between revisions of "Air Quality Implementation Sandbox"
From Earth Science Information Partners (ESIP)
m ([BOT] Misspelling correction: | occurance -> occurrence) |
|||
(7 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
* Detailed Scenario | * Detailed Scenario | ||
+ | ** see use cases and scenarios on [http://wiki.esipfed.org/index.php/Technology-Application_Use_Cases air quality cluster page] | ||
* Available Services | * Available Services | ||
+ | ** [http://datafedwiki.wustl.edu/index.php/Compact_Catalog_-_Alphabetical Data access services (WCS)] from DataFed | ||
+ | ** [http://niceguy.wustl.edu:8080/c/portal/layout?p_l_id=PUB.1.2&p_p_id=resources&p_p_action=0&p_p_state=maximized&p_p_mode=view&p_p_col_id=&p_p_col_pos=0&p_p_col_count=0&_resources_struts_action=%2Fext%2Fresources%2Fopen_entry&_resources_entryId=216 Emissions WCS services] from NEISGEI | ||
+ | ** [http://datafedwiki.wustl.edu/index.php/2007-05-17:_DataFed_Services_Table Processing services] from DataFed | ||
+ | *** Binary Grid Operator | ||
+ | *** Point-to-Grid Operator | ||
+ | |||
+ | * Web Applications | ||
+ | ** [http://niceguy.wustl.edu/NEISGEI/EmisComp/ Emissions Comparison Tool] | ||
* Wish List | * Wish List | ||
+ | ** Spatial-temporal processing service suite (something like GRASS for SOA - GMU has SOAP interfaces to GRASS, maybe we can try those?) | ||
+ | *** '''Example:''' ''Extract grid values at a set of point locations.'' GRASS function is [http://grass.itc.it/grass63/manuals/html63_user/v.what.rast.html v.what.raster]. GMU's SOAP interface is described on [http://geobrain.laits.gmu.edu:8099/webservices/grass/Grass_Webservices.html their site] and as part of a [http://gsa.confex.com/gsa/2007GE/finalprogram/abstract_122248.htm conference abstract]. Such a web service has multiple uses for air quality applications including: | ||
+ | ****Comparing fire occurrence locations derived from surface or satellite data with thermal imagery from another satellite | ||
+ | ****Extracting land cover type for fire locations | ||
+ | ****Comparing measured surface particulate matter concentrations with estimated concentrations from air pollution or smoke forecast models | ||
+ | ****Comparing measured surface air pollutant concentrations with satellite derived indicators (e.g., AOT, NO2 column) | ||
+ | ** Spatial reprojection service for data arrays (reprojections services I've found operate only on GeoTiffs) |
Latest revision as of 05:26, December 20, 2007
Use Case 1: SolutionsUseCase_AirQuality-Atmosphere_Smoke_1a
- Detailed Scenario
- see use cases and scenarios on air quality cluster page
- Available Services
- Data access services (WCS) from DataFed
- Emissions WCS services from NEISGEI
- Processing services from DataFed
- Binary Grid Operator
- Point-to-Grid Operator
- Web Applications
- Wish List
- Spatial-temporal processing service suite (something like GRASS for SOA - GMU has SOAP interfaces to GRASS, maybe we can try those?)
- Example: Extract grid values at a set of point locations. GRASS function is v.what.raster. GMU's SOAP interface is described on their site and as part of a conference abstract. Such a web service has multiple uses for air quality applications including:
- Comparing fire occurrence locations derived from surface or satellite data with thermal imagery from another satellite
- Extracting land cover type for fire locations
- Comparing measured surface particulate matter concentrations with estimated concentrations from air pollution or smoke forecast models
- Comparing measured surface air pollutant concentrations with satellite derived indicators (e.g., AOT, NO2 column)
- Example: Extract grid values at a set of point locations. GRASS function is v.what.raster. GMU's SOAP interface is described on their site and as part of a conference abstract. Such a web service has multiple uses for air quality applications including:
- Spatial reprojection service for data arrays (reprojections services I've found operate only on GeoTiffs)
- Spatial-temporal processing service suite (something like GRASS for SOA - GMU has SOAP interfaces to GRASS, maybe we can try those?)