Merge pull request #130 from Florian-Katerndahl/develop

Re-opening #123 as new PR becaus I just don't git it and Restrict docker uploads in forked repos

Author: davidfrantz

.github/workflows/docker-publish-debug.yml

@@ -16,6 +16,7 @@ env:
 jobs:
   push:
     name: Push debug image to Docker Hub
+    if: github.repository == 'davidfrantz/force'
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repo

.github/workflows/docker-publish.yml

@@ -16,6 +16,7 @@ env:
 jobs:
   push:
     name: Push image to Docker Hub
+    if: github.repository == 'davidfrantz/force'
     runs-on: ubuntu-latest
     steps:
       - name: Check out the repo

README.md

@@ -27,7 +27,7 @@ Non-native data sources can also be processed, e.g. Sentinel-1 SAR data or envir
 
 **Learn how to use FORCE**. Have a look at the [Tutorials](https://force-eo.readthedocs.io/en/latest/howto/index.html). Check regularly for new content.
 
-**Get help**, and help others in the FORCE self-help [Google group](https://groups.google.com/d/forum/force_eo)
+**Get help**, and help others in the FORCE [discussion section](https://github.com/davidfrantz/force/discussions)
 
 **Follow** the FORCE project at [ResearchGate](https://www.researchgate.net/project/FORCE-Framework-for-Operational-Radiometric-Correction-for-Environmental-monitoring)
 

docs/source/howto/l2-ard.rst

@@ -9,7 +9,7 @@ This tutorial explains what Analysis Ready Data are, and how to use the FORCE Le
 
 .. admonition:: Info
 
-   *This tutorial uses FORCE v. 3.2*
+   *This tutorial uses FORCE v. 3.7*
 
 
 What are Levels?
@@ -108,29 +108,26 @@ An empty Level 2 parameter file can be generated with
 
 .. code-block:: bash
 
-   force-parameter /data/force/param LEVEL2 1
+   force-parameter /data/force/param/l2ps.prm LEVEL2
 
-   LEVEL2
    An empty parameter file skeleton was written to
-     /data/force/param/LEVEL2-skeleton.prm
+     /data/force/param/l2ps.prm
    Note that all parameters need to be given, even though some may not be used
    with your specific parameterization.
-   You should rename the file, e.g. my-first-LEVEL2.prm.
    Parameterize according to your needs and run with
-   force-level2 /data/force/param/my-first-LEVEL2.prm
+   force-level2 /data/force/param/l2ps.prm
     or for a single image:
-   force-l2ps image /data/force/param/my-first-LEVEL2.prm
+   force-l2ps image /data/force/param/l2ps.prm
 
 
-The trailing ``1`` means that descriptions for every parameter will be included.
-If you prefer a shorter parameter file, give a ``0`` instead.
+This will generate a verbose parameter file which includes a description for every parameter. If you
+prefer a shorter parameter file, set the optional ``-c`` flag (see :ref:`aux-parameter` for detailed documentation).
 The descriptions can also be found here: :ref:`l2-param`.
 
-Let’s rename the file, and have a look:
+Let’s have a look:
 
 .. code-block:: bash
 
-   mv /data/force/param/LEVEL2-skeleton.prm /data/force/param/l2ps.prm
    head /data/force/param/l2ps.prm
 
    ++PARAM_LEVEL2_START++