Difference between revisions of "2006-07-30 GEOSS User V - AQ Data Systems"
From Earth Science Information Partners (ESIP)
Line 1: | Line 1: | ||
− | + | <center><font size=5>Architectures and Technologies for Agile, User-Oriented Air Quality Data Systems</font ></center> | |
− | <center> | + | <center>A white paper prepared by an ad hoc virtual workgroup using open collaborative tchnologies</center> |
+ | <center>Possible presentation venues: GEOSS User Workshop, Jul 2006, Denver; Fall AGU, Dec 2006, San Francisco; HTAP Workshop, Jan 2007, Geneva</center>. | ||
− | + | ===[[Current and Near Future AQ Information System of Systems]]=== | |
− | |||
− | === | ||
====..Current Situation==== | ====..Current Situation==== | ||
: Few users; limited, sporadic data/model; poor integration; Dedicated 'Stove Pipe' Systems -> Stiff and limited decision support | : Few users; limited, sporadic data/model; poor integration; Dedicated 'Stove Pipe' Systems -> Stiff and limited decision support | ||
Line 12: | Line 11: | ||
: Community assessment of AQ IT; User feedback to GEOSS Architecture; Aid to agency planners | : Community assessment of AQ IT; User feedback to GEOSS Architecture; Aid to agency planners | ||
− | ===AQ Data System | + | ===[[AQ Data System Architectures]]=== |
− | ====..User-Driven Design==== | + | ====..User-Driven: User Drives Design==== |
− | ====..Distributed over | + | ====..Distributed: Structure over Dimensions==== |
− | ====..Loosely Couppled | + | ====..Loosely Couppled: Software Components, System of Systems, Architcture of Participation==== |
− | |||
− | ===Information Technologies=== | + | ===[[Information Technologies]]=== |
− | ====..Software Components: Web Services==== | + | ====..Software Components: Data as Service, Web Services==== |
− | ====..Interoperability Technologies | + | ====..Interoperability Technologies: Standards/Conventions, Wrappers and Adopters==== |
− | + | ====..Web 2.0 Technologies: Searching, Tagging==== | |
− | ====..Web 2.0 Technologies==== | ||
===Challenges=== | ===Challenges=== | ||
Line 34: | Line 31: | ||
: Grasping and harnessing Web 2.0 | : Grasping and harnessing Web 2.0 | ||
− | ===Prototype Application Examples=== | + | ===[[Prototype Agile AQ Application Examples]]=== |
====..FASTNET==== | ====..FASTNET==== | ||
: Fast Aersosol Sensing | : Fast Aersosol Sensing |
Revision as of 05:09, June 23, 2006
.
Current and Near Future AQ Information System of Systems
..Current Situation
- Few users; limited, sporadic data/model; poor integration; Dedicated 'Stove Pipe' Systems -> Stiff and limited decision support
..Near Furure
- Diverse users, More sensory/model data-GEOSS; Extensive integration and 'mashing'-Web 2.0; Network effect ->Responsive decisin support
..Paper purpose and outline
- Community assessment of AQ IT; User feedback to GEOSS Architecture; Aid to agency planners
AQ Data System Architectures
..User-Driven: User Drives Design
..Distributed: Structure over Dimensions
..Loosely Couppled: Software Components, System of Systems, Architcture of Participation
Information Technologies
..Software Components: Data as Service, Web Services
..Interoperability Technologies: Standards/Conventions, Wrappers and Adopters
..Web 2.0 Technologies: Searching, Tagging
Challenges
..Human Factors
- The 4 C's: Communication, Cooperation, Coordination, Coopetition
- Attracting user participation
..Architecture
- Maximize the 'Network Effect'....
..Technologies
- Grasping and harnessing Web 2.0
Prototype Agile AQ Application Examples
..FASTNET
- Fast Aersosol Sensing
..AQ Event Analysis
- Exceptional Events Analysi for Regulatory Decision Making
..CATT
- Combined Aerosol and Trajectory Tool