Fix EU TRACES NT Error: 'Latitude Exceeds [-90, 90] Bounds (Swapped Lat/Lon Columns)'
Automatically detect and flip Excel [Latitude, Longitude] columns into strict GeoJSON [Longitude, Latitude] order.
Automatically detect and flip Excel [Latitude, Longitude] columns into strict GeoJSON [Longitude, Latitude] order.
Google Maps, Garmin screens, and farmer WhatsApp messages almost universally list Latitude first and Longitude second (for example, 6.244203, -75.581211). However, RFC 7946 GeoJSON and EU TRACES NT mandate [Longitude, Latitude] (X, Y) order.
When Longitude exceeds 90 or falls below -90 (e.g., -75.5 is fine, but 108.03 in Vietnam or -98.5 in Mexico), placing Longitude in the Latitude slot triggers an immediate Latitude outside [-90, 90] crash. In West Africa or Brazil where both values fall within [-30, 30], swapped axes silently place farms in the Atlantic Ocean.
| Compliance Parameter | EU TRACES NT Spec v1.5 / Statutory Requirement |
|---|---|
| CRS & Coordinate Precision | EPSG:4326 (WGS-84), [longitude, latitude] order, >= 6 decimal places (~11 cm), 2D-only (no Z-altitude) |
| 4.0000 ha Geometry Rule | Closed Polygon > 4.0000 ha (non-cattle) | Single Point <= 4.0000 ha or cattle establishments |
| Required Feature.properties | ProducerCountry ("CO"), ProducerName, ProductionPlace, unquoted numeric Area (ha, 4 decimals) |
| Topology & Payload Caps | Closed CCW exterior ring (first == last), zero self-intersections, zero interior holes, <= 25 MB & <= 200 lines/DDS |
| HS / CN Scope & Deadlines | Annex 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 Code | C716 (Primary) | Y141 (SME until June 29, 2027, excl. EUTR timber) | C717 (EU SME producer) | Y188/Y196 (Downstream Export) |
| Reg. (EU) 2025/1093 Risk Tier | Low 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 |
{
"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
]
]
]
}
}
]
}
EU TRACES NT GeoJSON strictly follows RFC 7946 [longitude, latitude] order—the reverse of Google Maps' [latitude, longitude] display.
Checking coordinates visually on a satellite map against the declared country's geography (ProducerCountry, e.g. Ghana, Colombia, or Brazil) immediately catches plots that land in the ocean or another continent.
Yes. TraceGuard detects out-of-bounds latitudes and heuristic inverted coordinates in browser memory, flips [Lat, Lon] back to [Lon, Lat], and lets you confirm every plot on the interactive satellite map.
100% Client-Side Browser RAM Processing (Zero Cloud Upload, Zero GDPR Supplier Exposure). Supports Excel/CSV, KML, GPX, UTM, WKT, WhatsApp DMS & GeoJSON.