Skip to content

Plots and mapping

This is the most consequential page in the Supply Base section. A plot without a boundary can’t be checked for deforestation, which means it can’t appear properly in an EUDR report, which means the farm effectively can’t be sold into the EU market with confidence.

  1. Open the supplier from Suppliers.
  2. Open its Plots tab.
  3. Click Create to open the new-plot form.
  4. Fill in the details and save.

Open the plot menu - the … button - and choose one of three options.

Draw the boundary directly on the map. Use the map search bar to jump to the village or place first, then click the map to add points around the plot.

Best for plots you know well, or for correcting a boundary that came back from the field slightly wrong.

Upload an existing boundary file. Use this when boundaries were collected with other equipment, or supplied by a cooperative or government dataset.

For many plots at once, use bulk import instead - it accepts GeoJSON and KML.

Type a latitude and longitude, or drop a pin on the map.

A single point is weaker evidence than a boundary - it locates the plot but doesn’t describe its shape or area. Use it when a full boundary isn’t available, not as the default.

Separate from plots, a supplier has a house location - where the farmer actually lives, which is often not on the land they farm.

In the right-hand panel, next to Supplier House, use Set location or Edit location.

When two plot boundaries cross, the map can colour the overlapping area and label it with the plot names and the overlap percentage. That is on by default.

Under the map, in the third column after Satellite Analysis Overlay, use Plot overlays:

  1. Show nearby plots — off by default. Tick it to load neighbouring plots from other suppliers nearby. The choice is remembered in this browser.
  2. Show overlaps — on by default. Untick it to hide overlap colours and labels. Plot boundaries stay on the map.

A Supplier Report (Show Report on the supplier page) never shows those overlap names from other plots, on screen or in the printed PDF.

A boundary walked with the Field App keeps the GPS readings taken at each point. Open the plot and look under the map:

  1. Tick Show Coordinate Order to number the points in the order they were walked. The first point is green and the last is red.
  2. Hover over a point to see when it was recorded, plus its altitude, speed and accuracy.
  3. In the Geolocation Status & Warnings table, Walk time shows when the walk started and ended and how long it took.
  4. Click Replay walk to play the walk back on the map. A dot follows the route in the order and at the pace it was walked, drawing the path behind it, and the bar shows the time, speed and accuracy at that moment. Pause, drag the slider to any moment, or pick a faster speed (10x to 120x). With All Plots selected, choose which plot’s walk to replay next to the button.

Drawn, uploaded and imported boundaries have no walk times, so Walk time shows “-” for them and there is nothing to replay.

When a walked boundary has GPS errors, such as a point that jumped away, Orijin keeps the walk as recorded and also saves a cleaned-up copy, which is the one the plot uses. Open the plot to compare them:

  1. Under the map, the legend shows the Boundary in use and, as a blue dotted line, the Walk as recorded with its area. Untick it to hide it. Hover over its points to see the GPS readings.
  2. Above the boundary list, if the clean-up made the boundary worse, click Use walk as recorded. Add a reason if you like and confirm. The plot area, the farm total and the map then follow the walk as recorded, and a note is added to the plot saying what changed.
  3. To go back, click Use cleaned-up walk. Nothing is deleted either way.

To clean a boundary yourself, open Edit on the boundary in use and click Apply cleaner. The editor shows the cleaned boundary, the one before it, and how the area changed. Check it, then Save, or click Undo clean-up.

A plot is mapped once its boundary or GPS point is saved. That’s the definition behind every mapping-coverage figure in the product, so if your coverage number looks wrong, it’s counting exactly this.

The strongest boundary is one walked on foot with the Field App, at the plot, with the farmer present to confirm where the edges are. Everything else is a reconstruction. Where you have the choice, walk it.

The walk never stops by itself. When the walker comes back within 10 m of where they started, after walking all the way round, the Field App asks You’re back at the start: tap Finish walk to end the walk, or Keep walking if the boundary isn’t finished. It asks again only after the walker has moved more than 20 m away and come back.

A photo added with Take photo saves where the phone was at that moment, as long as the app is allowed to use the location. This also applies when the walker picks From Photos there instead of taking a new picture. When the photo carries its own GPS position, that position is used instead. Files added with Upload pictures don’t get the phone’s location.

When the walker taps Save & Exit (or leaves the walk), the Field App checks the boundary before saving it. A normal walk saves straight away.

Blocked - “This boundary can’t be saved yet”. The walk doesn’t look like a full plot: too few points, or the phone barely moved. A check set to Critical in Checks blocks the same way, for example an area smaller than a plot can be.

  1. Tap Walk again to start the walk over. This is the right answer almost every time.
  2. Only if the walk really is right, tap Save anyway, choose why (The plot really is this small, GPS problem, it can’t be walked again now or Other reason) and tap Save with this reason. The reason is saved with the boundary, together with who saved it and when.

Warning - “Please check this boundary”. Something looks unusual: the walk looks like a line rather than a loop, the walked area is very different from the area the farmer gave, the farmer’s area was entered as zero, part of the walk is missing because the GPS stopped, some points jumped far away from the walk, the boundary crosses itself, or the area is smaller or larger than a plot can be. Tap Walk again, or It is correct, save if the boundary is right. When part of the walk is missing, Resume also lets the walker carry on from where they stopped.

Open Organisation config → Checks. Under Boundary and walk and Area, each check can be switched off, set to Critical (the walk is blocked until the walker gives a reason) or Warning (the walker only confirms), and its limit changed: the fewest points in a walk, the shortest distance across the plot, how much a walk may look like a line, the GPS gap, the smallest and the largest area, and how far the walked area may differ from the farmer’s. Farmer’s area is zero flags a plot where the farmer entered 0 as the area, on the phone and in the survey review. Walk barely moved and Walk looks like a line only run in the Field App. When the walked area is far from the farmer’s, the Field App only warns, even if the check is Critical.

A survey’s own Checks tab can change these for walks done inside that survey; anything it leaves out follows the organisation. Walks recorded outside a survey use the organisation’s settings.

With internet, the Field App can also warn when the walk overlaps a nearby plot by at least Warn from under Overlaps, looking at plots within Compare within of the walk. This is off by default: switch Field app on for Overlapping plots on this tab, or on a survey’s Checks tab, to use it.