askcust develops digital field maps: field boundaries and areas, cadastral plots over the fields, crops by season, NDVI, soil and terrain layers, and export in formats that machinery terminals read. For farms where boundaries live in the agronomist's KML files while accounting, telematics and land contracts each keep their own version of a field.
A digital field map is a layer of the farm's field boundaries to which all other data is linked: crops and rotation by year, operations, costs, cadastral plots, satellite imagery and soil analyses. It sets one set of boundaries and areas for accounting, telematics and the agronomist. Unlike satellite monitoring, which shows the state of crops, a field map answers the question of where a field is and what it is.
Areas from a survey, from the cadastre and in the accounts differ because they were calculated from different boundaries and in different ways. The map keeps the source of every boundary and calculates area on the ellipsoid, so a discrepancy is visible and explained, and one agreed area goes into the accounts.
Field boundaries change: a field is split between two crops or merged after a neighbouring plot is bought. The map keeps boundary versions by season, so past yields and treatments stay linked to the part of the land where they happened.
The agronomist, the engineer and the telematics provider get field boundaries from one map through export or an API instead of forwarded KML files. When a boundary changes, every system that depends on it receives the updated version.
NDVI, soil survey, terrain and yield layers are overlaid on the same boundaries and compared across seasons. The agronomist sees the whole field (boundaries, soil, crop condition and history) instead of opening four different services.
The map is the base module: field records, the land bank and monitoring connect to it as layers and data.
A GPS receiver survey, machinery tracks, digitising from satellite images and cadastral plots; every boundary has a source, a date and an author, and changes go through approval.
Area is calculated on the WGS 84 ellipsoid, and cadastral coordinates are converted from the national USK-2000 system; differences between the areas of a field, its plots and the accounts appear in a separate report.
Plots with cadastral numbers as a separate layer above the fields: you see which plots a field consists of and where field and document boundaries do not match.
Crop, variety and previous crop on every field by season, a rotation plan for the coming years, and a field's history with treatments and yields on one page.
The NDVI vegetation index from Sentinel-2 imagery at 10 m resolution, soil survey results, terrain, yield maps from combines and scouting points.
Boundaries, layers and the current location on a phone, downloaded in advance for work in the field without a connection; notes and geotagged points synchronise later.
Boundaries and layers in KML, Shapefile, GeoJSON and ISOXML, and an API for accounting and telematics systems, so that all of the farm's software takes field boundaries from one source.
askcust builds the map and the format exchange; imagery comes from Copernicus open data, while surveys and soil analyses are done by the farm's contractors.
| criterion | Map in a ready service | Field map by askcust |
|---|---|---|
| Field boundaries | One current version of a boundary, and a change rewrites the field's history. | Boundary versions by season, with the source and author of every change. |
| Layers | The ones the service supports, in its format and at its update rate. | Any of the farm's layers: cadastre, soil, yields and its own points. |
| Link to other software | Boundaries have to be exported and imported into each system by hand. | Accounting, telematics and the land bank take boundaries from the map through an API. |
| Export to machinery | The formats the service supports, not tested on your terminal. | Export is tested on the farm's own files and terminals before launch. |
| Data | Boundaries and field history are stored on the vendor's servers. | The map and its whole history run on your server or in your cloud. |
| When to choose | Only an NDVI map is needed, with no link to accounting and contracts. | The map has to become the base for accounting, telematics and the land bank. |
askcust collects every existing set of field boundaries (the agronomist's KML, the telematics portal, cadastral files, accounting spreadsheets) and shows on one map where they disagree.
The agronomist and management decide which boundary is the working one for each field; the agreed area becomes the single one for accounting, and the rest stay as reference layers.
Crops, previous crops and yields of past seasons are moved from spreadsheets onto the agreed boundaries, so rotation and comparisons are visible from day one.
NDVI, the cadastre, soil and other needed layers are connected; export in terminal formats is tested on the farm's real terminal before the season starts.
Field records, telematics and the land bank switch to boundaries from the map through an API; support includes updating boundaries before every season.
examples of askcust's work →not agriculture, but the same kind of task: records, CRM, automation
From several sources, each with its own accuracy. The most accurate is a GPS receiver survey along the field edge; the fastest is digitising from a satellite image; cadastral plots show the boundaries on paper, and machinery tracks show the actual edge of cultivation. askcust brings them onto one map, and the agronomist approves the working boundary for each field, keeping the others for reference.
Most often because of different boundaries: a survey, the cadastre and digitising give different edges. The second reason is the calculation method: an area computed directly in web map coordinates (Web Mercator) is inflated 2 to 2.7 times at Ukraine's latitudes. The askcust map calculates area on the WGS 84 ellipsoid and shows which boundary each area comes from, so a discrepancy can be explained rather than guessed.
Yes, cadastral plots are a separate layer above the field boundaries. They are loaded from the XML exchange files of land survey documentation, and their coordinates are converted from the national USK-2000 system into the map's system. The layer shows which plots a field consists of and where the field goes beyond the documents. Contracts and rights holders are added to plots by the land bank module.
Yes. The mobile version downloads boundaries, the needed layers and the basemap for selected fields in advance, so the map, the current location and field edges are available without a mobile signal. Notes, photos and geotagged scouting points are stored on the phone and synchronise when a connection returns. The cache size is set to the farm's area and the devices' memory.
Yes. Field boundaries are exported to ISOXML for ISOBUS terminals and to Shapefile, which most other terminals and precision farming programs accept. File requirements differ between manufacturers (structure, coordinate system, field names), so askcust tests the export on a sample file and on the farm's real terminal, not just against the specification.
The cost depends on the number of boundary sources, layers, export formats and integrations with other systems, not on the farm's area. The first stage (agreed boundaries and areas, crop history and export) is estimated by askcust with a fixed scope after the existing boundaries are collected; layers and exchange with accounting and telematics are added in later steps.
A reply within one business day; a call only if we agree on one.