Skip to content

Commit b3a8efe

Browse files
committed
Merge branch 'develop' of https://github.com/davidfrantz/force into develop
2 parents 7c874de + 3a3a6f0 commit b3a8efe

File tree

18 files changed

+2466
-37
lines changed

18 files changed

+2466
-37
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ env:
1616
jobs:
1717
push:
1818
name: Push debug image to Docker Hub
19+
if: github.repository == 'davidfrantz/force'
1920
runs-on: ubuntu-latest
2021
steps:
2122
- name: Check out the repo

.github/workflows/docker-publish.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ env:
1616
jobs:
1717
push:
1818
name: Push image to Docker Hub
19+
if: github.repository == 'davidfrantz/force'
1920
runs-on: ubuntu-latest
2021
steps:
2122
- name: Check out the repo

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
**Framework for Operational Radiometric Correction for Environmental monitoring**
44

5-
**Version 3.7.1-develop**
5+
**Version 3.7.2-develop**
66

77
![FORCE Logo](/images/force.png)
88

@@ -27,7 +27,7 @@ Non-native data sources can also be processed, e.g. Sentinel-1 SAR data or envir
2727

2828
**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.
2929

30-
**Get help**, and help others in the FORCE self-help [Google group](https://groups.google.com/d/forum/force_eo)
30+
**Get help**, and help others in the FORCE [discussion section](https://github.com/davidfrantz/force/discussions)
3131

3232
**Follow** the FORCE project at [ResearchGate](https://www.researchgate.net/project/FORCE-Framework-for-Operational-Radiometric-Correction-for-Environmental-monitoring)
3333

docs/source/components/higher-level/index.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,6 @@ Multiple :ref:`hl-submodules` are available, which either process ARD or feature
4040
:hidden:
4141
:maxdepth: 3
4242

43-
higher-level.rst
4443
hl-input.rst
4544
hl-compute.rst
4645
hl-aux.rst

docs/source/conf.py

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,7 @@
7777
# a list of builtin themes.
7878
#
7979
html_theme = 'default'
80+
#html_theme = 'sphinx_rtd_theme'
8081

8182
# Theme options are theme-specific and customize the look and feel of a theme
8283
# further. For a list of options available for each theme, see the

docs/source/history/v3.rst

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,28 @@
11
.. _v3:
22

3+
FORCE v. 3.7.2
4+
--------------
5+
6+
Release: 20.10.2021
7+
8+
* **FORCE L2PS**
9+
10+
* ESA made major changes in their Sentinel-2 products, which will become effective as of October 26, 2021.
11+
Specifically, ESA introduced additive scaling factors to convert the DNs to TOA reflectance.
12+
Older FORCE versions will fail!
13+
Update to FORCE >= 3.7.2!
14+
Thanks to Vincent Schut and Patrick Griffiths for the heads-up!
15+
16+
* **General changes**
17+
18+
* Docker containers will only be published to Docker Hub, if working in the original repository.
19+
This solves failed GitHub Actions for users that have forked the repository.
20+
Thanks to Florian Katerndahl for implementing a fix!
21+
22+
* **New Program**
23+
24+
* There is now a new program ``force-cube-init``, which can generate a ``datacube-definition.prj`` file without needing to process Level 2 data.
25+
326

427
FORCE v. 3.7.1
528
--------------

docs/source/howto/coreg.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
.. _tut-coreg:
22

3-
.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN
4-
5-
63
Coregistration
74
==============
85

6+
.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN
7+
98
**How to coregister Sentinel-2 with Landsat**
109

1110
This tutorial explains how to generate co-registered Sentinel-2 Analysis Ready Data using the FORCE Level 2 Processing System.

docs/source/howto/l2-ard.rst

Lines changed: 32 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This tutorial explains what Analysis Ready Data are, and how to use the FORCE Le
99

1010
.. admonition:: Info
1111

12-
*This tutorial uses FORCE v. 3.2*
12+
*This tutorial uses FORCE v. 3.7*
1313

1414

1515
What are Levels?
@@ -108,29 +108,26 @@ An empty Level 2 parameter file can be generated with
108108

109109
.. code-block:: bash
110110
111-
force-parameter /data/force/param LEVEL2 1
111+
force-parameter /data/force/param/l2ps.prm LEVEL2
112112
113-
LEVEL2
114113
An empty parameter file skeleton was written to
115-
/data/force/param/LEVEL2-skeleton.prm
114+
/data/force/param/l2ps.prm
116115
Note that all parameters need to be given, even though some may not be used
117116
with your specific parameterization.
118-
You should rename the file, e.g. my-first-LEVEL2.prm.
119117
Parameterize according to your needs and run with
120-
force-level2 /data/force/param/my-first-LEVEL2.prm
118+
force-level2 /data/force/param/l2ps.prm
121119
or for a single image:
122-
force-l2ps image /data/force/param/my-first-LEVEL2.prm
120+
force-l2ps image /data/force/param/l2ps.prm
123121
124122
125-
The trailing ``1`` means that descriptions for every parameter will be included.
126-
If you prefer a shorter parameter file, give a ``0`` instead.
123+
This will generate a verbose parameter file which includes a description for every parameter. If you
124+
prefer a shorter parameter file, set the optional ``-c`` flag (see :ref:`aux-parameter` for detailed documentation).
127125
The descriptions can also be found here: :ref:`l2-param`.
128126

129-
Let’s rename the file, and have a look:
127+
Let’s have a look:
130128

131129
.. code-block:: bash
132130
133-
mv /data/force/param/LEVEL2-skeleton.prm /data/force/param/l2ps.prm
134131
head /data/force/param/l2ps.prm
135132
136133
++PARAM_LEVEL2_START++
@@ -373,6 +370,30 @@ The processing time (real time) is appended at the end.
373370
S2A_OPER_MSI_L1C_TL_SGS__20160916T135429_A006453_T33JYG_N02.04: dc: 100.00%. wc: 1.78%. sc: 2.85%. cc: 100.00%. Skip. Processing time: 12 mins 17 secs
374371
375372
373+
A more convient way to get an overview is to generate an html report:
374+
375+
.. code-block:: bash
376+
377+
force-level2-report /data/force/log
378+
379+
380+
This tool generates some interactive charts that visualize the information available in the logfiles:
381+
382+
.. raw:: html
383+
:file: ../html/report_20211011020320.html
384+
385+
386+
.. important::
387+
The first chart gives an overview about the processing success.
388+
``Success``, ``Too cloudy``, and ``Coregistration failed`` are all OK.
389+
The category ``Error`` is bad and means that something went wrong.
390+
If so, the names of the failed images will be listed below.
391+
392+
.. note::
393+
``Error`` can also mean that the images are still under processing.
394+
Run *force-level2-report* **after** *force-level2*!
395+
396+
376397
Output format
377398
-------------
378399

docs/source/howto/stm.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
.. _tut-stm:
22

3-
.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN
4-
5-
63
Spectral Temporal Metrics
74
=========================
85

6+
.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN
7+
98
**How to aggregate time series**
109

1110
This tutorial explains what Spectral Temporal Metrics are, and how to generate them using the Time Series Analysis (TSA) submodule of the FORCE Higher Level Processing system (HLPS).

docs/source/howto/tsi.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
.. _tut-tsi:
22

3-
.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN
4-
53
Time Series Interpolation
64
=========================
75

6+
.. |copy| unicode:: U+000A9 .. COPYRIGHT SIGN
7+
88
**How to interpolate and animate time series**
99

1010
This tutorial introduces the Time Series Analysis (TSA) submodule of the FORCE Higher Level Processing system (HLPS), shows how to interpolate time series, and how to visualize and animate them via QGIS plugins.
@@ -14,8 +14,8 @@ This tutorial introduces the Time Series Analysis (TSA) submodule of the FORCE H
1414
*This tutorial uses FORCE v. 3.5*
1515

1616

17-
----------
18-
Why interpolation?**
17+
Why interpolation?
18+
------------------
1919

2020
Despite regular observations, EO time series are generally not equidistant.
2121
Nominal equidistance is only given for areas that are not covered by orbital overlaps (16 days revisit at nadir for a single Landsat).
@@ -34,13 +34,13 @@ Equidistance is established, which might be needed for following processing step
3434

3535
Time Series interpolation is a basic option within the :ref:`tsa` submodule of the FORCE :ref:`hlps` Processing system (HLPS), and may be performed before using more advanced time series analysis methods:
3636

37-
.. figure:: img/force-tsa-workflow.jpg
37+
.. figure:: ../components/higher-level/tsa/tsa-workflow.jpg
3838

3939
*Time Series Analysis Workflow*
4040

4141

42-
----------
43-
RBF interpolation**
42+
RBF interpolation
43+
-----------------
4444

4545
In FORCE, a couple of interpolation methods are implemented.
4646

0 commit comments

Comments
 (0)