@CraigF, I didn’t take offense or consider any comment to be a personal attack. My wife often accuses me of coming on strong; I don’t deny that, but must add that I have mutual respect for anyone with equally strong opinions. My son opined that I don’t like weak people. I asked for examples, and after a brief discussion concluded that he is right. I respect disagreement and don’t give a hoot if someone fires back. If you have conviction, you owe it to everyone to stand by it. Don’t worry that you might hurt feelings. If I have something toxic to say, I’d rather side channel it so it is personal rather than public.
This topic had been covered previously. I backed off my assertions about GPS accuracy because I couldn’t counter negative points. That made me look more closely at my GPS data and cross reference the results. I respect the reality that many kayakers have no interest in speed or improving technique. If speed is not important to you, ignore the discussion. My goal is to pass on what I learn so paddlers with similar interest can build upon it. If you feel speed isn’t important, there is nothing of interest for you past this point:
______________________________________________
An accurate method for measuring speed is critical for assessing personal performance gains, evaluating equipment, comparing technique, monitoring energy expenditure, and for evaluating how changing conditions impact your plan, but only if it is IMPORTANT to YOU. What astounds me is how of all the sports I follow that measures success by calculating time over distance, kayakers are the only group where I’ve heard the comment, “speed doesn’t matter”, or GPS doesn’t work - I understand the limitations of GPS and potential for error, the problem of using GPS to measure elevation is indisputable, but there is no better way that I can think of to measure speed over diastance. I have no objection to any objection to questioning a comparison of one unit to another; however, I believe there is no better method, once the user verifies the relative limitations, than the GPS. My objection is to the claims that the GPS is largely unreliable. I simply ask those who feel that way to offer a better alternative, other than “speed isn’t everything!” That isn’t an argument, it’s a drop out of the discussion. Challenges to pure speed claims are valid, but that doesn’t mean the claim is wrong, it just isn’t “certified”, but it still can be valuable for a means of comparison.
It’s ironic how fans don’t questions the speeds recorded in a bike race, a kayak race, or a road race, we can jump in our car and plot a trip that gives three or four optional routes, each with an arrival time that typically calculates projected time within minutes.
I can think of only a few ways to verify speed over water - plot on a map/chart using a scale and calculate travel time, or use a GPS. I’m not offended when challenged about the speed I report when discussing a technique. My objection comes when the argument suggests that making a wide turn or drifting off track skews the accuracy. Before using such a riduculous claim, consider that by traveling further distance over a set course actually results in registering slower average speed, if the map/chart plot calculates a straight line between all turning points. Therefore, the avg speed would be higher if factoring in the actual extended course deviation, but the corrected avg speed typically amounts to only about .1 mph. My sister would typically deviate from my course by as much as 200 yards. I know she factually deviated, because I also carry a chart and note that she passes within an estimated 25 yards of green Channel Bouy no. 6 that’s located in a diverging channel. Yet she’ll argue I was off course and the GPS track is in error, despite an arrow straight GPS line. At our point of conversion on the targeted destination, I would see her boat broadside too me, so please forgive me if I find suggestions that GPS tracks are not accurate - my experience suggests otherwise. I can show charts where I follow another paddler or allow the wind to blow my boat around. I also have tracks for comparison that I control through edging. The results, as well as the perception is vastly different. I trust the GPS every time. The same is true of perceived speed. I’ve turned a corner that put the course into current or winds, only to have the person with me proclaim that it feels like we’re going faster. I break the news that our speed actially dropped by 2 mph, only to have them protest in disbelief. I take GPS over perception EVERY time.
Discussions about GPS accuracy isn’t just about how fast someone can paddle. If the unit is subject to error
it will typically be consistent error. My GPS shows the accuracy is typically (+/-) 12 to 16 ft. (I don’t display that value anymore; I rearrange the dashboard and selected a display with a bigger MPH readout - watching the accuracy of a satellite pings is of no value to me, because I concentrate on staying at a specific MPH readout).
My assessment is based on the years I’ve been paddling, the miles I’ve traveled in the same boat and others under various conditions, and evaluation of my logs that include conditions such as time of high/low tides, temp/humidity, water temp, wind direction and speed as reported and as perceived by the Beufort scale. The test course I’ve practiced since starting kayaking has two near equal 2 mile legs with a 1/4 mile neutral zone at the middle and the influence of a constant outflow current of about .5 mph from the Gunpowder River on the 2nd leg. You can verify the distances yourself - get a 7 1/2 minute topo map or a nauticsal chart and measure the distance compared to my printed course track. The values are good enough for me, but if I made a mistake, I’ll be happy to consider corrections. I measured the distance as roughly 8.5 miles, round trip. The range of GPS values for that set distance range from a low of about 8.36 miles to 8.64 miles, depending on how wide I make a turn or where I turn around. That is less than .3 miles deviation between all trips and can be accounted for by how I make turns or the loop at midway. Other factors that skew numbers depend on whether I beach the boat to stop the moving time or allow the boat to drift. I typically limit the water stop at esch two mile leg to about 30 seconds, so that could mean my actual average speed could incease by .05 to .1 mph. Boo hoo!
I made a test chart for 8.5 miles, listing in one column, the avg speed, time in hours/minutes, then a column that converts the time into a decimal equivalent, (4.0 mph avg = 2 hrs 7.5 min = 2.125 hrs). That chart has every finishing time for 8.5 mph in .1 avg mph speed intervals. I dont need a GPS to tell me the overall average speed. I know the measured distance and GPS data readout for eah turn. I know how many minutes it takes to get to turn A, B, C, D, and E, then time to landing. That’s how I validated the accuracy of “my” GPS. I accept that the distance based on turning point, going off course and time stopped will impact actual overall average speed and distance, but I found that any error, based on the 8.5 mile/total time chart, amounts to around .1 mph. Furthermore, the time spent setting the app and GPS, listing the actual start/stop times, then beginning to paddle or stopping the devices and capturing data with a screen shot increases the run time by 30 to 90 seconds. If you look look at the chart example, you’ll see that for the 8.5 mile track, about a three minutes difference changes the average speed by about .1 mph. So a 90 seconds delay means a final reading of 4.55 mph is actually 4.6 mph. Rather than nit-pick seconds, accept 4.55 mph and the next time if I register 4.65 mph, it means I jumped .1 mph rather than a mere .05 mph. The point isn’t the speed today, it’s how much I improved as well as what time I need to finish the course and reach 5 mph (1 hr 42 min, or 3 minutes faster than my top speed of last year and 19 minutes faster than my speed average speed from yesterday).
8.5 mph Course:
4.2 mph = 2 hrs 1.4 min = 2.0238 hrs
4.1 mph = 2 hrs 4.3 min = 2.0731 hrs
4.0 mph = 2 hrs 7.5 min = 2.1250 hrs
3.9 mph = 2 hrs 10.7 min = 2.179 hrs
3.8 mph = 2 hrs 14.2 min = 2.236 hrs
4.84 mph = 1 hr 45.6 min = 1.756 hrs
5.00 mph = 1 hr 42.0 min = 1.875 hrs
An argument can be made that I need a different chart if the GPS displays 8.36 miles or 8.6. It doesn’t
- all I need to do is check the specific distance and moving time, and accept that it’s accurate within a .1 or .2 mph of the average speed, about the range that I see on the MPH display. Feel free to believe what you will, I trust the relative accuracy based on comparisons with the chart. (+/- .1 mph overall).
When padding in water with a relatively constant current or a flat current like a lake, the best I can do to stay at a select speed is (+/-) .2 mph. For example, paddling at 4.0 mph, I can manage to keep at 4.0 for a few seconds, typically 5 seconds at most. While striving for 4.0 mph, i can expect to get readoits of 3.9, 3.8, 4.0, 3.8, 4.0, 4.0, 4.0, 4.1, 4.2, 4.0, 3.7, 4.0. 4.0, 4.0 3.7, 3.9. The question is what’s the right speed. If my goal is 4.0, I paddle to keep as close to 4.0 as possible. That’s my speed! Does it matter if the actual speed is 3.9 or 4.1? Check the 8.5 mile chart.
I’m certain the boat isn’t speeding up and slowing down by that much. So I simple accept that 4.0 mph is in between those extremes. Even if I can get a consistent readout of 4.0 mph that shows up more consistently, that doesnt mean its true, because the error is about (+/-) .2 mph above or below 4.0. If it hits 4.3 mph, I paddle slower, and if it hits 3.8 mpg, I paddle faster until I hit 4.0 imph. Works for me. However, I know four things from watching my GPS:
If I stop paddling, speed drops consistently, for example, from 4.0, to 3.8, to 3.6 to 3.2 mph. Its linear. When I accelerate to get back up to 4.0 mph speed, ot takes two strokes for each .1 mph increase to get back to 4.0 mph. Each stroke is one second each, and I can see the second digits tick by on the GPS.
I don’t mind a challenge to my math, but I won’t accept a challenge unless someone actially paddles with me. Renember that I cam vark, but I can’t bite you. I hope somebody can benefit from this. I already did the work. Hopefully it helps someone check and validate their own GPS readout.
The advantage to being able to trust the reading is that you can compare paddles lengths and blade surfsce area, boats, conditioning, recognize over working and recovery time, and more. If this seems like a lot of work, it is, but once you gain confidence in the GPS unit, the work is over. A you have to do is check it occasionally over measured courses. Scrutiny and challenges from the forum gave me the motivation to check the potential. As usual, I have the forum to thank for my improvement. I never said paddling is fun, just challenging . . . and satisfying.