On Garmin Connect Golf course club performance I have a number of clubs with far too long maximum distances. How can I get rid of these without having to check all the rounds and holes I played to find the badly registered drives?
On Garmin Connect Golf course club performance I have a number of clubs with far too long maximum distances. How can I get rid of these without having to check all the rounds and holes I played to find the badly registered drives?
I have about 50 rounds and a 444 yd 8 iron. Who knows how many other crazy numbers are in there. How can any app this good not have a simple way to fix something so ridiculously bad?
The missed shot thing is my guess as well. Pretty sure I would have remembered hitting my 8 iron 444 or a 200 ft putt.
I can live with a tracking error...especially given mulligans. I'd even argue that…
Are there any updates on this? Feels like this shouldn't be a huge issue to correct and implement on the client-side app.
I assume this still hasn’t been updated? According to the app, my upper range with my driver is over 400y ….. if only that were true! I have no idea where this number comes from and I can’t edit it. As I understand it, my only option is to delete my driver and lose all the data.
I love my s40 approach watch but I find the software incredibly clunky. There are lots of features I would expect but Garmin are not making the investments. For a company of this size and reputation, it’s very disappointing.
There is another way if the driver is wrong.
Open a scorecard and press the red flag. Then You should get the overall statistics. If You scroll down You should see Your longest drive ever. And if You click on the scorecard symbol, You should be redirected to the actual scorecard, and can delete or modify this shot.
It will only work for Your longest shot. So if Your longest shot is 250 yds on Your lob wedge and 260 on Your driver, it's not easy to find out where the 250 lob wedge shot comes from..
Thanks - I didn’t know this. Unfortunately it doesn’t fix the issue as none of my longest shots are showing as over 400y on any of the courses.
Indeed the stats in the app are contradictory:
“In the bag” shows the range for my drivers as:
Driver 1 248-446
Driver 2 234-437
“Performance stats” shows my lifetime longest drive with Driver 2 = 351 y on Course A (this one is correct)
I’ve looked through each of the courses I’ve recorded and can’t see anything at 400+. Strangely, when I look at Course A (using the red flag method) it shows a longest drive of 269 ….. even though I can see the shot of 351 recorded on Course A.
All very confusing - and it does seem to be an issue people have been raising for a few years. I’d rather not delete the clubs and start again.
Thanks for the flag thing. Didn't know that existed. I would have replied to that message, but reply doesn't work. :-/
And given that I've got over a hundred rounds, the flag solution is still very brutal to do.
Here's my take. The Solution Architect who designed this should be fired. Product Manager too. Pretty obvious that the distance data is updated at submission of scorecard, but for some stoopid reason the data about that source scorecard isn't being captured. So, Garmin doesn't even know where those distances came from because the Solution Architect is an idiot. And that means the data architecture is also probably F'd, and the fix would require a complete rebuild of all the past data, which would takes tons of time and money. Thus, no fix has been made on something that is very basic and very bad.
If what I'm saying is wrong, then this is an easy code fix to link the distance to the scorecard/hole so the user (us) can edit. Shouldn't take more than a week to code, UAT and push to prod.
And yea...I do this stuff for a living.
I agree - though I don’t pretend to understand everything you said ;0).
I did wonder if the phantom distances come from errors made on the course; ie my watch misses a second shot so thinks I hit my drive 400y to my third shot; I edit this after the round to add my true second shot, so there’s no history of the phantom shot but it is still used in performance stats. What a cr*p design if that is the case….. and I don’t do this for a living!
The missed shot thing is my guess as well. Pretty sure I would have remembered hitting my 8 iron 444 or a 200 ft putt.
I can live with a tracking error...especially given mulligans. I'd even argue that Garmin should have assumed it would happen... Which makes this ongoing issue all the more frustrating.
These issues with the lack of manual intervention of scores on CT10 / app have been flagged for about 3 years - how is it that there have been no improvements
The idea that you would have to search by scorecard, by hole for your incorretly recorded yard pitching wedge is something clearly developed by someone who never played golf.
Seriously disapointed that I spent close to €800 on watch and sensors - as the averages are of little benefit unless you religously go in after each round and check each shot.
Please note Garmin - that you competition automatically discount outliers in the average figures - the ability to select the outlier range woudl be very beneficial. As someone who plays links all the time - not unusual to have a 3 club wind which plays havoc with the averages
I'm with you. I have a lot of money in Garmin products, but the current discounts for Arcos make it worth considering walking away for better software and stats. I certainly won't shell out for an S70 if everything else isn't upgraded.