GeoJSON & Geolocation Requirements Under the EUDR: The 4-Hectare Rule Explained

Why Geolocation Matters for EUDR Compliance

At the heart of the EUDR is traceability: the ability to link every product back to the specific plot of land where it was produced. This is what makes the regulation fundamentally different from previous legislation like the EUTR: it requires geolocation data for every production area, not just paperwork showing origin.

For operators, this means that before you can submit a Due Diligence Statement (DDS), you need accepted geolocation data for every plot in your supply chain. The legal requirement is the geolocation itself; GeoJSON is not mandated by the EUDR as the only format. It is the key format for bulk uploads to the Information System, while the system also supports map drawing and individual coordinate entry.

Data quality can become a major compliance bottleneck. Operators may receive plot coordinates that use the wrong coordinate system, reverse longitude and latitude, or contain invalid geometry. Understanding the legal and system requirements upfront reduces rework.

The 4-Hectare Rule

One of the most important technical rules in the EUDR is the 4-hectare threshold, which determines what type of geolocation data you need for each plot:

Plots Larger Than 4 Hectares

Must be identified using Polygon or MultiPolygon geometry. The actual boundaries of the production area must be mapped with GPS coordinates. This means someone must physically walk or digitize the perimeter of the plot, recording coordinates along the boundary.

Plots Smaller Than or Equal to 4 Hectares

Can be identified using a single Point coordinate (latitude/longitude). The operator should still retain evidence that the production plot is not larger than 4 hectares; the point option is a simplification for small plots, not a way to avoid knowing the production area.

Why This Rule Exists

This is a practical compromise driven by the reality of smallholder farming. Millions of coffee, cocoa, and rubber farmers around the world cultivate plots of 1-2 hectares. Requiring polygon boundary mapping for every smallholder plot would be logistically impossible and prohibitively expensive. The 4-hectare point option makes compliance feasible while still providing sufficient data for satellite-based deforestation screening.

The Edge Case: Plots Exactly 4 Hectares

If a plot is exactly 4 hectares, a Point coordinate is sufficient. The rule specifies "plots of land used for the production of the relevant commodity that are not larger than four hectares." The practical advice: if a plot is near the 4-hectare boundary, using polygon data provides more accurate deforestation analysis results and avoids any ambiguity.

GeoJSON Format Requirements

For structured upload, geolocation data should be prepared in GeoJSON format as defined in RFC 7946. The EUDR Information System also supports manual entry and drawing tools, but GeoJSON is the practical format for scalable operator workflows. The EU's Technical Specifications add several specific requirements on top of the standard:

Coordinate Reference System

• Must use WGS84 (EPSG:4326), the standard GPS coordinate system used by consumer GPS devices and smartphones
• Coordinates are expressed as [longitude, latitude]. Longitude comes first in GeoJSON, which is the opposite of how most people naturally express coordinates (latitude first). This is a frequent source of errors: data submitted as [latitude, longitude] will place plots in the wrong location.

Coordinate Precision

• The EUDR definition of geolocation requires coordinates using at least 6 decimal digits
• Six decimal places represent a coordinate increment of roughly 11 cm at the equator, but this formatting resolution does not mean that a field measurement is accurate to 11 cm
• Use [35.123456, -1.234567] as the preferred submission format. According to the Commission FAQ, the Information System automatically pads coordinates entered with fewer decimal places with trailing zeros, so [35.12, -1.23] is not rejected solely for having fewer displayed digits
• Padding with zeros satisfies formatting but does not improve the accuracy of the original measurement

File Size Limits

• Current EUDR Information System technical rules limit the total uploaded GeoJSON data associated with an individual declaration to 25 MB
• For supply chains with many plots, simplify unnecessarily complex geometry and organize source datasets so that the data included in each declaration remains manageable and matches the products it covers
• Very complex polygon boundaries (hundreds of vertices) can be simplified using standard GIS tools without significant loss of accuracy

