Documentation

Create location

In DiPAgE, open Partial Data → Location Management and select Add new item. Saved locations can then be reused directly in future plant protection product applications.

Select location reference

First choose how the location should be uniquely identified. DiPAgE supports different types of location referencing: coordinates, parcel identifier (ALKIS), InVeKoS ID (FLIK), area geometry, railway track, forest area, as well as road or path. This allows recording locations from various sectors of professional plant protection.

Describe location

Depending on the selected location reference, the necessary details will be requested. In addition, the type, value, and unit of the location size as well as a custom name for the location can be stored.

Use map features

For suitable location references, DiPAgE supports input via a map view. For instance, coordinates or areas can be selected spatially instead of entering all details manually. Official field blocks with a FLIK are currently only available for North Rhine-Westphalia.

Sequential cultivation and migratory or rotational cropping

In sequential cultivation within a fixed field, sub-parcel, or permanent facility, the field or sub-parcel remains the decisive observation unit — with the sub-parcel (Teilschlag) being the smallest observation unit. Individual batches are sub-areas of this object and do not need to be separately georeferenced or created as independent objects. The actual area treated for each batch is recorded via the treated object. The specific batch can optionally be noted in the description.

Furthermore, the crop does not need to be spatially referenced for each individual batch. In principle, the treated crop species must be stated. Especially in ornamental and vegetable production, the corresponding BVL-EPPO crop group may be specified instead under the conditions set out in the data standard, provided the plant protection product is authorized for that crop group. Arbitrary grouping of distinct crop groups is not permitted.

This is to be distinguished from migratory or rotational cropping with changing or multiple occupancy, such as succession plantings or multi-batch cycles within the production period. Here, geolocation and area specifications can be based on the operating site (Betriebsstätte). The operating site constitutes the smallest unit of observation. Individual greenhouses, outdoor plots, or other interchangeably used sections within the operating site do not need to be registered as independent, separately georeferenced objects.

How search works

Product search queries the Synops register live as you type, scoped to the crop you have already selected. It requires a connection — see Offline usage for what to do without one. The search supports product name and registration number; parallel imports are grouped directly under their reference product.

Crop-first workflow

The product and dosage section is locked until you select a valid crop via its EPPO code. This is intentional: DiPAgE requires a crop-first approach so that no product is recorded for a crop for which it is not authorized. Once the EPPO code is confirmed, the entire product section unlocks and the Synops API filters results to that crop.

Hazard-aware application timing

DiPAgE reads the hazard classification of each product from the Synops response. Products with a bee-toxicity hazard class make an application time field mandatory. An informational banner explains the requirement and how to resolve it: open the Informative section, choose a specific indication and application time — the time restriction is automatically removed and the selected indication is added to the record notes for regulatory compliance.

Emergency-authorized products (Art. 53)

Products under an emergency authorization do not carry a regular registration number, so DiPAgE searches for these by product name only, restricted to the selected crop — the same emergency-authorized name may be permitted for one crop and not for another. Choose a match from the list or continue typing if it has not yet been found.

Keeping crop and emergency authorization data up to date

Unlike product search, the crop list, emergency authorizations, and bee-protection requirements are stored on your device. DiPAgE updates them automatically on start-up once the stored data is older than 30 days, and when you switch the app language. If a crop or product you expect is missing, use Refresh database at the bottom of the search list; it also shows when the data was last synced. Product and indication search remains live; no updates or synchronizations occur there.

Machine-readable exports

DiPAgE supports exporting application records as XML, CSV, and JSON. These formats are machine-readable and designed for the legally compliant electronic export of documented plant protection product applications. Exported files can be opened in any text editor; do not edit them by hand, though — make changes in DiPAgE instead, otherwise importing them again may fail.

PDF for human-readable presentation

In addition, records can be output as PDF. The PDF is intended for clear presentation and human filing. Because it is not machine-readable, it does not constitute a legally compliant electronic export.

Filter and batch export records

In the Records → Filter & Export section, saved applications can be filtered by location, plant protection product, crop, or treated object. The selected records can then be exported individually or in batches in one of the available formats.

Information in PDF

Under Profile, personal details such as first name, last name, and email address, as well as company name and address, can be stored. This information is used exclusively for generating PDF reports.

Passing data on

DiPAgE does not automatically transmit stored documentation data to a server or third parties. If you want to pass records on to an advisory service or an authority, export them in the required format and send the file yourself.

What works without internet

DiPAgE stores the application and your documentation data locally on the device used. Therefore, you can fill out forms, save, edit, and export records even without an internet connection. Generating PDF files is also possible offline.

Which features require internet

Some features access live external data sources and therefore require an internet connection. These include, in particular, searching for plant protection products and indications, as well as map display and selection.

