Global FieldID

Simplify Farm & Field Data Sharing

play

Integration options

Discover how our technology offers versatile solutions

Icon
Discover our API

If you're utilising 3rd party applications, Global FieldID offers an API-based solution that integrates with your existing digital systems. With the GFID API, 3rd party applications can effortlessly access, search, contribute field and boundary data.

blue circle
green circle
yellow circle
feature
Icon
Visit our platform

Our Global FieldID User Interface offers a responsive, user-friendly solution for farmers and agronomists to easily discover and update fields, while also serving as a valuable tool to visualise and demonstrate the GFID concept.

blue circle
green circle
yellow circle
feature

Open data initiative

Download country boundaries in bulk from our database, and use Global FieldID

to simply reference land plots in a standard way

 

Our goal is to make field boundary data easily accessible to provide the building

blocks of new products to support the transition to a nature-positive food system

initiative icon
For businesses
Assign a unique reference to land plots across your products and exchange data more swiftly
initiative icon
For NGOs
Use our boundary data to build and connect new products that will support transparency for climate action
initiative icon
For research
Easily compare multiple datasets to gain insights from different sources

France

9.000.000 boundaries

Global FieldID Coverage

Our partners

GreenO
Slow Philosophy
Farmie
BTG Pactual
METOS by Pessl
InCeres
Ever.Ag
Meteotrack
Syngenta Group
Agmatix
Simpsons Malt
IMBR ARGO
Yara
Climate Engine
GreenO
Slow Philosophy
Farmie
BTG Pactual
METOS by Pessl
InCeres
Ever.Ag
Meteotrack
Syngenta Group
Agmatix
Simpsons Malt
IMBR ARGO
Yara
Climate Engine
GreenO
Slow Philosophy
Farmie
BTG Pactual
METOS by Pessl
InCeres
Ever.Ag
Meteotrack
Syngenta Group
Agmatix
Simpsons Malt
IMBR ARGO
Yara
Climate Engine
arrow
arrow

Frequently asked questions

1. What is the difference between a field and a boundary?

arrow

FIELD

  • It’s a conceptual object. Fields have a defined location, but they aren’t tightly tied to a specific geometry. The shape of the field can change over time and still be the same field with the same ID.
  • It has a degree of permanence beyond seasons and retains history over time. Therefore, it’s more stable than a Boundary and can be used for use cases that do not require complex spatial processing and just need to match related data (e.g., group data for traceability).

BOUNDARY

  • It’s a spatial concept. It is based on geometry and spatial delineation of a land parcel.
  • Boundaries are used most in precision agriculture. They refer to an area of land specific to an operation, even if it only covers part of a field.
  • In the Global Field ID product, new boundaries are created within a Field based on types, seasons, users, and sources.

 

One Field ID can connect many boundaries IDs

Seasons

Harvest 2021, Harvest 2022, etc.

Users

User 1 of field 1, user 2 of field 1

Origins

Government LPIS, grower’s FMIS, earth observations

Practices

Delineated, Fertilizer, Harvest boundary, Etc.

feature

FIELD ID 1

Boundary IDs are based on geometry and spatial delineation of a land parcel.

New boundary IDs are created within a field ID based on practise, season, user and origin.

Field ID is not tied tightly to geometry like a boundary ID.

It has a degree of permanence beyond seasons and retains history over time.

2. What is the relationship between fields and boundaries?

arrow

We have a 1-to-many relationship between fields and boundaries. However, each field always has one active boundary, defining its spatial footprint at a time, which must not overlap with any other field’s active boundary.

The Global FieldID product allows any number of boundaries to be registered, and thus any point on the map might have multiple boundaries representing specific operations.

The boundary of a field can change over time, but the history is retained using a link between the field and boundary, each of which has a timestamp. Any ‘old’ boundary is retained. This helps application developers to maintain an up-to-date view as boundaries change.

3. How does Global FieldID keep track of changes to fields over time?

arrow

The Global FieldID product tackles changes over time by decoupling the concept of the field and its boundaries and storing history.  

There are two types of changes: 

