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

From Earth Science Information Partners (ESIP)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
==John White==
+
'''Stefan Falke:''' <math>
wildfire scenario
+
 
satellite products for media
+
'''John White:''' wildfire scenario satellite products for media SEVIR (Central America) goal is to develop group based data to integrate into satellites
SEVIR (Central America)
 
--goal is to develop group based data to integrate into satellites
 
  
 
Two GEOSS like activities that seem to be going on:
 
Two GEOSS like activities that seem to be going on:
Line 9: Line 7:
 
* SEVIR (Central America)
 
* SEVIR (Central America)
 
* AirNOW International  
 
* 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
 +
and to get input from other countries and make applicable to non-North American countries.
  
present a scenario that includes Global components
+
'''Frank Lindsay:''' - What are EPA's goals for the Ispra Meeting/Scenario Development?  
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
+
'''Rudy Husar:'''  pointed out that the Pilot serves both the Architecture & Data and the User Interface Committees of GEOSS. On the  [[GEOSS_AIP_Pilot_Scenario_Development_Proccess|Scenario Development wiki page]] he outlined the likely steps in the AI Pilot process:
Possible pilot dates and background material is posted on
+
# Feb 2008: Scenario, a short narrative description of functionality from end user point of view.
 +
# Jun 2008?: Call for Participation (CFP): To ientify, GEOSS components, services relevant to the Scenario
 +
# Oct 2008?: Responses to CFP - Begin scenario implementaion developemt using given components
 +
# .. ..009?: Pilot operational?
  
wiki: http://
 
  
 
Ernie Hilsenrath
 
Ernie Hilsenrath
Line 36: Line 24:
 
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
+
* [http://wiki.esipfed.org/images/0/0d/ESIP_Hilsenrath.pdf 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
+
'''Karen Moe:''' Can help to identify users in other countries
-how to bring all those pieces together
+
If we look at Airnow and IDEA sites that show aerosol and smoke trajectories.
-smoke dispersion model
+
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
-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
+
'''Rich Scheffe:''' Can't define specific users needs ahead of time. The information system should be adoptable and and evolve organically.
  
Rudy:
+
'''Rudy:''' So evidently, for some AQ smoke situations the scenario need well defined with specific end-to-end data flow. In other cases it is important the the data flow can be configured as needed. We need the make sure that the AIP Scenario narrative allows for both kinds of implementations.  </math>   
How to define user role
 
  
Rich Scheffe:
 
Can't define ahead of time specific users.
 
System should evolve organically
 
  
Karen Moe:
+
'''David McCabe:'''
Can help to identify users in other countries
+
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
If we look at Airnow and IDEA sites that show aerosol and
 
  
smoke trajectories.
+
Ernie:
If we start with EPA user, it helps technology team on the
+
real-time but still in research mode / Concerns about wiki method for scenario development
 
 
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
+
Frank: Is EPA going to compile/assemble the wiki content to present at Ispra?
  
David McCabe:
+
John: Yes. Wiki-away!
Scenario is where end user is public, instead of
 
 
 
necessarily a 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
 
  
  
  
 
[[Category:News]][[Category:GEOSS AIP AQ Scenario]]
 
[[Category:News]][[Category:GEOSS AIP AQ Scenario]]

Latest revision as of 18:10, January 25, 2008

Stefan Falke: <math>

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 and to get input from other countries and make applicable to non-North American countries.

Frank Lindsay: - What are EPA's goals for the Ispra Meeting/Scenario Development?

Rudy Husar: pointed out that the Pilot serves both the Architecture & Data and the User Interface Committees of GEOSS. On the Scenario Development wiki page he outlined the likely steps in the AI Pilot process:

  1. Feb 2008: Scenario, a short narrative description of functionality from end user point of view.
  2. Jun 2008?: Call for Participation (CFP): To ientify, GEOSS components, services relevant to the Scenario
  3. Oct 2008?: Responses to CFP - Begin scenario implementaion developemt using given components
  4. .. ..009?: Pilot operational?


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)

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

Rich Scheffe: Can't define specific users needs ahead of time. The information system should be adoptable and and evolve organically.

Rudy: So evidently, for some AQ smoke situations the scenario need well defined with specific end-to-end data flow. In other cases it is important the the data flow can be configured as needed. We need the make sure that the AIP Scenario narrative allows for both kinds of implementations. </math>


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!