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
Re-save the file as UTF-8 from your editor or GIS tool.

What the Information System does

The GeoJSON standard requires UTF-8 (RFC 7946, §12). The Information System's documentation does not describe what it does with other encodings; in practice a byte that is not valid UTF-8 either stops the file being parsed or arrives as a replacement character in the producer's name.

Why it happens

UTF-8 can write every accent in every language. Older encodings (Windows-1252, ISO-8859-1) write the common Western European ones as a single byte that UTF-8 treats as invalid. The file looks perfect in the program that made it, and broken everywhere else.

This matters more for EUDR files than most, because producer and cooperative names are full of accents: Coopérative, São João, Asociación, Nông trại. A name that arrives as Coop�rative is no longer the name of anyone.

Common sources: Excel's plain "CSV" save on Windows, older GIS exports, and databases exported with default settings.

A broken example

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

What the checker reports for this file:

  1. The file contains 1 character that could not be decoded as UTF-8. Producer names with accents are the usual casualty.
Before
Before. Centred on 6.1240° N, 5.1230° W.

Fix it in EUDRplot

  1. Open the file in the checker. The checker reads the bytes before decoding them, so it can tell a UTF-8 file from one saved in another encoding.
  2. Re-save the file as UTF-8 at the source. In the program that made it, choose UTF-8 when saving or exporting. In Excel, use CSV UTF-8 rather than plain CSV. Then open the new file in the checker.
  3. Check the names. Look at a producer name with an accent (é, ã, ñ, ç) in the editor. If it reads correctly, the encoding is right.

Fix it in QGIS

  1. Tell QGIS the real encoding. Layer › Add Layer › Add Vector Layer, choose the file, and set Encoding under Options to the one it was saved in, usually windows-1252 for files from Western European Windows machines.
  2. Check the attribute table. Open the attribute table and confirm the accented names now read correctly.
  3. Export as GeoJSON. Right-click › Export › Save Features As…, format GeoJSON, CRS EPSG:4326. QGIS writes GeoJSON as UTF-8.

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-005, 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 .