FAQ EUDR Check

For registering EUDR plot of lands or (parcels in our API) start with this API endpoint here.

You can use the API User interface directly after you authorized with your API Key or use any other method to send a HTTP POST request to the API (e.g. Postman).
There are some requirements to match when you register EUDR parcels in our API. First, the data has to be in proper GeoJSON format (check your file e.g. with GeoJSON Lint). Additionally make sure the properties of the GeoJSON match the EUDR requirements. The following attributes are mandatory:

• commodity: valid options are: cattle, cocoa, coffee, oilpalm, rubber, soya or wood
• production_end: date of production / harvest in ANSI format: YYYY-MM-DD. The EUDR risk analysis will be conducted on this date.

After you have sucessfully registered an EUDR parcel you can expect the risk analysis after 24 hours at maxium. Please refer to the the parcel risk API endpoint. A HTTP GET request along with your parcel_id from the registration process and the API Key will show you the EUDR check result in GeoJSON format. Note, that you can always query a list of your registered parcels with the parcel list endpoint.

The EUDR Check will comprise the following items:

• Deforestation risk low / medium / high
• Land cover in % for forest, plantation, shrubs and no-trees at base line date (31.12.2020 or before)
• in case forest was present at baseline date: assessment of deforestation or degradation (wood only) for the forest patch, in case no forest detected on the parcel the deforestation risk is low.
• sufficient reference information allowing to understand the assessment. This information will also be used in case of an audit.
  • auxiliary information such as: generation date, model version, area of polygon, center point, vertices, country risk, geohash, map items like legend, scale
  • link to the landcover map (PNG) close to the baseline date
  • link to the True color satellite image (PNG) close to the baseline date and close to the production end date
  • in case forest has been detected on the parcel: link to the deforestation risk map (PNG) close to the production end date

We are using various datasets to conduct the EUDR risk analysis, e.g. Sentinel-1 SAR, Sentinel-2 and other open datasets. The datasets are augmented and improved by methods developed by Geocledian. Final results are verified and validated by samples. Please contact us for further details - we are happy to share the complete list of datasets to our customers to be fully transparent.

Please refer to the EUDR parcel risk API endpoint. In the response of the EUDR risk retrieval you will find links to all the images available.

During the registration process the following is ensured:

• only polygons or points are allowed
• mandatory attributes for EUDR are checked (commodity, production end date)
• validation for correct spatial reference system (WGS84)
• technical validation of the provided geometry (sliver polygons, self intersections)

Please note that the creation of a batch of EUDR parcels provides further validation steps such as overlap checks with other parcels.

A batch represents a group of geolocations of a supply chain to be placed on the EU market. The formation of a batch allows to check and validate the consistency of a set of parcels, such as same geographical area, no overlaps, minimum distance, and formation of a region.
Please note: If an error occurs during the creation of a batch then the batch will not created.

The following validation rules apply:

Errors

• parcel geometries may not be duplicate within the batch
• parcels may not be duplicate regarding all attributes within the batch
• parcels need the same attributes for country_iso and commodity

Warnings

• overlapping geometries will be flagged
• outlier geometries will be flagged

Internally when a EUDR batch is created a regional geometry is automatically derived from all parcels of the batch. This regional geometry can be assessed later in the EUDR regional risk assessment.
So to summarize when creating a batch of EUDR parcels you can make use of another level of validation which is often required in a shipment that is placed on the EU market and would not be possible on single parcel level.

A EUDR batch is created with a simple list of already registered EUDR parcel_ids in an HTTP POST request against this API endpoint.

Currently this is not possible, because this would introduce a lot of complexity to the validation process of a batch.

Yes, currently GeoJSON is the only supported input format for our EUDR endpoints. This is aligned with the EU Information System for the EUDR which also handles only GeoJSON currently.