EUDR GeoJSON Structure: MultiPolygon vs FeatureCollection for Co-op Shipments
When to package 50 to 200 smallholder farm plots as individual Features inside a FeatureCollection for EU TRACES NT API V4.
When to package 50 to 200 smallholder farm plots as individual Features inside a FeatureCollection for EU TRACES NT API V4.
When preparing supplier field data covered in 'EUDR GeoJSON Structure', upstream agricultural cooperatives frequently collect coordinates as raw GPX trackpoints, 3D KML altitude coordinates, KoboToolbox/ODK space-separated strings, WhatsApp Degrees-Minutes-Seconds (DMS) pins, or MultiPolygons with shared boundaries that fail EU TRACES NT Spec v1.5 schema validation.
Converting messy field exports inside browser memory into 2D EPSG:4326 [longitude, latitude] with >= 6 decimal places (~11 cm precision), closed counter-clockwise exterior rings (> 4.0000 ha), explicit numeric Area (ha), and verified ISO-2 ProducerCountry tags prevents DDS rejections and port demurrage.
| 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 File Description v1.5 strictly accepts 2D RFC 7946 GeoJSON in [longitude, latitude] order (EPSG:4326) with >= 6 decimals—rejecting raw GPX/KML XML, ODK strings, DMS text, Z-altitude, and unclosed rings.
Use a GeoJSON FeatureCollection where each production plot is its own Feature carrying individual ProducerName, ProducerCountry, ProductionPlace, and numeric Area properties.
Yes. All coordinate conversion, geodesic hectare calculation, and satellite boundary previews execute 100% locally in your browser RAM with zero server upload.
100% Client-Side Browser RAM Processing (Zero Cloud Upload, Zero GDPR Supplier Exposure). Supports Excel/CSV, KML, GPX, UTM, WKT, WhatsApp DMS & GeoJSON.