Each check has a stable rule ID so you can search for it and cite it. Errors are blocking: TRACES will reject the file. Warnings are worth fixing but may not block. The last column shows what the fixer can repair deterministically versus what needs your input (we never invent a producer name, an area, or a projection you did not give us).
| Rule | Level | What it means and why TRACES objects | Auto fix |
|---|---|---|---|
| EUDR-STRUCT-001 | error | The file is not valid GeoJSON or CSV that we can read. TRACES cannot parse the upload and rejects it before checking any plot. | manual |
| EUDR-STRUCT-002 | error | The top level is not a GeoJSON FeatureCollection. TRACES expects a FeatureCollection of plots and rejects anything else. | yes |
| EUDR-STRUCT-003 | error | The FeatureCollection contains no plots. TRACES rejects an empty geolocation file because there is nothing to check. | manual |
| EUDR-STRUCT-004 | error | The file is larger than the 25 MB upload limit. TRACES refuses uploads above 25 MB. Split the file into smaller batches. | manual |
| EUDR-STRUCT-005 | warning | The file has an unusually large number of plots. Very large files can time out in TRACES. Consider splitting into batches. | manual |
| EUDR-GEOM-001 | error | Unsupported geometry type. Only Point, Polygon and MultiPolygon are allowed. TRACES accepts only Point, Polygon and MultiPolygon and rejects the rest. | manual |
| EUDR-GEOM-002 | error | The plot has no usable geometry. TRACES rejects a plot with no coordinates. | manual |
| EUDR-CRS-001 | error | A non WGS84 coordinate system is declared. TRACES requires WGS84 (EPSG:4326). A different declared CRS is rejected. | yes |
| EUDR-CRS-002 | error | Coordinates look projected, not WGS84 longitude/latitude. TRACES requires WGS84 degrees. Values outside longitude 180 or latitude 90 are rejected. | manual |
| EUDR-COORD-001 | warning | Coordinates carry more than 6 decimal places. TRACES expects about 6 decimals. Extra precision is unnecessary and can be flagged. | yes |
| EUDR-COORD-002 | warning | Coordinates carry fewer than 6 decimal places. Low precision (under 6 decimals) can place a plot imprecisely for TRACES. | manual |
| EUDR-POLY-001 | error | A polygon ring is not closed (first and last point differ). TRACES requires closed rings and rejects a ring that does not return to its start. | yes |
| EUDR-POLY-002 | error | A polygon ring has fewer than 4 positions. TRACES rejects a ring that cannot form a closed area (needs at least 4 positions). | manual |
| EUDR-POLY-003 | error | A polygon self-intersects or is otherwise invalid. TRACES rejects self-intersecting or invalid polygons. | yes |
| EUDR-POLY-004 | warning | A polygon ring has duplicate consecutive vertices. Repeated points can make a ring invalid in TRACES. | yes |
| EUDR-POLY-005 | warning | Polygon winding order does not follow the right-hand rule. The GeoJSON standard wants exterior rings counter-clockwise. TRACES can be strict about this. | yes |
| EUDR-POINT-001 | error | A point plot has no Area property. TRACES requires an area for a point geolocation and rejects a point without one. | manual |
| EUDR-POINT-002 | error | A point plot declares an area of 4 hectares or more. TRACES only allows a point for plots below 4 ha. Larger plots need a polygon. | manual |
| EUDR-PROP-001 | warning | The plot is missing the ProducerName property. TRACES expects a producer name on each plot. | manual |
| EUDR-PROP-002 | warning | The plot is missing the ProducerCountry property. TRACES expects a producer country (ISO code) on each plot. | manual |
| EUDR-PROP-003 | warning | ProducerCountry is not a 2 letter ISO country code. TRACES expects ProducerCountry as an ISO 3166-1 alpha-2 code, for example BR or CI. | manual |
| EUDR-PROP-004 | warning | The plot is missing the Description property. A plot description helps TRACES and downstream operators identify the plot. | manual |
| EUDR-MIX-001 | warning | The file mixes different geometry types. Mixed geometry types are allowed but often signal a data problem worth reviewing. | manual |
| EUDR-CSV-001 | error | The CSV could not be converted to plots. Without a latitude and longitude column there are no coordinates to submit. | manual |
Errors versus warnings
An error means TRACES rejects the file until it is resolved: an unclosed ring, a self-intersection, a projected CRS, a point over 4 hectares. A warning means the file may still pass but the item is worth attention: low precision, a missing producer name, a mixed geometry set.
What can be repaired for you
The deterministic repairs are safe to automate: closing rings, rounding precision to 6 decimals, removing duplicate vertices, repairing self-intersections, correcting winding, and stripping a wrong CRS declaration. When a repair changes a plot area by more than a whisker, it is flagged so you can review it.
Common questions
What does a rule ID like EUDR-POLY-001 mean?
It is a stable identifier for a specific check, here an unclosed polygon ring. Every finding carries one so you can search, cite, and track it.
Which errors can be fixed automatically?
Precision, unclosed rings, duplicate vertices, self-intersections, winding, and a wrong CRS. Missing producer data or areas cannot be invented and are listed for you to supply.
See which errors are in your file
Paste it and get every error by rule ID, plot, and reason, then repair the fixable ones automatically.
Fix my file