Geometry Rules

• Polygons must be closed: the first and last coordinate pair in each ring must be identical
• No self-intersections: polygon boundaries must not cross themselves
• Interior rings (holes): current EUDR technical validation restricts interior rings in polygon geometries. If a plot has excluded areas, such as a protected forest patch within the plot boundary, the workaround depends on the specific case. In most cases, representing the production area as a MultiPolygon with separate exterior rings for each cultivated section is the recommended approach.
• Winding order: RFC 7946 recommends the right-hand rule for polygon rings. This is a useful interoperability convention, but it should not be presented as a separate EUDR rejection rule solely because a ring uses the opposite winding order.

Example: Valid GeoJSON for a Coffee Plot

Point (plot under 4 hectares)

{
  "type": "Feature",
  "geometry": {
    "type": "Point",
    "coordinates": [36.817223, -1.286389]
  },
  "properties": {
    "ProducerName": "Farm Kahawa",
    "ProducerCountry": "KE",
    "ProductionPlace": "Kiambu County",
    "Area": 2.5
  }
}

Polygon (plot over 4 hectares)

{
  "type": "Feature",
  "geometry": {
    "type": "Polygon",
    "coordinates": [[
      [36.810000, -1.280000],
      [36.820000, -1.280000],
      [36.820000, -1.290000],
      [36.810000, -1.290000],
      [36.810000, -1.280000]
    ]]
  },
  "properties": {
    "ProducerName": "Cooperative Kahawa",
    "ProducerCountry": "KE",
    "ProductionPlace": "Kiambu County",
    "Area": 12.3
  }
}

Note that in both examples, the coordinates use 6 decimal places and follow [longitude, latitude] order. The polygon's first and last coordinates are identical, ensuring the ring is properly closed. The property names use the fields recognized by the current EU file description; arbitrary custom properties may be ignored by the Information System.

FeatureCollection (multiple plots)

When submitting data for multiple plots, wrap them in a FeatureCollection:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [36.817223, -1.286389]
      },
      "properties": {
        "ProducerName": "Farm Kahawa",
        "ProducerCountry": "KE",
        "ProductionPlace": "Kiambu County",
        "Area": 2.5
      }
    },
    {
      "type": "Feature",
      "geometry": {
        "type": "Polygon",
        "coordinates": [[
          [36.810000, -1.280000],
          [36.820000, -1.280000],
          [36.820000, -1.290000],
          [36.810000, -1.290000],
          [36.810000, -1.280000]
        ]]
      },
      "properties": {
        "ProducerName": "Cooperative Kahawa",
        "ProducerCountry": "KE",
        "ProductionPlace": "Kiambu County",
        "Area": 12.3
      }
    }
  ]
}

Common Validation Errors

When submitting geolocation data, watch out for these frequent issues. The descriptions below are plain-language issue categories, not official Information System error codes:

Coordinate Order Errors

One of the most insidious errors is swapped latitude and longitude. Since many coordinate systems use [latitude, longitude] order, data that looks valid may actually place plots in the wrong hemisphere. A coffee plot in Kenya at [36.817223, -1.286389] (correct GeoJSON order: lon, lat) would appear in the wrong location if submitted as [-1.286389, 36.817223] (wrong order: lat, lon). Always verify that your coordinates place plots where they should be by previewing them on a map before submission.

Coordinate Precision in Practice

The 6-decimal-place requirement sounds straightforward, but in field conditions it raises practical questions:

Smartphone GPS Accuracy

Consumer smartphones typically achieve GPS accuracy of 3-5 meters in open conditions, which corresponds to roughly 5 significant decimal places. Under dense tree canopy (common in coffee and cocoa production areas), accuracy can degrade to 10-20 meters. The 6-decimal-place requirement is a formatting rule. The data must have 6 digits after the decimal point, but the underlying accuracy of the measurement may be less precise.

GPS Drift Between Surveys

