Severity
Error. The Information System rejects the file, or silently stores something other than what you meant.
Fixed automatically?
No, this needs a decision only you can make.
In short
Add a ProducerCountry with the two-letter country code to every feature, or import the file at producer level instead.

What the Information System does

A Type II file, imported through the web interface at commodity level, "contains multiple producers grouped by the "ProducerName" and "ProducerCountry"" and "includes the "ProducerCountry" property per "Feature"" (GeoJSON File Description, File Variants Description, Type II). Without it the grouping the system relies on is incomplete, and the validation rules require every production place to have a valid country (Information System validation rules, Production country).

Why it happens

The specification describes two variants of the same file (GeoJSON File Description, File Variants Description). Type I is used at producer level, through the API or the web interface. Type II is used at commodity level, and carries plots for many producers in one file, so each feature has to say whose it is and which country it is in.

The checker decides which variant a file is from its contents: a file with more than one ProducerName is treated as Type II. If that guess is wrong for your file, it is worth knowing before you upload it.

The code is the two-letter ISO 3166-1 code: CI for Côte d'Ivoire, BR for Brazil, ID for Indonesia, never the three-letter code or the country's name.

A broken example

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerName": "Producer A",
        "ProducerCountry": "CI",
        "ProductionPlace": "Parcelle 1",
        "Area": 1.2287
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [-5.123456, 6.123456],
            [-5.122456, 6.123456],
            [-5.122456, 6.124456],
            [-5.123456, 6.124456],
            [-5.123456, 6.123456]
          ]
        ]
      }
    },
    {
      "type": "Feature",
      "properties": {
        "ProducerName": "Producer B",
        "ProductionPlace": "Farm B",
        "Area": 1.2
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [-1.123456, 5.623456],
            [-1.1224559999999997, 5.623456],
            [-1.1224559999999997, 5.624456],
            [-1.123456, 5.624456],
            [-1.123456, 5.623456]
          ]
        ]
      }
    }
  ]
}

What the checker reports for this file:

  1. This file carries several producers, so every plot needs a ProducerCountry. This one has none., line 42, column 21
Before
Before. Centred on 5.8740° N, 3.1230° W.

Fix it in EUDRplot

  1. Open the file in the checker. Every feature missing ProducerCountry is listed and highlighted on the map.
  2. Add the code. Add "ProducerCountry": "CI", with the right two-letter code, to the properties of each listed feature in the editor. The map shows which country each plot is in.
  3. Or import it as Type I. If the file really is one producer's plots, it can be imported at producer level, where ProducerCountry is optional. The Type I and Type II guide explains the difference.

Fix it in QGIS

  1. Select the plots without a country. Select by expression: "ProducerCountry" IS NULL OR "ProducerCountry" = ''.
  2. Fill in the code. Open the Field Calculator, tick Update existing field, choose ProducerCountry, and set the expression to the code in quotes, for example 'CI', with Only update selected features ticked. Repeat per country.
  3. Export. Save Features As… GeoJSON, EPSG:4326, and check it again.

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

Rule FILE-007, 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 .