GithubHelp home page GithubHelp logo

grseb9s / smos-box Goto Github PK

View Code? Open in Web Editor NEW

This project forked from senbox-org/smos-box

0.0 1.0 0.0 142.85 MB

A SNAP Toolbox dedicated to the SMOS sensor

Home Page: http://www.brockmann-consult.de/beam-wiki/display/SBOX/SMOS+Toolbox+for+BEAM

License: GNU General Public License v3.0

Java 55.66% Batchfile 0.04% Shell 0.03% Haskell 0.03% HTML 44.13% CSS 0.11%

smos-box's Introduction

<!--
  ~ Copyright (C) 2010 Brockmann Consult GmbH ([email protected])
  ~
  ~ This program is free software; you can redistribute it and/or modify it
  ~ under the terms of the GNU General Public License as published by the Free
  ~ Software Foundation; either version 3 of the License, or (at your option)
  ~ any later version.
  ~ This program is distributed in the hope that it will be useful, but WITHOUT
  ~ ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  ~ FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
  ~ more details.
  ~
  ~ You should have received a copy of the GNU General Public License along
  ~ with this program; if not, see http://www.gnu.org/licenses/
  -->

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
    <meta name="generator" content=
            "HTML Tidy for Mac OS X (vers 25 March 2009), see www.w3.org"/>

    <title>About SMOS-Box</title>
    <style type="text/css">
        /*<![CDATA[*/
        body {
            background-color: #FFFFFF;
            color: #000000;
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 12;
            padding: 6pt;
            margin: 6pt;
        }

        p {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            margin: 6pt;
        }

        .i1 {
            margin-left: 30;
        }

        .i2 {
            margin-left: 50;
        }

        .note {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            color: red;
        }

        .inote {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            background-color: #DDDDDD;
        }

        .code {
            color: blue;
            font-family: courier new, courier, Monospaced, cursive;
            text-align: left;
            font-weight: normal;
            text-decoration: none;
            font-style: normal;
        }

        h1 {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 25;
            font-weight: bold;
            margin-top: 18pt;
            margin-right: 6pt;
            margin-bottom: 12pt;
            margin-left: 6pt;
        }

        h2 {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 21;
            font-weight: bold;
            margin-top: 18pt;
            margin-right: 6pt;
            margin-bottom: 12pt;
            margin-left: 6pt;
        }

        h3 {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 18;
            font-weight: bold;
            margin-top: 18pt;
            margin-right: 6pt;
            margin-bottom: 12pt;
            margin-left: 6pt;
        }

        h4 {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 15;
            font-weight: bold;
            margin-top: 18pt;
            margin-right: 6pt;
            margin-bottom: 6pt;
            margin-left: 6pt;
        }

        h5 {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 12;
            font-weight: bold;
            margin-top: 18pt;
            margin-right: 6pt;
            margin-bottom: 6pt;
            margin-left: 6pt;
        }

        h6 {
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 11;
            font-weight: bold;
            margin-top: 18pt;
            margin-right: 6pt;
            margin-bottom: 6pt;
            margin-left: 6pt;
        }

        li {
            margin-top: 4pt;
            margin-bottom: 4pt;
        }

        table {
            border-width: 0;
            border-collapse: collapse;
            padding: 1px;
            margin: 0;
        }

        invisibletable {
            border-width: 0;
            border-style: solid;
            border-color: #FFFFFF;
            border-collapse: collapse;
            padding: 1px;
            margin: 0;
            font-family: Verdana, Arial, Helvetica, sans-serif;
            font-size: 12px;
            font-style: normal;
        }

        th {
            font-size: 12;
            text-align: left;
            border-width: 1;
            border-color: #BBBBBB;
            border-style: solid;
            border-collapse: collapse;
            padding-left: 6px;
            padding-right: 6px;
            padding-top: 3px;
            padding-bottom: 3px;
        }

        td {
            font-size: 11;
            border-width: 1;
            border-color: #BBBBBB;
            border-style: solid;
            border-collapse: collapse;
            border-spacing: 0;
            padding: 0;
            padding-left: 6px;
            padding-right: 6px;
            vertical-align: top;
        }

        table.header {
            width: 100%;
            height: 29;
            font-size: 17;
            color: #ffffff;
            vertical-align: middle;
            background-color: #993333;
            border-width: 0;
            padding: 0;
            margin: 0;
        }

        .header {
            font-size: 17;
            height: 29;
            color: #ffffff;
            vertical-align: middle;
            background-color: #993333;
            border-width: 0;
            padding: 0;
            white-space: nowrap;
        }

        hr {
            height: 4;
            color: #000063;
            border-color: #000063;
            border-style: solid;
            border-width: 1;
        }

        /*]]>*/
    </style>
</head>

