Fix EU TRACES NT Error: 'Duplicate Consecutive Vertices / Zero-Length Polygon Edge'
Clean stationary GPS logger points from Garmin GPX and KoboToolbox field traces before uploading to EU TRACES NT.
Clean stationary GPS logger points from Garmin GPX and KoboToolbox field traces before uploading to EU TRACES NT.
Drone surveys and QGIS exports frequently emit 14-decimal coordinates spaced less than 10 centimeters apart, or repeat the same GPS point twice consecutively when a surveyor pauses while walking a boundary. When TRACES NT truncates or checks coordinates at 6 decimal places (~11 cm), adjacent vertices collapse into identical points, creating zero-length edges.
Zero-length edges cause self-intersection and degenerate-ring rejections in TRACES NT v1.5, blocking operators from obtaining a DDS Reference Number for EU customs Box 44 (TARIC C716).
| 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
]
]
]
}
}
]
}
When GIS shapefiles contain vertices closer than 11 cm, rounding 14-decimal floats to TRACES NT's 6-decimal grid collapses two adjacent points into the exact same coordinate, creating a zero-length edge.
Round vertices to 6 decimal places first, strip consecutive duplicates (excluding the final closing vertex matching [0]), and verify the remaining ring still has at least 4 coordinate pairs and zero intersections.
No. Removing zero-length duplicate points preserves the true plot perimeter and keeps geodesic hectare area intact for plots > 4.0000 ha.
100% Client-Side Browser RAM Processing (Zero Cloud Upload, Zero GDPR Supplier Exposure). Supports Excel/CSV, KML, GPX, UTM, WKT, WhatsApp DMS & GeoJSON.