Digipaths for aircraft
My business partner and I have been kicking around firmware changes for airborne applications. At first, we combined both high altitude balloons and fixed wing aircraft into one mode of thinking, and quickly realized that there are no parallels between the two, with the exception of limiting the digipath above some altitude. Unfortunately, the GPS only knows its altitude above sea level, and it does not store an atlas that keeps track of your AGL.
My thinking is that in general, during most flight, altitude is a function of velocity; if you are going fast, you are most likely flying high, and we could switch to a narrower digipath to keep you from pinging digipeaters out to the geometric horizon and beyond, but use the wider, mobile path for those times you are sitting on the ramp, or hanging upside down in the trees. I know this is imperfect, so I am looking for ideas on how best to upgrade the firmware for typical flight profiles. Of course, we would keep all the configuration options open, and not try to brute-force you into any new and untested ideas.
Other than just for the sake of polite operating, the only real problem I have ever seen with using too wide a digipath at altitude is hitting a bunch more digipeaters and I-gates than you really need to. Even this is not crippling to the APRS network, unless it is combined with sending lots of extra packets. This can happen when using SmartBeaconing and flying aerobatics at high altitudes.
So basically, I am soliciting you for your thoughts on how best to improve performance, while at the same time not incurring the wrath of the secret APRS police for abusive operation.