tri

Global FieldID™

Simplify Farm & Field Data Sharing

play

We aim to

Tackle the challenge of data fragmentation in the agricultural industry and address the lack of standards of data produced on farms every day. 

How?

After ingesting and validating field boundaries, Global FieldID assigns a unique alphanumeric code to each field, enabling field identification of agricultural land plots, globally.

tri

Our users

user

Ag Input distributors / retailers

Bring together multiple data sources and improve interactions with your customers and suppliers.

user

Input manufacturers

Enhance the connectivity of your operations, collaborating more easily with the industry ecosystem.

user

Farmers

Integrate multiple field data sources, extracting more value from precision farming tools and making regenerative farming practices more visible to your customers.

user

Food companies

Strengthen traceability across your value chain and document real impact from your net-zero programs.

Without Global FieldID

The problem

Multiple field formats and identification systems exist across applications

portalmask
portalmask

Visit our developer portal

Global FieldID is an API-based system that assigns a Unique ID number to every agricultural land plot.

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. Does Global Field ID 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. 

We currently have coverage of the UK, France, and the Netherlands, and we are planning a rollout in the Americas during 2023 (starting with Brazil and the US). We expect smallholder geographies in Asia and Africa to be added in 2024.  

However, we will soon introduce the capability for users of the GFID product to create field IDs by submitting boundaries from anywhere in the world, even without having done the rollout for that country. 

7. 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​.  

8. What is the format of a Global FieldID?

arrow

There are two main types of identifiers in the Global FieldID product: 

  1. The Global FieldID, designed to be reliably communicated in both digital and non-digital channels. It is a short sequence of characters, like this: 15KW.V5JZ  

  1. The Global BoundaryID is designed for software data exchange, and is a UUID, like this: 2bbc9443-7b65-4a9c-806b-78d20298ab4b 

Further technical information is available on our Developer Portal

`
contact

Want to know more?

Reach out for more information

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

France

9.000.000 boundaries

Global FieldID™ Coverage

coverage