Severity
Error. The Information System rejects the file, or silently stores something other than what you meant.
Fixed automatically?
Yes, in one click. The change is listed in the change log.
In short
Remove the outer brackets. We can do this for every affected point at once.

What the Information System does

"Point geometry types consist of two coordinate values" (GeoJSON File Description, Definitions): one position, not a list of them (RFC 7946, §3.1.2). Version 1.5 of the specification lists this exact mistake among its data representation issues: "The coordinates for points should be array and not array of arrays" (GeoJSON File Description v1.5, §6.14).

Why it happens

A Point is a single position: [longitude, latitude]. Wrapping it in another pair of brackets makes it a list of positions, which is what a MultiPoint or a LineString is, not a Point.

We follow the normative text and the GeoJSON standard: the example is wrong, and the fix is to remove one pair of brackets.

A broken example

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerCountry": "CI",
        "ProductionPlace": "Nested point",
        "Area": 2
      },
      "geometry": {
        "type": "Point",
        "coordinates": [
          [-5.123456, 6.123456]
        ]
      }
    }
  ]
}

What the checker reports for this file:

  1. This Point's coordinates are [[lon, lat]] instead of [lon, lat]. The Information System renders no coordinates for it, so the plot vanishes without an error., line 13, column 24
Before
Before. Centred on 6.1235° N, 5.1235° W.
After the fix
After the fix. Unwrapped the coordinates of plot 1 so the point has a position again. Centred on 6.1235° N, 5.1235° W.

Fix it in EUDRplot

  1. Open the file in the checker. Every nested point is listed; the map cannot place them until they are fixed.
  2. Unwrap them. Choose Unwrap the point, or Fix N safe problems to do it with the other safe fixes. [[-4.377412, 5.324871]] becomes [-4.377412, 5.324871] and nothing else changes.
  3. Fix the template. If your file was generated from a template or a script, fix the extra brackets there too, or the next file will have the same problem.

Fix it in QGIS

GDAL, which QGIS uses to read GeoJSON, may refuse or misread a point written this way, so the fix is in the text: remove the outer pair of brackets around each point's coordinates. The checker does this for every point in one step.

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 STRU-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 .