1 / 22

OPeNDAP infrastructure in European Operational Oceanography T Loubrieu (IFREMER) T Jolibois (CLS)

OPeNDAP infrastructure in European Operational Oceanography T Loubrieu (IFREMER) T Jolibois (CLS). The Mersea project.

imelda-porter
Download Presentation

OPeNDAP infrastructure in European Operational Oceanography T Loubrieu (IFREMER) T Jolibois (CLS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OPeNDAP infrastructure in European Operational Oceanography T Loubrieu (IFREMER) T Jolibois (CLS) opendap dev - meeting, Boulder, Feb 2007

  2. The Mersea project • The objective of MERSEA is to provide an integrated service of global and regional ocean monitoring and forecasting to intermediate users and policy makers in support of safe and efficient offshore activities, environmental management, security, and sustainable use of marine resources. • From a technical point of view it aims at setting up : • From : • 5 ocean forecasting centres • 1 in-situ data centre • 4 remote sensing data centres • Into one european ocean monitoring and forecasting system. opendap dev - meeting, Boulder, Feb 2007

  3. The main overall services • Discovery • Catalogue of products (ISO19115) • Dataset inventory based on THREDDS • Visualize • Images browser (maps, sections, time series…) • Centralized image generator based on OPeNDAP resources • Download • Restricted or freeOPeNDAP servers • Single Sign On system. • Monitor • Check timeliness of datasets delivery thanks to THREDDS inventory opendap dev - meeting, Boulder, Feb 2007

  4. Global architecture (SERVICES USERS) Mersea Portal SSO MIM Discovery Viewing V1 (quicklooks) Viewing V2 (Google Earth) Download User Management (catalogue/inventory) Autres http(s) OpenDap (http/https) WMS (http/https) ftp TEPs (DATA PROVIDERS) opendap dev - meeting, Boulder, Feb 2007

  5. Data access infrastructure opendap dev - meeting, Boulder, Feb 2007

  6. Dataset Inventory : requirements • The Mersea Dataset Inventory lists the references to the actual datasets the project disseminates through http and opendap services. • The inventory access is free. • It is useful for : • Downloading the datasets • Monitoring the availability of the datasets. opendap dev - meeting, Boulder, Feb 2007

  7. Dataset Inventory : TDS usage • The TDS servers in version 3.X are used to make inventory available (THREDDS catalog V1). • Hierarchical organisation : one top THREDDS inventory federates remote THREDDS inventories with ‘catalogRef’ tags. • So the distributed catalogs are directly maintained and updated by the data providers, but the user sees only one catalogue. opendap dev - meeting, Boulder, Feb 2007

  8. Dataset Inventory : Metadata • The set of mandatory metadata has been defined at the project level so that the catalogs are homogeneous. • Then a searching or browsing tool work the same way for all the distributed catalogs. • The mandatory metadata are : • Documentation (link to the ISO19115 Mersea product catalog web page). • GeospatialCoverage • TimeCoverage • Variables (using CF convention). opendap dev - meeting, Boulder, Feb 2007

  9. Dataset Inventory : browsing interface • The development of a browsing web interface is planned. • Technically : it is planned to provide html pages with signed javascript code (AJAX) embedded for accessing the distributed THREDDS XML catalogs. opendap dev - meeting, Boulder, Feb 2007

  10. Dataset inventory : architecture opendap dev - meeting, Boulder, Feb 2007

  11. Integrated Viewing Service • Centralized daily images generator (using FERRET) and accessing datasets through OPeNDAP servers of the project (TDS, server3, dap4cor). • The images can be browsed through a php web interface : • Raster maps • Scattered maps (in-situ measurement positions + values) • Time series • Vertical section are processed. opendap dev - meeting, Boulder, Feb 2007

  12. Integrated viewing service opendap dev - meeting, Boulder, Feb 2007

  13. Integrated download service : functions • OPeNDAP servers (mainly TDS) are used for download. • A Single Sign On (SSO) is needed because : • Some datasets download accesses are restricted. • In order to make users feel as if they were requesting one only European data centre : they must log in only once (even if they are requesting distributed services). • Central Authentification Service (CAS) from Yale University has been chosen for SSO. opendap dev - meeting, Boulder, Feb 2007

  14. Integrated download service : SSO • CAS provides • an authentification server (login/password form or POST request). • A java tomcat filter (CASClient) added to TDS configuration so that any data provider can trust the users authentification (login). • The CASClient filter is going to be patched so that a data provider can easily configure the authorizations/restrictions of access depending on the login of the users and the currently requested URL. opendap dev - meeting, Boulder, Feb 2007

  15. Integrated download service :demonstration client • A lightweight download demonstration tool dedicated to MERSEA was required. • Its specifications are : • Graphically builds opendap request. • Saves opendap responses as netCDf files. • Lightweight and highly portable desktop software. • Manage CAS authentification (need for cookies management and automatic URL redirection -http status 302- management, process the login form). • To Be Properly Define : Integrates a THREDDS metadata searching tool. opendap dev - meeting, Boulder, Feb 2007

  16. Download Scenario (1/5) opendap dev - meeting, Boulder, Feb 2007

  17. Download Scenario (2/5) opendap dev - meeting, Boulder, Feb 2007

  18. Download Scenario (3/5) opendap dev - meeting, Boulder, Feb 2007

  19. Download Scenario (4/5) opendap dev - meeting, Boulder, Feb 2007

  20. Download Scenario (5/5) opendap dev - meeting, Boulder, Feb 2007

  21. Seadatanet (G Maudire, IFREMER) • Seadatanet aims at setting up a pan-european infrastructure for ocean observation data management. • In the version 2 of the system (next year), Seadatanet will use distributed OPeNDAP servers (dapper, TDS…) in order to : • Provide overall and cross checked observation inventory (with double identification, quality assesment information). • Set up an integrated download service. Naiad (JF Piollé, IFREMER/CERSAT) • Processing server : • for satellite swath data retrieval (time and geographical indexation of datasets) • Data-mining. • Uses DAP data model for internal data exchanges. • DAP Request syntax not yet implemented opendap dev - meeting, Boulder, Feb 2007

  22. What we would need ? • Security management with SSO (or identity federation) over distributed OPeNDAP servers. • Easy configuration of the presentation layer for THREDDS, so that the output graphical charter can be adapted to the project it is used for. • Simple semantic thing (upper layer) to really interoperate servers  AIS ? opendap dev - meeting, Boulder, Feb 2007

More Related