EUDR GeoJSON validator: pre-check against the TRACES format
Drop your plot file and see in seconds whether the EUDR Information System (TRACES) will read it – with plain-language explanations, a map sketch and safe one-click fixes. Also converts Turkish ED50 and TUREF coordinates to WGS 84.
- Your file never leaves this device: it is read and checked by JavaScript in your browser. No upload, no server, no cookies, no analytics.
- No map tiles are loaded – the preview is a drawing, so no map provider learns where your plots are.
- Close the tab and everything is gone. You can even disconnect from the internet after the page has loaded.
Which coordinate system are these metres in?
What we check
Rules from the official GeoJSON File Description of the EUDR Information System, the DDS API reference and Art. 2(28) EUDR. Where the official texts say nothing, we say so.
| Check | Basis | Level |
|---|---|---|
| Valid JSON and GeoJSON structure; FeatureCollection with one Feature per plot | File Description; RFC 7946 | Error |
| Geometry types Point, MultiPoint, Polygon, MultiPolygon, GeometryCollection – LineString rejected | File Description; API V3 | Error |
| WGS 84 longitude/latitude in degrees (EPSG:4326); metres (UTM/TM) detected | File Description | Error |
| Longitude/latitude order – swap detected (with Türkiye hint) | RFC 7946 §3.1.1 | Error / Warning |
| Coordinates within ±180 / ±90 | RFC 7946 | Error |
| At least 6 decimal places (padding zeros does not count) | Art. 2(28) EUDR; API V3 | Warning |
| Rings closed, at least 4 positions | File Description (error 4); RFC 7946 | Error |
| Self-intersections, straight lines / zero area | File Description (common errors) | Error |
| Duplicate points, also after truncation to 6 decimals | File Description (error 7) | Warning |
| Holes (inner rings) not supported | File Description | Error |
| Ring orientation (counter-clockwise) | RFC 7946 recommendation – not named in the File Description | Warning |
| Point used for a plot > 4 ha (cattle exception) | Art. 2(28) EUDR; API V3 | Warning |
| Area property: number in hectares vs. calculated geodesic area; "Area":"3" as text | File Description (error 14) | Error / Warning |
| Property names ProducerName, ProducerCountry, ProductionPlace, Area (case-sensitive) | File Description | Warning |
| ProducerCountry as ISO 3166-1 alpha-2, plot inside that country | File Description; Natural Earth outline | Error / Warning |
| Overlapping plots, duplicate features | not named in the File Description | Warning |
| File size 25 MB per statement | File Description (error 16); User Guide | Error |
Spec checked: 16 October 2026. Pre-check against the TRACES format – not a legal assessment, not a deforestation analysis and not an approval by TRACES or any authority.
Coordinate converter: ED50 / TUREF / ITRF96 → WGS 84
Paste survey coordinates (one point per line: ID; easting; northing – or the Turkish order Y; X). Rows with the same ID become one polygon. The calculation runs on your device with proj4js.
Datum parameters and accuracy
- ED50 → WGS 84: EPSG:1784 “ED50 to WGS 84 (30)”, Türkiye onshore and offshore, Position Vector 7-parameter transformation: tX = −84.1 m, tY = −101.8 m, tZ = −129.7 m, rX = 0, rY = 0, rZ = +0.468″, scale = +1.05 ppm. Stated accuracy: 2 m. One national parameter set – locally the error can be larger, especially on old sheets.
- TUREF / ITRF96 → WGS 84: treated as identical (difference well below 1 m). TM zones EPSG:5253–5259 (k = 1, false easting 500 000); 3° Gauss-Krüger with zone prefix EPSG:5269–5275.
- ED50 3° TM (k = 1, false easting 500 000) has no EPSG code; we build it from the same ED50 parameters.
- Six-digit eastings look the same in ED50 UTM, ED50 TM, TUREF TM and ITRF96 UTM. A wrong choice shifts plots by tens of metres to kilometres – check the map sheet or the surveyor’s report. If in doubt: let us do it.
How the check works
- Areas are calculated geodesically on the WGS 84 ellipsoid (Lambert azimuthal equal-area projection centred on each plot) and compared with the
Areaproperty (tolerance 10 %). - Swapped axes are detected when latitude exceeds 90°, or when the plot lies outside the stated
ProducerCountrybut inside it with swapped axes (country outlines from Natural Earth 1:50m, buffered by about 15 km). - Fixes are never applied silently. Swapping axes, renaming look-alike fields and converting lines to polygons need your explicit tick. Self-intersections and holes are never “repaired” automatically, because that means deciding where the boundary really runs.
- The checker is open in your browser: the scripts
pdv-core.jsandpdv-ui.jsare readable as plain source.
Frequently asked questions
Is my file uploaded anywhere?
No. The page loads its scripts once; your file is read by your browser and processed in memory. Nothing is sent to PlotDossier or anyone else. The corrected file is created locally as a download.
Does a clean result mean my DDS will be accepted?
No guarantee. It means the file matches the published TRACES GeoJSON format in the points we check. The Information System may apply further checks, and the format says nothing about deforestation or whether these are the right plots.
Why are my coordinates swapped?
GeoJSON writes longitude first: [32.33, 41.63]. Many spreadsheets and Turkish lists write latitude first. In Türkiye, latitudes are 36–42° and longitudes 26–45°, so swapped values put the plot in the Indian Ocean or Arabia.
My surveyor gave me Y/X values in metres. Which system is it?
Usually ED50 (older surveys) or TUREF/ITRF96 (newer ones), in 3° TM or 6° UTM zones. The zone and datum are normally written on the sketch or parcel query. The converter shows the accuracy for each choice.
Do I need 6 decimal places?
Art. 2(28) EUDR requires at least six decimal digits, and the system truncates to six. Adding zeros to a 4-decimal coordinate formally meets the format but does not make the position more accurate – the plot should be measured properly.
Is this a legal or deforestation check?
No. It is a pre-check against the TRACES format only. Our paid service checks each plot against 2020 forest maps and Sentinel-2 imagery and documents the evidence – but it is a screening service, not a certification.
Sources
- EUDR Information System – GeoJSON File Description (updated 17 Aug 2026)
- EUDR Information System – Operator API Reference, Due Diligence Statement V3 (DdsProducerType / geometryGeojson)
- EUDR Information System – User Guide (last update 16 Sep 2026), hosted by BLE
- Regulation (EU) 2023/1115 (EUDR), Art. 2(28) – consolidated text, EUR-Lex
- IETF RFC 7946 – The GeoJSON Format
- EPSG:1784 – ED50 to WGS 84 (30), Türkiye, accuracy 2 m
- EPSG:23035 – ED50 / UTM zone 35N (also 23036, 23037)
- EPSG:5253 – TUREF / TM27 (series 5253–5259; 3° GK with zone prefix 5269–5275)
- proj4js 2.22 (MIT licence) – coordinate transformation in the browser
- Natural Earth 1:50m Admin 0 countries (public domain) – rough outlines for the swap/country hint
Spec checked: 16 October 2026
Pre-check against the TRACES format – not a legal assessment, not a deforestation analysis and not an approval by TRACES or any authority. Screening service – not a certification and not legal advice. Due diligence and the due diligence statement (DDS) remain the operator’s responsibility.
Errors you would rather not fix yourself?
Send us the file – we fix the geometry, convert the coordinates and check the plots against 2020 forest cover. The first 3 plots are free, without obligation.