Note - this is an out-of-date wiki page, the latest Xenia features are listed at VMwareProducts

• Google Earth and Maps
• observation quality control and notification
• data availability and metrics
• convert from ObsKML to other formats (netcdf,CSV,shapefile)
• time-series graphs
• vector graphs (ADCP)
• html table styling
• MicroWFS
• DIF SOS

Xenia uses ObsKML as a default XML import/export format. Some of the following products are derived purely via ObsKML which means that they are equally applicable to scripts which can supply ObsKML whether from a Xenia instance or otherwise.

Some of the following scripts utilize a combination of ObsKML and additional XML lookup files.

Some of the following scripts run against the Xenia db directly.

Google Earth and Maps

see http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/ObsKMLGenerate#Merging_and_styling_several_ObsK

http://code.google.com/p/xenia/source/browse/trunk/obskml/products/gearth

Latest placemarks

http://carocoops.org/gearth/latest_placemarks.kmz

Note the above KML/KMZ styling has the following features:

• layer folders toggle on/off by operator(visualize individual operator/data provider status)
• platform styling highlights non-reporting platforms as shaded red - platform link information still available. Don't want platforms or observation to disappear from the map if they are intermittently reporting.
• by 'operator' layer listing all the latest observations available at each platform
• by 'observation' layer listing observations of the same obs_type.uom_type for all associated platforms
• acts as a observation type 'inventory'
• optional style.xml to provide basic default blue/green/red color scale for obs_type.uom_type measurement value range limit
• naming/reference hierarchy
• platform = operator.platform<.package> where operator and platform names are controlled vocabularies and package name is optional unique string
• sensor = sensor_id (an integer id) = obs_type.uom_type.s_order s_order is an integer counter to help distinguish between redundant or profiling sensor arrays of the same obs_type.uom_type
• a feature which I would like to implement is use of regions to help break the entire layer into more manageable data blocks/levels of detail for better download/display concerns similar in concept to the Google Maps implementation at http://tidesandcurrents.noaa.gov/gmap3 or using some automated solution possibly like http://www.mapeed.com

Note that the time window control can be manipulated (moved, increased, decreased) - see the following documentation

http://earth.google.com/userguide/v4/ug_gps.html#timeline

ObsKML can be merged and revisualized shown in the following image

observation quality control and notification

see http://trac.secoora.org/datamgmt/wiki/RangeTests

data availability and metrics

http://trac.secoora.org/datamgmt/wiki/PercentageUptime

convert from ObsKML to other formats (netcdf,CSV,shapefile)

see http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/ObsKMLGenerate#Convert_from_ObsKML_to_other_for

time-series graphs

TBD

http://code.google.com/p/xenia/source/browse/trunk/sqlite/time_series

http://code.google.com/p/xenia/source/browse/trunk/postgresql/time_series

http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/XeniaSampleCase

http://carocoops.org/xenia

http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/CarolinasCoastLite#a_description_of_the_graph_xml_f

The time-series graphs shown at http://weather.gov/carolinascoast are generated by the Xenia related gnuplot scripts.

http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/CarolinasCoastSetup

vector graphs (ADCP)

see ADCPProfilerNotes

html table styling

TBD

http://nautilus.baruch.sc.edu/twiki_dmcc/bin/view/Main/CarolinasCoastNotesAjax

http://code.google.com/p/xenia/source/browse/trunk/obskml/products/html_tables

MicroWFS

see http://code.google.com/p/xenia/wiki/XeniaPackageSqlite#MicroWFS

DIF SOS

see http://code.google.com/p/xenia/wiki/XeniaSOS