When a vineyard is split — for example because one half is leased out or planted with a new grape variety — you previously had to delete the existing vineyard and create two new ones. In the process, all linked data was lost: tasks, reports, time tracking.
Split vineyards directly on the map
From now on this works directly on the map: draw a line across the vineyard, and the area is automatically cut into two parts. Both new vineyards keep their connection to the original — tasks, reports and time entries remain intact.
That sounds simple, but was technically quite demanding. The polygon-splitting logic has to be able to handle all possible shapes: concave areas, areas with holes, and edge cases where the line runs exactly through a corner point. For this we use the Turf.js library on the client and validate the result server-side once more.
Reworked area editor
In the course of the splitting function, we reworked the entire area editor. Points can be moved more intuitively, the handles are larger and more visible, and operation on touch devices works considerably better.
The most important improvements at a glance:
- Larger grab points — well usable on mobile devices too
- Visual feedback when moving points
- Undo/redo for all editing steps
- Snap-to-grid option for precise input
47 predefined task types
Instead of starting from scratch, new businesses now start with the usual viticulture tasks: cutting, tying up, defoliating, thinning, plant protection, embankment mowing and much more. The types can be adjusted, extended or deleted at any time.
We put the 47 types together together with winegrowers from the Wachau, the Burgenland and Southern Styria. They cover the entire annual cycle and are named the way they are common in German-speaking viticulture.
Technical modernisation
Behind the scenes there was a major technical update: Spring Boot 4 with Hibernate 7 on the server, Angular 21 in the dashboard and Riverpod 3 in the mobile app. These updates bring better performance and enable us to develop new functions faster.
The migration to Spring Boot 4 was the biggest technical change since our start — but it is already paying off. The server’s startup time has halved.
For you as a user, nothing visible changes as a result — but the faster foundation enables us to deliver the next features considerably faster.