Skip to main content

Architecture Overview

AgriFoodData is structured along three pillars — data acquisition, data management, and data sharing — wrapped around a single canonical object, the digital farm twin.

The architecture functions as an integration layer. It does not replace existing FMIS, sensor stacks or AI services; it gives them a common contract.

The integration layer​

        Edge devices       Machinery            Services
Sensors & IoT FMIS & tractors GeoAI providers
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌────────────┐ ┌────────────────┐
│ Data │ │ Service │ │ Scheduling │
│ connector │ │ connector │ │ connector │
└─────────────┘ └────────────┘ └────────────────┘
│ │ │
▼ ▼ ▼
┌──────────────────────────────────────────────────┐
│ Digital farm twin · JSON-LD / WoT │
└──────────────────────────────────────────────────┘
▲ ▲ ▲
┌─────────────┐ ┌────────────┐ ┌────────────────┐
│ IAM & │ │ App / │ │ Clearing │
│ consent │ │ service │ │ house │
│ │ │ store │ │ │
└─────────────┘ └────────────┘ └────────────────┘
│
▼
┌──────────────────────────────────────────────────┐
│ Data spaces · Gaia-X · IDSA · external catalogues │
└──────────────────────────────────────────────────┘

The blueprint does not replace existing FMIS, sensor stacks or AI services — it gives them a common contract.

The six consented building blocks​

#BlockStatus
01Actor rolesConsented
02Core system componentsConsented
03Data modelsConsented
04API interfacesConsented
05Service registryConsented
06Data spaces (Gaia-X / IDSA)Draft

The digital farm APIs​

APIRole
Digital Farm APIThe REST binding of the data model — master data and operations: organisations, users, farms, fields, regions, cultivation, work, products, machines, animals, observations, economics, compliance, processing runs
Sensor Things APIIoT sensor management & real-time observations
Spatio-Temporal APIMaps, layers, rasters, vectors, AI outputs

See it in action​