<body>
<h3>About the BEAM SMOS-Box Version ${project.version}</h3>

<h4>Introduction</h4>

<p>The BEAM SMOS-Box project has been brought into life in order
    to support users of data acquired by ESA's Soil Moisture and
    Ocean Salinity (SMOS) mission. BEAM and the SMOS-Box are user
    tools which ESA/ESRIN are providing free of charge to the Earth
    Observation Community.</p>

<p>The SMOS-Box software has been developed by <a href=
                                                          "http://www.brockmann-consult.de/">Brockmann Consult</a> under
    ESA contract initiated by Steven Delwart (ESTEC, ESRIN) and coordinated
    Peter Regner (ESRIN).</p>

<h4>License</h4>

<p>BEAM and the SMOS-Box are free software; you can redistribute
    it and/or modify it under the terms of the <a href=
                                                          "http://www.gnu.org/licenses/gpl.html">GNU General Public
        License</a> as published by the Free Software Foundation. This
    program is distributed in the hope it will be useful, but WITHOUT
    ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
    General Public License for more details.</p>

<h4>New in Version ${project.version}</h4>

<p>Version ${project.version} of the BEAM SMOS-Box resolves
    <a href="http://www.brockmann-consult.de/beam-jira/issues/?jql=project%20%3D%20SBOX%20AND%20issuetype%20in%20(Bug%2C%20Improvement%2C%20%22New%20Feature%22%2C%20Requirement)%20AND%20fixVersion%20%3D%20%223.0%22%20AND%20status%20%3D%20Resolved">several
        issues</a>.</p>

<h4>Supported Data Products</h4>

<p>Version ${project.version} of the BEAM SMOS-Box is capable of reading SMOS
    data products complying with Schemas Release
    2014-04-04_v06-02-03. The product types supported are listed in
    the table below. In addition, SMOS L1C NRT products (Earth Explorer, Light-BUFR, BUFR) are supported as well.</p>

<table>
    <tr>
        <th>Type</th>

        <th>Level</th>

        <th>Description</th>
    </tr>

    <tr>
        <td colspan="3">SMOS Products</td>
    </tr>

    <tr>
        <td>MIR_BWLD1C</td>

        <td>1C</td>

        <td>Browse Land Dual-Polarisation Product. In the BEAM data
            model all measurements in the <code>BT_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_BWLF1C</td>

        <td>1C</td>

        <td>Browse Land Full-Polarisation Product. In the BEAM data
            model all measurements in the <code>BT_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_BWSD1C</td>

        <td>1C</td>

        <td>Browse Sea Dual-Polarisation Product. In the BEAM data
            model all measurements in the <code>BT_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_BWSF1C</td>

        <td>1C</td>

        <td>Browse Sea Full-Polarisation Product. In the BEAM data
            model all measurements in the <code>BT_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_SCLD1C</td>

        <td>1C</td>

        <td>Science Land Dual-Polarisation Product. In the BEAM data
            model all measurements in the <code>BT_Data_Type</code>
            record are represented as bands. The user can specify whether
            the band data should be provided by a simulated browse
            product, which is computed on-the-fly, or by an individual
            snapshot. The former is the default. Brightness temperature
            measurements, pixel radiometric accuracies and Stokes
            parameters are represented in the Satellite's as well as in
            the Earth's reference frame
        </td>
    </tr>

    <tr>
        <td>MIR_SCLF1C</td>

        <td>1C</td>

        <td>Land Full-Polarisation Product. In the BEAM data model
            all measurements in the <code>BT_Data_Type</code> record are
            represented as bands. The user can specify whether the band
            data should be provided by a simulated browse product, which
            is computed on-the-fly, or by an individual snapshot. The
            former is the default. Brightness temperature measurements,
            pixel radiometric accuracies and Stokes parameters are
            represented in the Satellite's as well as in the Earth's
            reference frame
        </td>
    </tr>

    <tr>
        <td>MIR_SCSD1C</td>

        <td>1C</td>

        <td>Level-1c Science Sea Dual-Polarisation Product. In the
            BEAM data model all measurements in the
            <code>BT_Data_Type</code> record are represented as bands.
            The user can specify whether the band data should be provided
            by a simulated browse product, which is computed on-the-fly,
            or by an individual snapshot. The former is the default.
            Brightness temperature measurements, pixel radiometric
            accuracies and Stokes parameters are represented in the
            Satellite's as well as in the Earth's reference frame
        </td>
    </tr>

    <tr>
        <td>MIR_SCSF1C</td>

        <td>1C</td>

        <td>Level-1c Science Sea Full-Polarisation Product. In the
            BEAM data model all measurements in the
            <code>BT_Data_Type</code> record are represented as bands.
            The user can specify whether the band data should be provided
            by a simulated browse product, which is computed on-the-fly,
            or by an individual snapshot. The former is the default.
            Brightness temperature measurements, pixel radiometric
            accuracies and Stokes parameters are represented in the
            Satellite's as well as in the Earth's reference frame
        </td>
    </tr>

    <tr>
        <td>MIR_OSDAP2</td>

        <td>2</td>

        <td>Ocean Salinity Data Analysis Product. In the BEAM data model
            all measurements in the <code>Grid_Point_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_OSUDP2</td>

        <td>2</td>

        <td>Ocean Salinity User Data Product. In the BEAM data model
            all measurements in the <code>Grid_Point_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_SMDAP2</td>

        <td>2</td>

        <td>Soil Moisture Data Analysis Product. In the BEAM data model
            all measurements in the <code>Grid_Point_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>MIR_SMUDP2</td>

        <td>2</td>

        <td>Soil Moisture User Data Product. In the BEAM data model
            all measurements in the <code>Grid_Point_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td colspan="3">Auxiliary Products</td>
    </tr>

    <tr>
        <td>AUX_DFFLAI</td>

        <td></td>

        <td>Leaf area index (LAI) auxiliary product. In the BEAM data
            model all measurements in the
            <code>DFFG_LAI_Point_Data_Type</code> record are represented
            as bands
        </td>
    </tr>

    <tr>
        <td>AUX_ECMWF_</td>

        <td></td>

        <td>ECMWF auxiliary product. In the BEAM data model selected
            measurements in the <code>ECMWF_PARAMS_Data_Type</code>
            record are represented as bands
        </td>
    </tr>

    <tr>
        <td>AUX_LSMASK</td>

        <td></td>

        <td>Land/sea mask auxiliary product. All flags in the
            land/sea mask are represented as masks in BEAM
        </td>
    </tr>

    <tr>
        <td>AUX_VTEC_C</td>

        <td></td>

        <td>Consolidated Vertical Total Electron Content auxiliary
            product. In the BEAM data model all measurements in the
            <code>VTEC_Data_Type</code> record are represented as
            bands
        </td>
    </tr>

    <tr>
        <td>AUX_VTEC_P</td>

        <td></td>

        <td>Predicted Vertical Total Electron Content auxiliary
            product. In the BEAM data model all measurements in the
            <code>VTEC_Data_Type</code> record are represented as
            bands
        </td>
    </tr>
