Digital Farm Twin
The digital farm twin is the canonical object at the centre of the platform. It is the virtual representation of all physical and operational entities of a farm — and the contract the digital farm APIs cooperate around.
Entities
| Entity | Source |
|---|---|
| Organization, Farm, Site | Digital Farm API |
| Field, Region (ROI) | Digital Farm API |
| CultivationPeriod, Stand, CroppingPlan | Digital Farm API |
| Task, Activity | Digital Farm API |
| Product, Lot, StockMovement, Machine, Animal … | Digital Farm API |
| Device and Observation records | Digital Farm API |
| Sensor & Datastream (high-frequency series) | Sensor Things — referenced by Device.sensorThingsUrl |
| Map & Layer | Spatio-Temporal |
| ProcessingService, ProcessingJob, Result | Digital Farm API |
The digital farm API serves 47 entities in 14 packages; see Packages & Entities.
Properties
- Spatial. Fields, regions, sites and activities carry a GeoJSON geometry; other locatable entities — devices, machines, observations — point at a region or a site (or, for sensors, at a STA Location).
- Temporal. Every observation, activity and layer carries a timestamp; history is queryable.
- Semantic. Classifications are concepts of the ontology, with AGROVOC as primary vocabulary, for cross-language and cross-platform interpretability.
- Relational. Every record links back to its parents by foreign key (e.g. an Activity references the Region it was carried out on, the Task it fulfils and the CultivationPeriod it belongs to; the machines and people deployed and the inputs and outputs are records of their own that point back at it).
See it in action
- Data Model — the entities, conventions and an example payload
- Ontology — the vocabulary behind every
…Uriattribute - Concepts · Architecture Overview — where the twin sits in the stack