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?
No, this needs a decision only you can make.
In short
Check the country code and the coordinate order. This is our own plausibility check, not a rejection reason in the Information System.

What the Information System does

This is our own plausibility check, not a documented rejection reason. The validation rules require a valid country for every production place (Information System validation rules, Production country); whether the plot lies inside it is not a check the documentation describes (Our own check, not an Information System rule).

Why it happens

A plot declared as Ghanaian that sits in Côte d'Ivoire is not something the documentation says the Information System checks. It is, however, something anyone reviewing the statement would notice, and it almost always means something went wrong in the file.

For now the test is deliberately loose: the centre of the plot is compared with a padded rectangle around the declared country, not with its border. That means it can miss a plot that is just across a frontier, but it cannot flag a plot that is really inside the country. A test against real borders is planned. It is a warning, and the message says it is our own check.

A broken example

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerName": "Coopérative Example",
        "ProducerCountry": "BR",
        "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]
          ]
        ]
      }
    }
  ]
}

What the checker reports for this file:

  1. This plot sits at -5.12306, 6.12386, which is outside BR. Check the country code and the order of the coordinates. This is our own check, not a reason the Information System would reject the file., line 14, column 24
Before1
Before. Numbered circles mark where the checker located the problem. Centred on 6.1240° N, 5.1230° W.

Fix it in EUDRplot

  1. Open the file in the checker. The plot is drawn on the map with the declared country named.
  2. Check the coordinate order. If swapping latitude and longitude would put the plot in the country, the checker says so and offers Swap longitude and latitude.
  3. Otherwise check the code or the source. A wrong ProducerCountry, or a plot copied in from another supplier's file, are the other usual causes. Correct whichever is wrong.

Fix it in QGIS

  1. Load country boundaries. Add a country boundary layer, for example Natural Earth's Admin 0 countries.
  2. Compare. Run Join attributes by location with the plots as the base layer and countries as the join layer, then select features where the joined country code differs from ProducerCountry.

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 PLAUS-001, 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 .