OceanBrowser viewing service, overview and upgrades Alexander Barth (1) , Charles Troupin (2) ,

1. OceanBrowser viewing service, overview and upgrades Alexander Barth(1), Charles Troupin(2), Aida Alvera Azcárate(1), Jean-Marie Beckers(1) (1) University of Liège (Belgium), (2) IMEDEA (Spain)

2. OceanBrowser • Web-based view of data products • http://gher-diva.phys.ulg.ac.be/emodnet/ Overlay of different data products

3. Web-based viewer • Web-based viewer of climatologies (in NetCDF) • Based on OGS standards (Open Geospatial Consortium): WMS, WFS • Server: • Implemented in Python and running on Apache using mod_wsgi • NetCDF files organized in folders → file structure mapped in a hierarchy of Layers • Adding a new climatology requires just to copy a file in the data folder of the WMS Server • Client: • Based on OpenLayers javascript library • Support for animations in web-browser

4. Vertical sections

5. User interface improvements

6. Output formats • Available output formats for exporting graphics: • PNG (ubiquitous web browser support) • Scalable Vector Graphics (SVG). W3C standard since 1999. Supported by all major browsers except Internet Explorer. • Keyhole Markup Language (KML). Google Earth and NASA World Wind • Encapsulated PostScript (EPS). Preferred format for numerous scientific journals • Animations (mp4 and webm)

7. Available styles • Styles • Interpolated • Filled contours • Simple contours • Colorbar options • Colormap • Range

8. New features • Search for layers • User feedback • Export animation as mp4 or webm

9. OceanBrowser 3D • Experimental 3D version (based on WebGL) • User library EarthGL tinyurl.com/EarthGL • No browser plug-in required

10. Client side rendering • http://gher-diva.phys.ulg.ac.be/OceanBrowser-opendap/ (experimental) • Data access through OPeNDAP (binary)

11. 1d and 2d plots • Axes can be longitude, latitude, depth or time • Possibly to interact directly with the data • Rendering data in the web browser is possible but can be challenge of large data set

12. Upgrades for EMODNET Chemistry • Which observations (CDI) were used in a data product? • Data extraction along the coast line with a list of predetermined sections • Labels indicating geographical features (e.g. towns, borders, river outlets) • User Feedback • Integration with other portals for the physical environment (EMODNET physics or GMES) • Measurement density

13. Work flow forSubmitting gridded products • Info at http://tinyurl.com/OceanBrowser (link to http://modb.oce.ulg.ac.be/mediawiki/index.php/OceanBrowser) • Have a look at the DIVA output before sending them (look for artefacts, impact of outliers, …) • Verify that the netCDF attributes (in particular long_name, unit, title, institution) are accurate. • Upload the file to our server • New products are not automatically visible • Send me an email (a.barth@ulg.ac.be), I will update the server • This call: emphasis on validation!

14. Time series products • Procedure: • Create an index file (see http://tinyurl.com/OceanBrowser for format) • It is suggested to use ODV for manual generation of plots (other tools might be used for batch mode). • The minimum number of points per plot should be 4 or 5. • Data centers will generate plots in EPS format and then convert them in SVG format • Only the SVG files need to be submitted • Scatter points plots should be used without lines to connect plotted measures. • Submitting: • Check all plots and the index file using the validator at http://gher-diva.phys.ulg.ac.be/emodnet-chemistry/html/validator.html. • Send the new products to emodnet-timeseriesprod@googlegroups.com for a general revision about guidelines points • Issues • Problems in converting EPS to SVG. • No interaction with the time series