Defines and prepares a project (§3): its folder in the tree, where its bulk statistics live, the database its results go to, the field-polygon layer it is assessed against, and the registry of sampling periods every other app then selects from.
Defines and prepares a project (§3): its folder in the tree, where its bulk statistics live, the database its results go to, the field-polygon layer it is assessed against, and the registry of sampling periods every other app then selects from.
Use the menu on the left; each panel has its own help topic.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Define the project title and its folder name, and create the year/project tree.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Set an alternative filesystem path for the large sampled statistical tables.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Set the PostgreSQL/PostGIS connection holding the processing results.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Register sampling periods and the statistical data files loaded into each.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Retrieve and convert the field-polygon vector layer to a common format (GeoPackage).
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Clean topology, geometry, character-encoding and attribute-schema errors.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Harmonise crop codes to standard nomenclature via cross-reference dictionaries.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Filter out objects below the Minimum Mapping Unit (MMU) threshold.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Sample per-field statistics from the satellite product grid into a period's stats folder.
TODO — what must already be true. Most panels here need a project selected in the top bar, and the step before them to have completed.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.