If a plot is surveyed on two different occasions, the coordinates may differ slightly due to GPS drift. This is normal and does not indicate an error. However, significant discrepancies (more than 50 meters) between surveys of the same plot should be investigated.

Improving Field Accuracy

• Use GPS averaging (multiple readings at the same point) to reduce error
• Avoid dense canopy, buildings, steep terrain, and other obstructions that degrade satellite visibility when possible; ordinary cloud cover is not generally the central GPS limitation
• For polygon plots, take readings at corners and straight sections rather than along curves
• Consider using external GPS antennas for systematic surveys of large numbers of plots

How to Collect Geolocation Data

There are several practical methods for gathering GPS data from producers. The right choice depends on your supply chain structure:

1. Mobile GPS Apps

Farmers or field agents use smartphones to record plot center points or walk polygon boundaries. This is the most common approach for smallholder supply chains. Free apps like GPS Essentials, SW Maps, or purpose-built compliance apps can capture coordinates in the required format.

2. Bosqio App Capture

Producers or field agents can capture plot coordinates directly in the Bosqio app, including point locations for small plots and polygon boundaries where required. This keeps geolocation, producer questionnaires, photos, and supporting documents in one structured workflow instead of scattering evidence across screenshots, email attachments, and loose coordinate files.

The same capture record can store who submitted the data, when it was captured, the coordinate precision, and which producer questionnaire or document set it belongs to.

3. Satellite Imagery Digitization

Plot boundaries are traced from high-resolution satellite or aerial imagery using GIS software. This approach is useful for larger plots or when on-the-ground access is limited. However, it requires skilled GIS operators and may not capture boundaries accurately where plot edges are not visible from above.

4. Government Land Registries

Some countries maintain official cadastral databases with plot boundaries. Where available, this is the most authoritative source of geolocation data. However, cadastral data quality varies significantly between countries and regions, and many smallholder plots are not formally registered.

5. Cooperative Records

Farmer cooperatives in the coffee and cocoa sectors may already have GPS data from certification programs (Rainforest Alliance, UTZ, 4C). This data can often be repurposed for EUDR compliance, provided it meets the format and precision requirements. Always validate existing data against the EUDR technical specifications before relying on it.

Frequently Asked Questions

Can I submit a Point coordinate for a plot I know is larger than 4 hectares?

No. If the plot is larger than 4 hectares, the EUDR definition of geolocation requires polygon data with enough points to describe the plot perimeter. A single point would not satisfy that legal information requirement. The EU Information System records geolocation data; it should not be described as automatically performing a legally determinative deforestation analysis on a fixed four-hectare buffer.

What if I have existing GeoJSON data from another system?

Existing data can usually be used, but it must be validated against the EUDR technical specifications. Common issues with legacy data include wrong CRS (many systems use projected coordinate systems rather than WGS84), insufficient precision, and non-standard geometry types.

How do I check my coordinate precision?

Count the digits after the decimal point in your coordinate values and preserve at least six digits in your source and export workflows. If your data shows 36.81, the Information System can pad it to 36.810000, but this does not add measurement accuracy. Most GIS tools and programming languages can format coordinates consistently without changing the underlying observation.

What GeoJSON geometry types does the EUDR accept?

The current Information System file description supports Point, MultiPoint, Polygon, and MultiPolygon geometry, using Feature or FeatureCollection structures where appropriate. LineString, MultiLineString, and GeometryCollection are not accepted for plot-data submission.

Sources

• RFC 7946: The GeoJSON Format: Official GeoJSON specification
• Consolidated Regulation (EU) 2023/1115, Article 9: Geolocation requirements
• European Commission: EUDR Information System: GeoJSON upload and system technical information
• Implementing Regulation (EU) 2024/3084: IT system specifications
• Implementing Regulation (EU) 2026/1565: 2026 amendment to the Information System rules
• European Commission: FAQ on EUDR Implementation: Current clarification on coordinate formatting and evidence methods