EUDR: The map file opens but is it the right rubber plot?

A rubber supplier sends a digital map of the plots from which it sources. The file opens, and several tidy shapes appear. That is a useful first check, but it does not establish that those shapes identify the land behind a particular shipment.

One common file format is GeoJSON. In plain terms, it is a way to store locations and boundaries as coordinates, often with details such as a plot identifier.

It is a type of digital plot map file, or, more technically, a geospatial data file. It can tell a system where a boundary has been drawn. On its own, it cannot tell a buyer who supplied the rubber or whether the boundary is the right one.

Start with the location

A map can look convincing even when its coordinates are wrong. GeoJSON lists longitude before latitude. If the order is reversed, a plot may appear far from the declared sourcing area while the file remains readable.

Check whether each location fits the stated country and local area, whether plot identifiers are present and unique, and whether the file contains the points or boundaries expected for those plots.

Then look at the shapes. A boundary can cross itself, contain repeated points or enclose no meaningful area. Some faults are obvious on screen; others need a geometry check.

An upload that succeeds only shows that the software accepted the file. It does not prove that every shape is usable, correctly located or linked to the supplier named in the purchasing record.

Imagine a fictional file from a rubber supplier with three mapped plots. Two carry the same plot ID. The third has a bow-tie boundary that crosses itself.

All three may appear on a map. None of these problems should be quietly passed along as settled source data.

Ask what the boundary represents

Even a technically sound shape may describe the wrong field. Compare it with the supplier's stated location, the producer or collection point, and the plot ID in the purchase record.

An unexpectedly large area or a location far from the stated source is a question for the supplier, not immediate proof of wrongdoing. Coordinates can be mistyped, converted from another map system or attached to the wrong record.

A satellite image can help someone notice an odd location. It cannot establish who produced the rubber there. That requires source records and a review of how the plot was linked to the goods.

Keep a trail of any repair

Technical repairs can remove duplicate points or correct a malformed boundary. They can also change the area that a plot represents. Keep the original file, record what was changed and preserve the corrected version separately.

If a correction materially moves or reshapes the boundary, ask the supplier to confirm it before treating it as its plot.

A dated source file, a short review note and an approved corrected file are more useful to the next person than a file called `final_v7.geojson`.

The note should say which plot was affected, what the problem was, who made the change and who confirmed the result.

Follow the material as well as the map

The map is only one link in a rubber supply chain. Material may pass through collection, aggregation, processing and blending before it reaches a buyer.

A plot file needs a durable connection to the supplier, intake or purchase record, material lot and eventual shipment. If material from several plots is mixed, the records need to retain the relevant source set rather than point to one convenient shape.

This is a record-keeping question, not something a GeoJSON file can answer. Pick a shipment and work backwards through the lot and purchase records. Do the plot IDs in those records match the plots in the file? If the connection breaks, a neat map cannot repair it.

Under the EU Deforestation Regulation, geolocation is part of the information needed for due diligence. It is not a substitute for assessing origin, applicable legality, land-use history and risk, or for making any required official filing.

A map check can catch preventable data errors before those decisions are made. It cannot make the decisions for the operator.

Before a file moves downstream, a short handoff note can answer six questions: which file arrived, which checks ran, which issues remain, what changed, who confirmed the plot, and which purchases or lots use it.

That will not prove compliance. It will make the next review less likely to start with a clean-looking map whose link to the rubber was never checked.

Sources for fact-checking:

GeoJSON standard (RFC 7946): https://www.rfc-editor.org/rfc/rfc7946

Consolidated Regulation (EU) 2023/1115: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02023R1115-20251226