What does the free EUDR GeoJSON validator check?
It checks whether a bounded GeoJSON FeatureCollection is readable and whether each feature has geometry, a stable plot_id, supported coordinate ranges, and a structure suitable for further EUDR plot review. The structural validation runs locally in your browser. It does not prove that a boundary identifies the correct production land or make a compliance decision.
What an EUDR GeoJSON plot file contains
GeoJSON stores geometry and properties together. For an EUDR workflow, each feature should represent an identifiable production plot or location and retain a stable link to the supplier, producer, batch, or source record that supplied it. Valid JSON is only the first layer: reviewers also need to know what the boundary represents and where it came from.
Structure, coordinates, and geometry checks
The validator expects a GeoJSON FeatureCollection and checks bounded file size and feature count before inspecting features. It reports missing geometry, missing plot_id values, and coordinates outside normal longitude and latitude ranges. These checks catch common handoff errors such as malformed JSON, swapped axes, incomplete features, and files that are too large for the public browser tool.
- FeatureCollection structure
- Maximum 1 MB and 500 features
- Geometry and plot_id presence
- Longitude and latitude ranges
Browser privacy and optional WHISP screening
Pasting or uploading the GeoJSON does not automatically send the file to Filovara. The bounded structural check runs in the browser. After a supported area plot passes validation, you can separately consent to send that one geometry to FAO Open Foris WHISP for a live satellite screening response. The local validator and the external WHISP request are distinct steps.
What this validator cannot establish
A clean result cannot confirm that the coordinates belong to the intended farm or forest, that the source record is authentic, that all production plots are present, or that a shipment satisfies EUDR. It also does not replace final product classification, legal review, risk assessment, or an authorised person’s submission decision.
Questions about this tool
Is the EUDR GeoJSON validator free?
Yes. The bounded browser validation and one optional public WHISP trial are available without a paid plan or account.
Is my GeoJSON uploaded during validation?
No. Structural validation runs locally in the browser. A supported area plot is sent to WHISP only after you explicitly choose the satellite-screening step.
Does a valid GeoJSON result mean the plot is EUDR compliant?
No. It means the bounded file passed the checks described on this page. Plot identity, completeness, evidence quality, risk conclusions, and legal obligations still require review.
What should I do after validation?
Confirm the plot’s real-world identity and source, connect it to the relevant supplier and product flow, resolve warnings, and retain the validated file version with the case evidence.