EUDR GeoJSON format

The EUDR Information System takes plot coordinates as GeoJSON. The file description, updated 17 August 2026, is the structure

Direct answer. The European Commission’s GeoJSON File Description (page title “EUDR GeoJSON File Description”, updated 17 August 2026) says the EUDR Information System supports the import, processing, and export of GeoJSON files for defining production place coordinates for declared commodities in a due diligence statement. GeoJSON is IETF RFC 7946. The page says it uses the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees, and that coordinates in another system must be converted to WGS84 (EPSG:4326). Position order is longitude, then latitude. The page does not state a feature-count limit. It does state a file size limit of 25 Mb for individual DDS submissions, which includes the total size of uploaded GeoJSON files. Regulation (EU) 2023/1115 Article 2(28) is the legal geolocation definition; that reading is EUDR geolocation, not repeated here. This page is not legal advice.

EUDR Records Manager (Shopify App Store · Write a review) tracks supplier lots, product links, missing fields, document packs, CSV exports, and audit logs for EUDR record review. The listing does not say the app creates or validates GeoJSON. Application dates are EUDR scope: 2026 vs mid-2027.

Related: CRALedger Duty Records — CRA duty records before an Article 14 incident. Does not file ENISA notifications.

Free check first: EUDR product scope check runs in your browser and sends nothing. Type a product or HS code and see which EUDR Annex I lines it may touch.

Checklist before you upload a file

What the file description says the geometry is

A geometry object other than GeometryCollection must have a member named coordinates. A position is an array of numbers with at least two elements. The order is longitude, latitude in EPSG:4326. Point geometry consists of two coordinate values. MultiPoint consists of two or more points. Polygon consists of at least four pairs of coordinates, and the first and last points coincide. MultiPolygon contains two or more polygon definitions. A Feature contains a single geometry plus properties. A FeatureCollection is one or more features. GeometryCollection is two or more geometries. The page’s Feature example nests the Point position as [[longitude, latitude]]. Its FeatureCollection Point example uses [longitude, latitude]. This page follows the FeatureCollection Point form in the snippet below.

Polygons with holes (doughnut shapes) and shapes with crossing lines are not supported and will not be processed. If a doughnut shape is needed, the page says it can be defined by combining two half-doughnut shaped polygons.

Type I, Type II, and the properties the system accepts

The page describes two variants. Type I is for the web services interface (API) and for the UI import utility at producer level. It includes the required features from the definitions section and may include any of the optional properties. Type II is for the UI file import utility at commodity level. It contains multiple producers grouped by ProducerName and ProducerCountry, and it includes the ProducerCountry property per Feature.

Optional properties the system accepts and will process are: ProducerName, an optional producer name; ProducerCountry, the country of production ISO2 code; ProductionPlace, an optional name for the geometry; and Area, the area in hectares of a Point. Any other syntactically valid property is ignored. The page recommends ProductionPlace to describe the production place name.

The information system will truncate coordinate points to 6 decimal places before storing. The page says it is superfluous to send a higher resolution, and that higher resolution may, in extreme cases, result in invalid geometries where the original is valid. The property Area for points is optional. If it is not provided, it will be set by default to “4” (four) hectares when processed by the EUDR system.

An illustrative FeatureCollection, not a real plot

The coordinates and property values below are placeholders. They are not a farm, a plot, or a coordinate from the official examples. XX is not an ISO2 code; an invalid producer-country ISO2 code is one of the errors the page lists. The number 4 is the default the page states when Area is omitted for a point; it is shown here only so the value is a number, not a string.

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProductionPlace": "PLACEHOLDER",
        "ProducerCountry": "XX",
        "Area": 4
      },
      "geometry": {
        "type": "Point",
        "coordinates": [0.000001, 0.000001]
      }
    }
  ]
}

What the Information System treats as a file error

The page lists common GeoJSON file errors. It does not point to a third-party validator. The checks below are the ones that page describes for import into the Information System:

  1. Coordinate lines crossing, such as a figure-eight or intersecting polygon lines.
  2. Overlapping sides. Internal overlap or holes where part of the polygon folds inward are not accepted.
  3. Coordinate shapes with holes. The workaround on the page is two half-moon shapes.
  4. Open polygons. The first coordinate pair must be the same as the last.
  5. Invalid geometry types, for example LineString.
  6. Coordinates representing straight lines.
  7. Duplicate coordinates after truncation to 6 decimals. The page’s example is two points with 10 decimals that become the same after truncation: 2.348800000,48.8534345673 becomes 2.3488,48.853434, and both -5.8227391234,144.2567071234 and -5.8227394567,144.2567074567 become -5.822739,144.256707.
  8. File syntax errors, such as a missing ) or }.
  9. Invalid property names, or the wrong case, such as productionplace instead of ProductionPlace.
  10. Invalid file format, such as PDF or txt.
  11. Invalid coordinate range, outside 90/−90 or 180/−180.
  12. Invalid producer country ISO2 code.
  13. Password-protected files.
  14. A value of the wrong type. The page says "Area": "3" instead of "Area": 3 results in area = 0, because the quoted 3 is not recognized as a number.
  15. Polygons with holes. The page says the user will be shown an error message.
  16. GeoJSON files exceeding the 25 Mb size limit.

The page says operators are required to obtain geolocation data that is as granular as possible, and that the system has a file size limit of 25 Mb for individual DDS submissions, which includes the total size of uploaded GeoJSON files. Its workarounds for that limit are: reduce the number of points used to describe straight lines, using only two points to define a line instead of adding coordinates at frequent intervals (the page’s example interval is every 5–10 meters); and use single geolocation points to represent plots under 4 hectares, rather than creating polygons. The regulation’s own polygon rule, including the cattle exception, stays on EUDR geolocation.

What this page is not

Related pages

Confirm the live GeoJSON File Description and Regulation (EU) 2023/1115 before you treat a file as accepted. EUDR Records Manager tracks supplier lots, product links, missing fields, document packs, CSV exports, and audit logs for EUDR record review. It does not create or validate GeoJSON.