TG
TraceGuard
Open Free GeoJSON Converter →

Fix EU TRACES NT Error: '3D Coordinates / Z-Altitude Not Permitted in GeoJSON'

Strip elevation values from Google Earth KML and Garmin GPX exports to create strict 2D [longitude, latitude] coordinate arrays.

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

Section 1 · Why EU TRACES NT Rejects 3D Z-Altitude Coordinates

Google Earth Pro (.kml), handheld Garmin GPX units, and surveyor shapefiles routinely export 3-element coordinate tuples [longitude, latitude, elevation] (for example, [-75.612345, 2.192346, 1650]). Under EU TRACES NT GeoJSON File Description v1.5 and strict RFC 7946 validation, production plot geometries must be strictly 2-dimensional.

Any Z-altitude coordinate value in a Polygon ring or Point array causes immediate upload rejection during Due Diligence Statement (DDS) submission, stalling customs clearance under TARIC code C716.

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)

Why does EU TRACES NT reject GeoJSON coordinates with altitude values?

EU TRACES NT GeoJSON File Description v1.5 requires strictly 2D EPSG:4326 [longitude, latitude] coordinate arrays. Exporting a 3rd elevation (Z) coordinate from KML, GPX, or QGIS triggers a schema validation failure.

How do I remove Z-altitude coordinates without losing GPS precision?

TraceGuard EUDR automatically strips the 3rd elevation element from every KML, GPX, ODK, or GeoJSON vertex inside your browser while preserving at least 6 decimal places (~11 cm ground resolution).

Does stripping 3D elevation change the EUDR hectare area calculation?

No. EUDR Article 9(1)(d) calculates production plot area geodesically on the 2D WGS-84 ellipsoid in hectares to 4 decimal places (Area), independent of terrain elevation.

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 →