| [21:18:17] | * farmBOT has joined #farmos |
| [06:18:00] | * ian_vai[m] has quit (Quit: Client limit exceeded: 20000) |
| [12:02:30] | <symbioquine[m]> | Just ran into https://github.com/farmOS/farmOS/pull/814 - Awesome to find it's already fixed! |
| [15:04:03] | <mstenta[m]> | symbioquine: I started playing around with a proof-of-concept "Geometry Report" module for core, that would let you click a point on a map to search all logs/assets with an intersecting geometry. |
| [15:04:14] | <mstenta[m]> | Some fun considerations... :-) |
| [15:04:32] | <mstenta[m]> | We looked at it briefly on the dev call |
| [16:45:45] | <gbathree[m]> | just dipping my toe, but looking into groups and animals for surveystack integration to push grazing logs. I'd love pretty soon to talk about what those look like. Overall it seems good, but I sure wish there was a group `type: animals` or something like that, which then constrained the members. It would also help a lot for external users to specify groups of animals, and not other groups the user may use. |
| [16:45:46] | <gbathree[m]> | Lastly, a little weird thing: often, when providing yearly reporting data, you don't have the next movement location for the final grazing event. So in a sense, the last grazing event just 'ends' (ie... the animals aren't on a field anymore). In a way this is like an grazing log with a movement to... nowhere? It doesn't make sense when the events are movements, but it makes sense when the events are Grazing Events (ie a period in which |
| [16:45:46] | <gbathree[m]> | grazing occurred) which typically how someone thinks about this. Wondering if folks have thoughts on this |
| [18:39:33] | <mstenta[m]> | gbathree: these might be good questions/ideas for a forum topic |
| [18:43:14] | <mstenta[m]> | the old v1 grazing module had a concept of "grazing events" in the plan level, which linked to actual movement logs |
| [18:43:54] | <mstenta[m]> | but even there, you do need to say you moved the animals out of the last paddock, and that requires a final movement log |
| [18:44:31] | <mstenta[m]> | this could be something like "move animals to the barn for the winter" (or maybe they rotate into a new plan!) |
| [18:44:59] | <mstenta[m]> | also worth knowing: a movement log can be used to unset asset location by not including any location reference |
| [18:45:14] | <mstenta[m]> | thus moving the animals to "nowhere" |
| [18:45:52] | <mstenta[m]> | but i think what you're probably after is a grazing plan entity with grazing events as plan records (we called them rotations, but i like "grazing event" better for v2!) |