Free public geometry desk
Validate an EUDR geolocation file before it reaches your due diligence workflow. Drop GeoJSON, KML or WKT and inspect every feature for coordinate, polygon and 4-hectare rule problems.
Runs entirely in your browser. Your plot data never leaves your device.
Desk protocol
Six checks per feature
Geometry type and area estimate
Point versus polygon at the 4 ha threshold
WGS84 coordinate value sanity
Ring closure and duplicate vertices
Self-intersection detection
Latitude and longitude swap heuristic
Geometry validation is not an EUDR compliance conclusion. It does not assess deforestation, legality, traceability or the truth of supplier declarations.
Input desk 01
Accepted: .geojson · .json · .kml · .wkt
Drop a plot file here or click to browse
GeoJSON, KML or WKT · parsed locally
Before TRACES upload
Most rejected or misleading plot files are not exotic GIS failures. They are small format mistakes that survive a visual check and only appear when a strict parser reads the coordinates.
Failure 01
GeoJSON requires [longitude, latitude], which is the reverse of how coordinates are often spoken or copied from a form. Out-of-range swaps are easy to flag, but an in-range swap can place a plot in the wrong region without making the file technically invalid.
Failure 02
The final coordinate pair in a polygon ring must exactly repeat the first pair. Some GIS viewers draw the closing edge on screen even when the saved coordinates omit it, so a shape that looks complete can still fail strict processing.
Failure 03
A figure-eight or bow-tie polygon has an ambiguous inside and outside and is not valid plot geometry. Redraw the boundary in sequence around the perimeter, or split genuinely separate areas into valid features.
Failure 04
For commodities other than cattle, a plot of more than 4 hectares needs a polygon that delineates its perimeter. Cattle establishments are the exception and may be represented by points regardless of establishment size.
Failure 05
UTM and national grid coordinates are measured in metres, not WGS84 decimal degrees. Changing the CRS label does not transform the numbers, so reproject the data to EPSG:4326 before creating the GeoJSON.
Failure 06
EUDR geolocation uses latitude and longitude with at least six decimal digits. Rounding too early can move a point, collapse nearby vertices into duplicates, or turn a small valid polygon into a broken ring.
Point or polygon?
For commodities other than cattle, a plot of 4 hectares or less may be represented by a point. A plot of more than 4 hectares must be represented by enough latitude and longitude points to delineate its perimeter as a polygon.
Cattle use a different location concept: geolocation refers to the establishments where the animals were kept, and an establishment may be represented by a point regardless of its size. Choosing the cattle context in the validator applies that exception without treating it as a rule for crop or forestry plots.
Read the full EUDR geolocation requirements guideReference format
Every coordinate pair is written in [longitude, latitude] order, and the last pair exactly repeats the first to close the ring. Keep at least six decimal digits so precision survives conversion and nearby vertices do not collapse during normalisation.
{
"type": "FeatureCollection",
"features": [{
"type": "Feature",
"properties": { "ProductionPlace": "Plot A-12" },
"geometry": {
"type": "Polygon",
"coordinates": [[
[-3.863245, 6.107891],
[-3.861900, 6.107891],
[-3.861900, 6.109100],
[-3.863245, 6.109100],
[-3.863245, 6.107891]
]]
}
}]
}Validator questions
No. File reading, parsing and geometry checks run in your browser, and the validator does not send the plot data to plotvera. Apply your own device and access controls when handling supplier coordinates.
The tool reads GeoJSON or JSON, KML and WKT. It checks Point, MultiPoint, Polygon and MultiPolygon features, while unsupported or malformed geometry is reported for correction.
No. Valid geometry only means the file passes the checks this tool performs. It does not prove the production location, deforestation-free status after 31 December 2020, legality, traceability or completion of the wider due diligence process.
Yes, you can validate supported point and polygon placemarks from KML here. Review the converted coordinates and geometry, then prepare the final TRACES geolocation in the required GeoJSON profile.
No. It flags a common out-of-range swap pattern, but both values can remain inside valid longitude and latitude ranges. Confirm the plotted location against the supplier country, a known place or a map before relying on it.
Geometry is step one
Once the geometry is usable, screen the plot against evidence around the 31 December 2020 cutoff and keep the output as one input to the wider risk assessment. A geometry pass alone never proves EUDR compliance.