Data Requirements
The European Union Deforestation Regulation requires operators to submit the geolocation of plots of land in GeoJSON format to the EUDR Information System.
Vantage validates plot geometry at registration and import time to help users detect issues before running analysis or preparing due diligence submissions.
Geometry Types
| Geometry Type | Description | EUDR Usage | Vantage Handling |
|---|---|---|---|
| Point | A single coordinate pair [lon, lat]. | Allowed for plots smaller than 4 hectares, except cattle. | Accepted. Expanded into a buffer polygon for analysis. |
| Polygon | A closed shape with at least 4 coordinates where first equals last. | Required for plots larger than 4 hectares. | Accepted. Validated for closure and geometry issues. |
| MultiPoint | A set of multiple points. | Supported by the EUDR spec for edge cases. | Not currently supported. |
| MultiPolygon | Two or more polygons grouped together. | Supported by the EUDR spec for multi-parcel properties. | Supported by the analytics backend where available; validate current API behavior in the API Reference before integration. |
| LineString / MultiLineString | Sequences of points forming lines. | Not valid for production place declaration. | Rejected. |
Common GeoJSON File Errors
The following list follows the common EUDR GeoJSON requirement categories published by the European Commission.
| # | Error Type | Description | Vantage Handling |
|---|---|---|---|
| 1 | Coordinate lines crossing | Polygons cannot self-intersect. | Rejected. |
| 2 | Overlapping sides | Internal overlaps or folds inside polygons are not accepted. | Rejected. |
| 3 | Doughnut shapes | Holes inside polygons are not accepted by the EUDR system and may need splitting. | Supported in some workflows; review before EUDR submission. |
| 4 | Open polygons | First and last coordinates must be identical. | Rejected. |
| 5 | Invalid geometry types | LineString and MultiLineString are not valid plot geometries. | Rejected. |
| 6 | Straight lines | A polygon must enclose an area. | Rejected. |
| 7 | Duplicate coordinates | Points can collapse into duplicates when rounded. | Accepted in some cases; reviewed during validation. |
| 8 | File syntax errors | Missing or extra characters make the GeoJSON invalid. | Rejected. |
| 9 | Invalid property names | Wrong property names or casing can break external submissions. | Rejected when they do not match the API schema. |
| 10 | Invalid file format | EUDR upload workflows expect GeoJSON. | Not applicable to direct API JSON payloads. |
| 11 | Invalid coordinate range | Latitude must be within +/-90 and longitude within +/-180. | Rejected. |
| 12 | Invalid ISO2 country code | Producer country must be valid where required by a submission workflow. | Not required for plot geometry registration. |
| 13 | Password protected files | Locked files cannot be processed. | Not applicable to direct API JSON payloads. |
| 14 | Data representation issues | Values must use the expected types and coordinates must be [lon, lat]. | Rejected when they do not match the API schema. |
| 15 | Polygons with holes inside | The EUDR system can treat holes differently than analysis systems. | Supported in some workflows; review before EUDR submission. |
| 16 | File size above EUDR limits | EUDR upload size limits can reject large files. | Not applicable to direct API JSON payloads. |
Summary
Vantage validates geometry before analysis so teams can catch common data quality problems early. The validation is designed to support operational analysis and EUDR preparation, while still giving teams enough flexibility to work with real-world geospatial datasets.