The Commission’s list of common file errors

The specification ends with sixteen errors it sees most often (GeoJSON File Description, Common errors). Each one maps to a rule here:

  1. Coordinate lines crossing: The boundary of this plot crosses itself
  2. Overlapping sides: The boundary folds back on itself
  3. Shapes with holes: This plot has a hole in it
  4. “Open” polygons: This polygon is not closed
  5. Invalid geometry types: This shape type is not accepted for production places
  6. Coordinates representing straight lines: This polygon encloses no area
  7. Duplicate coordinates after truncation to six decimals: Two points in a row become identical at six decimals
  8. File syntax errors: The file has a JSON syntax error
  9. Invalid property names: A property name is misspelled or has the wrong capitals
  10. Invalid file format: This file is not JSON
  11. Invalid coordinate range: A longitude is outside -180 to 180, A latitude is outside -90 to 90
  12. Invalid producer country ISO2 code: ProducerCountry is not a valid two-letter country code
  13. Password-protected files: The file is a password-protected archive
  14. Data representation issues: Area is written as text instead of a number, A coordinate is not a number
  15. Polygons with holes inside: This plot has a hole in it
  16. Files exceeding the 25 MB size limit: The file is larger than 25 MB

The file itself

Problems that stop the file being read at all, or that apply to the whole statement.

Structure

The file is JSON, but not shaped the way the Information System reads it.

Coordinates

Numbers in the wrong order, the wrong units, or with too little precision.

Plot shapes

Polygons that cross themselves, fold back, are open, or have holes.

Properties

ProducerName, ProducerCountry, ProductionPlace and Area: names, types and values.

Plausibility (our own checks)

Not rejection reasons in the Information System. Signs that something in the file is probably wrong.

Check a file against all of them

Drop a GeoJSON, KML, shapefile or CSV here, or .

Checked in your browser. The file is not uploaded, stored or sent anywhere.

Rule set 2026.09.2. The same registry drives the checker, the command-line tool, the PDF report and these pages, so they cannot disagree.