Versions Compared

Old Version 3

changes.mady.by.user Former user (Deleted)

Saved on

compared with

New Version Current

changes.mady.by.user Marco Peters

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Target releaseS3TBX 3.0
Epic
Jira Legacy
serverJIRA (senbox.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId34c99a62-e5be-31ca-898a-01c2aded1b99
keySIIITBX-25
Document status
Status
titleDRAFT
Document owner

Former user (Deleted)

DesignerFormer user (Deleted), Olivier Sardou (Unlicensed), Philippe Garnesson (Unlicensed) Marco Peters
DevelopersFormer user (Deleted), Olivier Sardou (Unlicensed),  Philippe Garnesson (Unlicensed) Marco Peters
QAOlga Faber (Unlicensed)

...

#TitleUser StoryImportanceNotes
1State-of-the art anaylsis

Before a final desihgn for the feature is dervied, a state-of-the-art analyis shall be performed:

  • look into existing standards in this domain such as the OGC Sensor Observation Service (SOS)
  • look at similar systems such as Felyx, an approach to harmonise various in-situ data sources, combine them with satellite data and to make the data and data match-ups searchable in a scalable way
  • consider candidate providers such as GHRSST MDB, MERMAID, CORIOLIS, MyOcean In-Situ TAC database, CEOS CalValPortal, Aeronet, NASA SeaBAS, CNES SAD database, OC-CCI Phase 2 in-situ database
Must have 
2Developer guideCreate new "How to" wiki pages describing (a) how to implement a new service, and (b) how to use the web service's RESTful API on the client side.Desired 
3Data policyPay attention to legal conditions regarding the publication of the data (intellectual property rights, ownership, copyrights, licensing). Published data shall always be correctly cited. Must have 
4MetadataIn-situ data must be attached by metzadata metadata and made visible to users so they know how to correlate the remote data with their EO data.  

...

The client tool will have a GUI similar to the OPeNDAP client included since BEAM 4.11. Users will be able to use the tool to select subsets of in-situ data. The client tool shall also make intelligent use of the current context the user is working in. For example, a function will be provided that performs a query based on the current scene the user is working with: Spatial region and temporal range are determined, so the user could use a one-click action that would download and display all in-situ data found for that particular scene. Uses can select the web service name / URI they wish to get the in-situ data from.

For demonstration purpose, it is planed to use in-situ coming from MERMAID or from SeasideRendezvous (BIO-ARGOS from CORIOLIS).

The client tool is further documented in In-Situ Client Tool

Web Service

For the server-side, a web service will be developed which translates a request coming from the Toolbox into the query language understood by the in-situ database. The data retrieved from the database in translated back into the response understood by the client tool in the Toolbox.  We will provide at least an in-situ service for the MERMAID database focusing on MERIS / Sentinel-3 data. A second service for SLSTR SST data is very desireable (see GHRSST SST in-site data). The NASA OBPG might contribute a service for the SeaBASS database as well.

...