TG
TraceGuard
Open Free GeoJSON Converter →

Fix EU TRACES NT Error: 'LinearRing Not Closed' (First & Last Vertex Mismatch)

How to automatically append the starting [longitude, latitude] vertex to close open polygon rings for EU TRACES NT v1.5.

Reg. (EU) 2023/1115 & 2025/2650 TRACES NT GeoJSON Spec v1.5 GeoJSON & GIS Formats

Section 1 · Why Open LinearRings (First != Last Coordinate) Reject in EU TRACES NT

In RFC 7946 GeoJSON and EU TRACES NT Spec v1.5, a Polygon's exterior LinearRing must have at least 4 coordinate pairs and its final coordinate [N-1] must match its initial coordinate [0] character-for-character. Field GPX tracks, WhatsApp corner lists, and Excel tables almost always omit the closing duplicate point.

An unclosed LinearRing triggers immediate topology failure in TRACES NT (LinearRing not closed), preventing operators from generating DDS reference numbers required for EU customs clearance.

Section 2 · Step-by-Step Technical & Statutory Checklist

Section 3 · Pre-Flight GeoJSON & Customs Box 44 Reference Table

Compliance Parameter EU TRACES NT Spec v1.5 / Statutory Requirement
CRS & Coordinate PrecisionEPSG:4326 (WGS-84), [longitude, latitude] order, >= 6 decimal places (~11 cm), 2D-only (no Z-altitude)
4.0000 ha Geometry RuleClosed Polygon > 4.0000 ha (non-cattle) | Single Point <= 4.0000 ha or cattle establishments
Required Feature.propertiesProducerCountry ("CO"), ProducerName, ProductionPlace, unquoted numeric Area (ha, 4 decimals)
Topology & Payload CapsClosed CCW exterior ring (first == last), zero self-intersections, zero interior holes, <= 25 MB & <= 200 lines/DDS
HS / CN Scope & DeadlinesAnnex I Regulated Commodities (Ch. 09, 12, 15, 18, 40, 44, 47, 48, 94, 01–02) — Dec 30, 2026 (Large/Medium & EUTR Timber) | June 30, 2027 (Micro/Small Art. 38(3), excl. EUTR timber) | Reg. 2026/2102 Sept 2026 / Dec 2027 updates
Customs Box 44 TARIC CodeC716 (Primary) | Y141 (SME until June 29, 2027, excl. EUTR timber) | C717 (EU SME producer) | Y188/Y196 (Downstream Export)
Reg. (EU) 2025/1093 Risk TierLow Risk (1% quota, Art. 13) | Standard Risk (3% quota, Art. 10–11) | High Risk (9% quota: BY, KP, MM, RU) — Art. 9 GeoJSON mandatory across all tiers; Art. 10/11 required unless 100% segregated Low-Risk origin
Valid EU TRACES NT Spec v1.5 GeoJSON Reference Example:
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerCountry": "CO",
        "ProducerName": "Verified Cooperative Lot 01",
        "ProductionPlace": "Verified Production Plot #1",
        "Area": 6.4215
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -75.612345,
              2.192346
            ],
            [
              -75.609845,
              2.192346
            ],
            [
              -75.609845,
              2.194666
            ],
            [
              -75.612345,
              2.194666
            ],
            [
              -75.612345,
              2.192346
            ]
          ]
        ]
      }
    }
  ]
}

Section 4 · Technical FAQ (EU TRACES NT Spec v1.5 & 2026/2027 Compliance)

How do I fix a 'LinearRing not closed' error in EUDR GeoJSON?

Copy the exact [longitude, latitude] pair from the first coordinate in the polygon ring and append it as the final coordinate so ring[0] equals ring[last] identically.

How many vertices does a valid closed EUDR polygon require?

At least 4 coordinate pairs [longitude, latitude]: at minimum 3 distinct triangle corner vertices plus the 4th closing vertex matching the first.

What if closing an open GPX track creates a crossing edge?

TraceGuard EUDR closes open rings automatically and then runs self-intersection topology checks so crossed closing segments are caught and repaired immediately.

Section 5 · Related EUDR Technical Guides (Internal Pillar Hub)

100% Client-Side Browser RAM · Zero Cloud Upload

Validate, Convert & Auto-Repair Supplier Files in 10 Seconds

100% Client-Side Browser RAM Processing (Zero Cloud Upload, Zero GDPR Supplier Exposure). Supports Excel/CSV, KML, GPX, UTM, WKT, WhatsApp DMS & GeoJSON.

Open Free GeoJSON Converter →