Changes to the boundary that don’t turn it into a different field. 

  • The old boundary ID is ‘deactivated’ (not deleted) and a new boundary is linked in its place (the date of the change is recorded). The field ID doesn’t change. 
  • Since the old boundary still exists with its own ID, use cases that depend on identifying a specific boundary are not impacted but are able to understand that the field itself has since changed. 

Changes to the boundary that turn it into a different field (e.g., splits, merges, and farmland development).

  • It is possible to ‘deactivate’ one or more field IDs and replace them with new fields, each of which has its own boundary (e.g., when a tree line is removed to create a larger single crop area, one new field ID can be created to replace the previous two).
  • All applications integrating the Global FieldID product will be able to trace these events and access the history. 

4. What is the relationship between fields and crop zones polygons?

arrow

A crop zone is identified as a boundary within the Global Field ID product (GFID). A boundary ID can be used to identify a specific area of land within the field because GFID also allows the registration of multiple boundaries.  

5. Does Global Field ID support all kinds of different field shapes?

arrow

Yes. Alongside the primary boundary used to define the location of a field, there can be other types of boundaries, each used for a specific purpose. Even if there is a region within the field, spanning multiple fields or a region that is not part of any field, it can be identified with a boundary ID. 

We will soon introduce the ability for API client applications to register such boundaries on behalf of their users.  

6. Where is Global FieldID available?

arrow

The Global FieldID™ service can be used to create identifiers anywhere in the world, by submitting a boundary. Users can directly draw or upload their own fields in our free web application, enabling a ‘crowdsourcing’ approach. In addition, co-operatives, retailers, ag-tech software vendors and other actors in the supply chain can also do this on their behalf, allowing the identity of the field and its spatial footprint to be shared across the supply chain and between all the systems the grower interacts with, no matter where the field is located.

However, the ambition of the Global FieldID™ initiative is to map all the world’s agricultural land and make this map visible to the whole industry. To accelerate this process, we actively source boundary data to ‘pre-map’ entire countries and regions using a combination of open government data (when available) and remote sensing techniques. You can see the countries for which we currently have significant coverage at the bottom of this page, and can access the data on our download hub.

7. Does Global FieldID plan to serve smallholder farmers outside Europe?

arrow

The Global FieldID product aims to have a complete set of boundaries for each country it covers. 

Global FieldID™ is live  in the UK, France, the Netherlands, Germany, Belgium, Poland, Italy, as well as the Nordic and Baltic countries. In 2023, we have also expanded it to include the US and Brazil. In 2024, in addition to coverage in Europe we have also been working to add smallholder geographies in Asia and Africa.

Furthermore, it is also possible to create field IDs by submitting boundaries from anywhere in the world, even without having done the rollout for that country. The user can either draw their field boundary on the map or upload a JSON file directly to the GFID user interface. 

8. Does Global FieldID serve smallholder farmers?

arrow

Yes! The ambition of the Global FieldID™ initiative is to map all the world’s agricultural land including countries where smallholdings are prevalent, and our existing coverage is not limited to industrialized farms.

In smallholder markets fields can be more difficult to reliably delineate from space and therefore ‘crowdsourcing’ can be more effective. The Global FieldID™ service has been built to facilitate this process. Smallholders can directly ‘claim’ their fields by drawing or upload their own fields in our free web application. In addition, co-operatives, retailers, ag-tech software vendors and other actors in the supply chain can also do this on their behalf by integrating with Global FieldID™, helping to literally ‘put smallholders on the map’ as in countries that have already developed sophisticated land parcel identifications systems (LPIS).

9. Does Global FieldID store information about the field (e.g., carbon footprint)?

arrow

The Global FieldID API only collects metadata about the field itself and does not hold any type of data (e.g., data about farmers’ practices). 

We believe that GFID should be an enabler for all, and not compete with existing data providers or farm management applications. It aims to be a “universal language” that ensures data exchange between applications and data discovery throughout the supply chain​.  

contact

Want to know more?

Reach out for more information

We respect your privacy, for more info check our Privacy Policy