Error COORD-006
Coordinates not in WGS84 degrees (UTM, national grid, Web Mercator)
The Information System accepts only WGS84 (EPSG:4326) in decimal degrees. Projected coordinates such as UTM metres are not converted for you.
- Severity
- Error. The Information System rejects the file, or silently stores something other than what you meant.
- Fixed automatically?
- Yes, after you have seen the change in hectares and accepted it.
- In short
- Tell us the source system, or let us guess it from the values, and we will reproject to WGS84.
What the Information System does
It does not convert them. The specification supports WGS 84 in decimal degrees exclusively: "If the geocoordinates available to the Economic Operator are in another coordinates system, these must be converted to the WGS84 (EPSG:4326) coordinate system with longitude and latitude units of decimal degrees" (GeoJSON File Description, Introduction).
Why it happens
WGS 84 in degrees is what GPS receivers report and what GeoJSON uses. But much survey, cadastral and forestry data is kept in a projected system, which flattens the Earth onto a grid and measures in metres: UTM zones, national grids, or Web Mercator from web maps.
You can usually tell at a glance:
| What the numbers look like | What they probably are |
|---|---|
-4.377412, 5.324871 | WGS 84 degrees: fine |
458213.4, 588641.9 | UTM or a national grid, metres |
-487254.1, 593810.6 | Web Mercator (EPSG:3857), metres |
Converting is exact when the source system is known. The risk is guessing it wrong. The checker only guesses when exactly one UTM zone puts every plot inside the declared country, and says that it guessed.
A broken example
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"ProducerCountry": "CI",
"ProductionPlace": "UTM metres",
"Area": 1.2
},
"geometry": {
"type": "Polygon",
"coordinates": [
[
[486123.45, 677123.45],
[486223.45, 677123.45],
[486223.45, 677223.45],
[486123.45, 677223.45],
[486123.45, 677123.45]
]
]
}
}
]
}What the checker reports for this file:
Fix it in EUDRplot
- Open the file in the checker. Coordinates in metres are detected from their values. If the file declares its system, the checker uses that.
- Convert. Choose Convert to WGS84 degrees. If the system cannot be worked out (no declaration, and more than one UTM zone could fit) you are asked to choose, with the likely candidates listed for the declared country.
- Check where the plots land. The converted plots are drawn on the map. Check they are where they should be before downloading. The conversion is recorded in the change log and the PDF report.
Fix it in QGIS
- Set the layer's real CRS. If QGIS does not know the system (no .prj file), set it in Layer Properties › Source › Assigned coordinate reference system, or run Assign projection. Choose the system the data was surveyed in.
- Reproject on export. Save Features As… GeoJSON with CRS EPSG:4326 – WGS 84, or run Reproject layer first.
- Check against a basemap. Load the exported file over a satellite layer. A wrong UTM zone puts plots hundreds of kilometres away.
Try it: check the example, or your own file
Drop a GeoJSON, KML, shapefile or CSV here, or .
Checked in your browser. The file is not uploaded, stored or sent anywhere.
Sources
- EUDR GeoJSON File Description (EUDR Information System help, updated 17 August 2026), Introduction, European Commission
Rule COORD-006, 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 .