One single PDF generation for all activities

[lcentorame]

The current service generates separate and operation-specific reports (e.g., one for irrigation, one for fertilisation, etc.). This approach is misaligned with agronomic workflows and the European requiriments for Field Notebook. It requires a unified chronological view of all activities related to the field parcel. Moreover, actually user-entered observations are systematically excluded from reports, despite being relevant agronomic data.
A single and unified field activity report would be significantly more practical and aligned with standard farm management information system (FMIS) conventions.

What we expect to be included in the report:

1. Farm information (farm name, VAT, contact, address and so on)
2. Farm parcel data (map, crop, area, etc.)
3. Forecasting models (summary of the last 15 days, which pest is active and at high risk level, etc.)
4. Pest treatments activities (all the information added in the Activity Type dedicated to pesticides, with cronological order of activities recorded)
5. Fertilization activities (all the information added in the Activity Type dedicated to fertilizers, with cronological order of activities recorded)
6. Irrigation activities (all the information added in the Activity Type dedicated to irrigation, with cronological order of activities recorded)
7. Crop data (all data recorded for crop data and a specific section for quality certification in which user can add manually upon request)

A PDF structured as described could be really useful for the farmer to demonstrate the activities carried out on a specific crop in the farm parcel and insert agronomically relevant information and observations.

Keep us update :)

[JoleVLF]

@lcentorame Just one short note, observations are not excluded from the report, observations are in the report when they are related to compost operation provided :) but not relevant to this part of the reporting anyway.

I have question here regarding:
-> Forecasting models (summary of the last 15 days, which pest is active and at high risk level, etc.).
Where exactly do we receive this information from? Are you using PDM or another external service?

Are all other data described here populated on Farm Calendar?

[lcentorame]

@JoleVLF I get it but what about all the other observation (e.g. treatments notes or others)? It would be useful if observations will be always included, without struggling with linking to compost operation (if it's not the specific case).

Regarding the second question, we reasoned about the report based on what we suggest to change also in the PDM service. So, if the OpenAgri team makes changes about the PDM, you can receive all these information.

Lastly, if you mean the information was entered by us into the Farm Calendar, still not (I'm going to do this morning). But every information suggested above has been taken as example from the FC.

[JoleVLF]

@lcentorame Thank you for confirmation and input! All observations related to field/parcel, correct?
I understand, info will come from PDM then.

Yeah I wanted to check will we use FC for query all data above (example).
Ace! So we will have data example to create PDF report on, that is great!

[lcentorame]

@JoleVLF yep!

I've just created 3 activities (1-2 of April) and 1 observation (31 March) referenced to SIP 10 Farm and, in more detail, 01 - Cherry Farm parcel.

Let me know if everything goes well :)

[JoleVLF]

@lcentorame
Short question here, is this added to test server or sip10 deployed env?
If it is added to your specific env could I receive an email with login creds and URL?

[lcentorame]

@JoleVLF
I've used this URL https://fc.test.horizon-openagri.eu/ to manage the activities and farm/farm parcel.
Bad move?

[JoleVLF]

@lcentorame No no that is ok! Thanks!

[fedjo]

Just to clarify a bit more, compost_operation is related to all farm/argonomical activities that an active compost pile needs (raw materials, temp, humidity observations etc) . It must not be used for any other type of activity (eg pest monitoring, disease detection, etc)

[JoleVLF]

@lcentorame from where do we get:
Crop data (all data recorded for crop data and a specific section for quality certification in which user can add manually upon request)?

Should we add optional parameters to the API so certification info can be added (like type, reference etc)

[lcentorame]

@JoleVLF Crop data refers to the Crops section inside the Farm Calendar, so basically crop species, variety, growth stage.

[JoleVLF]

@lcentorame Sorry, my question is related to certification info

[lcentorame]

@JoleVLF ok, great! Certification information should be entered by the user inside the crop section or inside the "description" box

[JoleVLF]

@lcentorame For PDM models, currently what I see we need model ids for which we want forcast and we miss PDM API with days offset when FC is used, can you please open an issue (if not already) on PDM to create this endpoint.

Also point there do we need API which iterates over all pest modes for parcel or different approach.