Take photos of the tree from 6 different angles, feed into a 3D model generator, erode the model and generate a 3D graph representation of the tree.
The tool suggests which cuts to make and where, given a restricted fall path (e.g. constrained by a neighbors yard on one side).
I create the fallen branches in their final state along the fall plane, and create individual correction vectors mapping them back to their original state, but in an order that does not intersect other branch vectors.
The idea came to me as a particularly difficult tree needed to come down in my friends yard, and we spent hours planning it out. I've already gotten some interest from the tree-surgeon community, I just need to appify it.
Second rendition will treat the problem more as a physics one than a graph one, with some energy-minimisation methods for solving.
This is the kind of thing that makes me love HN. An idea I would never have thought of, with an immediately obvious use in multiple ways (fall path plus ideal lumber cutting?), probably very difficult, yet being tackled with one implementation already... and spoken of quite humbly.
Having joined may father and his friend during the process of cutting down big trees in the village neighborhood I can personally vouch that this indeed a cumbersome and very complex task for both the planning and the execution phases. However, for us the tasks are made easier by the trimming of the tree's branches since my father's friend is the expert tree climber.
From your descriptions, it seems that your tree cutting procedures do not involved precut of the tree's branches before cutting the tree down.
I've got the feeling that this cutting tree problem can be solved by constraint programming techniques [1],[2]. Alternatively generic tools for constraint programming, for example OR-Tools and MiniZinc can probably do the same if not better [3],[4].
[1] Logic, Optimization, and Constraint Programming: A Fruitful Collaboration - John Hooker - CMU (2023) [video]:
Funny, one of mine also involves trees -- but is mostly outdoor cleanup. The kind that involves decades' worth of it, thanks to what I'll just say is a lot of maintenance that wasn't done over a long time. There's an extensive amount of brush, leaves, etc of varying ages that could maybe be shredded up into something useful, invasive vines I'm still trying to deal with, and more old trash than I've fully figured out how to properly dispose of.
It's turning into various DIY rabbit holes, actually, with the next one (outside of various related landscaping stuff) being to gut a basement.
I would love to have such a model tell me how to prune my fruit trees as they grow up. Should be a fairly straightforward supervised problem with the right front end for the graph generation.
You can start right now with an algorithm I learned from an expert when I was working in a landscaping business.
It is a very simple three-pass plan: "Deadwood, Crossovers, Aesthetics".
So, first pass, go through the tree cutting out only and all the dead branches. Cut back to live stock, and as always make good clean angle cuts at a proper angle (many horticulture books will provide far better instructions on this).
Second pass, look only for branches that cross-over other branches and especially those that show rubbing or friction marks against other branches. Cut the ones that are either least healthy or grow in the craziest direction (i.e., crazy away from the normal more-or-less not radially away from the trunk).
Then, and only after the other two passes are complete, start pruning for the desired look and/or size & shape for planned growth or bearing fruit.
This method is simple and saves a LOT of ruined trees from trying to first cut to size and appearance, then by the time the deadwood and crossovers are taken later, it is a scraggly mess that takes years to grow back. And it even works well for novices, as long as they pay attention.
I'd suspect entering the state and direction of every branch to an app would take longer than just pruning with the above method, although for trees that haven't fully leafed out, perhaps a 360° angle set of drone pics could make an adequate 3D model to use for planning?
In any case, good luck with your fruit trees — may they grow healthy and provide you with great bounty for many years!
When i read OP this is what I thought it was going to be - these branches are going to be apex competitors, these are crossing or going to cross, this one shows signs of disease, this one interrupts air flow through the centre, etc.
I was imagining something like this for pruning fruit trees — something to help noobs like me see how to put pruning guidelines into practice on a real, overgrown tree. Good luck!
Making this determination alone will sink you in legal fees
Does an insane amount of fine print really save you? Even if you say the model is only an aide to be used by licensed or certified professional arborists or whatever, I fear some Joe blow whose tree lands on his house will be suing you.
I've been thinking for years about a safer alternative to chain saws. Something along the lines of a carbide coated wire driven by an electric motor and battery. Strap it to the tree, turn it on, walk away and some minutes later the tree falls down. The main difficulty is in how to drive the wire. Using friction would create fast wearing parts. Maybe a chain could be used instead of a wire. It could oscillate back and forth, instead of having to be wrapped and spliced to form a circle around the tree. It seems really strange that no one has come up with an alternative to chain saws for decades (except for large scale trucks that can process whole trees.) For small trees and branches even a sawz-all is safer than a chain saw. Inspired by spending some time sharing a hospital room with a guy who had a chain saw accident, but I still haven't come up with a workable idea. Maybe someone else can.
I was thinking I could use a tool just like the wire you described to remove a stump, after I spent 6 hours with a 5ton Bobcat trying to dig up a 3ft diameter pine stump to no avail today. For felling trees though, you need precise front cuts/back cuts to drop the tree at a desired angle, you can't just cut in one direction even if you have a cable attached.
Perhaps drilling in a wedge shape so it weakens the branch and it eventually breaks off naturally but it seems like more work than just a chain saw. The holes could also be used for steam treatment, enzymes [0] or something else to break it.
I use a tool called the Alligator. Is is a tool you can use like scissors. It has 2 chains on the inside of the the business ends. You put around the branch. Close the end and press the button. Springs will then close the end even more and cut the wood. No open chains
Forgive my ignorance but all the tree cutting I've observed has been based on climbing and cutting in segments from the top rather than letting the tree fall. Under what circumstances is it better or necessary to actually let the tree fall?
IANAL (L=lumberjack) but it's clearly going to be cheaper if you can just chop it down, right? Quicker and less equipment required, less danger to life from having to climb and wield a chainsaw in an elevated position. Also, if you are interested in getting long planks out of the trunk, you would not want to cut it down progressively.
Any tree near civilization that someone wants to pay to cut down is likely going to be at a distance from a structure, powerlines, or pipes in the ground (that's also the reason they want it removed) where felling it as it lies is not likely an option which is why you see them sectioned down or done with a crane or bucket truck. A lot of these trees done by tree care companies in residential or commercial areas are also sprawling hardwood trees like oaks that can't always be safely just dropped from the ground even if there's a clear area to drop it in. For logging or wildland firefighting, most of the trees being dropped are straight growing softwoods like pine or fir that are just dropped from the ground (or by machine).
I think it depends on how much space there is for the tree to safely fall. If there isn’t enough space to accommodate the height of the tree, it needs to be done in controlled segments.
I was thinking of something similar during pruning season for my apple trees a few months ago. I even went so far as to take a scan of one of my trees with Luma and had it generate a 3D render of it. This worked surprisingly well, though it did take several days to get it rendered as it seemed their service was saturated.
My need/idea was to post that some where (r/backyardorchard probably) to get help in determining which limbs to prune. However, there didn't seem to be an easy way to share that sort of thing and time was of the essence, so I just forged ahead on my own.
Where I live this could be very helpful becuase people is too, how to say it, maybe ignorant in safety and logic specs. Also could be usefull to know or estimate what tree are in a innminent or highr posibilities of fall with wind.
Cool idea. Just wondering why you wouldn't use Lidar for this? I'd have thought the spatial fidelity of a Lidar model would provide a much better model of the weight distribution of a tree.
Do consider the value of the wood in relation to your cuts. A well-placed cut not only guarantees safety but will also take the maximum board feet from the tree.
i work a lot with NVEL for this. one time even tried porting nvel to wasm for fun and client accessibility. we "virtually buck" trees which seems like could be applied to your proposed use case. if op wants to go down this path: https://github.com/FMSC-Measurements/VolumeLibrary/tree/77d4...
with dimension lumber it's way more about the width you can cut than length; sometimes shorter is more valuable depending on supply & demand (and transport). Accounting for the fact that trees are not perfect cylinders (or cones, really) is where all the fun optimization comes from anyways.
the right cuts at the right heights while working down the tree from a specific max height of the tree to still produce viable board feet while maximizing boards per cut. in most places, unless youre pulping the entire tree, its quite a bit more complicated than cut as low as possible.
its surprising to me how little work is done to make the tools which do this accessible considering how much money and open data there is.
it gets less open and more complicated is when you consider certain mills only can make certain cuts, produce certain products, and accept certain logs. then factor in distance between mills and the products they can make, and also log lengths accepted by the trucks which can travel those routes.
its all solvable and should be, but its so niche and that i still think there isnt an accessible solution
This is great idea - I have a huge tree in front yard that will either cost be $5-10k to come down or was going to rent lift and do it myself - A few particular branches scare me though in terms of how they will come down... Bonus points for where to tie things off.
I plan for a time-bomb license (closed source for 10 years, make my money (if any), GPLv3 after that).
My methods are all over the place. Tree is taken as-is on the day, and cuts calculated on the fly, no future growth-modelling if that is what you're asking
I was mixing methods, sorry. My initial rendition for solving the cuts would initialise a somewhat sparse network from tree to ground, and solve for non-overlapping paths.
This became convoluted and I just opted for a far easier method of solving vector intersections.
Its also not perfect since I haven't factored in rotation origin very well, and I'm now pursuing a far simpler physics-based approach
Take photos of the tree from 6 different angles, feed into a 3D model generator, erode the model and generate a 3D graph representation of the tree.
The tool suggests which cuts to make and where, given a restricted fall path (e.g. constrained by a neighbors yard on one side).
I create the fallen branches in their final state along the fall plane, and create individual correction vectors mapping them back to their original state, but in an order that does not intersect other branch vectors.
The idea came to me as a particularly difficult tree needed to come down in my friends yard, and we spent hours planning it out. I've already gotten some interest from the tree-surgeon community, I just need to appify it.
Second rendition will treat the problem more as a physics one than a graph one, with some energy-minimisation methods for solving.