I analyze data for a living, so I'm firmly in the "I love data" camp. I also know that often we're flummoxed about what to do with some of the data we "just had to collect". I know, why did we collect it if we didn't have a plan for it? Good question. Some of it we figure out eventually and put to good use. Some of it ends up on the cutting room floor.
What you've done, jssailem, is laid out a couple of use cases for this data, which I'll label as the "Lazy Captain" (I can't be bothered to get up and look at the chartplotter - I might spill my boat drink), the "Mute helmsman" (no need to communicate with anyone, I have all the data I need right here on the bow), and the "Are we there yet?" (for the screen addicted 13-year-old who didn't want to come on this stupid trip anyway) use cases.
I guess I would add one to that list: Building polars. I am not a racer, in fact, have never raced a sailboat. It is a hobby that brings me great joy for its relaxation, problem solving and occasional physical challenges. OK, its mostly problem solving. But I do want to learn how to sail better, and in particular, want to sail my boat as near to its reasonable potential as possible. The precursor to doing that, is understanding what the performance possibilities are for my particular boat and sailplan, in the context of my skillset. Building my own polars will help me get that "baseline", upon which I can slowly improve as I try to "beat" myself by improving my sailing skills. I think that collecting data as I sail will give me the information I need to start building polars. I've seen a few software apps which purport to help you do just that. We'll see. Its going to be a goal this season.
Would love to see other use cases for the wireless data from other people who have found genuine uses for it.
