Should Summary Value have an Acres property?

[knelson-farmbeltnorth]

@zwing99 brought up the scenario of 2 combines harvesting a field. As such, we have one Operation Group per combine within the Work Record, each of which has a single harvest Operation that contains Summary Values. If combine 1 harvested 60 acres with an average yield of 65 bu/ac, and combine 2 harvested 20 acres at 40 bu/ac, how would one calculate an average yield for the field without being able to associate the acres to to the 2 Summary Values of 64 & 40.

We could add Area as a property on Summary Value but it would need to be optional as it would not pertain to all cases. The expected usage of Summary Value is that Operation Area would be its own Summary Value. If we instead put Area as an optional property on Summary Value, would it be more likely to be populated?

[strhea]

I think there are two area values to be communicated here. One is the "area total" at the work record level that represents what was done to the field as a whole. The other is the "area allocated" to each device; which added together should equal the "area total"

[knelson-farmbeltnorth]

Initial discussion 8 Feb 2023 meeting. Consensus was Area should be its own Summary Value. Will review once more next meeting.

[knelson-farmbeltnorth]

No additional discussion on 15 Feb meeting. Moving to approved.