Blogger troubles and Garmin struggles



The lost post is still lost. Note today's date

 Yesterday's run (street): 2.5 miles
Today's run (street) 2.3 miles

It looks like yesterday's post may be gone forever. According to the status reports from Blogger, I should have seen my last post restored when the system was brought back up. This has not been the case. It's frustrating and a little scary. You assume that Google would have been competent enough to back up its servers or cache recently posted content before taking down the system for "maintenance."  I may reconstitute Thursday's post using both my original draft and a prematurely published version. Or maybe I'll just let it go and call it the Great Lost Post. Although I should say it wasn't all that great.

Editor's note: Missing 5/12 post has been restored by Google

My post: "Garmin 210 -- Upload troubles but consistent inaccuracy" referred to an unsuccessful attempt to upload run data from the Garmin 210 to Garmin Connect. I'm hoping to resolve that issue this weekend. Wednesday and Thursday the Garmin under-counted my runs by about 3.5%. This was a disappointment, but not entirely unexpected, since my prior experience with GPS tracking on my iPhone showed substantial inaccuracies. I want to see what the Garmin recorded in terms of route vectors compared to my actual path so I can better understand where the 210 came up short.

This morning I went out for a run and I followed a different route from Wednesday and Thursday's. This time the error was only 2.2%. I had discussed the accuracy issues with FS who suggested that this morning's route may have had less curves and turns which would explain the higher accuracy. I believe she has a point. I'm really hoping I can get the Garmin to actually connect to Garmin Connect so I can upload and analyze my runs. Tomorrow morning KWL and I are  planning to do a mountain bike ride and follow it with a 5K or 4 mile run. It will be the first time trying the 210 in the woods. Should be interesting.