OCSM extension for the Compost monitoring log.

[nikoskal]

For the needs of SIP5 we need to extend OCSM to model parameters relevant with compost management and monitoring. The indicative example in the following table includes all the relevant properties that need to be modeled.

This is also necessary for the OpenAgri "Farm Calendar" component and the the OpenAgri "Reporting Service".

<br / id="docs-internal-guid-638dbad9-7fff-8bbf-202d-0ed54cce06dd">

Date	Composting Data	source
5/1/2025	“Action”: “Start composting”	user
5/1/2025	“Action”:  “Add raw material”,  “Compost Inputs”:[{“Type”: “Cow Manure” , “Quantity”: 100, “unit”; “Kg”},{Type: “Vegetables” ,“Quantity”: 100, “unit”; “Kg”},{Type: “Straw/hay” , “Quantity”: 100, “unit”; “Kg”},{Type: “composty” , “Quantity”: 50, “unit”; “Kg”},]	user
6/1/2025	“Measurements”: {“Type”: “Temperature”, “Quantity”: 50, “unit”; “Celsius”},{“Type”: “pH”, “Quantity”: 6, “unit”; “”},{“Type”: “Moisture”, “Quantity”: 45, “unit”; “%”},	Sensors
7/1/2025	“Measurements”: {“Type”: “Temperature”, “Quantity”: 51, “unit”; “Celsius”},{“Type”: “pH”, “Quantity”: 6, “unit”; “”},{“Type”: “Moisture”, “Quantity”: 45, “unit”; “%”},	Sensors
8/1/2025	“Action”: “irrigate”, “Dose”:10, “Unit”: “Lt”	Actuator solenoid valve
9/1/2025	“Action”: “turn”	user
10/1/2025	“Measurements”: {“Type”: “Temperature”, “Quantity”: 49, “unit”; “Celsius”},{“Type”: “pH”, “Quantity”: 6.1, “unit”; “”},{“Type”: “Moisture”, “Quantity”: 48, “unit”; “%”},	Sensors
11/1/2025	“Measurements”: {“Type”: “N”, “Quantity”: 10, “unit”; “%”},{“Type”: “P”, “Quantity”:15, “unit”; “%”},{“Type”: “K”, “Quantity”: 25, “unit”; “%”}	NPK sensor
10/2/2025	“Action”: “Finish composting”	User

[nikoskal]

@arruda Some more details with regards to Farm Calendar

The example data mentioned in this issue need to be maintained in the OpenAgri Farm Calendar.
The data types that are assigned with source "user" will be imported through the GUI.
The data types that are assigned with source "sensor" will be derived from sensor measurements and will use the REST API of the Farm Calendar.

[JoleVLF]

This is fine, when API is ready, I need API endpoint info (response, request params) and reporting will be integrated with that one.

[arruda]

Hi @nikoskal I'm thinking here if we can use this as a generic observation for the measurements and the generic operations for the actions, and I believe this could be done.
For this operation, I think the IrrigationOperation works as it is:
8/1/2025 “Action”: “irrigate”, “Dose”:10, “Unit”: “Lt”

The only one that it might be a bit bad and will require a built-in Operation is the Add raw material, since it's not just a simple field, and it would be hard for the user to, lets say, write a json with all the compost inputs in the generic operation description field for instance.

Although we have a tight schedule, I believe I can create one built-in AddRawCompostMaterial Operation to the farm calendar (although this will probably have to be fine-tuned later along with the OCSM specific for this operation).

[arruda]

@JoleVLF You can check out the swagger docs for the current farm calendar API schema:
https://editor-next.swagger.io/?url=https://raw.githubusercontent.com/openagri-eu/farmcalendar/refs/heads/dev/schema.yml

For the generic observations and operations what are you looking for is this workflow:

1. GET /api/v1/FarmCalendarActivityTypes/?name={ObservationTypeName}&: This will filter out for you and show only the types of activity with that specific name, so you can use this to find the the ID of the CalendarActivityType you are looking for.
2. GET /api/v1/Observations/?=activity_type={UUID}&: this will return only the observations of the calendar activity type you are looking for. You can use this for the measurements.
3. GET /api/v1/FarmCalendarActivities/?=activity_type={UUID}&: I believe you can use this for the generic operations (ie. compost turning and compost start/finished).

The Irrigation can be retrieved by using existing IrrigationOperation, I believe it should fit this case:
GET /api/v1/IrrigationOperations/

[JoleVLF]

@arruda I can request json data from Farm Calendar APIs? (So I do not need to use json ld for this examples)?
One important thing, with data you have provided here (API calls), I can have similar information like example above?
Could you also please add example data here:
https://github.com/openagri-eu/OCSM/blob/main/examples/generic_farm_calendar_v2.json

You can create _activity, observations and farm_a_calendar json examples just to have it.
I will need to change current template rendering because data is different from examples we currently have.

[JoleVLF]

@arruda

Do we have any info on SIP2 integration livestock:
The geometries of the pastures and details/properties about the animals of the herd
will be modeled in the OpenAgri Farm Calendar. As it is detailed described in D2.7
the following parameters will be maintained:

[JackJackUM]

Hi, a late response...sorry for that...indeed these are all action or measurements that should be available in the farm calendar. Sensors make measurements that are modellen in the OCSM as sosa:Observations. I propose to model the "actions" (by the user or any other entity) as ploutos:Operations. We already have quite a set of possible operations (irrigation, fertilization, pestmanagement etc) in the OCSM, so we can add a ploutos:Composting operation that models the start and end of a composting process and some sub-operations like, ploutos:AddRawMaterialOperation and ploutos:Turn (what does this mean exactly?). ploutos:IrrigationOperation already covers the action "irrigate" under the assumption that this is similar to irrigating a field with some irrigation system (correct?).

[JackJackUM]

Hi, a late response...sorry for that...indeed these are all action or measurements that should be available in the farm calendar. Sensors make measurements that are modellen in the OCSM as sosa:Observations. I propose to model the "actions" (by the user or any other entity) as ploutos:Operations. We already have quite a set of possible operations (irrigation, fertilization, pestmanagement etc) in the OCSM, so we can add a ploutos:Composting operation that models the start and end of a composting process and some sub-operations like, ploutos:AddRawMaterialOperation and ploutos:Turn (what does this mean exactly?). ploutos:IrrigationOperation already covers the action "irrigate" under the assumption that this is similar to irrigating a field with some irrigation system (correct?). Copy from above....something went wrong 🤨

[arruda]

We also would need to defined what is a Compost (or compost pile) that the operations (actions) refers to. Using the current implementation of FarmCalendar we could refer to the specific compost pile in a generic Farm Calendar Activity by registering the compost pile as an AgricultureMachinery (since ploutos:operations have a reference to these machineries), so we could then reuse this same relationship.

I'm unsure if the idea of compost piles as Agri Machines is too much of a stretch.