ISOXML, shapefile and GeoJSON: formats for switching farm software
Which file formats matter when you switch farm record software, what ISOXML, shapefile, GeoJSON and CSV contain and what to watch when exporting and importing.
Key points
- Shapefile: the standard for field boundaries, for example from the subsidy application. It consists of several files that belong together.
- GeoJSON: a simple text format for geometries, always in geographic coordinates (WGS84).
- ISOXML: standard ISO 11783-10 for exchange with terminals; its core is the file TASKDATA.XML with tasks, fields and quantities.
- CSV: a table for records and master data; machine-readable and therefore suitable for plant protection records from 2027.
- PDF: good for reading and archiving, but not machine-readable.
Try PhytAI free for 30 days
- No payment details needed
- Export all your data as CSV, JSON and Shapefile at any time
- from €59.00 a year
Anyone switching farm record software quickly comes across file extensions such as .shp, .xml or .geojson. Behind them are open formats exchanged between programs, terminals and authorities. This article explains the most important formats, what they contain and how to avoid typical import problems.
Shapefile: field boundaries from applications and software
The shapefile is a geodata format described by Esri. A "shapefile" always consists of several files with the same name:
| File | Content |
|---|---|
| .shp | the geometries, i.e. the outlines of the fields |
| .shx | the index that makes geometries quick to find |
| .dbf | the attributes as a table, for example field name and FLIK |
| .prj | the coordinate reference system, for example ETRS89/UTM or WGS84 |
Without .shx and .dbf the data cannot be read meaningfully; without .prj the program has to guess the coordinate system. This is why shapefiles are usually passed on as a ZIP folder. Do not unzip the folder if you are importing it into other software.
Typical sources: field lists from the subsidy application programs of the German federal states, exports from farm record software, GIS programs.
GeoJSON: simple and readable
GeoJSON is described in the IETF standard RFC 7946. A GeoJSON file is a text file that contains areas as lists of coordinates with associated properties. The standard specifies WGS84 with longitude and latitude as the coordinate system. This simplifies exchange because no .prj file is needed.
GeoJSON is well suited for web applications and for exchange between programs. Many state portals and subsidy application programs, however, tend to offer shapefiles.
ISOXML: the language of terminals
ISOXML is the common name for data exchange according to ISO 11783-10, part of the ISOBUS series of standards. An ISOXML transfer consists of the file TASKDATA.XML and often further binary files. It contains:
- tasks with customer, farm and field
- field boundaries and guidance lines
- products, quantities and application maps
- after the work, the documented data such as times and quantities applied
ISOXML is ideal for sending tasks to a terminal and retrieving the results. For a complete plant protection record, however, the terminal often lacks details such as the EPPO code or the authorisation number; these come from the farm record software.
ISOXML files from different manufacturers can differ in details. After an import, check whether fields, quantities and units arrived correctly.
CSV: tables for records
CSV stands for "comma-separated values". In Germany the semicolon is common as a separator because the comma is the decimal mark. A CSV file has a header row with column names and one record per row.
CSV is the obvious format for:
- plant protection and fertiliser records
- master data such as fields and crops
- stock movements and harvest
The German plant protection services name CSV, alongside JSON and XML, as a suitable machine-readable format for plant protection records from 2027. More in Electronic plant protection records from 2027.
Coordinate systems in brief
Geodata describe places with coordinates, and the numbers depend on the coordinate system. In Germany, agricultural administrations mostly use ETRS89 with UTM projection for fields; the values are then metres, for example easting and northing. GPS devices, smartphones and GeoJSON use WGS84 with longitude and latitude in degrees. Both systems describe the same location, but with different numbers. If a program reads UTM metres as degrees, fields end up far outside Europe or become huge. That is why the .prj file matters so much for shapefiles, and why it is worth looking at the map and the calculated field sizes after every import.
Typical import problems
| Problem | Cause | Solution |
|---|---|---|
| fields appear in the sea or are huge | wrong or missing coordinate system | include the .prj file or choose the correct system |
| file is not recognised | shapefile unzipped, individual files missing | use the complete ZIP folder |
| broken umlauts | character encoding of the CSV | choose UTF-8 or Windows-1252 when opening |
| wrong numbers | decimal comma and thousands separator mixed up | check separator and number format |
| duplicate fields | names differ slightly | match by field identifier (FLIK) |
Checklist for exporting from your old software
- Export field boundaries as a shapefile (ZIP) or GeoJSON.
- Export records per harvest year as CSV.
- Save reports as PDF for the archive as well.
- Save terminal data as ISOXML, if available.
- Open each file briefly and check that it is complete.
The steps for 365FarmNet are described in Back up your data from 365FarmNet.
Formats in PhytAI
PhytAI imports field boundaries from shapefiles (ZIP, ETRS89/UTM or WGS84), GeoJSON and ISOXML and suggests the columns for name and field identifier. Master data come in via CSV templates. Boundaries are exported as GeoJSON and shapefile, records as CSV, JSON and XLSX, and the whole organisation as a ZIP with all tables and files.
Frequently asked questions
Which format is best for field boundaries? For exchange with authorities and most farm record software, the shapefile is the most widespread. GeoJSON is simpler but not offered everywhere.
Can I open ISOXML in Excel? ISOXML is an XML file and can technically be opened, but it is hard for people to read. Use software that understands ISOXML, such as your farm record software or the terminal manufacturer's program.
Is an Excel file machine-readable? A well-structured table is, especially when saved as CSV. What matters are fixed columns and complete details.
Sources
- ISO: ISO 11783-10: Task controller and management information system data interchange, retrieved 16 Sep 2026
- IETF: RFC 7946 – The GeoJSON Format, retrieved 16 Sep 2026
- Esri: ESRI Shapefile Technical Description, retrieved 16 Sep 2026
- Free and Hanseatic City of Hamburg: EU implementing regulation on digital, machine-readable documentation, retrieved 13 Sep 2026
This article reflects the situation on the date shown, based on the sources named, and is not legal advice. Laws, approvals, official decisions and the guidance of the competent authorities prevail.