TG
TraceGuard
Open Free GeoJSON Converter →

Fix EU TRACES NT Error: 'Invalid CRS / Projected Coordinates Must Be EPSG:4326'

Reproject local UTM meters, SIRGAS 2000, MAGNA-SIRGAS, and Web Mercator (EPSG:3857) coordinates into WGS-84 decimal degrees.

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

Section 1 · Why Non-WGS84 CRS & Legacy 'crs' Blocks Fail EU TRACES NT

Regional forestry cadastres and agricultural surveys routinely store polygons in UTM meters, SIRGAS 2000, MAGNA-SIRGAS, ETRS89, VN-2000, or S-JTSK. Furthermore, older GeoJSON tools insert a deprecated top-level 'crs' JSON object—which RFC 7946 explicitly disallows.

EU TRACES NT GeoJSON File Description v1.5 strictly requires implicit EPSG:4326 (WGS-84) coordinates in decimal degrees [longitude, latitude]. Projected meter coordinates exceed [-180, 180] and [-90, 90] bounds and fail instantly.

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)

Which coordinate reference system does EU TRACES NT require?

EU TRACES NT GeoJSON File Description v1.5 requires EPSG:4326 (WGS-84) geographic coordinates in [longitude, latitude] decimal degrees with at least 6 decimal places.

Why did TRACES NT reject my file even after I reprojected to WGS-84?

Older GIS exporters often write a deprecated 'crs' key into the GeoJSON header or keep 3D Z-coordinates. Removing the 'crs' block and stripping Z-altitude resolves the error.

Can TraceGuard EUDR reproject UTM meters to EPSG:4326 in the browser?

Yes. TraceGuard EUDR converts UTM Zones (1N–60S) and metric survey grids to 6-decimal WGS-84 GeoJSON locally in browser RAM without uploading confidential farm files.

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 →