I work with ocean observing systems (OOS's) and wanted to share some hourly refreshed KML files available from the following network link

http://carocoops.org/gearth/Near Real-Time Ocean Observing Data.kml

which contain near real-time data for:

several map imagery overlays collected and shared using WMS
http://carocoops.org/gearth/latest_overlays.kml

platform data and graphs (> 1000 platforms for US)
http://carocoops.org/gearth/latest_placemarks.kmz

The observations currently aggregated to the placemark info are: wind_speed,wind_from_direction,wind_gust,air_temperature,air_pressure,sea_surface_temperature,sea_bottom_temperature,salinity,current_speed,current_to_direction,significant_wave_height,dominant_wave_period,water_level

If you have a collection of platforms and would like to see their measurements included similarly to this data layer, please send me an email at jcothran[at symbol]asg.sc.edu

The perl code demonstrates transforming a series of WMS calls into KML groundoverlay elements and XML data returned from a web service into KML placemark elements.

The code elements are listed under the directory
http://carocoops.org/gearth (see the 'readme.txt' file)

Planning to add more map images and platforms/observations to this as things progress. Sorry if the server response is slow.

Questions/feedback welcome,
Cheers
Jeremy Cothran
http://carocoops.org
http://seacoos.org
http://openioos.org

Thanks for sharing!

There is something wrong with the unit of pressure,
it shows 1.01mb after 3pm, March 4. It should be around 1000 mb, right?

Northsea

1000 mb instead of 1.0 millibars is right. Bug fixed.

Meant to also document that if you're working with WMS then the file
http://carocoops.org/gearth/wms.xml

gives a listing of the WMS references used.

Thanks
Jeremy

See also

ObsKML
ObsKML bulletin post

XeniaPackage

OOSTechKML

Added the following network link which will update the point data hourly and the coverage data daily

http://carocoops.org/gearth/Near Real-Time Ocean Observing Data.kml

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

Hello Jeremy,

For info, we have included in our marine collection of GE mashups, a kmz file related to :
- weather buoys and stations from NDBC website

Please have a look on :
Marine GE mashups

--
Peio Elissalde
Magic Instinct Software

Peio,

Just looked at your buoy collection and it's really slick. I hope you noticed the upcoming changes to the data source at the NDBC.

See Xenia Package

I've been working to develop a standard relational table reference schema for observation system aggregation and product development. Be glad to compare notes with others doing relational schema development as to what works. I'm trying to keep the schema more modular so folks can add or take away components depending on the end products they want to support.

With this kind of development, the table schema represents the format and the data dictionaries are support/lookup tables.

If the database and derived web services/xml records/products become more packaged, then hopefully the job shifts more towards getting messy data into a 'standard' database that provides a minimum set of agreed community web services and records. Redundancy in data sources can provide a failover capacity. Data could be replicated via mirroring for copied implementations or web services where implementations are different.

Jeremy

see ObsCatalog

I've put together a google based visualization tool for a basic observation catalog visualization via kml/google earth. Folks can either download and modify the base scripts or use it as an http service which when supplied a basic CSV file and observation types list produces a KML file.

Might be useful for encouraging/engaging other observation systems to list their assets via KML. We are struggling as a community to provide some consistent metadata(xml schemas, controlled vocabularies/codelists, web services) across our organizations and I'm hoping KML and it's easy visualizations can help provide some incentive(a carrot) towards this.

Short description from another post below.

=======

If you can provide an input catalog csv file via http similar to the following sample file:
catalog_in.csv

and use or supply your own observation types list similar to the following:
obs_types.txt

You can get a google earth kml file which should view similar to the attached sample screenshot by supplying those arguments to the following link similarly:

http://carocoops.org/gearth/catalog/csv2...l/obs_types.txt