Just wanted to post some additional technical links for others who might be interested.

Adding more of the same datatypes from other platforms is fairly straightforward if others are interested in adding more data points or reproducing this type of system in whole, send me an email at jcothran[at]asg.sc.edu.

We've done a fair amount of open source documented development work setting up aggregations of near real-time data flows ( http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/SEACOOSCookbook2 ) for in-situ and model output using a netCDF convention. I would like to create redundant type server setup and data feeds perhaps packaging the software to something like knoppix ( http://en.wikipedia.org/wiki/Knoppix ) that would allow other developers to try/demo the software before installing to a server. A very basic system and software is discussed here ( http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/MultiObsSchema ) . I'm also working with another group to try and better define XML schemas and some basic common web services ( http://twiki.sura.org/twiki/bin/view/Main/OosTechServiceDefinition ) which seems to be moving towards adoption of the OpenGeospatial Consortium Sensor Web Enablement ( OGC SWE ) schemas and specifications ( http://www.opengeospatial.org/functional/?page=swe ).

Would be interested in sharing development ideas, code with any developers or teams that have more time/ability to refine/package these system components for free and open source use.

I'm sure google gets ideas about what it could or should do all the time. Here's another one - why not adopt/extend the xml standards at OGC for Sensor Web Enablement http://www.opengeospatial.org/functional/?page=swe and have a google instrumentation and observation data service registry/catalog that organized this data as viewable in google earth using the OGC xml schema specs and services like SensorML and WMS?

Somebody's going to develop this at some point, why not google?

Jeremy