Farming
The largest area of the system. Draw and import parcels, value the soil against the official survey, manage leases and plough exchanges, plan the cropping year, check the subsidy application — and finally work out which direction the field gets driven in.
Worked example · Plough exchange
The same number of hectares does not mean the same value. The soil index decides — and that is in the official soil survey, not in anyone's gut feeling. Nemus.One intersects both sides with the survey and calculates in soil points.
Compensation can be calculated per soil point, per arable point, as a flat sum, or not at all. The result goes to both parties as a PDF — with every intersection listed as evidence.
| Side | Usable area | Avg. soil index | Soil points |
|---|---|---|---|
| Farm A gives | 18,40 ha | 52 | 956,8 |
| Farm B gives | 19,10 ha | 44 | 840,4 |
| Difference | −0,70 ha | +8 | +116,4 |
Illustrative figures. Real values come from the soil survey of the parcels involved.
Everything starts with the piece of land. Draw parcels, group them into fields, overlay official map services — at the desk and on the phone in the field.
The farm's working map. Create, cut and colour parcels by crop code. The legend doubles as the editing tool: colour and pattern per crop are changed where you look at them. Always starts on satellite imagery, with cadastral parcels one toggle away.
A workbench for geometry, modelled on QGIS. Snap vertices, split and merge areas, fill holes, delete a single part of a multipart shape. Everything runs in an edit buffer with its own undo history — only Save writes back. Parcels can be grouped into layers, locked and hidden.
Bundle parcels into fields that are worked as one unit. A field carries its parcels, its area and its crop — and is the unit that route planning and reporting build on.
The table behind the map: every parcel with its area, crop code, protected zone, field and management flags. Shapefile and PDF exports start here; every parcel name opens its detail view without leaving the page.
153 official geodata services from 15 German states plus national and European sources — aerial imagery, topographic maps, protected areas, soil survey, cadastral parcels. Try one without consequence, then star it to add it permanently to the layer panel of every map.
Every map view in the system in one place — parcels, leases, soil, hunting grounds, cropping. Useful when you know what you are looking for but not where it lives.
Read-only access to the crop map for people without an account — a neighbour, a contractor, an authority. The link expires, and it deliberately exposes only harmless colourings: owners, lease end dates, soil indices and contract data never leave the farm.
Photos with GPS coordinates appear on the map where they were taken and can be assigned to a parcel. Plus spherical panoramas in which spots can be marked and labelled. Field photos are a layer you can switch on from any map in the system.
Pin a map extent and evaluate it again and again. What is stored is the extent, not the result — opening it recalculates against current data.
What a parcel is worth is written in the official soil survey. Nemus.One fetches it, intersects it with your own geometry and produces the point values you can actually negotiate with.
Loads the official soil survey as object data and intersects it with a cadastral parcel or a managed parcel. Result: area-weighted soil index and arable index, total soil points, and every single intersection listed as evidence. Checked against the field block register so the eligible area is reported separately. CSV export for the spreadsheet.
Every calculated result side by side — which parcel has which soil index, where a closer look pays off. Values are cached so not every view has to query the service again.
Play through what a different boundary would mean for the soil points before drawing it. The basis for lease negotiations and plough exchanges.
Who owns what, who pays whom how much, and when does it run out. People live in ONE list — the owner in the lease contract is the same record as the shareholder in the hunting association.
The cadastral inventory from the official register: district, parcel section, number, official area, type of ownership. Co-ownership is recorded in full rather than just the first-named owner — otherwise a person is missing exactly those parcels they hold jointly.
Cadastral parcels coloured by ownership type, owner or contract status. At a glance: which parcel expires in the coming years, and where your own operation sits on someone else's land.
Contracts with term, notice period, rent and the parcels they cover. Price per hectare, as a total, or per soil point. Upload a contract PDF and the AI assistant reads it and pre-fills the form.
The other direction: your own land let out to others — with the same contract data and the same deadlines.
What is due when and to whom, on an annual, semi-annual or custom schedule. Outstanding and settled payments per contract and per person.
Swapping cultivation between two farms, properly calculated. Both sides are captured with their parcels; the system determines each side's usable area, area-weighted soil and arable index and from those the total soil points. Compensation can be calculated per soil point, per arable point, as a flat sum, or not at all — including the lease equivalent in euros and which way the payment goes. Result as a PDF for both parties.
Owners, tenants and contract partners in a single list. Rename a person and every contract follows. Duplicates are detected and a merge is suggested — the decision stays with the user.
Rents, terms and area shares at a glance: what the farm pays on average, where it sits above its own mean, which contracts are coming up.
From crop rotation through sowing to the wheel track in the field — and to the question of who does it on which day with which machine.
The sequence of crops per parcel across years, checked against required breaks. Violations are named, not just counted — including the parcel they hang on.
A crop code per cropping year that overrides the parcel's default. Stored as a range: an orchard planting across 30 years is ONE entry, not 30.
Nine connected views for the cropping year: crops with their key figures, work steps per crop, the machinery pool, dates with a capacity check, a calendar, the daily plan, ordering seed and inputs, and a weather window for sowing.
How the field gets driven. The system determines the most efficient heading, how many passes to skip when turning, how deep the headland has to be and which turn actually fits — loop, pear or flag turn. It computes in a metric plane rather than in degrees, because otherwise the error would be as large as the result. It reports overlap, leftover areas, hard-to-reach pockets and the cost. The plan can be played back: the map shows pass by pass in which order the field is worked.
What needs doing, with a deadline, an owner and a link to a parcel or installation. Photos and notes hang on the task rather than in a separate folder.
Two cropping plans side by side: a different crop distribution, different eco-schemes, a different outcome. The comparison spells out the difference in area and payment rather than putting two numbers next to each other.
The view beyond a single application year: how rotation, commitments and land holdings develop across several years.
The application is the goal, but the check beforehand decides. Nemus.One carries the rules of the CAP 2023–2027 and Brandenburg state funding and tells you what does not fit before you submit.
Basic payment, redistribution, young farmer, eco-schemes 1 to 7 and the rural development measures — assigned per parcel and calculated in euros. Conditionality (GAEC) runs as a continuous check: findings are graded by severity and attached to the parcel they concern. Rates and tiers come from a maintained rule base, not from hard-wired numbers.
A report is a named collection of evaluations: dataset, filter, grouping, metric, presentation. What is stored is the question, never the answer — change a crop code and the next open shows the new state. Templates to start from, CSV export for everything else.
Parcel schedule as PDF, parcels as shapefile, evaluations as CSV, contracts and plough exchange agreements as a print-ready document.
A complete snapshot of the project, taken before the big change. If the new layout does not hold up, the old one comes back.