Skip to content

GGU-FIELDCAPACITY: Exchanging data with GGU-CONNECT

GGU-FIELDCAPACITY takes over samples from GGU-CONNECT and hands the results back there. The exchange works through a GGUML file (.xml extension). The commands are in the GGU-CONNECT menu and, with the same names, in the File menu. Available from version 0.10.

Importing samples from GGU-CONNECT

  1. In GGU-CONNECT, export the samples as a GGUML file. At most six samples fit on one sheet, so export only the samples for one sheet. If the file contains more, all of them are taken over, but the sheet only appears once you have removed enough of them under Edit / Samples to leave six at most.
  2. In GGU-FIELDCAPACITY, choose GGU-CONNECT / Import data from GGU-CONNECT… and open the file.

The file replaces the open project. The program does not ask for confirmation, so save an open project first. The imported project is not yet linked to a project file; the first time you Save, the program asks for a name.

A file may contain only one project. If it contains several, a message appears and the open project stays unchanged.

What is taken over

  • from the project: project number, project name, client and operator,
  • one column per sample with sample name, borehole and sampling depth,
  • clay, silt, sand and gravel, the dry bulk density and the TOC or humus content.

Company and logo, report and annex number and the sheet headings are empty afterwards; enter them under Project and company.

The program looks for the values first in the sample's KA5 experiment, then on the sample itself and in its other tests, for example the sieve and sedimentation analysis. Samples without usable values are still taken over as an empty column.

If a value has different entries, the field stays empty and a message names the sample; enter the value by hand in that case. If both TOC content and humus content were measured, the program takes over the TOC content and calculates the humus content from it. If there is no humus content, it takes over the loss on ignition as the humus content; in clayey soils the loss on ignition is higher than the humus content, so the humus class and the surcharge then come out too high.

Several KA5 experiments on one sample

If a sample in GGU-CONNECT has several KA5 experiments, the program asks before opening, for each such sample, which experiment you want to work with. To help you decide, the dialog shows the status, date of change, operator and values of each experiment. Only the chosen experiment is read and overwritten when the results are handed back. The others stay in GGU-CONNECT. Cancel leaves the open project unchanged.

Mixed samples

A mixed sample becomes a column of its own. It has no borehole and no sampling depth. Whether a column is a sample or a mixed sample is shown in the Samples dialog; on the sheet you can show the row "Sample type" for this (see Evaluation sheet).

Protected values

Values from GGU-CONNECT carry a lock in the Samples and Project dialogs and cannot be changed by accident. A click on the lock unlocks the value. If you then change it, it counts as your own input. The protection is kept when you save the project file and open it again (see Entering samples).

Handing results back to GGU-CONNECT

  1. Choose GGU-CONNECT / Export data to GGU-CONNECT. The program writes the file FIELDCAPACITY-CONNECT-EXPORT.XML to this folder and shows the path: 
    %APPDATA%\GGU-Software\GGU-CONNECT
  2. In GGU-CONNECT, read the file in with the "GGUML file" import. The folder is hidden in Windows; paste the path into the address bar of the file dialog. The results go to the existing samples, not into a new project.

GGU-CONNECT / Export GGU-CONNECT data as GGUML… saves the same file to a location of your choice, for example the project folder.

If the KA5 experiment of a sample was already marked as done in GGU-CONNECT when you took the sample over, the program asks before handing the results back. Hand over anyway overwrites the results there, Cancel writes nothing.

What is handed back

  • One KA5 experiment per sample with all input and all calculated values, regardless of which rows are shown on the sheet. As operator, the program enters the operator from Edit / Project. The status is "done" (erledigt) if all results have been calculated, otherwise "in progress" (in Bearbeitung).
  • In addition, directly on the sample: soil type according to KA5, field capacity, air capacity and available field capacity of the soil.
  • The master data project number, project name, client, operator, borehole, sample name and depths: with your change, otherwise as they were read when the samples were taken over. A field you have emptied does not count as a change.

Handing the results back again updates the same KA5 experiment and does not create a second one.

If you have unlocked and changed a value that comes from another test, for example a grain fraction from the sieve and sedimentation analysis, that test stays unchanged. The new value is stored in the KA5 experiment.

What is not handed back

  • Samples that were only created or duplicated in GGU-FIELDCAPACITY.
  • Results that could not be calculated. The sample is still handed over, and a message names it. An older result from an earlier hand-over stays in GGU-CONNECT and may then no longer match the input; remove it there.
  • Input you have emptied. Its previous value stays in GGU-CONNECT and is read again the next time you take the project over; a message points this out.

Caution: if someone changes the master data or the KA5 experiment in GGU-CONNECT after you have taken the samples over, handing the results back overwrites that change. In that case, take the samples over again.