1 / 4

OPeNDAP-based models for ALTICORE

OPeNDAP-based models for ALTICORE. SLA,SWH NetCDF. Model 1: precomputation of corrected params. Raw data NetCDF. corr1. corr2. corr3. 1. SLAs (+ SWH, wind speed) are precomputed offline from raw data + corrections and stored. Preprocessor.

yves
Download Presentation

OPeNDAP-based models for ALTICORE

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-based models for ALTICORE

  2. SLA,SWH NetCDF Model 1: precomputation of corrected params Raw data NetCDF corr1 corr2 corr3 1. SLAs (+ SWH, wind speed) are precomputed offline from raw data + corrections and stored Preprocessor 2. When user asks for data, the OPeNDAP server serves the precomputed SLAs OPeNDAP server PROs: simple, no extra client required CONs: allows only predefined correction schemes USER running standard OPeNDAP client

  3. Raw data NetCDF corr1 corr2 corr3 Model 2: computation at the user The user runs a specialized client which gets raw data + corrections via the OPeNDAP server and computes the parameter OPeNDAP server PROs: trivial to setup on server side CONs: needs separate, non-standard user clients for each application Custom client USER

  4. Model 3: “on the fly” computation Raw data NetCDF corr1 corr2 corr3 The request from the user to the OPeNDAP server prompts an interface server that retrieves the raw data and corrections and computes the parameter on the fly Interface server OPeNDAP server PROs: request is fully customizable CONs: interface server needs to be implemented and be able to interpret OPeNDAP request - CDAT possible candidate? USER running standard OPeNDAP client

More Related