On my farm I have a few big fields that I split up and graze differently year to year. To make rotions easier I create child locations (paddocks) inside the main location (field). Usually my logs are at a paddock level unless I am doing something to the entire field at once. Because I graze these differently every year I make some changes to the paddocks. Usually the changes year to year are just direction on which I graze and some minor changes in size/shape of the paddocks. This is easy enough to represent by just changing the shape of the paddocks to match the current years plan.
This year I am doing a large reconfiguration of my paddocks so keeping the existing ones and modifying them just don’t make sense. I will be adding a lot more and making them significantly smaller. It makes sense to just archive these paddocks and start fresh.
The problem lies with going back and seeing history on some of these paddocks. If I make new paddocks every year to match my grazing patterns for the year then going back to view archived locations can get tedious. Even just remembering the locations name could be an issue to look back at historical records. IE. this year its name is UFR12, last year I believe it was UFR14, the year before that I don’t remember.
I’m wondering how others are handling this type of change up.
A cool feature would be to drop a pin or draw a box and retrieve all relevant to that area. I’m sure this is quite a challenge thought.
Yea definitely. I think this is one of the problems that the Grazing Plan will solve. It allows you to make a plan for each year (or multiple), and references the movement logs (which in turn reference the assets and locations), so it’s a quick way to get to everything you need to for a single year/plan/set of movements.
It adds a module called “Geometry Report: Find all records across time that intersect with a geometry.” There is more to do to finish it, but you can see the proof-of-concept query here:
I would love to see this completed! I’ve talked about this idea for a looooong time, and it’s a perfect demonstration of a feature that is relatively simple to implement thanks to farmOS’s data model.
Sorry if this is really obvious (or otherwise a terrible idea for your use-case), but it seems like one convention that could make things simpler would be to create a copy of all the paddocks each year/season with the year/season in the name and archive the old ones. That way you preserve the complete history of the year’s/season’s paddocks.
You could then search for land assets with the year/season prefix/suffix to access the historical map for that year/season.
Maybe you’re already doing this, but it might also be worth creating a printed map of the current arrangement to help with memorizing the current naming.
