Severity: Warning. The file may be accepted, but something is probably wrong, or the evidence in your statement is weaker than it should be.
Fixed automatically?: Yes, in one click. The change is listed in the change log.
In short: Split the collection into one feature per shape. We can flatten it into a plain FeatureCollection.

What the Information System does

Not clearly documented. The specification lists GeometryCollection ("Two or more geometries") among its type strings (GeoJSON File Description, Definitions), but neither file variant nor any example uses it, and the GeoJSON standard discourages it (RFC 7946, §3.1.8). We warn rather than fail (Our own check, not an Information System rule).

Why it happens

A GeometryCollection bundles several geometries (a point and a polygon, say) into one feature with one set of properties. It is valid GeoJSON, but it raises a question the specification does not answer: which of the shapes is the production place, and which does the Area belong to?

We have not found any official statement that the Information System processes these, and none of the examples use one. Rather than call it an error on no evidence, the checker warns, and offers to split the collection into ordinary features, which are certainly accepted. We re-check this every time the specification changes.

A broken example

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerCountry": "CI",
        "ProductionPlace": "Collection",
        "Area": 1.2
      },
      "geometry": {
        "type": "GeometryCollection",
        "geometries": [
          {
            "type": "Point",
            "coordinates": [-5.123456, 6.123456]
          },
          {
            "type": "Polygon",
            "coordinates": [
              [
                [-5.123456, 6.123456],
                [-5.122456, 6.123456],
                [-5.122456, 6.124456],
                [-5.123456, 6.124456],
                [-5.123456, 6.123456]
              ]
            ]
          }
        ]
      }
    }
  ]
}

What the checker reports for this file:

This plot is a GeometryCollection. The specification lists the type but no official example uses one, so we cannot promise the Information System will process it., line 12, column 17

Before. Centred on 6.1240° N, 5.1230° W.

After the fix. Split plot 1 into 2 plots, one per shape in its GeometryCollection. Each keeps the original properties. Check that Area and ProducerCountry are right for each one. Centred on 6.1240° N, 5.1230° W.

Fix it in EUDRplot

Open the file in the checker. The collection is highlighted with the geometries it contains.
Split it. Choose Split the GeometryCollection. A collection holding one geometry is replaced by that geometry; one holding several becomes one plot per geometry, each with the original properties.
Check the new plots. Look at the result on the map before downloading: points and polygons that were grouped together are now separate plots.

Fix it in QGIS

Split multi-part features. Run Multipart to singleparts from the Processing Toolbox. QGIS stores a layer as one geometry type, so a collection mixing points and polygons may have to be loaded twice, once per type.
Export. Save Features As… GeoJSON, EPSG:4326, and check the result.

Try it: check the example, or your own file

Drop a GeoJSON, KML, shapefile or CSV here, or .

Open the full checker

Checked in your browser. The file is not uploaded, stored or sent anywhere.

Sources

EUDR GeoJSON File Description (EUDR Information System help, updated 17 August 2026), Definitions, European Commission
RFC 7946: The GeoJSON Format, §3.1.8, Internet Engineering Task Force
Our own check, not an Information System rule, recorded as A3 in our specification notes

Rule STRU-006, rule set 2026.09.2. The same rule runs in the checker, the free tools and the command-line tool.

Last verified against these sources on 23 September 2026.