</table>

<h4>Tools and commands</h4>

<p>Version ${project.version} of the SMOS-Box includes five SMOS-specific tools
    and commands:</p>

<ul>
    <li>Grid point data table: all measurements made for the grid
        point selected by either the mouse pointer or a selected pin
        are displayed in a table.
    </li>

    <li>Grid point flag matrix diagram: all flags associated with
        the measurements made for the grid point selected by either the
        mouse pointer or a selected pin are displayed in a flag
        matrix
    </li>

    <li>Grid point brightness temperature chart: All brightness
        temperatures measured for the grid point selected by either the
        mouse pointer or a selected pin are displayed in a chart
    </li>

    <li>Snapshot information tool: information for all snapshots
        contained in a Level-1c Science product can be browsed with a
        slider
    </li>

    <li>Grid point export facility: exports all data for a
        user-defined set of SMOS grid points into a plain text
        file
    </li>
</ul>

<h4>Known Limitations</h4>

<p>Version ${project.version} of the SMOS-Box has the following known
    limitations:</p>

<ul>
    <li>All SMOS data products are represented as global products
        covering the whole surface of the Earth. Therefore SMOS
        products do not have a geographical boundary
    </li>

    <li>Due to the representation of SMOS products as global
        products, it is not possible to draw lines or shapes crossing
        the anti-meridian
    </li>

    <li>Statistics, scatter plots, histograms and profile plots use
        image pixel data rather than SMOS grid point data
    </li>
</ul>

<h4>Further Information</h4>

<p>The most important source of information for BEAM and the
    SMOS-Box are the <a href=
                                "http://www.brockmann-consult.de/cms/web/beam/forum">BEAM
        Forum</a> and the <a href=
                                     "http://www.brockmann-consult.de/beam-wiki/display/SBOX/">SMOS-Box
        Wiki</a>.</p>

<h4>Reporting Issues</h4>

<p>You can submit BEAM bug reports or feature request to the
    <a href=
               "http://www.brockmann-consult.de/beam-jira/browse/SBOX">SMOS-Box
        Issue Tracker</a>.</p>
<hr/>

<p><i>Copyright &copy; 2010-2014 by Brockmann Consult (<a href=
                                                                  "mailto:[email protected]">[email protected]</a>).
    All rights reserved.</i></p>
</body>
</html>

smos-box's People

Contributors

tomblock avatar heptaflar avatar marpet avatar mzuehlke avatar forman avatar julienmalik avatar

Watchers

James Cloos avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.