EUDR geolocation requirements: polygons, points and GeoJSON files
Geolocation of every plot of land is at the heart of an EUDR due diligence statement. Here is when a point is enough, when a polygon is required and which GeoJSON errors make a file fail.
Posez votre question
Compte gratuit requisLes réponses sont rédigées par un modèle de langage à partir des seuls documents de cette base, avec leurs sources numérotées. Elles peuvent être inexactes et ne constituent pas un conseil juridique, médical ou financier : vérifiez les sources avant toute décision importante.
Point or polygon: the four-hectare rule
The regulation defines geolocation as latitude and longitude coordinates with at least six decimal digits. For plots of more than four hectares used for commodities other than cattle, a polygon describing the perimeter of each plot is required; smaller plots can be described with a single point.
For cattle, the geolocation refers to all the establishments where the animals were kept. When a product contains commodities from several plots, every plot must be included.
File format accepted by the information system
The EUDR Information System imports GeoJSON files in WGS 84 (EPSG:4326), decimal degrees, longitude first. Coordinates are truncated to six decimal places, so extra precision is useless and can create invalid shapes.
Type I files describe one producer; Type II files group several producers by 'ProducerName' and 'ProducerCountry'. A due diligence statement, GeoJSON files included, is limited to 25 MB, so use two points for straight lines and single points for plots under four hectares.
Questions fréquentes
What are the most common reasons a GeoJSON file is rejected?
Common errors are crossing lines, polygons with holes, open polygons whose first and last coordinates differ, LineString geometries and invalid ISO country codes. Property names are case sensitive ('ProductionPlace', not 'productionplace').
What is the default area when a point has no Area property?
The system sets it to four hectares. The value must be a number: "3" in quotes instead of 3 gives an area of zero.
How do I describe a plot shaped like a ring around a protected area?
Polygons with holes are not accepted. The documentation suggests drawing the ring as two half-doughnut polygons.
Intégrer / API / MCP
Branchez cette base à Claude, Cursor, ChatGPT ou votre propre application. Chaque requête API ou MCP coûte 0,10 €, débitée de votre crédit Kopik (non facturée si rien n'est trouvé). Il vous faut une clé API : créez-la depuis votre tableau de bord.
MCP pour vos agents
Adresse du serveur MCP de cette base (outils ask_base et search_base) :
https://kopik.io/api/mcp?base=eu-eudr-deforestationClaude Code, Cursor et autres clients
claude mcp add --transport http kopik-eu-eudr-deforestation "https://kopik.io/api/mcp?base=eu-eudr-deforestation" --header "Authorization: Bearer kpk_…"{
"mcpServers": {
"kopik-eu-eudr-deforestation": {
"url": "https://kopik.io/api/mcp?base=eu-eudr-deforestation",
"headers": {
"Authorization": "Bearer kpk_…"
}
}
}
}API REST pour vos applications
mode vaut "answer" (réponse rédigée + sources) ou "passages" (passages bruts seulement). Ajoutez un maxPriceCents facultatif pour plafonner le prix : si la base coûte plus cher, l'appel est refusé sans rien débiter.
curl -X POST https://kopik.io/api/v1/bases/eu-eudr-deforestation/query \
-H "Authorization: Bearer kpk_…" \
-H "Content-Type: application/json" \
-d '{"question": "Votre question ici", "mode": "answer"}'Pour commencer
- Créez une clé dans votre tableau de bord et rechargez votre crédit.
- Remplacez
kpk_…par votre clé. - Tout le détail (réponses, erreurs, exemples JS et Python) : documentation développeurs.