How can I correct the longest recorded shot of a specific club? 235 meters with an iron 9 sounds pretty good, almost to good. :-)
How can I correct the longest recorded shot of a specific club? 235 meters with an iron 9 sounds pretty good, almost to good. :-)
Sometimes I wonder about the "genious" that designed the software... does this person play golf? I could even live with the option to fix it online.
Our Garmin Connect developers removed "Dream Round" stats but it was a popular feature. We heard your voice, so we have added it back into Garmin Connect web. However, this age old issue is now…
Your really hit 'em hard, don't you?
I had the problem with the driver, too. Since I "knew" the date of problematic shot Icould exclude the round I played from the statistics. But this isn't a real solution.
I agree I have just change from the ACCROS sensors and like the Garmin for the real ease of use but would like a bit more control of my stats like exclude duffed shots from my stats.
Sometimes I wonder about the "genious" that designed the software... does this person play golf? I could even live with the option to fix it online.
Our Garmin Connect developers removed "Dream Round" stats but it was a popular feature. We heard your voice, so we have added it back into Garmin Connect web. However, this age old issue is now going to be seen again. Also, we recently added new functionality into our Golf APP, the ability to adjust your shot distance when something odd happens on a shot when you are reviewing your scorecard.
I will be happy to research to see what can be done. It will most likely take more development for Garmin Connect web but I will update what I learn either way.
Update 8/6/2020:
For the longest shot to be corrected in your Dream Round stats, the original scorecard with that specific shot would need to be located and that shot deleted. Consequently, there is no easy means to adjust the Dream Round stat information.
Thanks for your answer, that's how far I've come myself, too. Deleting the shot manually is okay with me. Thing is, I can't load/show that specific hole in the web app at all. Since the "origin" of that specific shot is way off the map, it never finishes loading the data to this hole.