Validator scope

Supported checks

Publication-ready draft · owner approval required

This copy is ready for owner review, not evidence of publication authorisation. Confirm the final wording, source links and operational privacy statements before treating this page as approved public guidance.

PlotProof is a no-login, browser-only preparation aid. It reads a selected GeoJSON, JSON or CSV file in the open tab, reports the checks below, and offers a separate derived file only after you review and confirm the changes shown. The submitted source is not replaced.

Accepted input

GeoJSON or JSON up to 25 MiB: a FeatureCollection, Feature or supported geometry object.
CSV up to 25 MiB with plot_id, longitude and latitude columns and one row per plot vertex.
UTF-8 CSV with an optional BOM, quoted fields and escaped double quotes.
Duplicate CSV headers after case, whitespace and separator normalisation are rejected.

Checks and result meanings

Definite format findings: malformed JSON, unsupported GeoJSON shapes, malformed coordinate positions, missing CSV columns, duplicate headers and unreadable CSV rows.
Definite range findings: longitude outside −180 to 180 or latitude outside −90 to 90. A numeric range cannot prove that the source used the right axis order.
Heuristic warnings: values that look like latitude and longitude may have been reversed. Compare the source labels and reference information; PlotProof never swaps coordinates.
Preparation information: each longitude and latitude value is checked for at least six decimal digits under the EUDR preparation criterion. PlotProof does not add digits or round coordinates.
Geometry findings: open polygon rings can be proposed for closure by repeating the first position; self-crossing rings are checked pairwise up to 2,000 positions; exact repeated geometries are reported; polygon pairs that appear to share area are reported as possible overlaps.
Touching boundaries are not reported as area overlap. Containment is reported when the geometry check can establish that one assessed polygon lies within another’s material area; holes and invalid or oversized rings can make a result unassessable.

Unassessable cases and recovery

Missing geometry, unusable positions, invalid or degenerate rings, CSV rows with missing or non-numeric coordinates, and rings over 2,000 positions are identified or skipped where the affected check cannot be trusted. Review the named record or CSV source row, correct the original source from authoritative data, and run the validator again. A warning or a clean result never proves that an unassessed case is correct.

Exports and traceability

GeoJSON exports retain FeatureCollection metadata and feature properties and show ring closure before download. CSV exports identify omitted source rows, group rows by the first plot_id, retain the first extra-property values when a group conflicts, and disclose header, BOM, quoting, ordering and line-ending changes. Very large or unusual inputs should be compared with the retained original preview before use.

What this does not establish

A syntactic or geometry result is not proof of data origin, supplier identity, geographic eligibility, EUDR compliance, legal compliance, authority acceptance or submission to any government system. PlotProof does not provide legal advice, transform coordinate reference systems, verify country borders or inspect a supplier portal. Review the source and obtain the decisions or acceptance required by your own process.

Sources

RFC 7946 §3.1.1 — Positions — GeoJSON positions use longitude first and latitude second; the validator does not swap axes.
RFC 7946 §3.1.6 — Polygon — A linear ring is a closed LineString with at least four positions, with the first and last positions equivalent.
RFC 7946 §4 — Coordinate reference system — RFC 7946 GeoJSON uses WGS 84 coordinates; this checker does not transform another reference system.
RFC 4180 — Common CSV format — Quoted fields, escaped double quotes and record separation inform the CSV reader; CSV is accepted only with the required PlotProof columns.
EUDR Information System GeoJSON description — The product’s preparation guidance repeats the published longitude/latitude order requirement.
EUDR Information System operator FAQ — geolocation — The six-decimal check is presented as an EUDR preparation criterion, not as a general GeoJSON validity rule.

← Open the validator

Read the current preview privacy information or return to the free validator.