Planva keeps the field register, crop rotation, agroplans and machine tasks on one object: the field. The boundary is the anchor. Plans, machinery and reports attach to it.
A map without tasks is a picture. A task list without boundaries is a spreadsheet. What you want is a named field, an area, an owner, a deadline and a record of what was planned and what was done.
What the field register carries
- Catalogues and groups. Fields are grouped, and each group has three areas: calculated, official and workable.
- Boundaries. Load them from Shapefile or KML, or edit them on the map. Earlier boundaries stay in an archive. Export goes to KML or SHP.
- Field card. Boundary, areas, region and district, and cadastral numbers.
- Rotation by season. Crop, variety, sowing and harvest dates, yield and output. The rotation map with a crop filter prints to PDF or JPEG with an area summary.
How agroplans and machine tasks sit on those fields
- Agroplan. Pick the season, fields, type of work, dates and owner, and set an operation accounting code for reconciling with your accounting system. View plans as a list, on the map or in a calendar, and export them to XLSX.
- Inputs. For sowing and application, plan seeds, fertilisers and crop-protection products by rate or quantity, plus water rate. For tillage, set depth and speed.
- Plan versus actual. Each agro-operation stores the plan, the actual and the linked machine tasks. The field shows its operation history with the planned and actual rates.
- Machine task. Machine, driver, equipment, fields, the linked agroplan and minimum and maximum planned speed. The task shows full, net and confirmed area, stops, and refuels and drains from fuel-level sensors.
Who should not buy
Do not buy Planva if you only need a one-off cadastral drawing. Do not buy if tasks will keep living in a messenger that nobody attaches to a field. This is for teams that will work the register and the plans every week.