Fix EU TRACES NT Error: 'Exterior Ring Winding Order Violation (RFC 7946 Right-Hand Rule)'
Automatically orient exterior polygon rings counter-clockwise to satisfy RFC 7946 and EU TRACES NT GeoJSON validators.
Automatically orient exterior polygon rings counter-clockwise to satisfy RFC 7946 and EU TRACES NT GeoJSON validators.
Under RFC 7946 Section 3.1.6 (the 'Right-Hand Rule') adopted by EU TRACES NT GeoJSON File Description v1.5, every Polygon exterior LinearRing MUST wind counter-clockwise (CCW). Legacy GIS exporters, manual Excel coordinate lists, and older ArcGIS scripts frequently output clockwise (CW) rings.
A clockwise exterior ring can be misread as the complement of the Earth's surface or rejected outright by TRACES NT geometry parsers, blocking primary operators from generating a valid DDS reference number before the December 30, 2026 deadline.
| 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
]
]
]
}
}
]
}
RFC 7946 mandates that Polygon exterior rings wind counter-clockwise (CCW) so the interior of the farm plot lies to the left as you traverse the vertices in order.
No. Reversing vertex order preserves the exact boundary coordinates and geodesic hectare area while bringing the geometry into strict TRACES NT Spec v1.5 compliance.
Yes. TraceGuard EUDR detects clockwise rings in browser memory and reverses them to RFC 7946 counter-clockwise orientation automatically alongside ring closure, 2D coordinate, bowtie repair, and 6-decimal Spec v1.5 normalization.
100% Client-Side Browser RAM Processing (Zero Cloud Upload, Zero GDPR Supplier Exposure). Supports Excel/CSV, KML, GPX, UTM, WKT, WhatsApp DMS & GeoJSON.