Difference between revisions of "2008-01-25: ESIP AQ Cluster Telecon"

From Earth Science Information Partners (ESIP)
Line 21: Line 21:
  
 
Rudy Husar
 
Rudy Husar
-Driven by architecture committee. Key is interoperability  
+
-Driven by architecture committee. Key is interoperability and driven by soceital benefit area.
 +
-Focus on scenario development at this stage. followed by call for participation Possible pilot dates and background material is posted on
  
and driven by soceital benefit area.
+
wiki: [[GEOSS_AIP_Pilot_Scenario_Development_Proccess|Scenario Development]]
-Focus on scenario development at this stage. followed by
 
  
call for participation
 
Possible pilot dates and background material is posted on
 
 
wiki: http://
 
  
 
Ernie Hilsenrath
 
Ernie Hilsenrath
Line 36: Line 32:
 
Provide GEO with a space component for GEOSS
 
Provide GEO with a space component for GEOSS
 
4 Pilot Projects (Constellations)
 
4 Pilot Projects (Constellations)
-Land Surface Imaging  
+
*Land Surface Imaging  
-Ocean Topography
+
*Ocean Topography
-Precipitation
+
* Precipitation
-Atmospheric Composition (Aura, ENVISat, and Canadian
+
* Atmospheric Composition
 
+
** stratosphere
mission)
+
** climate (radiative processes, aerosols)
--stratosphere
+
** air quality
--climate (radiative processes, aerosols)
+
1) NO2 from METOP combined with OMI (NOAA Lead), create common algorithm for NO2
--air quality
+
* improve NO2 inventories, imporive aq forecasts
 
 
1) NO2 from METOP combined with OMI (NOAA Lead), create  
 
 
 
common algorithm for NO2
 
-improve NO2 inventories, imporive aq forecasts
 
 
2) Volcanic ash advisories
 
2) Volcanic ash advisories
3) Smoke forecasts from fires
+
3) Smoke forecasts from fires - already demonstrated a smoke forecast based on satellites
already demonstrated a smoke forecast based on satellites
 
 
for GEOSS
 
for GEOSS
-enhance that, deposit data into IDEA
+
* use multiple satellites that are directed to fires and serve data for forecasts (sensor web capability)
-use multiple satellites that are directed to fires and  
+
* how to bring all those pieces together (demonstrate that you can add value if you use more than one satellite)
 
 
serve data for forecasts
 
-how to bring all those pieces together
 
-smoke dispersion model
 
-sensor web capability
 
-have users (but how to bring it all together)
 
-demonstrate that you can add value if you use more than  
 
 
 
one satellite
 
  
 
Rudy:
 
Rudy:
Line 70: Line 51:
  
 
Rich Scheffe:
 
Rich Scheffe:
Can't define ahead of time specific users.
+
Can't define specific users ahead of time.
 
System should evolve organically
 
System should evolve organically
  
 
Karen Moe:
 
Karen Moe:
 
Can help to identify users in other countries
 
Can help to identify users in other countries
If we look at Airnow and IDEA sites that show aerosol and  
+
If we look at Airnow and IDEA sites that show aerosol and smoke trajectories.
 
+
If we start with EPA user, it helps technology team on the back end on how to bring in the technology tools. Usually good to focus on scenario on a narrow scoped problem. Work out how systems interact with a well know set of users and then transport that to other groups/areas
smoke trajectories.
 
If we start with EPA user, it helps technology team on the  
 
 
 
back end on how to bring in the technology tools
 
Usually good to focus on scenario on a narrow scoped  
 
 
 
problem
 
Work out how systems interact with a well know set of  
 
 
 
users and then transport that to other groups/areas
 
  
 
David McCabe:
 
David McCabe:
Scenario is where end user is public, instead of  
+
Scenario is where end user is public (not necessarily scientist). Work off of California and how to deal in other parts of the world where you don't have observations real-time oriented
  
necessarily a scientist
+
Ernie:
work off of California and how to deal in other parts of
+
real-time but still in research mode / Concerns about wiki method for scenario development
  
the world where you don't have observations
+
Frank: Is EPA going to compile/assemble the wiki content to present at Ispra?
real-time oriented
 
  
Ernie:
+
John: Yes. Wiki-away!
real-time but still in research mode
 
  
  
  
 
[[Category:News]][[Category:GEOSS AIP AQ Scenario]]
 
[[Category:News]][[Category:GEOSS AIP AQ Scenario]]

Revision as of 17:26, January 25, 2008

John White

wildfire scenario satellite products for media SEVIR (Central America) --goal is to develop group based data to integrate into satellites

Two GEOSS like activities that seem to be going on:

  • satellite products for media
  • SEVIR (Central America)
  • AirNOW International

present a scenario that includes Global components John knows AirNow - is seeking input from other air

quality organizations to develop this scenario For Ispra meeting: take result of wiki and present to other countries. -so that AQ stays on the table -get input from other countries and make applicable to non-North American countries

Frank Lindsay - Is this EPA?

Rudy Husar -Driven by architecture committee. Key is interoperability and driven by soceital benefit area. -Focus on scenario development at this stage. followed by call for participation Possible pilot dates and background material is posted on

wiki: Scenario Development


Ernie Hilsenrath CEOS Constellation Committee for Earth Observing Systems Provide GEO with a space component for GEOSS 4 Pilot Projects (Constellations)

  • Land Surface Imaging
  • Ocean Topography
  • Precipitation
  • Atmospheric Composition
    • stratosphere
    • climate (radiative processes, aerosols)
    • air quality

1) NO2 from METOP combined with OMI (NOAA Lead), create common algorithm for NO2

  • improve NO2 inventories, imporive aq forecasts

2) Volcanic ash advisories 3) Smoke forecasts from fires - already demonstrated a smoke forecast based on satellites for GEOSS

  • use multiple satellites that are directed to fires and serve data for forecasts (sensor web capability)
  • how to bring all those pieces together (demonstrate that you can add value if you use more than one satellite)

Rudy: How to define user role

Rich Scheffe: Can't define specific users ahead of time. System should evolve organically

Karen Moe: Can help to identify users in other countries If we look at Airnow and IDEA sites that show aerosol and smoke trajectories. If we start with EPA user, it helps technology team on the back end on how to bring in the technology tools. Usually good to focus on scenario on a narrow scoped problem. Work out how systems interact with a well know set of users and then transport that to other groups/areas

David McCabe: Scenario is where end user is public (not necessarily scientist). Work off of California and how to deal in other parts of the world where you don't have observations real-time oriented

Ernie: real-time but still in research mode / Concerns about wiki method for scenario development

Frank: Is EPA going to compile/assemble the wiki content to present at Ispra?

John: Yes. Wiki-away!