Parcel boundaries, vectorised, not traced by hand.
An annual, edit-ready polygon layer for the cultivated parcels in your region.
- GSD
- High, 0.5–2 m
- Cadence
- Annual, one reference year per layer
- Platform
- High-res satellite
- Spectral
- RGB + NIR
- Formats
- GeoJSON or Shapefile
- Area unit
- hectares, per parcel
The files
| Ref | File | Format | What's in it |
|---|---|---|---|
| FB-001 | Polygon layer | GeoJSON or Shapefile | One closed polygon for each cultivated parcel in your region, following the visible cultivation edge. Built to be opened in your GIS and corrected polygon by polygon, then loaded into the registry. Delivered once a year, for the reference year you name when you send the region. |
| FB-002 | Per-parcel area | Hectares | Each polygon carries its area in hectares, computed from the polygon itself. It is a mapped area, so it sits beside your recorded area for the parcel. It does not replace it. |
| FB-003 | Reference timestamp | Reference year | The layer records the reference year of the imagery it was built from, so a reviewer can see which cycle any edge belongs to. |
How it works
P1In
Region in
Send the region boundary as a Shapefile or GeoJSON, and the reference year you want mapped.
P2Process
High-res pass
We pick high-resolution satellite imagery for that year over the region, at 0.5–2 m with RGB and near-infrared bands.
P3Process
Segmentation and vectorisation
Cultivated edges are segmented in the image, then turned into closed polygons with shared edges kept clean.
P4Out
Layer delivered
The polygon layer comes back in the format your system loads. Your team edits it in the GIS it already uses, checks the changed parcels against the orthophoto, then runs its usual registry update.
Limits
| No. | Condition | Effect on the layer |
|---|---|---|
| L-01 | Small and fragmented parcels | At 0.5–2 m a pixel is a fair slice of a narrow strip. Very small parcels and thin strip fields come out as a few pixels wide, and the edge may merge with a neighbour. Expect these to need the most editing. |
| L-02 | Visible edges only | The layer follows what shows in the image: a change of crop, a track, a hedge line. Where two parcels are cultivated alike with no visible edge, the split is missing. Ownership records are never consulted. |
| L-03 | One reference pass a year | The layer is as current as its reference year. Changes after the imagery date, such as a field split in spring, are not in it. It is not a live or on-demand map. |
| L-04 | Cloud and season | Imagery has to be usable for the reference year. Cloud, haze and bare-ground timing can hide an edge. Areas with no usable scene are listed rather than filled in. |
| L-05 | Not a legal boundary | This is a mapping layer for registry work. It is not a cadastral survey or a legal boundary determination, and it does not decide eligibility. |
Why this exists
Every update cycle a technician opens the newest orthophoto behind the registry, finds each parcel whose edge has moved and redraws it. It is careful work and there is a lot of it. When the schedule slips, farmers apply against parcels that still show the last cycle's edges, and the differences surface later as area mismatches. This gives the technician a first draft to correct instead of a blank screen to trace.
Who it's for
Who it's for
- GIS officers at paying agencies who keep the land parcel identification system and run its update cycle.
- Agri-lenders and insurers who hold a parcel layer for collateral checks or underwriting and need it refreshed.
- The technicians who will edit the layer afterwards.
Who it's not for
- Teams that need a legal or certified boundary. That takes a cadastral survey.
- Teams that need eligibility decided. The layer shows parcels, and the agency's own rules decide what is eligible.
- Real-time or on-demand boundaries. The layer is annual.
- Parcels well below the pixel size, such as garden plots and narrow strips.
Technical and procurement questions
Q01Does this replace a legal survey?
No. It is a mapping layer for registry use. It follows visible cultivation edges and makes no legal boundary determination.
Q02What do you do with shared or ambiguous boundaries?
The layer follows the cultivated edge as it shows in the image. Where two parcels look the same and no edge shows, the split is missing and your team adds it.
Q03What resolution do you work at?
0.5–2 m GSD. Fine field edges below that may not resolve, and the smallest parcels will need the most editing.
Q04How current is a delivered layer?
As current as the annual reference pass. It is not real-time.
Q05What formats does it come in?
GeoJSON or Shapefile. Tell us which your registry loads, and which coordinate system it uses.
Q06Who edits the layer once it arrives?
Your technicians do. The polygons are a first draft for the photo-interpreter to accept, move or delete, parcel by parcel, using the same review steps your update cycle already has.
Q07Can we check it against our existing registry?
Yes. Every polygon carries its area in hectares, so you can lay the layer over your reference parcels and compare edge by edge and area by area before loading anything.
Q08Who owns the layer you deliver?
Use and ownership terms for the delivered layer are set in the contract before work starts. The satellite archives the imagery comes from keep their own licences.
Send us the region and the reference year.
Or ask about your registry in the chat.