Error PROP-001
Misspelled property names: productionplace, geomerty, producer_country
Property names are case-sensitive. "productionplace" and "geomerty" are not recognised, so the value is silently ignored and the field arrives empty.
- 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
- Correct the spelling and the capitals. We can rename every occurrence at once.
What the Information System does
It does not recognise them. Invalid property names ("incorrect property keyword case – "productionplace" instead of "ProductionPlace"") are one of the common file errors (GeoJSON File Description, Common errors 9), and "any other properties that are syntactically valid but not included in the optional properties list … will be ignored" (GeoJSON File Description, Definitions). A misspelled geometry means the feature has no shape.
Why it happens
The Information System reads exactly four properties, spelled exactly like this:
| Property | What it holds |
|---|---|
ProducerName | The producer's name |
ProducerCountry | Two-letter ISO country code |
ProductionPlace | A name for the plot |
Area | Hectares, as a number (used for points) |
Anything else is ignored, including productionPlace, Producer_Name, area_ha and
Country. The trouble is that "ignored" is silent. A file with area instead of Area
is accepted, and every point in it is treated as four hectares.
The checker compares each property name against the four and flags names within a
couple of letters of one of them, or differing only in capitals. The specification's
own list of mistakes includes geomerty, a misspelled geometry, which leaves the
feature with no shape at all.
A broken example
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {
"ProducerCountry": "CI",
"productionplace": "Wrong case",
"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:
Fix it in EUDRplot
- Open the file in the checker. Every near miss is listed with the name it was probably meant to be.
- Rename them. Choose Correct the property name, or Fix N safe problems to rename every occurrence at once. Values are not touched.
Fix it in QGIS
- Rename the fields. Run Refactor fields from the Processing Toolbox. In the field mapping, set the output names to exactly
ProducerName,ProducerCountry,ProductionPlaceandArea. - Export. Save the refactored layer as GeoJSON in EPSG:4326.
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), Common errors 9, European Commission
- EUDR GeoJSON File Description (EUDR Information System help, updated 17 August 2026), Definitions, European Commission
Rule PROP-001, 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 .