The MyOcean View Service: demo Jon Blower, Guy Griffiths, Kevin Yang, Keith Haines (University of Reading, UK) Thomas Loubrieu (Ifremer, France)

MyOcean : GMES Marine Core Service

Analyses, forecasts, satellite products Operational View Service interface Gridded data THREDDS + ncWMS Gridded data THREDDS + ncWMS Gridded data THREDDS + ncWMS

Analyses, forecasts, satellite products Operational View Service interface Gridded data THREDDS + ncWMS Gridded data THREDDS + ncWMS Gridded data THREDDS + ncWMS Point data Oceanotron + WMS Point data Oceanotron + WMS Experimental interface In situ observations

What it gets used for Quicklooks – “Is this the data I want?” Diagnostics – “Is the model behaving itself?” Communication – Simple visualizations, posted to blogs In future, may be an alternative MyOcean catalogue front-end

Important points ncWMS implements some extensions to help scientific visualization – In situ data visualization is particularly challenging to WMS By embedding into THREDDS, “WMS-enabling” the system was reasonably straightforward – THREDDS was familiar technology in the community Data providers sometimes reluctant to spend time on configuration! – Color scale ranges were a particular problem! I’d assumed that reliability would be a big problem, but so far so good – However, third-party background map services are frequently unreliable – But scalability still worries me!

Interoperability challenges Most WMS clients seem to work fine against MyOcean WMS servers – (they can’t of course access the “extensions”) Some clients don’t respect parts of the WMS spec: – TIME and ELEVATION dimensions – Nested Layers – Layer property inheritance – Legend graphics – start/stop/period syntax for time axes Need to harmonize styles to compare with third-party WMS Error handling and reporting in clients is frequently unhelpful

Plans for MyOcean2 Incorporate in situ data into operational View Service Integrate with access control Research into developing intercomparison tools – In-situ observations plus models