This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Specificity for "Out of Bounds" metrics

Scenario 1: You tee off into a water hazard.  The ball did not enter laterally, so you decide to tee off again, taking a 1 stroke penalty.

Scenario 2: You tee off into a water hazard.  The ball went about 200 yards, crossing into the hazard at 150 yards, but you drop further back from where the ball laterally entered the hazard (e.g., 100 yards of the total allowable 150 yards distance).

############################

Scenario 1 Problem: You cannot pinpoint where the ball landed in the water.  Furthermore, when you hit your 2nd shot, it currently shows that the previous shot was 1 or 2 or 3 yards.  Not accurate since you are just teeing off again after having taken a 1-stroke penalty.

Scenario 2 Problem: You cannot pinpoint where the ball landed in the water.  Thus, when you hit your 2nd shot, the app assumes your first drive -- flagged as out of bounds -- only went 100 yards -- the spot where you dropped.  This messes up distance metrics and is an inaccurate landing position for the previous shot.

The Solution: 

  • Add a flag to attribute shot distance and location to an estimated landing point for out-of-bounds shots.  This will help with metrics for poor shots on a hole and where they went and how far.
  • Add another flag to indicate that a ball was dropped at a location.
  • Add a flag to not include out-of-bounds shots in distance metrics.

  • Add a flag to attribute shot distance and location to an estimated landing point for out-of-bounds shots.  This will help with metrics for poor shots on a hole and where they went and how far.

    I think I understand. But if I attribute the first tee shot with the estimated landing point as oob, does it still contribute to distance metrics or not?

    Add another flag to indicate that a ball was dropped at a location.

    Does that mean to add or position (if already there) a shot where you dropped the new ball (in your example, it would be the third shot)?

    Add a flag to not include out-of-bounds shots in distance metrics.

    I´m not sure I understand. Do I have to attribute this fake "second" shot (from the estimated landing point to the point of the drop) as "out of bounds" or unmark the club selection or both so this "shot" would not count in distance metrics?