smart-data-models/datamodel.agrifood

Agrifood topic data models repository

dataModel.Agrifood

List of data models

The following entity types are available:

• AgriApp. This entity contains a harmonised description of a generic app made for the Agrifood domain. This entity is primarily associated with the agricultural vertical and related IoT applications.

• AgriCrop. This entity contains a harmonised description of a generic crop. This entity is primarily associated with the agricultural vertical and related IoT applications.

• AgriFarm. This entity contains a harmonised description of a generic farm made up of buildings and parcels. This entity is primarily associated with the agricultural vertical and related IoT applications.

• AgriGreenhouse. This entity contains a harmonised description of the conditions recorded within a generic greenhouse, a type of AgriParcel.

• AgriParcel. This entity contains a harmonised description of a generic parcel of land. This entity is primarily associated with the agricultural vertical and related IoT applications.

• AgriParcelOperation. This entity contains a harmonised description of a generic operations performed on a parcel of land. This entity is primarily associated with the agricultural vertical and related IoT applications.

• AgriParcelRecord. This entity contains a harmonised description of the conditions recorded on a parcel of land. This entity is primarily associated with the agricultural vertical and related IoT applications.

• AgriPest. This entity contains a harmonised description of an agricultural pest.

• AgriProductType. This entity contains a harmonised description of a generic agricultural product type. This entity is primarily associated with the agricultural vertical and related IoT applications. The AgriProductType includes a hierarchical structure that allows product types to be grouped in a flexible way.

• AgriSoil. This entity contains a harmonised description of a generic soil. This entity is primarily associated with the agricultural vertical and related IoT applications.

• Animal. An observation of animal conditions at a certain place and time. This data model has been developed for the IoF2020 UC ShareBeef by UCO and SensoWave.

• AnimalDisease. Object modelling an animal disease for a livestock farm.

• AnimalMovement. Object modelling of an animal movement for a livestock farm.

• Carcass. Object modelling a carcass of an animal for a livestock farm.

• Compartment. Artificial area in a building or department that is measured by certain sensors. A compartment is not necessarily a physical separator. It can be a department or a grouping of several pens within a department that are being measured by the same sensor.

• FeedRegistry. Object modelling a feed registry for a livestock farm.

• MeatProduct. Object modelling a meat product for a livestock farm.

• Pen. Fenced area in a building or department or outside housing a group of animals. Animals in a pen can move and interact freely. Pens are often not completely separated from each other (half walls, iron bars, fences,…), making it possible that animals from neighbouring pens can see/touch

• VeterinarianTreatment. Object modelling a veterinary treatment for a livestock farm.

Contributors

Link to the 11 current contributors of the data models of this Subject.

Contribution

You can raise an issue or submit your PR on existing data models

datamodel.agrifood's Issues

Broken links in context.jsonld

Most of the links in context.jsonld seem to be broken (404) e.g.

https://smartdatamodels.org/dataModel.Agrifood/AgriApp
https://smartdatamodels.org/dataModel.Agrifood/AnimalMovement

Question regarding workOrder and workRecord

Hi guys,

In AgriParcelOperation there are strings for workOrder and workRecord. The descriptions for each refers to Relationship with the workorder/workrecord for the execution. I would have expected this relationship to be further elaborated on, but see no other reference in your Agrifood Data Model of these concepts. Maybe i'm just missing them?

I imagine they could each be an entity on their own? But looking at the elegant nature of your data model i'm sure there is a reason.
I'm hoping that you could assist in directing me to more detail regarding these items, if you have elaborated on them somewhere...

Thanks

Some links swapped between Normalized and KeyValues flavours

Hello,

Some links are swapped between Normalized and KeyValues flavours.

It's the case for Agrifarm, but I suspect there may be other places where it happens.

The NGSI-LD kv/normalized examples "embedded" in the spec are swapped.

The 2 examples links are swapped : link1 and link2.

There's a last more subtle diff.
The hasAgriParcel Relationship isn't modelled the same way here (array of objects) and in the spec example (array of values).