Why is my GeoJSON file rejected?

The most common reasons for a rejected GeoJSON file

A GeoJSON file is usually rejected due to a technical defect in the geometry, not due to the content of the due diligence declaration itself. Common causes include an incorrect coordinate reference system, which causes plots to appear in the wrong location on the map, and invalid geometry: polygons whose lines intersect themselves, rings that do not close, or areas that have been accidentally saved as separate points. A mix of geometry types within a single file — for example, points and polygons mixed together — also often leads to an error message when reading the file.

Additionally, problems frequently occur during conversion from another format. Files exported from a shapefile, a GPS app or an agricultural management system sometimes carry rounding errors, missing attributes or incorrect character encoding, which only becomes apparent once the file is opened or read elsewhere. A file may look fine in a mapping program yet still be technically unusable for further processing, because the underlying structure does not match what the receiving system expects.

Where the technical requirements for geolocation data come from

The technical requirements that geolocation data must meet are described in the EU information system for the deforestation regulation, the register in which market participants submit their declarations. That system automatically checks uploaded files for readability and validity of the geometry before an submission is accepted. We structure and validate geolocation data in these types of formats before they go to the register, but the assessment of whether a plot, supplier or product meets the substantive requirements of the regulation remains with the market participant.