| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | State-of-the art anaylsis | Before a final desihgn for the feature is dervied, a state-of-the-art analyis shall be performed:
| Must have | |
| 2 | Developer guide | Create 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 | |
| 3 | Data policy | Pay 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 | |
| 4 | Metadata | In-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. |
...
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.
...