Surge GPS Accuracy

[A1sportsdad]

I am very disappointed in the accuracy of the GPS on my Surge.  It's good if I'm running in the open with no tree coverage, but under any kind of cover, it loses way too much mileage.  I can understand if it's losing signal on occasion, but I would expect it to do a straight line approximation from the last good data point.  Instead it seems to keep the timer running, but throw out all distance in between.  I wait until it finds a satelite and I set my display for AVG PACE before I begin my run.  I am using both my Surge and my old Nike iPhone App.  On the Surge my mileage is lost and my pace goes way down.  It cannot be accounted for by straight line approximation error.  The course run is pretty much a straight 3 miles out and back for a total 6 mile run.  There are mileage markers along the way and I have run this route for years.  My GPS loses about a half a mile over the 6 mile route.  NO GOOD.  My old Nike iPhone App is pretty much dead on.  I am back to using my Nike App for tracking my runs (and shoe mileage) and just using my Surge to tally my steps.  Major FAIL. 

[ingvarietyshow]

I am on this thread for the same reason. I've been running the same route the last few days and it keeps giving me different distances. It didn't find my location until a good half mile into my run today. My maps seem to look incomplete or show that I ran in an area I know I didn't pass. I am with you, OP. It's very frustrating. 

[shipo]

Losing accuracy due to tree cover, tall buildings, and even heavy cloud cover is kind of a fact of life when it comes to GPS.  I too get annoyed when the map and mileage get hosed up; the good news is the Surge seems to be accurate more often than my running mates with tethered trackers like the Blaze and Charge HR.