Error catalogueEUDReudr.geo.geometry-type

EUDR GeoJSON rejected: geometry type not accepted

A production place must be a Point, Polygon or MultiPolygon — lines and other geometry types are refused.

BlockingFix at the source

What the check requires

The geometry must be one of the types accepted for the selected EUDR upload mode. Type II accepts Point, MultiPoint, Polygon and MultiPolygon; Type I also accepts a GeometryCollection whose nested geometries are valid.

A blocking error — this record cannot pass deterministic validation until it is resolved.

Why this is reported

The most common cause is a boundary recorded as a GPS track: walking the field edge produces a LineString, and many tools export it unchanged. A line has no interior, so the registry cannot compute an area from it.

GeometryCollections, missing geometries and other exotic types fail for the same reason — the EUDR information system only understands points and polygons.

How it gets fixed

Converting a line into a polygon is a mapping decision, not a mechanical fix — the engine cannot know whether your track was a closed boundary or an open path, so nothing is changed automatically.

In your GIS tool, convert the recorded track into a polygon (most tools call this "line to polygon" or "close path"), then run the check again. Plots below the polygon threshold can be submitted as a single point instead.

CitationEUDR GeoJSON File Description v1.5, European Commission, Type I and Type II geometry tablesprofile 1.0.5 · Effective from 2025-05-05 · captured 2026-07-16