Every project you may open, summarised from its folder under the project base (set by an Administrator in ADMIN β Settings). Nothing here is a registry: the summary is read from the folders each time, so it shows what is really there.
| Row | Means |
|---|---|
| Client | the Client the project belongs to; no Client (amber) β only Administrators see it |
| Season | the farming season its field layer declares |
| Managers | the Client's Managers (shown to Managers and Administrators) |
| Granted to | the people granted the project by name; Managers only if nobody |
| Field layer | inputs/fields.db β how many fields, and the source it was built from; not imported until FIELDS has run |
| Other inputs | the other files in inputs/ β the statistics Inputs produced |
| Periods | each period under outputs/; green ones have results, with the number of algorithm runs |
| Algorithms | the algorithms and models that wrote results (the folders under each period's results/) |
| Configuration | sound, with how many versions are saved, or the problems in words |
copied from another project. name is protected in SETTINGS, so an Administrator corrects the file on the server.
PROJECTS β Users β Projects with no Client.
CAPCON* β open SETTINGS and save once: that records the current file as a version.
Administrators also see, at the bottom, folders under the base that are not working projects β no settings/project.yaml (for example a folder made with the layout used before 2026-11-01), a file that does not parse, or a folder name that is not a valid project name.
A project is one Client's field layer for one season β for example a Paying Agency's declarations of one farming season β kept in one folder:
<base>/<project>/
settings/project.yaml every setting (every saved version kept in settings/history/)
inputs/ fields.db, the archived source layer, the Inputs statistics
outputs/<period>/ what each period's runs produce
The projects of the Client chosen at the top of the sidebar. If you work for one Client there is nothing to choose; a Manager of several Clients picks the Client there, and this list (and every other app) shows that Client's projects. Select makes a project the one every panel works on.
Managers (for a Client they manage) and Administrators (for any Client):
-and _. It cannot be changed later: every file is named by it.
Create project makes the folder with settings/, inputs/ and outputs/, writes the first settings/project.yaml, and selects the project. Next, import its field layer in FIELDS β until then it is listed as no field layer.
Edit changes the title, season and description. Each save is kept as a version in SETTINGS. Everything else is edited in SETTINGS.
own Clients.
ADMIN β Settings.
The project's field layer: field boundaries, a unique id per field and the declared crop, for one season. It is checked, repaired and converted once into inputs/fields.db, which every period, check and model reads.
Choose the project at the top of the sidebar first.
GeoPackage (.gpkg), Shapefile (zipped with its .dbf, .shx, .prj), GeoJSON or KML. Text encoding: leave auto unless the crop names in step 3 show wrong national characters β a shapefile without a .cpg file is often CP1257 (Windows Baltic).
| fields.db | from |
|---|---|
field_id | a source column β the unique id of each declared field; never repaired |
crop_name | a source column β corrected against the code by majority, kept in UTF-8 |
crop_code | a source column β converted to an integer |
crop_ewoc | the EWOC reference tables (reviewed in step 3), a column of the layer, or left empty |
area_ha | a source column, or computed (equal-area EPSG:3035) |
center_x Β· center_y | computed β longitude and latitude of a point inside the field |
Each attribute must come from a different source column.
Analyse the layer reads the whole layer and reports, without writing:
(dropped), stray line or point parts (removed).
in inputs/topology_report.csv and not altered.
(computed instead), and how the source compares with the computed area. A ratio near 10 000 means the column is in square metres.
found, number of fields, and the EWOC code: proposed from the tables in docs/ewoc/ (or from your previous import), editable. Confirm each one.
Any change in steps 1β2 discards the analysis, so what is imported is always what was reviewed.
Enabled once the analysis has run and found nothing blocking. It writes, in inputs/:
| File | |
|---|---|
fields.db | GeoPackage, table fields, the seven columns above, MultiPolygon, EPSG:4326 |
topology_report.csv | the overlapping pairs and their overlap in ha |
deleted_fields.txt | each dropped field id and why |
source_layer.zip | the upload exactly as received |
project.ini | the record of this import |
The mapping, encoding and your EWOC decisions are recorded under fields: in settings/project.yaml; the decisions pre-fill the next import. A new import replaces fields.db (the season's corrected layer); it is built aside and moved in only when complete.
Placed in docs/ewoc/ as CSV β see docs/ewoc/README.md for the columns. Until they are there, nothing is proposed and codes are entered by hand.
The project's region: the standard 0.5Β° image tiles its fields need, and which monthly composites, dekads and periods SAR preparation computes for them. The region belongs to the project and is recorded in its settings (region: in settings/project.yaml), so every change is kept in the settings history. INPUTS and FARMING read the region from there; they do not define their own.
listed from its field centres.
Settings β World grid.
Everyone who may open the project can read the region.
upper-case letters, digits and _; it is the prefix of the region's files and cannot be changed later) and the scene archive the S1 scenes are read from (EUROPE). The year is the project's season. Create region lists every standard tile that holds the centre point of at least one field.
Save tiles to keep the changes.
and empty β SAR preparation computes nothing for it until you tick the monthly composites, dekads and periods and active. For different settings on part of the region, Add zone, choose it for those tiles in the Tiles table, and Save zones.
changed since the tiles were listed*. List the tiles again: the automatic tiles are listed from the new field centres; tiles you added or removed by hand stay so, and the zones are kept.
Vector layers the FARMING algorithms read, imported here since every vector import into a project is in PROJECTS: forest stands (Deforestation), the KZS polygons (Soil moisture), and parcels with the TEXT crop codes crop lodging needs (fields.db keeps the numeric code and the crop name). Field Statistics never uses them.
.zip with itssiblings, or .gpkg / .geojson / .kml); its fields are listed.
forest_2026 becomes<REGION>_forest_2026_3035.gpkg), the CRS (EPSG:3035 or 4326) and the Kind.
metres) to drop what lies outside the region's tiles; features are kept whole, not clipped. Optionally compute area_ha and centr_x / centr_y.
crop code, the forest stand IDβ¦; the file keeps its own field names.
Edit changes the kind, mapping and description without re-importing; Delete removes the layer and its file.
region: in settings/project.yaml β the name, scene archive, theautomatic tiles with the field layer they came from (number of fields, checksum, date, who), the tiles added and removed by hand, the zones and which tiles are not in the default zone.
inputs/region/grid.gpkg β the tiles, with the zone columns SARpreparation reads (zona, menuo, dekados, periodai, aktyvus).
inputs/region/boundary.gpkg β the union of the tiles, EPSG:4326.inputs/region/layers/ β Farming's layers, recorded in region: layers.Both files are regenerated from the record on every save; never edit them. The region: block is protected in PROJECTS β Settings: edit it here.
Settings β World grid.
centre columns existed; import it again in PROJECTS β Fields.
exist; check its spelling.
tile in the Tiles table or delete it.
Every algorithm of Farming, Checks and Models inspects particular crops: it takes those crops' polygons from the project's fields.db and, if it works on zonal statistics, some columns of the statistics Inputs sampled into the project. This panel sets, per algorithm, the project defaults for both. PROJECTS β Periods then records from them what the algorithm runs on in each period.
Changing a default never changes what a period already recorded.
inputs/statistic/ β the values offered are the ones present there.
number of fields of each). None ticked means every field. Farming's algorithms (crop lodging, the classifications) work on the text crop codes of the region's parcels layers (KVΕ½, RAΕ½ β¦): those are offered with their parcel counts, and other codes can be typed. Farming then runs only on the crops a period records.
Checks' algorithms work on the NMA crop codes β the crop_name of fields.db (AVV, KVΕ½ β¦, with the numeric code and the number of fields) β or, for Arable land and GAN and for Latvia, on land covers and product numbers typed as codes. Each starts from the list it was written with, marked (the algorithm's default) until you save your own:
| Algorithm | Lists |
|---|---|
| Crop recognition | Crops; Excluded crop (at most one) |
| Stubble recognition | Crops; Crops on the no-filter models (p95) |
| Organic farms Β· Crop quality Β· Crop heterogeneity | Crops |
| DGP/GPΕ½ Β· Fallow (PDJ) | The declared crops read |
| Arable land and GAN | Land covers (ppz_danga) |
| Arable land (LAT) 04-10 | Grassland products (product_co); Excluded crop groups |
Fallow still writes PDJ as its marker to NMA whatever crops it reads. Mowing and COETUS take no list.
(d10 dekad, m01 month), quartiles and statistics it needs; none ticked in a row means every value. Set the dates (MMDD): from where the season starts for this algorithm, to left empty to end at each period's last day β so one rule gives the 061120 period the dekads up to 20 June, and the 070110 period those up to 10 July.
settings/project.yaml, kept in the settings history:
algorithms:
farming.classification:
crops: [111, 112]
columns: {pol: [vh, vv], kind: [d10], quartile: [q2], stat: [avg],
date_from: "0401", date_to: ""}
checks.crop_recognition:
crops: [AVV, KVΕ½, RAΕ½]
lists: {excluded: [RUΕ½]}
crop_code is numeric.in <module>/algorithms.yaml yet.
this project yet.
A period is the unit every algorithm runs in: a folder named MMDDDD β month, first day, last day β so 061120 is 11β20 June. This panel creates the project's periods and records, for each algorithm of Farming, Checks and Models, what it runs on in that period:
Nothing is cut into files. The algorithm extracts these inputs on the fly when it runs, so this record β kept in settings/project.yaml β is the evidence of what a result was computed from.
Recording is a Manager's job. Operators see the periods and their records, and may create an empty period from the selector of any app.
rule). Without them it takes every field and every statistics column up to the period's end.
inputs/statistic/.
061120) and, optionally, a note.version, its crops and the size of its inputs.
full β crops, the field layer snapshot, every statistics file with its checksum, the column list.
them for this period if needed, and write a note. Preview shows the number of fields and the columns and files the rule selects for this period. Record fingerprints the statistics files (each is read once; progress streams into the console) and makes the new version active.
When results disappoint, record again with other crops (or change the column rule in Algorithms first) β earlier versions stay β and switch between them with Make active.
settings/project.yaml
periods:
"061120":
note: β¦
algorithms:
farming.classification:
active: v2
versions:
- version: v1
crops: [111, 112]
fields: {name: fields_farming_classification_061120_v1,
snapshot: inputs/fields_versions/<sha>.db, sha256, records}
stats: {name: stats_farming_classification_061120_v1,
id_column: field_id, rule, sources: [{path, size, mtime, sha256, rows}]}
columns: [vv_d10_q2_2026_06_01_avg, β¦]
at, by, note
inputs/fields_versions/<sha>.db the field layer as it was when recorded
The field layer is kept as it was, so a version stays usable after fields.db is re-imported; ten versions of one layer are one file. Versions are never edited or deleted.
re-sampled a statistics file this version names. Results from the old version are still explained by its record, but it can no longer be extracted. Record a new version.
dimensions and dates exclude everything for this period, e.g. it starts after the period ends, or the statistics of those dates are not sampled yet.
current field layer. The version records it anyway; check the list.
versions or results. Deleting it removes the results; the records stay readable in the settings history.
settings/project.yaml of the project chosen at the top of the sidebar: every operational setting β the field layer record, the databases, the periods, and the parameters of checks, algorithms, connections and delivery packages as those apps record them.
The project's Managers and Administrators edit the YAML in place and press Save. Others see it read-only. The server refuses:
key: value pairs) at the top level;settings/.secrets.env, set by thepanel that uses them, never in project.yaml.
name (the folder), company (who sees the project), region (edited in PROJECTS β Region), created and the updated stamps are protected: whatever the edit says, they are kept, and the status line names any that were.
Every save is kept in settings/history/, newest first, with who saved it. View shows a version; Load into the editor puts it in the editor, and saving it makes it the newest version. Nothing is ever overwritten, so the settings behind any earlier result can always be read back.
The administration of the Clients you manage, for their Managers. Managers have no ADMIN application: here you set the role of each of your Client's people and the modules they open, keep their details, suspend them or ask for their deletion, send them messages and tasks, and decide who may open each of the Client's projects. Nothing you change here reaches another Client.
For each Client you manage there are three cards: people, messages and tasks and project access. An Administrator sees every Client here, and one more card, Projects with no Client.
someone yourself; once they are in the Client, they appear here.
Administrator has deactivated does not appear: nobody opens anything through it, you included.
Every member of the Client:
| Column | Means |
|---|---|
| person | e-mail, with name and affiliation when recorded |
| role in <Client> | their role in this Client β a select you can change. Your own is shown as a tag: your own β an Administrator sets it |
| modules | for an Operator, a tick per module β CHECKS, MODELS, DATABASE, RESULTS β all ticked by default, and FARMING when your contract includes it. every module, by role for a Manager; RESULTS for a Viewer. A module your contract lacks is greyed out |
| status | active, suspended (in this Client), deletion requested, or account disabled (by an Administrator) |
| buttons | Message, Details, Suspend / Resume, Request deletion / Withdraw deletion |
The role is one per Client: it applies to this Client's projects only. The same person may hold another role in another Client.
| Role | What they open |
|---|---|
| Manager | every application but ADMIN β FARMING too, when the contract includes it; every project the Client owns; this panel |
| Operator | the modules ticked for them among CHECKS, MODELS, DATABASE and RESULTS β and FARMING when ticked β for the projects granted to them |
| Viewer | RESULTS only, read-only, for the projects granted |
| β no role β | nothing; they stay in the Client |
To set someone up:
<Client>.* Fellow Managers' roles can be changed too β Managers of one Client are peers.
FARMING if they need it. Changing the role away from Operator clears the unticked modules; an Operator always starts with every module.
Suspend stops the person in this Client at once β open applications notice within a minute β and keeps their role, modules and project grants, so Resume puts everything back. It does not touch their work for another Client.
Request deletion is for someone who should no longer have an account. It suspends the account in every Client at once, and an Administrator then deletes it β with its keys β in ADMIN β Users. You may give a reason for the Administrator. Withdraw deletion cancels the request; the account stays suspended until you resume it.
Editing details and requesting deletion concern the account, which is shared by every Client the person works for. They are refused for someone who also works for another Client β ask an Administrator.
FARMING is a commercial add-on. If it is not in your Client's contract the card says FARMING is not in <Client>'s contract. It is an add-on an Administrator sets up.
New message or task opens the form: tick the people it is for, choose Message or Task, write a subject and a text, and optionally name a project and β for a task β a due date. Message on a person's row opens the form with them ticked.
The person sees it on the entry page (the CAPCON home page), with a red badge beside their sign-in pills in every application until they have read the message or marked the task done.
Below the form, everything sent in this Client: to whom, and whether it was read (messages) or done (tasks). Withdraw removes one person's copy.
For each project your Client owns: who may open it besides the Managers, who always can. Use + grant toβ¦ to add one of your Client's Operators or Viewers, remove one with Γ, then Save. Access saved for <year>/<name>.
Managers and the Administrators only.
while the person holds a role in <Client>**: set their role to β no role β, or have an Administrator remove them from the Client, and every project of it closes for them at once.
The projects that belong to no Client β or to a Client name that no longer exists (β¦ (unknown Client)). Administrators see such a project, and so does anyone already granted it by name. Choose the Client in belongs to and press Move: <year>/<name> now belongs to <Client>. The project then appears to that Client's Managers. The files do not move.
Operators create sampling periods themselves, from the Period selector of the application they work in (+ new periodβ¦), inside the projects you granted them.
them, they are suspended, or the contract does not cover it.
the person also works for another Client; an Administrator edits or deletes that account.
the Client; reload the panel.
Done on the entry page; a message until Mark read.
Ask an Administrator to place them.
Client's contract does not cover the application β an Administrator sets the contract.
to them in project access.
box, FARMING is not in your contract.
'<permission>' β ask that Client's Manager* β their role in this Client does not allow it. Change their role; what each role may do is set by an Administrator in ADMIN β Roles.
exactly that.
you manage (or you are no longer its Manager); reload the panel.
the Client (any more); reload the panel.
CLIENTS* β exactly that.
moves a project to another Client.
role is not Manager in any Client, or every Client you manage is deactivated.