If the connection drops during entry

A lost connection does not mean your previous entries are lost. You can generally continue documenting and save your work. Features that require live online data will be temporarily unavailable. The corresponding details can also be entered manually where provided.

Back up local data regularly

Since your data is stored on the device you use, we recommend regular backups. Especially on mobile devices, browsers may clear stored data under certain circumstances, such as when freeing up storage space. Via data backup in DiPAgE, you can download a complete backup of your data and restore it whenever needed.

Where your data is stored

Your application records, partial data, and details regarding your user profile and company are stored locally in the browser on the device used. Technically, DiPAgE uses the browser's local storage (IndexedDB) for this purpose. Your saved documentation data is not automatically transmitted to the Julius Kühn-Institut or anywhere else.

When an internet connection is used

Certain functions access external online services, such as searching for plant protection products or displaying maps. During such queries, the information required for the respective request as well as, for technical reasons, the IP address are transmitted. Your locally stored application records are never sent along.

What leaves the device

Your documentation data leaves the device only when you trigger an export yourself and pass the file on. You decide which data you share, when, and with whom.

Deleting local data

You can remove locally stored data at any time via your browser settings (clearing saved website data for DiPAgE) or, if the app is installed, through your operating system's app settings (clearing app storage).

DiPAgE cannot be installed

Not every browser automatically displays an installation prompt. Therefore, open the browser menu and look for an option such as Install app or Add to Home Screen. If this option is not displayed, you can still continue using DiPAgE directly in your browser.

Crop list or emergency authorizations are not up to date

This information is updated automatically via the internet. First check whether your device is connected to the internet. You can then trigger the update yourself via Refresh database in the crop search list. If that still does not work, try again later.

Plant protection product search returns no results

Searching for plant protection products and indications requires an internet connection. Therefore, check your connection first. If no connection is available, the required details can also be entered manually where provided.

My device reports low storage space

DiPAgE stores your data locally on the device used. When free storage space is very low, the browser may evict stored application data under certain circumstances. Therefore, regularly create a data backup via the Profile section and store it in a safe location.

The plant protection product section is unavailable

Check whether you have selected a crop beforehand. In the form, select the desired crop by name or EPPO code. The corresponding input fields for plant protection products will then become available.

DiPAgE additionally requests an application time

For certain plant protection products, specifying the application time may be required due to the associated conditions of use. In this case, DiPAgE alerts you during entry. Complete the requested details accordingly in the form.

A record is incomplete and cannot be exported

DiPAgE highlights missing required information. Open the affected record and fill in the highlighted fields. After saving again, the complete record can be exported.

I want to delete all local data

You can delete all stored data through your browser settings by clearing the website data for DiPAgE. If you have installed the app, you can clear its storage via your device's app settings. Make sure to back up any data you may still need beforehand using the export or backup feature.

Importing a backup

Go to Profile → Data Management → Import Backup and select the backup file (.zip) from your previous device. After a confirmation, DiPAgE compares each record with existing records that have the same ID. Identical records are skipped automatically; partial data, profile, and app settings are taken over from the backup.

Importing files

In the Records section, you can read in files in .json, .csv, .xml, or .zip format via Import — including an XML export file you filled in yourself in Excel. If a record is missing required details, DiPAgE shows it for review first: you decide whether it is imported anyway. It is then marked as incomplete and excluded from exports until it is completed.

Conflict resolution

When an imported record differs from a local one, the import dialog shows both versions side by side. Tap a version to select it, or keep the local record unchanged. If two records have different IDs but the same content — for example because the same file was imported twice — you can also choose Keep both. Each conflict can be resolved individually before saving.

What the red highlight means

Every property that differs between the imported and local version is marked in red — including composite fields such as operator name and GPS coordinates. The visual comparison covers timestamps, authorization numbers, usage type, BBCH stage, and all standard fields.

Treat multiple objects together

In the Object Manager on the home screen, switch on Multi-select mode and tick at least two objects with the same crop; objects with a different crop are marked Different crop and cannot be combined. Then choose Add application of plant protection product. This eliminates the need to create comparable applications individually for each object.

Change the location or usage context of an object

In the Object Manager, choose Edit Location for the group on the object's card. The form switches to Group Edit: change the location or usage context and save — the change applies to all applications recorded for this object. The plant protection product section stays locked in this mode.

Tank mixes and multiple plant protection products

In Tank Mix mode, multiple plant protection products can be recorded within the same application. Each product is documented with its own details, such as application rate. Frequently used combinations can be saved via Save tank mix on the first product's card and reused in future applications.

Multiple location references for the same object

If needed, multiple location references can be stored for a single object. These always refer to the same object and the same location, which is merely described in different ways. The function therefore does not serve to record multiple different locations within one object.