Difference between revisions of "GEOSS and the AirNOW Data System"
From Earth Science Information Partners (ESIP)
Line 9: | Line 9: | ||
[[Image:StovepipeArch.png|500px]] | [[Image:StovepipeArch.png|500px]] | ||
[[Image:FederatedArch.png|500px]] | [[Image:FederatedArch.png|500px]] | ||
+ | |||
+ | The implication and the impediments to the implementation of the AirNOW data system transition are two-fold: | ||
+ | * The data provided by the AirNOW data system needs to be accessible through standard interfaces, such as |
Revision as of 16:20, February 28, 2008
What links here: GEOSS and the AirNOW Data System
AirNow in an Network
Traditional air quality information systems provide end-to-end solutions through dedicated ‘Stovepipe’ processing streams However, many formerly closed data systems are now opening up and they share their data – through DataFed or other mediators In a federated approach data are homogenized and augmented with services and tools streams… The federated resources in turn can be fed back into individual project processing streams
The transition from the stovepipe to the networked, service oriented architecture can be gradual and non-disruptive.
The implication and the impediments to the implementation of the AirNOW data system transition are two-fold:
- The data provided by the AirNOW data system needs to be accessible through standard interfaces, such as