Field data sits in different files
Soil sampling results, combine yield maps and vegetation indices are brought onto the same field boundaries in one coordinate system, so layers can be overlaid and compared instead of opened in three programs.
Fields, machinery and production
Precision farming software from productivity zones to prescription maps
askcust develops precision farming software that combines soil sampling, yield maps and vegetation indices into productivity zones, prepares prescription maps for variable rate application in terminal formats and checks the as-applied data. For farms whose machinery can already apply by map while the data for it sits in separate places.
- layers
- soil tests, yields, indices, terrain
- result
- productivity zones and prescription maps by field
- formats
- ISOXML, Shapefile for the farm's terminals
- reply
- within one business day
What precision farming software is
Precision farming software is a system that brings together data on in-field variability (soil tests, yields, vegetation indices, terrain) into zones, turns the agronomist's rate decisions into prescription maps for machinery and then compares them with the as-applied data. The software itself applies nothing: the implement's rate controller changes the rate, and the software prepares its data and checks the result.
Who needs precision farming software
- ·Farms whose drills and spreaders already support map-based application, but whose prescription maps are made by a contractor or nobody.
- ·Agronomists who have soil sampling, yield maps and NDVI but combine them by hand or not at all.
- ·Agroholdings that want the same zoning and prescription method across all clusters and machinery brands.
- ·Agricultural service companies that run soil sampling and variable rate application for clients.
Which tasks precision farming software solves
Combine yield maps are unusable for decisions
Raw yield data contains false points: pass starts and ends, overlaps, sudden speed changes. The software cleans it under transparent rules and makes maps from different years and combines comparable.
Field zones are redrawn every year
Productivity zones are built from several seasons of yields and indices rather than one image; the agronomist sees how stable the zones are between years and can adjust them before use.
The terminal cannot read the prescription map
Prescription maps are exported in the format a specific terminal accepts, ISOXML or Shapefile with the right attribute structure, and are tested on the farm's actual terminal before work starts, not on the day of application.
Nobody knows whether rates were applied as planned
As-applied data from the terminal is overlaid on the prescription map: areas with rate deviations, gaps and overlaps become visible, and the next season shows whether yields changed in the zones where rates were changed.
What precision farming software does
The module set depends on the data the farm already has and on what its machinery can do.
Field data layers
Soil sampling by grid or zone, yield maps, Sentinel-2 vegetation indices, terrain and field boundaries from the digital field map, all in one coordinate system.
Yield data cleaning
Filters for flow delay at the start of a pass, overlaps, sudden speed changes and impossible values; the parameters are visible and adjustable, and the raw data is kept unchanged.
Field productivity zones
Zones built from several seasons of yields and indices with a stability score between years; the agronomist sets the number of zones and adjusts boundaries where they know the field better than the data does.
Prescription maps for application
Seed, fertiliser or soil amendment rates by zone under rules the agronomist sets, with checks against the implement's minimum and maximum rate and a total material requirement per field.
Export to machinery terminals
ISOXML for ISOBUS terminals and Shapefile for terminals that accept it; the file structure is adapted to the specific models the farm has.
As-applied data and checks
Import of as-applied data from the terminal, comparison with the prescription map, and a report on rate deviations, gaps and overlaps by field, zone and implement.
Results by zone
Next season's yield by zones with different rates, so the agronomist judges decisions by data from their own fields rather than by advertising promises.
Formats and data sources
askcust works with the data machinery and labs provide; for map-based application the implement and terminal must support variable rate, for example the ISOBUS TC-GEO functionality.
- ISOXML (ISO 11783-10)
- Shapefile
- GeoJSON / KML
- yield maps from combine terminals
- soil lab results (Excel / CSV)
- Sentinel-2 / Sentinel Hub
- digital field map
- machinery manufacturers' cloud services (where API access exists)
- REST APIs
A machinery maker's software or your own data pipeline
| criterion | Machinery maker's or agri platform's software | Precision farming software by askcust |
|---|---|---|
| Mixed-brand fleet | Works best with its own brand's machinery; other formats are supported only in part. | Data and prescription maps for all of the farm's terminals in one place. |
| Zoning method | The provider's algorithm; how zones are built is not always visible. | Transparent rules the agronomist can see and change, with a zone stability score. |
| Your own data | Soil tests and yield data have to be converted to the platform's formats. | Lab spreadsheets, yield archives and indices are used as they are. |
| Link to records | Applied rates stay in the platform; cost records are kept separately. | Planned and applied amounts flow into the farm's field and material records. |
| Start | Fast if the whole fleet is one brand and the platform is already connected. | After a data audit and a format check on the farm's terminals. |
| When to choose | A single-brand fleet and standard application scenarios the platform covers. | A mixed-brand fleet, your own data and method, and a link to records. |
How askcust builds precision farming software
Data and machinery audit
Which layers already exist (soil tests, yields, indices), in which formats, and what the farm's terminals and implements can do. The result is a list of fields where variable rate application is possible this season.
Pilot on a few fields
Zones and a prescription map for a few fields of one crop; the file is tested on the actual terminal before work starts so that format, units and rates match.
Data pipeline
Automatic loading and cleaning of data, zones and prescription maps for all fields, export for each terminal model and import of as-applied data.
Checking the result
Reports on as-applied deviations from the prescription, yields by zone after harvest, and rule and zone adjustments with the agronomist before the next season.
examples of askcust's work →not agriculture, but the same kind of task: records, CRM, automation
questions and answers
Which prescription map formats are supported?
ISOXML (ISO 11783-10) for ISOBUS terminals and Shapefile for terminals that accept maps in that format. Attribute structure and rate units differ between models, so askcust sets up the export for the farm's specific terminals and tests the file on the actual machine before work starts.
Is special equipment needed for precision farming?
For variable rate application, yes: the implement must be able to change the rate on the move, and the terminal must read the prescription map, for example through the ISOBUS TC-GEO functionality. askcust's software installs nothing on machinery and sells no hardware: it prepares data for what the farm already has and checks the result.
Where do field productivity zones come from?
From several seasons of data: yield maps, vegetation indices and, where available, soil sampling and terrain. Zones from one year or one image are unreliable, so the software shows how stable they are between seasons, and the final boundaries are agreed with the agronomist who knows the field best.
Can yield maps be imported from a combine?
Yes, if the combine terminal exports them in a standard format such as ISOXML or Shapefile, or through the manufacturer's cloud service with API access. Raw data is cleaned of false points, and maps from different years and combines are brought onto one grid so they can be compared.
How much does precision farming save?
askcust does not quote savings percentages: the result depends on field variability, crop, prices and data quality. The software provides a way to check: yields by zones with different rates on the farm's own fields, so the effect is judged by your data after the season, not by advertising figures.
How much does precision farming software cost?
The cost depends on the number of data layers and sources, the terminal models that need exports and how closely it links to records, not on the area. You can start with a pilot on a few fields of one crop; askcust estimates it with a fixed scope after the data and machinery audit. Field data, zones and prescription maps are stored on the farm's own server or cloud.
Describe your data and machinery; askcust will propose a pilot
A reply within one business day; a call only if we agree on one.