US20250312682A1

US20250312682A1 - Management of golf tournament scoring data

Info

Publication number: US20250312682A1
Application number: US19/170,473
Authority: US
Inventors: Jeffrey Howell; Troy Cooke; Jeremy Craven; Jonas Gredenhag
Original assignee: PGA Tour Enterprises LLC
Current assignee: PGA Tour Enterprises LLC
Priority date: 2024-04-04
Filing date: 2025-04-04
Publication date: 2025-10-09
Also published as: WO2025213100A1

Abstract

A scoring module for managing golf tournament scoring data may include a score management device, location device, and an object detection device. The score management device may include a user interface having a display. The object detection device may be used to determine ball locations on a golf course from a location remote from the ball locations. The scoring module may be movable throughout the golf course during play of a golf tournament and the location device may be employed to determine a current location of the scoring module following each move. Determination of ball locations may utilize the current location of the scoring module.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Patent Application No. 63/574,753, filed Apr. 4, 2024, the contents of which are hereby incorporated herein in their entirety.

TECHNOLOGY

The present application is directed to managing golf tournament scoring data collected by various tracking systems for verification, replacement, and entry of missing scoring data.

SUMMARY

In one aspect, a scoring module for managing golf tournament scoring data may include a score management device, location device, and an object detection device. The score management device executes a score management application and includes a user interface having a display. The object detection device determines ball locations on a golf course from a location remote from the ball locations. The scoring module is movable throughout the golf course during play of the golf tournament and the location device is configured to determine current location of the scoring module following each move. The object detection device is configured to utilize the current location determined by the location device to determine the ball locations on the golf course. In one example, the object detection device includes a laser range finder.
The location device may be configured to communicate with one or more location services to determine the current location, and the location services include a global satellite constellation network and a local location network. The location device may include a GNSS antenna. The GNSS antenna may be configured to receive correction data from a GNSS antenna base station of the local location network positioned at a known location.
The score management application may be configured to receive scoring data collected by one or more tracking systems. The scoring data may include stroke data of players competing on the golf course and location data of golf balls hit by the players.
The one or more tracking systems comprise a shot prediction system, an automated scoring system configured to track balls hit by players using at least a camera device, a manual scoring system whereby personnel set location data corresponding to shots using a camera device.
The score management application may be configured to cause the score management device to display the scoring data collected by the one or more tracking systems on the display.
The score management application may include a score management tool that interfaces a user of the score management device with management operations with respect to the collected scoring data. The management operations may include validation of the collected scoring data, modification of the collected scoring data, and cancelation of the collected scoring data. The score management application may be configured to enable the user to enter missing or canceled scoring data.
The score management tool may include a hole graphic representation comprising a display of a hole set as active by the score management tool or user interaction therewith.
The score management application may include a score management tool that interfaces a user of the score management device with management operations with respect to the collected scoring data. As collected scoring data is received by the score management application, the score management tool may be configured to plot location data corresponding to a current shot of a player on a hole set as active that was collected by one or more of the one or more tracking systems on the hole graphic representation.
The hole graphic representation may include source identifiers with respect to the plots that identify the tracking system that is the source of the location data.
The score management tool may be configured to provide the user an option of verifying location data corresponding to a location data plot or input new location data for the current shot. The score management tool may be configured to provide the user an option to collect the new location data using the object detection device or by plotting location of the golf ball on the hole graphic representation.
The score management tool may be configured to allow the user to one or more of enter strokes, drops, or penalties, alter timestamps, correct shot from locations set, or delete strokes collected by the one or more tracking systems.
In one configuration, the scoring module is configured to collect location data with respect to all shots on an active hole that are in the fairway of an active hole.
In one embodiment, once a shot is taken on an active hole, a shot hit indication is displayed on the hole graphic representation. The shot hit indication may include a line from where the shot was taken to a pin of the hole. The shot hit indication may include a distance to the pin. In one example, the shot hit indication is displayed before ball hit lands.
In one embodiment, the score management application is configured to analyze the collected scoring data and identify anomalies and includes a score management tool. The score management tool may include an actions panel to display the anomalies in action messages corresponding to a player and hole the anomaly relates.

DRAWINGS

The novel features of the described embodiments are set forth with particularity in the appended claims. The described embodiments, however, both as to organization and manner of operation, may be best understood by reference to the following description, taken in conjunction with the accompanying drawings in which:

FIG. 1A schematically illustrates a golf data collection and management system according to various embodiments described herein;

FIG. 1B illustrates tracking systems according to various embodiments described herein;

FIG. 1C illustrates a zone map according to various embodiments described herein;

FIG. 2 illustrates a scoring module according to various embodiments described herein;

FIG. 3 illustrates a score management tool schematically illustrates a tracking system according to various embodiments herein;

FIG. 4 illustrates a group score card interface of a score management tool according to various embodiments described herein;

FIG. 5 illustrates a team player stroke detail interface of a score management tool according to various embodiments described herein;

FIG. 6 illustrates an all groups on holes presentation interface of a score management tool according to various embodiments described herein;

FIG. 7 illustrates an actions panel interface of a score management tool according to various embodiments described herein; and

FIGS. 8A & 8B illustrate operations of hole graphic representation interface of a score management tool according to various embodiments described herein.

DESCRIPTION

FIGS. 1A-8B illustrate various components and operations of a golf data collection and management system 10 including a scoring module 20 for managing scoring data wherein like numbers represent like features.
With reference to FIG. 1A, a golf data collection and management system 10 may include a tracking system 11 comprising one or more score tracking systems configured to collect scoring data during a golf tournament. The tracking system 11 may collect scoring data via manual entry, utilization of sensors, or both. Nonlimiting examples of sensors that may be used by tracking systems may include GPS, radar devices, lasers, or camera sensors. The tracking system 11 may collect scoring data for each competing player, which may be competing in groups, during golf tournament play in a live scoring process. In some embodiments, one or more aspects of the tracking system 11 may be automated.
Scoring data may comprise tracking data collected or otherwise generated by the tracking system 11. The tracking data may comprise location data with respect to players, balls, or other objects. For example, location data may comprise sensor data collected by sensors, manual entry data entered by personnel, or both. The location data may comprise shot data with respect to ball locations, e.g., ball to or ball from, ball flight data, or the like, which may be collected by sensors or personnel via interaction with electronic communication devices. Tracking data may include stroke data with respect to player stroke count, which may be collected via sensor data, manual entry data by personnel, or both. As described in more detail below, in various embodiments, the tracking system 11 may use location data with respect to players and balls, e.g., ball to and ball from, to generate stroke data, which, in some implementations may further include incorporation of ball flight data. This location data may comprise sensor data, manual entry data, or a combination of sensor data and manual entry data. Tracking one or more of locations, shots, or stroke determinations may be fully or partially automated. As also described in more detail below, one or more aspects of the scoring data may include tracking data generated by a shot prediction system 14 using sensor data with respect to ball location and flight. Scoring data may also include tracking, location, sensor, manual entry, stroke, or other data collected or modified by the scoring module 20, as described in more detail below.
In some embodiments, electronic communication devices may be used to collect, record, or manage scoring data comprising location data. Electronic communication devices may include a handheld tablet, smart device/phone, personal data assistant, or a dedicated electronic communication device, as examples. Electronic communication devices may include interactive maps for presentation on a display of the electronic communication device and be configured with interface elements to receive user interactions with the interactive maps to indicate a location, e.g., with a pointer or by touch, of objects such as balls and players. Electronic communication devices may also be configured for use in combination with laser rangefinders or LIDAR for object detection, tracking, mapping, or combination thereof. Photogrammetry techniques may be used to analyze photographs or other images to extract measurements and other information. In the illustrated embodiment depicted in FIG. 1A, the one or more tracking systems of the tracking system 11 include one or more of a companion scoring system 12, an automated scoring system 13, a shot prediction system 14, or a manual scoring system 15.
With further reference to FIG. 1B, which illustrates an example tracking system 11 including tracking systems identified in FIG. 1A positioned around a hole of a golf course to collect scoring data, the tracking system 11 may utilize an array of sensors to collect various sensor data to track and manage golf play. The tracking system 11 may provide for the collection of sensor data and data derived therefrom to support statistical information for golf events. In various embodiments, multiple tracking systems may use the same or similar sensors in their operations to collect and/or derive scoring data. Example sensors may include global positioning sensors, e.g., global positioning sensors (GPS), radar, light detection and ranging (LIDAR), cameras, e.g., implementing computer vision, and lasers. Radar devices 132 may include those implementing ground-to-air Doppler radar. Camera devices 134 may include digital video cameras, infrared cameras, ultraviolet cameras, thermal cameras, high speed cameras, machine vision cameras, or other similar optical capture devices. Techniques such as photogrammetry may be implemented to extract location or other information from images. Laser devices may include those implementing laser technologies, such as LIDAR, for measuring geographic features and laser rangefinders for collecting location data. In some embodiments, GPS-enabled laser rangefinders or LIDAR may be implemented to measure distance of an object and collect location for that object. Such laser technologies may utilize real time kinematic (RTK), which increases the accuracy of location measurements by using a small ground network, including a GPS base station, to correct position measurements in real time.
Radar devices 132 may be used to collect and record location data for a golf ball at any point in flight. In some embodiments, the radar may be used to collect data indicating the location, velocity, trajectory, acceleration, or other parameters of the ball flight of a golf ball. Radar may be used to identify location of a golf ball at impact with a golf club and impact with ground. Radar may be used to determine ball flight and related location when the golf ball is at a location where the golf ball is no longer visible by cameras or lasers, such as when the golf ball is behind obstacles, such as trees, stones, etc. In some embodiments, radar may be used track golf balls up to 400 yards or more away from the radar source under various weather conditions, such as rain, fog, sunrise, and sunset. In one implementation, the tracking system 11 utilizes radar devices 132 employing ground-to-air Doppler. Radar devices 132 may be located a one or more locations along a golf course or hole. In the illustrated example radar devices 132 are placed behind each tee and green of a course, and may be angled towards the center of the fairway. In some embodiments, the radar devices 132 may be operated by a human, robot, or fully autonomous. In other embodiments, as described in more detail herein, the radar devices 132 may be mobile.
Laser devices may be utilized to measure and record the distance of objects, such as players or golf balls, from the device. For instance, in some embodiments, a laser device comprises a laser rangefinder. Laser rangefinders may be GPS-enabled to enable the laser rangefinder to record location data for objects detected by the laser rangefinder in addition to distance measurements. Laser rangefinders may utilize RTK to determine the location of an object with high accuracy, e.g., within centimeter. Laser rangefinders may be associated with other sensors of one or more tracking systems 11 such that the laser rangefinder measures and records the distance of objects detected by other sensors of the tracking system 11. In some embodiments, laser rangefinders may be operated by a human, robot, or fully autonomous. In one example, targeting of laser rangefinders may be remotely controllable by the tracking system 11. For instance, targeting of a laser rangefinder may be calibrated with a camera feed view and be mounted with positioning hardware that is remotely controllable by powered components, such as actuators, of the tracking system 11 such that the tracking system 11 may autonomously, or at the direction of a user, manipulate the laser rangefinder to target a particular location or object. In some embodiments, the tracking system 11 may employ laser devices implementing LIDAR to identify players and balls, track players and balls, or both.
Camera devices 134 may be used to determine location, track players, balls, or object movement. Camera devices 134 may be configured with player recognition, ball recognition, or other object recognition. In one embodiment, a player may carry or wear an optical, electromagnetic, or reflective maker identifiable by a camera or associated receiver that uniquely identifies the player. Camera devices 134 may utilize optical recognition/augmented reality (AR) to locate players and/or balls. Camera devices 134 may be configured with machine learning for optical recognition. For instance, the tracking system 11 may utilize camera devices 134 and employ facial recognition, body recognition, gait recognition, clothing recognition, ball/shape recognition, or the like with respect to camera data to identify participants and/or balls, pair location with player or player ball, or both. Camera devices 134 may typically be located at known locations, but in some instances one or more camera devices 134 may be utilized in a mobile environment, e.g., utilizing RTK. In some embodiments, camera devices 134 may be used to identify motion and objects in captured video or image frames thereof and a GPS-enabled laser or laser rangefinder associated with a camera may target such objects to determine distance of the object from the camera. In one example, combining camera view angle with distance, the location of the object may be determined. In some embodiments, topology of the region may be mapped or determined by LIDAR, photogrammetry, or combination thereof and added to the distance calculations. The tracking system 11 may utilize known size of objects for scaling to determine distances of objects captured in camera images. In some embodiments, such camera devices 134 are operated by a human, robot, or may be fully autonomous. Camera devices 134 may operate in the visual spectrum and/or optical spectrum to include one or more of the visual spectrum, ultraviolet spectrum, or infrared spectrum.
The tracking system 11 may implement an electronic communication device that personnel, such as scorers or spotters, carry to interact with the tracking system 11. For example, a companion scoring system 12, manual scoring system 15, or both may utilize electronic communication devices to track scoring data. In one embodiment, an electronic communication device includes an interactive display presenting digital interactive maps of the course. Users of the electronic communication devices may interact with the interactive maps to mark locations of golf balls, players, or both. In one example, one or more users carrying the electronic communication devices may be located on each hole to collect the location data. In some embodiments, electronic communication devices may be used to record the location of objects on the course and a laser, e.g., laser rangefinder, integrated or operatively coupled with the electronic communication device, may be used to measure the distance of the object. In one such embodiment, users may use the electronic communication device to record the location of the object by either tapping the location on the digital map, using the associated rangefinder to record the distance and location of the object, or a combine thereof. In some embodiments, the electronic communication device may utilize RTK to determine and record the location of objects.
The scoring data collected by the tracking system 11 may be transmitted to a data management system 16. The data management system 16 may transmit the scoring data for review to a scoring module 20. In some embodiments, one or more of the tracking systems of the tracking system 11 may transmit scoring data directly to the scoring module 20.
As introduced above, the tracking system 11 may include one or more tracking systems, thus, in some embodiments the scoring module 20 may operate in an environment wherein large amounts of scoring data are being transmitted from multiple tracking systems, which may include multiple sensor types and personnel. The scoring data may include location data such as player or ball location coordinates, zones, or both and data logging related to corresponding shots, which may include association of stroke data corresponding to the ball locations with respect to the competing players. However, as multiple scoring systems may be collecting such location and stroke data, with varying levels of accuracy, multiple locations may be present for a particular stroke, multiple strokes may be present for a particular location, a stroke may be present without a corresponding location, a location may be present without a corresponding stroke, strokes or locations may be present without identification of a player, and any of the above may be incorrect. Sensors collecting ball locations may also be partially or fully autonomous or automated such that the ball location coordinates may not be transmitted with data identifying a corresponding hole event, e.g., player and stroke. Every sensor type used by the one or more tracking systems may not collect scoring data for every hole event, may be offline, or may miss various events. Accordingly, it may be difficult to determine which locations correspond to which players and strokes. This problem is magnified in a tournament environment wherein three players are playing each hole of an 18 hole course at the same time with each player tallying multiple hole events on each hole.
The present disclosure describes various embodiments of a scoring module 20 and methods of managing scoring data collected by a tracking system 11 comprising one or more tracking systems 11. In various embodiments, the scoring module 20 may manage oncourse data collection and validation of one or more tracking systems 11. Nonlimiting examples of scoring data include location data and stroke data. Nonlimiting examples of location data may include location of a ball on the course before or after being hit; location of a player, such as at ball, approaching ball, in tee box, or on green; or location of a ball before or after being hit. The location may comprise coordinates, which may be GPS or other coordinates, such as a custom coordinate system. Coordinates may be translated between coordinate systems. In some embodiments, location may also include zones, such as those described herein. In some embodiments, the scoring module 20 is configured to translate coordinates to zones or compare a zone location determination of one of the one or more tracking systems with a coordinate determination of the same or different tracking system, e.g., to determine if they are consistent or if a notification or action message should be generated. Nonlimiting examples of stroke data may include stroke, swinging, ball hit, penalty, drop, provisional, or ball in hole.
The scoring module 20 may include a score management device 202, an object detection device 210, and a location device 208. The scoring module 20 may include or otherwise be configured to execute program instructions, which may be referred to herein as a score management application 204, and which may include access, run, emulate, or otherwise utilize the program instructions via interaction and operation of the score management device 202 and other scoring module 20 components, to perform score management operations. For instance, the scoring module 20 may include one or more processors and one or more memories storing the program instructions that when executed by the one or more processors perform the score management operations.
The scoring module 20 is configured to enable score management operations comprising management of the scoring data. As described herein, score management operations may include verification, correction of information that is received from data collection sensors or manual entry in the live scoring process, or entry of absent scoring data. In some embodiments, the scoring module 20 may override scoring data. The scoring module 20 may include or incorporate hardware enabling the scoring module 20 to receive tracking system 11 scoring data, such as one or more wired or wireless receivers, transceivers, or transmitters, as well as one or more processors configured to execute program instructions to determine scoring data, such as locations of balls or players, stroke data, or other scoring data. This may include the ability to enter in stroke-by-stroke detail information along with identify accurate shot locations, such accurate GPS shot locations, which may include providing interface elements to enable users to enter or identify such information via the score management device 202, object detection device 208, or combination thereof.
The score management device 202 may comprise an electronic communication device including one or more processors and one or more memories storing program instructions that when executed by the one or more processors performs score management operations. to perform score management operations. The score management device 202 may include a user interface 206. The user interface 206 may include a display, one or more hard or soft buttons, or other interface elements enabling users to interface with score management operations. The score management device 202 may be deployed to collect location data, such as GPS or other coordinate system coordinates, for balls some distance away from the score management device 202. In one example, the distance ranges from 5 feet to 100 yards. In one embodiment, the score management device 202 generates an interactive course map that is presented on the display. The user may interface with the interactive map to indicate a ball location. In this or another embodiment, a user may capture a current location of the score management device 202, or other component of the scoring module 20, and set the location as the location of a ball. For example, the score management device 202 may be positioned over a ball and the user may capture the location and set the location as the ball location. As described in more detail below, the score management device 202 may utilize the location device 208 to receive or determine its location.
As introduced above, the score management device 202 may include a user interface including a display and one or more interface elements. The display may be used to communicate information regarding operations of the scoring module 20, such as managing scoring data collected by the one or more tracking systems of the tracking system 11, which may include one or more of validating, modifying, replacing, or adding scoring data. The user interface 206 may additionally or alternatively include on or more hard or soft buttons the user may use to interface with the score management operations of the score management device 202, which may include those described with respect to the score management application 204, object detection device 210, or location device 208. In one example the display comprises a touchscreen to enable a user to communicate through interaction with the display by selecting soft buttons, map locations, or other interactive display elements.
The object detection device 210 may be configured to, at least in part, determine a location of an object on or around the golf course from a remote position. The object detection device 210 may be deployed to collect location, such as GPS or other coordinate system coordinates, for ball positions some distance away from the object detection device 210. In one example, the distance ranges from a foot to 100 or more yards.
The scoring module 20 may include or incorporate location services 18 such as those provided by one or more of a global satellite constellation infrastructure network 182 or a location network 184. The location network 184 will typically be a local location network 184 with respect to a golf course the tournament is played, such as an on-course location network 184, and may include or incorporate operation of various location network elements such as radio receivers, transmitters, transceivers, antennas, UWB antennas, anchors, initiators, responders, cell towers, Wi-Fi access points, beacons, geo-beacons, BLE gateways, or the like. In some embodiments, the location network 184 includes or incorporates external location/signal networks that utilize short range or long range location technologies, which may include signals of opportunity.
The location device 208 may be configured to communicate with location services 18 to determine its location. In various embodiments, the location device 208 may comprise a global navigation satellite system, or other location technology, device receiver, transmitter, transceiver, antennae, anchor, initiator, responder, or the like configured to communicate with location services 18 to determine its location. In one embodiment, the location device 208 may be integrated with the score management device 202, object detection device 210, or both. The scoring module 20 may be configured to be mobile, allowing a user to move the components of the scoring module 20 around the course while still enabling the user to use the components to accurately determine object locations on and around the course. For example, the location device 208 may be utilized to allow the scoring module 20 to be mobile and quickly determine its location when moved, preferably to an accuracy of a centimeter or less within 10 seconds of moving. Utilizing the location device 208 and communication with the location services 18, the scoring module 20 may quickly and accurately update its location for use in determining object locations, e.g., locations of balls, relative to its location.
In one embodiment, location services 18 include services provided by a global navigation satellite constellation infrastructure 182 that interact with one or more elements of the location network 184 to provide highly accurate location servicing. For example, such location network elements may include one or more global navigation satellite system (GNSS) base stations positioned at known locations on or around a course to provide location services with respect to a location device 208 comprising a GNSS antenna. For instance, the GNSS base station and GNSS antenna may receive GNSS signals for location determination. The GNSS base station and GNSS antenna may apply differential correction where the GNSS base station determines location correction data that is used to correct fine errors in location determinations that would occur by use of the GNSS antenna alone. In some embodiments, differential correction includes precise point position (PPP), RTK, or a PPP-RTK hybrid. In one embodiment, a location device 208 comprising a GNSS antenna is employed without a GNSS base station.
The score management device 202 may include one or more communication ports configured for wired or wireless communication with the location device 208 and object detection device 210. The scoring module 20 may include a communication port for wireless communication with the data management system 16. The communication port may be the same or different than the one or more communication ports utilized for communication between the score management device 202 and the object detection device 210 and location device 208.
The scoring module 20 may be configured to transmit the managed scoring data to the data management system 16 for additional analysis, modification, formatting, storage, or other desired application. In one embodiment, the managed scoring data may be transmitted by the scoring module 20 or data management system 16 to one or more data platforms 19 for use by various data consumers such as applications, websites, clients, distribution platforms, statistical analysis, archival application, television broadcasts, or the like.
In some embodiments, one or more tracking systems of the tracking system 11 may utilize GPS-monitoring devices worn or carried by players, caddies, or course personnel in order to obtain location data. As players walk the course from hole-to-hole, a GPS device may collect and record location data. The GPS device may be individualized to uniquely identify the player wearing the device. The location data recorded from the device associated with a specific player may also contain additional information to uniquely identify that player. The location data recorded from the GPS device may also be cross-referenced with location data recorded from other GPS-enabled sensors used in the tracking system 11. The locations may be used by the tracking system 11 in automated or manual tracking, such as with respect to companion scoring system 12, automated scoring system 12, shot prediction system 14, or manual scoring system 15, to pair or temporally pair stroke data such as ball hit or ball landing with a player by pairing a time stamp of a location of a player with the time stamp of the stroke data. In some embodiments, a player's location tracked on a hole may be available as “breadcrumbs”. These breadcrumbs may be used by one or more tracking systems 11 to identify a player at a location on a hole to pair with stroke data at the location having the similar time stamp as described above. In one embodiment, the breadcrumbs may be integrated into a graphic displayed on an electronic communication device used by the companion scoring system 12 or manual scoring system 15 to assist in player identification. In this or another embodiment, breadcrumbs may be integrated into a graphic displayed on a score management device 202 to assist in player identification with respect to live or past scoring data events.
While the present description generally refers to GPS, those having skill in the art will appreciate that such reference applies equally to other Global Navigation Satellite Systems (GNSS), such as GLONASS, BeiDou, Galileo, or other current or future GNSS. GPS location may be augmented with WAAS (Wide Area Augmentation System), Differential GPS (DGPS), e.g., Global Differential GPS (GDGPS), RTK, Continuously Operating Reference Stations (CORS), Signals of Opportunity (SOP)-based or augmented navigation, UWB, LTE, cellular, radio, television, Wi-Fi, other satellite signals, or the like.
The golf data collection and management system 10 may include or utilize one or more databases to store and relay information that traverses the platform, cache content that traverses the platform, store data about each of the devices, store coordinates, store raw or verified scoring data, store map data, or perform any other typical functions of a database. Furthermore, databases may include a processor and memory or be connected to a processor and memory to perform the various operations associated with the databases. In certain embodiments, databases may be connected to any process, program, device, system, element, network, or any combination thereof of the golf data collection and management system 10. Databases may comprise multiple or a single database. Databases may be local or remote. The databases may be distributed. The database may be cloud-based.
The golf data collection and management system 10 may be configured to communicate scoring and other data described herein over various communication networks, such as a mesh network, a local network, a cloud-computing network, an IMS network, a VoIP network, a security network, a VOLTE network, a wireless network, an Ethernet network, a satellite network, a broadband network, a cellular network, a private network, a cable network, the Internet, an intranet, an internet protocol network, MPLS network, a content distribution network, short range wireless communication network, or any combination thereof. One or more tracking systems, the scoring module 20, or any component thereof may include networking components configured to communicate directly or indirectly with location elements, such as location services 18 via the various communication networks.
The tracking system 11, scoring module 20, or both may utilize map data comprising a map of the course. The course map may be defined within a coordinate system such that locations or points on the course map are associated with coordinates, which may be referred as a coordinate map. Map data may include cloud point data collected from LIDAR and photogrammetry. Map data may also include tournament round data and location data for various zones and boundaries on the course that may be separately mapped before a tournament. Course maps may be generated using ground control markers placed on the course at known locations and recorded. For example, location data for the ground control markers may be used as reference points for generating the course map from point cloud data, which may be collected from techniques such as one or both of LIDAR or photogrammetry. Coordinates of the ground control markers may be used to key the point cloud data to a coordinate system.
As introduced above, the map data may include a zone map comprising a detailed identification of zones of the course. The zone maps may identify zones that may be as specific or as general as needed. Zones may include various grounds designations and/or physical features within the course of play and, in some embodiments, outside the course of play, such as out-of-bounds areas within the vicinity of the course where a player may potentially hit a ball. Thus, in some configurations, zones may correspond to areas within and/or around the course of play, such as physical structures (e.g., natural and/or manmade objects, structures, and features). For example, zones may correspond to parts of a golf course, such as tee box, fairway, green, hazard (bunker or water), rough, drop zone, and the like. Zones may include a tee box zone. A tee box zone may include one or more detailed tee box zones such as a tee left, tee right, or tee center detailed zone. Zones may include one or more zones corresponding to a fairway, such as fairway, fairway bunker, or the like. In a further configuration, zones corresponding to a fairway may include detailed zones such as one or more of left fairway, right fairway, left fairway bunker, right fairway bunker, or the like. Zones may include one or more zones corresponding to a hazard, such as hazard, grass bunker, fairway bunker, waste bunker, water, or the like. In a further configuration, zones corresponding to a hazard may include detailed zones such as one or more of front center greenside bunker, front left greenside bunker, left greenside bunker, left rear greenside bunker, rear greenside bunker, right greenside bunker, right rear greenside bunker, right front greenside bunker, or the like. Zones may include one or more zones corresponding to a rough, such as primary rough, intermediate rough, greenside rough, or the like. In a further configuration, zones corresponding to a rough may include detailed zones such as one or more of left rough, right rough, left intermediate, right intermediate, or the like. Zones may include one or more zones corresponding to a green, such as green, fringe, or the like. Zones may include one or more zones corresponding to landscape and/or nature features, such as bush, tree, step, landscaping, path, rock outline, tree outline, dirt outline, native area, water, or the like. Zones may include physical features such as manmade structures positioned around the course such as one or more of grandstands/seating, camera tower, hospitality tent, building, cart path, pedestrian path, walk strip, wall, bridge, or the like. In some embodiments, one or more zones may be identified as other or unmapped.
FIG. 1C illustrates zones designation of a portion of a hole and surrounding areas. As described above and elsewhere herein, each zones may be associated with corresponding coordinates. The example zone map includes fairway 190, green 191, rough 192, tee box 194, native area 195, cart path 196, and greenside bunker 198 zones. The zones further include detailed zones including left fairway 190 a, right fairway 190 b, left rough 192 a, right rough 192 b, left front greenside bunker 198 a, right front greenside bunker 198 b, and around the green 199.
With reference again to FIG. 1B, scoring data may be collected by one or more tracking systems 11. A companion scoring system 12 may utilize an electronic communication device, as described herein, and, with respect to the companion scoring system 12, may be referred to as a companion device 122, carried by personnel, referred to as scorers, that input stroke events and other scoring data. Scorers may include caddies, players, or others that are viewing play. Companion devices 122 may include a processor and memory storing program instructions that when executed by the processor perform the operations of the companion device 122. In one example, the program instructions include those of a scoring application that is executed or run on the companion device 122. The scorer, utilizing the companion device 122, will typically accompany players 110 whose score the scorer is tracking; however, in some embodiments, the scorer may remotely view the players 110 via a live or delayed feed. Companion devices 122 may be equipped with wireless data communication transceivers configured to wirelessly transmit scoring data to the data management system 16, scoring module 20, or both. During play, each player or player group may have an assigned companion device 122 that a scorer uses to collect scoring data. Companion devices 122 may be configured with various wireless communication technologies, such as those described above, which may include short range and/or long range communications. In some embodiments, companion devices 122 may be similar to companion devices 122 described in U.S. patent application Ser. No. 17/841,660, filed Jun. 15, 2022, titled Golf Event Management System with Scoring and Location Tracking, the contents of which are hereby incorporated by reference. Using the companion device 122, a scorer may record scoring data with respect to play. Recording scoring data, e.g., when a player addresses or hits a ball, may result in generation and recordation of an associated time stamp. As introduced above, the companion scoring system 12, another scoring system, scoring module 20, or combination thereof may utilize the time stamp to synchronize with other scoring data, such as location data or stroke data.
In one embodiment, the companion device 122 may be configured to receive group location data, e.g., location of a player group, which may include zone location. A scorer may interface with interface elements of a user interface 206 of the companion device 122 to input group location data by any suitable method, such as input into a provided field, select from a list of displayed options, or the like. In one example, when the players 110 in a group are on the tee box, the scorer inputs or selects “tee”. In a further or another example, when the first caddie or player of the group arrives at the player's ball in the fairway, the scorer may input or select “fairway”. In a further or another example, when the first caddie or player of the group arrives at player's ball around the green, the scorer may input or select “green”.
To track player hits, the companion device 122 may present a selectable list of players from which the scorer may select. When tracking player hits, the companion device 122 may be configured to present a selectable list of zone locations the player will be hitting the shot from. Example zone locations may include tee, fairway, green primary rough, bunker, sand, fringe, waste area, or native or natural area. In one configuration, “from location” is to be set at any time for a player and have it be “sticky” for the next shot. In other words, the scorer may set a player's “from location” as soon as that location is known and have that value persist until the scorer either changes the location or indicates the ball has been hit.
In one example, the companion device 122 is configured to receive a “player addressing ball” input from the scorer, which may be entered as an event, e.g., upon the occurrence of, when the player first addresses the ball. Additionally or alternatively, the companion device 122 may be configured to receive a “shot hit” input from the scorer when the player hits the ball. In some embodiments, “shot hit” may trigger recordation of a stroke for the corresponding player.
The companion device 122 may also be configured to score various stroke types, such as drop, penalty, and provisional. For instance, the companion device 122 may query the scorer or request entry of a shot type, if applicable. If the scorer selects “drop”, the companion device 122 may prompt the scorer to indicate if there was a penalty. If the scorer selects “penalty”, the companion device 122 may prompt the scorer to indicate if there was a drop. If the scorer selects “provisional”, the companion device 122, one the next stroke, may prompt the scorer to indicate if the provisional is being used. If yes, and the shot location was “from the tee”, a penalty stroke may automatically be added to the player's score. If not, and the shot location was “from the tee”, the companion device 122 may prompt the scorer to indicate if there was a drop and, if so, automatically add a penalty stroke to the player's score.
The automated scoring system 13 may include one or more tracking systems or components thereof described in U.S. Provisional Patent Application No. 63/599,557, filed Nov. 15, 2023, titled Golf Tracking System for Monitoring and Management of Data, the contents of which are incorporated herein by reference. An automated scoring system 13 may be fully or partially automated using sensors to detect players, ball and player movement, and locations thereof to pair players, shots, and ball positions for automated or partially automated scoring. Automated scoring systems 13 may include a processor and memory storing program instructions that when executed by the processor perform the operations of the system. Automated scoring systems 13 may include one or more camera devices 134 positioned around the golf course to track movement and identify distances using an associated laser or rangefinder or via optical calculations. For example, each camera may calculate the distance a ball or other object of known size by comparing the optically captured size of the object to that of the known size of the object. Further determination of the angle of the camera may be used to plot the location of the object at the distance and angle from the camera relative to a map of the region around the camera to identify location coordinates corresponding to the location. Location determination may be enhanced utilizing multiple camera devices 134, e.g., to triangulate or otherwise determine location of a ball or other object. In one example, an optical map of a region of the course from a view of a fixed camera may be utilized by a camera to determine location of objects relative to known locations within the mapped region.
For example, by comparing an image captured of an object to surrounding features in the image of known location, the approximate location of the object may be determined. Optical calculations such as those described above may be used to determine distance to enhance the accuracy of the location determination. In one embodiment, camera devices 134 are calibrated to a coordinate map of the course. The coordinate map may be a 3D point cloud map that the field of view of the camera is overlaid to determine location of balls. For example, the camera view and the 3D point cloud, e.g., lidar, view align such that when a user, laser rangefinder, or system component, e.g., tracking software utilizing object tracking, identification, or recognition, identify a location in the camera view, the coordinate or point in the 3D point cloud identifies the location. The coordinate may also be translated into another coordinate system as described herein for use by the tracking system 11, data consumer clients, or as otherwise desired. Other sensors, such as radar may similarly be calibrated. In one example, the coordinate map is collected using lidar; however, other mapping techniques may be used.
Optical recognition may be employed to identify balls or other objects. In one embodiment, automated scoring systems 13 may utilize optical recognition/augmented reality (AR) to identify balls. Camera devices 134 may typically be located at known locations, but in some instances one or more camera devices 134 may be utilized in a mobile environment, e.g., utilizing RTK base stations or network, such as RTK based GPS, or other location methodologies with respect to determining the location of the camera, such as those described herein with respect to laser rangefinders. In some embodiments, images captured by camera devices 134 may be used to identify motion and objects and a laser or rangefinder associated with a camera may target such objects to determine distance of the object from the camera. Combining camera view angle with distance, the location of the object may be determined. In some embodiments, topology of the region may be mapped or determined and added to the distance calculations. Locations may include a “shot from” coordinate, a final resting position coordinate, or both. In some instances, a ball may enter the field of view of a camera while in flight and the starting point of tracking by the camera is the first place the ball entered the field of view. Camera devices 134 may operate in the visual spectrum and/or optical spectrum to include one or more of the visual spectrum, ultraviolet spectrum, or infrared spectrum.
In some embodiments, automated scoring systems 13 may utilize radar devices 132 positioned around the golf course to track balls, which may include location, velocity, trajectory, acceleration, or other parameters. Radar may be used to track balls in the air. Multiple radar devices 132 may be positioned around the course to collect coordinates. Radar devices 132 may typically be located at known locations, but in some instances one or more radar devices 132 may be utilized in a mobile environment, e.g., utilizing RTK base stations or network, such as RTK based GPS, or other location methodologies, such as those described herein with respect to laser rangefinders. Processing of radar data may provide location coordinates with respect to a “shot from” location, i.e., where a ball flight initiated, and coordinates of an impact location. Radar devices 132 utilized by automated scoring systems 13 may be operated by a human or be fully or partially automated.
In some embodiments, automated scoring systems 13 may also include laser devices positioned around the golf course to measure distance of balls and generate coordinates of the ball. Lasers may provide coordinates with respect to a from location, a final resting position, or both. Laser devices may be operated by a human or by fully or partially automated. Laser devices may comprise LIDAR and may be utilized similar to camera devices 134 described above. Laser devices may typically be located at known locations, but in some instances one or more laser devices may be utilized in a mobile environment, e.g., utilizing RTK base stations or network, such as RTK based GPS, or other location methodologies with respect to the laser device, such as those described herein with respect to laser rangefinders.
Camera devices 134 and analysis of images used to collect scoring data may be operated by a human or be fully or partially automated. In one embodiment, manual scoring systems 15 may utilize camera devices 134 whereby scoring data is tracked by camera devices 134 as above and personnel enter the corresponding location data, scoring data, or both that is generated. For example, a laser associated with a camera tracking a ball may target the ball to return a distance to a producer that enters the output location. An image processor may similarly be used to perform optical calculations as described above to output a ball location. A producer may view camera data tracking a ball and visually determine a ball and input the location, which may be a coordinate, zone, or both.
Additionally or alternatively, in some embodiments, manual scoring systems 15 may include personnel or “spotters” 152 that collect coordinates. For example, spotters 152 may interact with digital maps or printed maps of a hole to identify a ball location relative to the map and transmit via an electronic communication device. For example, spotters 152 may indicate ball location on a touch screen of an electronic communication device that displays a digital map of the hole or enter ball coordinates into the electronic communication device determined by identifying the ball location on a grid or other coordinate map overlaying a map of the course. Another example may include spotters 152 utilizing a laser rangefinder wherein spotters 152 operate a laser rangefinder that when targeted to a ball generates a coordinate location of the ball. Laser rangefinders may be set up relative to the course at a known, stationary location such that the direction the laser is directed (e.g., using compass hardware such as one or more of a magnetometer, accelerometer, gyroscope, or mechanical position tracking) may be combined with the measured distance to obtain the coordinates of the ball. In some embodiments, mobile camera devices 134 or mobile LIDAR calibrated to the course map and employing location services 18 or technologies such as GPS or GPS augmented with RTK base stations or network, such as RTK based GPS, or other location methodologies with respect to improved GPS location accuracy. In one embodiment, spotters 152 may utilize an electronic communication device similar to the map interaction described above including a display screen that displays a map of the course for indicating or identifying the location of a ball relative to the map by interacting with the displayed map, e.g., by touching or plotting the location of the ball or viewing coordinates on the map and entering the coordinates. The electronic communication device may be sized and configured to be carried for handheld operation. The map may be a coordinate map such that indicating the ball location causes the corresponding coordinates to appear for further entry or automatically trigger collection of the coordinates.
A shot prediction system 14 may utilize ball flight data such as location, velocity, trajectory, acceleration, or other parameters collected by radar devices 132, lasers, camera devices 134, or combination thereof to predict a final resting position of the ball. The shot prediction system 14 may be configured to predict ball flight, impact coordinates, bounce, roll, final resting position, or combination thereof. In one configuration, the shot prediction system 14 may be similar in hardware, operation, and associated infrastructure to the prediction generator described in U.S. patent application Ser. No. 18,238,234, filed Aug. 25, 2023, titled System and Method for Estimating Final Resting Position of Golf Balls, the contents of which are hereby incorporated by reference. The shot prediction system 14 may be used to generate predictions with respect to the location of balls during golf play. The shot prediction system 14 may be configured to output coordinates of predicted ball locations corresponding to a final resting position of a ball following a hit. The shot prediction system 14 may utilize one or more prediction models to calculate a predicted bounce and roll behavior to predict final resting position coordinates. Predictions may consider various conditions of impact locations, such as topography, material, and properties thereof. Predictions models may be updated using data derived from comparison of actual and predicted bounce and roll behavior and/or final resting position. Predicative analytics employing a prediction model that incorporates metadata measured with respect to ball physics and the course environment may be used to predict bounce and roll behavior. The prediction model may take measured ball impact physics, impact coordinates, and properties of the material corresponding to the impact coordinates together with historical shot data corresponding to the impact coordinates to predict bounce and roll behavior and/or final resting position. The shot prediction system 14 may utilize a detailed map data that comprises a measured surface model specifying ground and object topography of coordinates of a golf course property. The surface model may comprise a three-dimensional coordinate model, which may comprise a digital surface model measured by LIDAR, photogrammetry, radar, and the like. It is to be appreciated that the system may alternatively utilize detailed maps of a course portion of a property for more limited application to predictive bounce and roll behavior for final resting position. Prediction models may incorporate physics, e.g., including ball impact physics variables, ball properties, and properties of ground and/or objects a ball impacts. Prediction models may further include one or more associated coefficients that modify prediction model terms, parameters, parameter estimates, or, otherwise, output. The coefficients may be applied to one or more terms or parameters of a prediction model. In one example, coefficients may include or alter terms, parameters, parameter estimates, or values corresponding to properties of impact materials. In some examples, coefficients include regression coefficients.
The shot prediction system 14 may include a processor and memory storing program instructions that when executed by the processor perform the operations of the shot prediction system 14. The shot prediction system 14 may include or access a database including one or both of course maps or location information with respect to radar, lasers, or camera devices 134 supplying flight parameters to identify locations, coordinates, ground characteristics, or combination thereof. In one embodiment, devices supplying flight parameters may transmit location information with flight parameters. In one example, the shot prediction system 14 takes ball flight parameters, such as those collected by radar devices 132 and applies AI to make an educated prediction on final resting point. Location of the ball in flight may be determined relative to a map of the course and the location of the device measuring ball flight parameters. The coordinates may be accompanied by or associated with data elements such as a timestamp corresponding to the predicted time the ball came to rest at the predicted coordinate. Data elements may also include a geographic identifier. The geographic identifier may include a hole or other area of the golf course. The geographic identifier may be determined by cross-referencing the coordinates with a coordinate map of the golf course, the sensor location corresponding to the coordinate source, the sensor location, and its field of view, or by other suitable methodologies.
As introduced above, the golf data collection and management system 10 may include a scoring module 20 configured to manage scoring data collected by the tracking system 11. With reference to FIG. 2 , illustrating an embodiment of a scoring module 20 according to various embodiments described herein, the scoring module 20 includes a score management device 202, location device 208, and object detection device 210, which may be as described above with respect to FIG. 1A. In the illustrated embodiment, the score management device 202 includes an electronic communication device comprising a tablet. The score management device 202 is configured to execute score management operations, such as those described herein with respect to the score management application 204 (see, e.g., FIG. 1A). The user interface 206 including interface elements such as a display configured with touchscreen technology to receive user interactions. In the illustrated embodiment, the scoring module 20 includes an object detection device 210 comprising a laser rangefinder, but those having skill in the art will appreciate that other object locating devices or techniques may be used. The object detection device 210 may be used to target objects such as balls, players, or other objects on or around the golf course to measure the distance the object is from the scoring module 20 or component thereof. For example, the score management device 202 or object detection device 210 may be equipped with global positioning or other location technology that is used together with direction targeted to determine location coordinates of an object. The object detection device 210 may connect to the score management device 202, e.g., wirelessly, and be configured to target objects. The available target distance and accuracy may vary based on the object detection device 210 technology, e.g., rangefinder technology, and equipment. In one example, the object detection device 210 may be configured to target objects from 1000 meters to an accuracy of +/−0.2 meters. The illustrated location device 208 comprises a GNSS antenna. The GNSS antenna may be accurate to a centimeter or less. The GNSS antenna may be configured to get an accurate GPS location within 10 seconds after moving to a new location. In one example, the GNSS antenna is configured to update the GPS location on the score management device 202 when moved and be accurate to 1 centimeter. As described above, the location device 208 may include or be configured to receive correction or offset data from a GNSS base station using PPP, RTK, hybrid PPP-RTK, or other correction methodology. In one example, RTK is utilized.
In the embodiment depicted in FIG. 2 , the GNSS antenna location device 208, score management device 202, and object detection device 210 are mounted to a frame 212, comprising a pole in the illustrated example, to allow the scoring module 20 to be moved and maintain an accurate proximity for application of the score management operations of the object detection device 210 and score management device 202. For example, the GNSS antenna may screw into the top of the frame 212 and clamps may be used to separately attach the object detection device 210 and score management device 202. While the score management device 202, object detection device 210, and location device 208 are shown as separate component devices, those having skill in the art will appreciate upon reading the present disclosure that two or more of the component devices or portion thereof may be integrated or combined in a housing, however, such an integration or combination is intended to be within the scope of the present claims and description of the component devices of the scoring module 20 irrespective of physical integration or combination. A bipod 214 is also mounted to the frame 212 to provide stability for placement on a surface after being moved.
As introduced above, the score management device 202 may include interface elements comprising a display to present a hole graphic representation whereon a user may interact with the digital map of the hole on the display. For example, the score management device 202 may include interface elements enabling users to verify, modify, replace, or add location data by indicating a ball location on a touch screen displaying a digital map. Additionally or alternatively, a user may verify, modify, replace, or add location data by utilizing the object detection device 210, such as a laser rangefinder, to target an object to identify the object's coordinates.
The scoring module 20 may be configured to monitor and manage scoring data collected by the tracking system 11. For example, the score management operations may configure the scoring module 20 to analyze the scoring data and identify anomalies and generate action messages that are presented on the display of score management device 202, as described in more detail below. Additionally or alternatively, the score management operations may configure the score management device 202 to communicate with the data management system 16 to receive identified anomalies in scoring data triggering generation of the action messages. The scoring module 20 may be configured to directly or indirectly communicate with one or more of the one or more tracking systems of tracking system 11 to receive collected scoring data. Thus, the score management operations may configure the score management device 202 to provide notifications of anomalies in scoring data to users so the user may take action to address the anomalies, e.g., by validating the scoring data, correcting or replacing scoring data, or obtaining missing scoring data and entering the same. The anomalies may relate to anomalous hole events, ball locations, player locations, strokes, ball identification, player identification, or other anomalies, such as those described below with respect to action messages.
FIGS. 3-7 illustrate example elements, e.g., interface elements, display elements, or associated operational elements, of a score management tool 300 provided on a scoring device of the scoring module 20 to one or more of review, edit, or enter scoring data recorded by one or more tracking systems. As introduced above, the score management tool 300 may access the scoring data from a data management system, directly from the one or more tracking systems or components thereof, or combination thereof.
FIG. 3 depicts an example user interface of the score management tool 300 for use with the scoring module 20 providing various elements in presentation blocks. The score management tool 300 may include one or more elements, selected from an event selector 301, round selector 302, course selector 303, group scorecard 304, team player stroke detail 305, all groups on holes presentation 306, active hole 10, hole graphic representation 308, edit mode notification 309, or actions panel 310. In various embodiments, the layout of the elements may be configured to enable connections to be created between blocks and/or data elements therein. For example, when selecting an element in one block, connections may be established for other blocks. Thus, elements may be configured to interact with each other. In a further example, the other blocks in which connections are established may be updated with an appropriate presentation. For example, if a team player is selected for a group in the group scorecard 304 element, the score management tool 300 updates the presentation in the team player stroke detail 305 to display the team player's stroke detail. However, it will be appreciated that the elements and the associated components and data thereof operable to provide the operations of the scoring module 20 may be provided in many formats and the present disclosure is not limited to the particular arrangements and combination of elements and user interface components depicted herein.
The event selector 301 may include a selectable listing of one or more events available for viewing and management of the associated data. In one example, the event selector 301 comprises a drop down list of all events that are available for viewing. Selection of an event may cause the presentation blocks to present or be operable to present the associated data for that event.
The round selector 302 may include a selectable listing of one or more rounds of an event available for viewing and management of the associated data. In one example, the round selector 302 comprises a drop down list of all available rounds for the event selected with respect to the event selector 301. In a further example, selection of a round may cause the elements in the presentation blocks to present or be operable to present the data for the round of the event selected. In a further example, the round selector 302 may default to the most recent round in progress and the other elements of the score management tool 300 may update to present data for the round. If no rounds are in progress, the default may be the earliest round having a grouping status designated in the data management system as official, which should correspond to the next round to begin play.
The course selector 303 may include a selectable listing of one or more courses for the event and round selected that are available for viewing and management of the associated data. In one example, the course selector 303 comprises a drop down list of all courses that are available for the selected event and round. Selection of a course may cause the elements in the presentation blocks to present or be operable to present the data for the course of the event and round selected. In one example, a default course may be set to a host course when multiple courses are being played for an event and round.
A user may interact with active hole 307 to select a hole for data review and management. Active hole 307 may also present the hole that is currently being reviewed and managed. In one example, when a user selects a hole via active hole 307 to change the active hole, the user may be presented with a confirmation request to accept or deny the change.
The edit mode notification 309 may include a display element comprising a notification that is presented when an edit has been made in any of the presentation blocks that scoring data has been edited. The edit mode notification 309 may be selectively programmable to provide notifications with respect to any desired edit. For example, in some embodiments, the notification is not displayed when changes are made only to play management blocks, described below. In one example, notifications are output when data element values are above or below a predefined threshold or within or outside a predefined range. The notification may be interactive such that a user may interact with the notification, such as select all or a portion of the notification, to accept or deny the changes. In one embodiment, a separate interface element is provided that a user may interact with to accept or deny the changes. The notification may be removed with the user accepts or denies changes to the data being managed. In some configurations, the notification may display or be operable to present a summary or identification of the changes causing the notification.
In various embodiments, when a user changes or enters data into the presentation blocks, the score management tool 300 may be automatically placed in an edit mode. While in edit mode, the user may enter or otherwise change additional data. While in edit mode, the data may not be transmitted to downstream clients or data viewing platforms thereof. For example, the score management tool 300 may not transmit the changes to the data management system. However, when a user accepts all the current edits, edit mode may be turned off and the data, including any changes made while in edit mode may be sent to downstream clients.
The hole graphic representation 308 may be provided in a 2D graphic (although more advanced graphics such as 3D may also be used). The hole graphic representation 308 may include various navigation functionalities. For example, the hole graphic representation 308 may include one or more of a zoom functionality allowing a user to selectively zoom in and out of the graphic; a graphic rotation functionality allowing a user to selectively rotate the graphics on a horizontal axis, vertical axis, and/or other axes; and/or a variable centering functionality allowing a user to move the center of the graphic in the presentation panel. In one example of a zoom functionality, a quick zoom may be provided to zoom into the green, zoom out to display an entire hole, and/or zoom out to display the entire course. In one example, the graphic is oriented in a method that allows maximum viewing from tee to green, such as an overhead view, tee view, or green view. In one configuration, hole setup information may be displayed on the hole graphic. For example, current hole information may be displayed for each round, such as one or more of tee locations, pin locations, and/or center of fairway points for the holes of the course. In one embodiment, the hole graphic presentation 308 may be configured to show all players of a group at one time upon request from the user, e.g., via interaction with a “show all group players” element. The hole graphic representation may include various displayed distances with respect to the hole. For example, one or both of a scorecard yardage distance or an actual yardage distance between the tees and pins as set for the round may be displayed.
Stroke or ball position coordinates may be plotted on the hole graphic representation 308. For example, the hole graphic representation 308 may include plots of ball positions relative to the hole. For example, ball position may be plotted in the hole graphic representation 308 to show the ending position of a team player's stroke. For a consecutive stroke containing location coordinates, a line may be displayed between the plotted points to depict a stroke trail. As the starting point is the tee and the ending point is the pin, the score management tool 300 may generate lines from these points to strokes with the coordinates or ending positions of the team player's strokes on the hole. In one example, distance of plotted ball positions from the tee, distance from the last stroke, and/or distance to the pin may be displayed or provided as a defined selectable format option. In one configuration, a user may interact with the hole graphic representation 308 to plot a location, e.g., by indicating a position with a pointer, touching the display at the desired location, inputting a location reading captured by an associated sensor, such as a rangefinder, or otherwise, and the score management tool 300 may display the distance of the plotted location from the teen, last stroke, and pin.
Additional functionalities may be provided for managing coordinates for a stroke, such as enabling a user to enter a location for a stroke received; move an existing location assigned to a stroke; create a stroke along with a location for the stroke; display GPS or other location coordinates collected for a team player (via a GPS device worn by the team player), and/or delete a stroke along with its location. In an example of the above functionalities, where breadcrumbs are present, the hole graphic representation 308 may be configured to enable a user to “lock” a stroke to a breadcrumb.
In one embodiment, the functionalities include displaying all GPS and/or other coordinates collected for a team player including ones not associated with a stroke, e.g., breadcrumbs. With the presentation of all coordinates, the hole graphic representation 308 may be configured to associate one location to a stroke of a team player.
As introduced above, the score management tool 300 may be configured to link with sensor data of the scoring module 20. The scoring device may be in wired or wireless communication with a laser rangefinder that may be utilized to capture object locations that are translated to course coordinates. The user may use the coordinates to replace coordinates captured by scoring systems by assigning the coordinates to a stroke via the score management tool 300. This may one or more of change, add, or remove a stroke; change a previously captured ball location by scoring systems with respect to a stroke; or create a stroke and an assigned ball location. In one example, the hole graphic representation 308 may plot the location of the coordinates on the graphic presentation of the hole. The user may be presented with a confirmation request to accept or deny the change.
The hole graphic representation 308 may display stroke related plots collected by sensors of one or more scoring systems. The score management tool 300 may receive coordinates from the data management system and plot the coordinates relative to the hole in the displayed hole presentation. For example, scoring system sensors may include radar that measures impact points for balls. This or other data, such as ball flight parameters measured by sensors such as radar, laser, camera, or other suitable sensors, may be used by a scoring system or the data management system to calculate a predicted impact point or end point, e.g., final resting position of the ball. Thus, the hole graphic representation 308 may display location coordinates for impact points for strokes, calculated predictive end points of strokes, or both if available. In this or another embodiment, the hole graphic representation 308 may display GPS breadcrumb trails of players as described above.
In various embodiments, selecting a group from all groups on holes presentation 306 may cause the group scorecard 304 to populate with the data associated with the group. In one example, the hole graphic representation 308 may similarly populate with shot and/or ball position data related to the group. In one example, selecting specific holes of a group via the group scorecard 304 causes the hole graphic representation 308 to zoom to the selected hole and display plotted ball positions and shot trails of the team players in the group.
FIG. 4 illustrates an example interface 410 of the group scorecard 304 that may be presented by or accessible via interaction with the group scorecard score management tool 300, all or a portion of which may be available in the respective presentation block view. Various elements of the group scorecard 304 may be displayed and/or editable via operation and functionalities of the group scorecard 304, as described in more detail below with respect to the respective elements. The group scorecard 304 may include various data elements such as one or more of team player name 411, stroke event 412, stroke count 413, total 414, total 415, today 416, front nine hole by hole scores 417, score out 418, back nine hole by hole scores 419, score in 420, stroke total 420, or strokes official 421.
Team player name 411 may list the team players in a group. For example, the team players may be presented by last name, first name. In one configuration, team player name 411 may not be edited via the group scorecard 304 of the score management tool 300.
Stroke event 412 may present the current state of a stroke event that has been received from the one or more scoring systems. Various stroke events may be presented, such as club selection, addressing the ball, shot hit, provisional, preliminary, final, and in the hole. The stroke event 412 may be configured to enable a user to change the state of the stroke event. For example, a user may change the state to addressing the ball, shot hit, or shot holed.
Stroke count 413 may be a representation of strokes currently recorded for the hole that the team player is on. If a team player has not started their round, the stroke count may default to show the starting tee time. In one configuration, stroke count 413 may not be edited via the group scorecard 304 of the score management tool 300 of the score management tool 300.
Total 414 may present the total par relative score for the event. In one configuration, total 414 may not be directly edited via the group scorecard 304 of the score management tool 300.
Today 415 may present the par relative score for the round. In one configuration, today 415 may not be edited via the group scorecard 304 of the score management tool 300.
Front nine hole by hole scores 416 may present a list of scores by hole for the first nine holes. In some embodiments, a column or row header, dependent on configuration, may be provided to show the hole numbers for improved clarity. In one configuration, front nine hole by hole score 416 may be edited via the group scorecard 304 of the management tool 300 by entering an integer or removing a score from a hole score field.
Score out 417 may present a stroke total for the scores entered on the front nine if completed. In one configuration, score out 417 may not be directly edited via the group scorecard 304 of the score management tool 300.
Back nine hole by hole scores 418 may present a list of scores by hole for the back nine holes. In some embodiments, a column or row header, dependent on configuration, may be provided to show the hole numbers for improved clarity. In one configuration, back nine hole by hole score 418 may be configured to be edited via the group scorecard 304 of the management tool 300 by entering an integer or removing a score from a hole score field.
Score in 419 may present a stroke total for the scores entered on the back nine if completed. In one configuration, score in 419 may not be directly edited via the group scorecard 304 of the score management tool 300.
Stroke total 420 may present a stroke total for the round. In one example, the stroke total 420 may be displayed only when score out 417 and score in 419 have been populated with data. In one configuration, score total 420 may not be directly edited via the group scorecard 304 of the score management tool 300.
Strokes official 421 may present the strokes received for the team player on all holes that are flagged as official. In one configuration, this element can be edited by the user to signify that no more edits will be conducted for any strokes on any holes for the team player.
FIG. 5 illustrates an example interface 508 of the team player stroke detail 305 of the score management tool 300 configured to interface a user with the operations thereof. The interface may be presented in or accessible via interaction with the team player stroke detail 305 element of the respective presentation block view to view stroke detail of a team player in the group. Elements of the team player stroke detail 305 may be displayed. In operation of the team player stroke detail 305 element a user may be enabled to edit various elements. In some embodiments, selecting a team player in the group scorecard 304 or all groups on holes presentation 306 populates the interface of the team player stroke detail 305 with the respective data elements of the selected group.
When selecting a team player for presentation and/or stroke editing with the team player stroke detail 305, the hole graphic representation 308 may default to display a course view, a current hole, next hole, first hole completed, last hole completed, or full course view. In one embodiment, selection of a particular hole from the group scorecard 304, e.g., by selecting a hole from the front nine hole by hole 416 or front nine hole by hole 418 (FIG. 4 ) data element views, causes the team player stroke detail 305 to present the stroke detail for the team player for the particular hole. Thus, the score management tool 300 may be configured to enable a user to selectively view strokes by hole with the group scorecard 304 or stroke detail for a hole via interaction with the team player stroke detail 305.
In one example, viewing stroke detail for a team player with respect to a hole via team player stroke detail 305 causes the hole graphic representation 308 to present a representation of the hole. The graphic may be oriented from left to right with the tee location being on the left side and the green on the right side. As noted above, functionalities such as zooming into and out of the graphic may be provided. In one example, a quick zoom operator may be provided to allow a user to quickly zoom to various areas of the hole, such as tee box, fairway, hazards, green area, or to a particular selected shot. The functionalities may also include moving the graphic to change the longitude and latitude of the view within a static viewing area, e.g., within any zoom value. Yardage distances may also be displayed with respect to the set positions of the tees and pins. Other yardages may be selectably presented in or relative to the graphic as described above.
The data elements of the team player stroke detail 305 may include various informationals and scoring data elements such as one or more of team player name 522, stroke number 523, strokes accessed 524, stroke event 525, time stamp 526, stroke type 527, location 528, club 529, provisional 530, or in the hole 531. The data elements may correspond to those collected by tracking system 11, such data entered by walking scores (e.g., associated with companion scoring system 12), automated soring system 13, predictive location systems (e.g., shot prediction system 14), or other tracking systems, such as manual scoring systems 15. As noted above, these data elements may be received score management tool 300 for review and editing, as necessary.
Team player name 522 may include a list of all team players in a group. For example, selecting a group from the all groups on holes presentation 306 or the group scorecard 304 may cause the team player name 522 to populate with the team players of the group. The presentation may display data with respect to a single team player, which may be defaulted to any team player, such as the last team player with a recorded stroke event or to have completed a hole, the first team player in the predefined order of teeing off, or the like. In one configuration, the team player name 522 may not be edited via the team player stoke detail 305.
Stroke number 523 may correspond to a stroke received. In one configuration, the stroke number 523 is editable via the team player stoke detail 305, allowing a user to enter an integer.
Strokes accessed 524 may correspond to a number of strokes that will count towards the hole score for a team player on that stroke received. In one configuration, the stroke accessed 524 is editable via the team player stoke detail 305, e.g., allowing a user to enter an integer.
In one embodiment, a user may create a stroke before or after any other stroke. If a stroke is created, the score management tool 300 may be configured to automatically set the stroke number as the number after the previous stroke. If a stroke is created between two other strokes, the other strokes following the created stroke may be automatically renumbered, starting from the stroke created. The score management tool 300 may edit the timestamp 526 to be set to a time either after the previous stroke or a time before the proceeding stroke. In one example, when a stroke is created, the default strokes accessed are one.
In one embodiment a user may delete a stroke using the score management tool 300. If a stroke is deleted, the score management tool 300 may be configured to automatically renumber the remaining strokes in sequential order. If a stroke is deleted and it is not the stroke within the hole 531 being flagged but rather a stroke where the “in the hole” flag is available, the score management tool 300 may recalculate the score with the new sum of strokes accessed. If the stroke with the “in the hole” flag is deleted, the score management tool 300 may be configured to clear the score calculated. As described below, the “in the hole” flag may be set or removed by the user. Following deletion of a stroke including the “in the hole” flag, the user may set the “in the hole” flag for another stroke from which a revised score is calculated by the score management tool 300.
Stroke event 525 may correspond to the latest stroke event received. Stroke event 525 may enable a user to identify a stroke event. Thus, in one configuration, the stroke event 525 is editable via the team player stroke detail 305. Editable options may be provided and may include one or more event types selected from club selection, addressing the ball, shot hit, preliminary, final or in the hole.
Time stamp 526 may correspond to that of a stroke event 525, such as the latest stroke event 525. In one configuration, the time stamp is editable via the team player stoke detail 305, allowing a user to edit the field in a format of a time and day entry.
Stroke type 527 may correspond to a stroke type identifier, such as stroke, penalty, or drop. In one configuration, stroke type 527 is editable by the score management tool 300 to change or add a stroke type from a list. In one example, interacting with stroke type 527 causes a dropdown to appear including a list of available stroke types enabling the user to select one of the stroke types to set. In various embodiments, the score management tool 300 may automatically apply various rules to edits of stroke type. For example, if a stroke type created is “drop”, the strokes accessed 524 may be zero. If a stroke type created is “drop”, the stroke number 523 may be the same as the previous stroke or penalty type. If a stroke type created is “penalty”, the strokes accessed 524 may be defaulted to one. If a stroke type created is “penalty”, the stroke number 523 may increment to an amount identified for strokes accessed 524.
Location 528 may correspond to a graphic location of the stroke as determined by location methodologies described herein. For example, location may be received from a companion scoring system entry, coordinated captured by a laser range or entered manually via indicating a location of ball positions relative to a displayed map, or a coordinate determined by the location system, e.g., automated scoring system sensors or predicted shot location system. The system may translate coordinates to locations that contain the coordinate by cross-referencing the coordinate with a coordinate map of the course that defines the course locations, which may also be referred to as a coordinate zone map. In one configuration, location 528 is editable to change a location from an available list of location descriptions for the golf course being played, e.g., tee box, fairway, rough, first cut, hazard, water, out of bounds, green, or the like. In one example, interacting with the location data element may cause a dropdown to appear including a list of available locations for the golf course that may be set for location.
Provisional 530 may be used to identify if a stroke is a provisional or not. In one configuration, the provisional field is editable with value options of “yes” or “no” with respect to if the stroke is a provisional stroke.
In the hole 531 may be used to identify if the specified stroke resulted with the ball in the hole or not. In one configuration, a user may set or remove a flag if the stroke is considered to be in the hole. The score management tool 300 may automatically apply various rules to “in the hole” flags. For example, if the last stroke with the highest stroke number is flagged “in the hole”, a score may be calculated and stored based on the sum of all strokes accessed. If a stroke that is not the last stroke with the highest stroke number is flagged “in the hole”, that stroke is set as the highest stroke number and all other strokes may be renumbered in sequential order.
FIG. 6 illustrates an example interface 606 of the all groups on holes presentation 306 of the score management tool 300 configured to interface a user with the operations thereof. All or a portion of the interface may be presented in the respective presentation block view or may be accessible via interaction with the all groups on holes presentation 306 therein provided. Various elements of the interface may be displayed and/or editable via operation of the all groups on holes presentation 306.
The all groups on holes presentation 306 may be configured to display a selected round, which may include displaying only the selected round. The all groups on holes presentation 306 is configured to display the groups that are currently playing a selected hole. For instance, the all groups on holes presentation 306 may display the groups that have completed the hole before the selected hole but have not been indicated as having completed the hole in the current round selected. In one configuration, none of the fields in the all groups on holes presentation 306 may be directly edited via the all groups on holes presentation 306. In one embodiment, the presentation of the all groups on holes presentation 306 may include a notification with respect to a team player's name if the team player's scorecard has been flagged as “official”, e.g., via a validation system described in more detail elsewhere herein.
The all groups on holes presentation 306 may include various data elements, such as one or more of group number 632, corresponding to a number assigned to the group; course 633, corresponding to course the group number is playing; starting hole 634, corresponding to first hole that the group started on, based the groupings for the round; tee time 635, corresponding to the starting tee time of the group; rank 636, corresponding to the projected rank of the team player during the progress of play during rounds in progress; team player name 637, corresponding to identification of the team player; total 638, corresponding to the current total par relative score for the event; today 639, corresponding to the par relative score for the round; front nine hole by hole scores 640, corresponding to a list of scores by hole for the first nine holes; score out 641, corresponding to a stroke total for the scores entered on the front nine; back nine hole by hole scores 642, corresponding to a list of scores by hole for the back nine holes; score in 643, corresponding to a stroke total for the scores entered on the back nine; or stroke total 644, corresponding to a stroke total for the round, which display when the score out 641 and the score in 643 have data.
FIG. 7 illustrates an example interface 705 of the actions panel 310 of the score management tool 300 configured to interface a user with the operations thereof. All or a portion of the interface may be presented in the respective presentation block view or may be accessible via interaction with the actions panel 310 therein provided. The actions panel 310 may include a presentation that includes notification of an action that is to be taken with respect to score management, such as verification and/or monitoring play for an identified team player and hole. Users may interface with the actions panel 310 or score management tool 300 to select a hole or group of holes to manage. As a default, a hole selected as the active hole via the active hole 307 element. The actions panel 310 may include team player name 755, group number 756 associated with the team player, and hole number 756 that corresponds to an action message 753. A user may utilize a flag option to flag an action as being completed to remove the action message 753 from the presentation. Multiple action messages 753 may be presented. For instance, action messages 753 may be presented in a scrollable format allowing a user to scroll through all actions in the action panel 310, as necessary. In one embodiment, the action panel 310 elements are not editable by the user.
In various embodiments, action messages 753 may be generated for various scenarios related to scoring and location tracking data received from various scoring systems, such as any of those described herein. For example, an action message 753 may be presented that relates to a ball position associated with a shot. For example, an action message 753 may be presented with respect to a predicted ball position on the hole associated with a stroke, such as water, out of bounds, native area, trees, off map, provisional, drop, or penalty. Action messages 753 may be generated when data from one or more scoring systems creates a stroke without a ball position coordinate for the shot. Thus, when a stroke is created an action message 753 an associated action message 753 may be generated when the stroke is missing a coordinate. Action messages 753 may be generated when a distance for a stroke is above a predetermined distance, e.g., above 500 yards. In some embodiments, the predetermined distance may consider the location the shot was taken, which may also include the hole. For instance, a measured shot distance more than a predetermined distance, such as 150 yards, of the stroke's shot to pin distance generate an action. Action messages 753 may be generated when multiple penalties in a row are received with respect to a team player. Action messages 753 may be generated when multiple drops in a row are received with respect to a team player. In any of the above or another embodiment, action messages 753 may be generated for a hole when scoring systems or related scoring system equipment are offline. For example, action messages 753 may be generated when ball and/or player tracking sensors such as cameras, radar, or lasers are offline. Action messages 753 may be generated when a scoreboard or switch is offline. The actions panel 310 may be configured to present any desired action messages 753, for example, action messages 753 may be defined to include one or more of team player out of sync with strokes of the other team players in their group; a drop is present without a penalty evident in a team player's stroke trail; stroke coordinates are not closer to the pin location than the previous stroke's coordinates; more than a predefined time period between strokes for a team player; multiple strokes contain a location from the tee absent penalty; non-typical score for a team player, such as double bogies or worst and eagles and better; elapsed of a predefined time period and a stroke has not received coordinates; driving distance is out of range of a normal distance on a par 4 and 5, such as less than 180 yards and longer than 380 yards; a stroke was flagged as in the hole that had a distance greater than 30 yards; pin has not been set and a stroke for a team player has been received on that hole; or tee has not been set and a stroke for a team player has been received on that hole.
As introduced above, the score management tool 300 may be configured to enable connections to be created between blocks and/or data elements therein. For example, when selecting an element in one block, connections may be established for other blocks. In a further example, the other blocks in which connections are established may be updated with an appropriate presentation. For instance, when selecting an element or otherwise interacting, e.g., making a selection, in one block view or otherwise with respect to an associated element, a connection is established for one or more other blocks to thereby update the appropriate presentation in the respective blocks.
The score management tool 300 may be configured to apply connection rules with respect to the all groups on holes presentation 309. In one example, selecting a team player's name 637 causes one or more of the group scorecard 304 to present the group the team player is in; the hole graphic representation 308 to present the current hole the team player has not completed; the team player stroke detail 305 to present the strokes received on the current hole the team player has not completed; or the actions panel 310 to present all action messages 753 for the team player selected on the selected hole. In the above or another example, selecting a group number 632 may cause one or more of the group scorecard 304 to present the group selected; the hole graphic representation 308 to present the current hole and default to the top team player in the group and the current hole the team player has not completed; the team player stroke detail 305 to display the strokes received on the current hole the top team player in the group has not completed; or the actions panel 310 to present all action messages 753 for the group for the active hole 307.
In any one of the above embodiments or another embodiment, interaction with the group scorecard 304 may cause connections with one or more other elements of the score management tool 300. For example, selecting a team player's name 411 may cause one or more of the hole graphic representation 308 to present the current coordinates of the team player selected or the team player stroke detail 305 to present the strokes received on the current hole the team player has not completed. In one embodiment, the hole the selected team player has not completed may be set as active. In any of the above or another embodiment, the actions panel 310 may present all action messages 753 for the team player selected on the active hole or the all groups on holes presentation 306 to present the group or team player at the top of the presentation. Selecting a hole of a team player, e.g., via hole by hole scores 416, 418, may cause the hole graphic representation 308 to present the associated team player and hole selected; the team player stroke detail 305 to present the strokes received on the hole and team player selected; the actions panel 310 to present all the action messages 753 for that hole and team player, including any action messages that have been flagged as reviewed; or the all groups on holes presentation to display the group or team player at the top of the presentation.
In any one of the above embodiments or another embodiment, interaction with team player stroke detail 305 may cause connections with one or more other elements of the score management tool 300. For example, selecting a stroke 523 may cause a location coordinate in the hole graphics representation 308 to be presented if a coordinate for the stroke is present.
In any one of the above embodiments or another embodiment, interaction with the hole graphic representation 308 may cause connections with one or more other elements of the score management tool 300. For example, selecting a location coordinate that is assigned to a stroke may cause the stroke selected in the team player stroke detail 305 to be highlighted.
In any of the above embodiments or another embodiment, interaction with the actions panel 310 may cause the group scorecard 304 to update based on the team player 755 and group 767 associated with the action message 753 interacted with. The hole graphic representation 308 and team player stroke detail 305 may also be updated based on the team player identified in the selected action message 753.
In one example, the scoring module 20 components may be powered on and connected to a network, such as a Wi-Fi, to connect the score management device 202 and location device 208. The location device 208 may begin receiving correction signals from the GNSS base station antenna. The score management device may also be connected to the object location, e.g., via Bluetooth communication protocol. Using the user interface, the user may select the appropriate tournament event via the event selector 301, round via the round selector 302, course via the course selector 303, and active hole 307 corresponding to the hole the scoring module 20 is currently positioned. This may cause the display to present a graphic of the hole in the hole graphic 308 presentation of the score management tool 300.
As scoring data is being collected, the scoring module 20 may be configured with an ability to make any modifications necessary and add missing data as appropriate. For instance, the scoring module 20 may be configured to provide access to scoring data in real time to allow users to one or more of verify all or a portion of the scoring data or make modifications to existing data or enter missing data based on their own visual observations. For example, the score management application 204 may enable users to review hit from locations, ball to locations, player, and stroke count and verify or modify, as necessary. For location scoring data, users may collect ball locations with the object detection device 210 or by indicating locations on the hole graphic presentation 308 for modification, e.g., replacement or entry for missing location data.
In some embodiments, the score management application 204 may configured the scoring module 20 to analyze scoring data to identify anomalies. For example, the score management application 204 include predefined rules that when executed identify or assist a user of the scoring module 20 in identification of anomalies in the scoring data that should be reviewed. The rules may include triggering notifications comprising action messages 753 directed to the user that specific scoring data needs to be reviewed, modified, or entered when anomalies are present. As described above, action messages 753 may populate an actions panel 310 to provide the user information regarding a type of anomaly in the data, a player the anomaly relates to, a stroke the anomaly relates to, a hole the anomaly relates to, or combination thereof, allowing the user to address the anomaly.
In various embodiments, and with further reference to FIG. 8A, a shot hit signal may be received by the scoring module 20. The shot hit signal may be triggered by an action of the tracking system 11 or, in one configuration, entered by a user of the score management device 202. For example, a shot hit signal may be triggered by a shot hit entry by a scorer into a companion device 122 of a companion scoring system 12 as described above. This event scoring data may be directly or indirectly transmitted to the score management device 202. The indication may cause, via execution of the score management application 204, generation of a shot indication 80 on the hole graphic representation 308 on the display of the score management device 202. In one example, the shot hit indication 80 may depict a shot from location 81. In this or another example, the shot hit indication 81 may depict a shot from location 81 and a line 82 extending from the shot hit location 81 to the pin 83. In some embodiments, the shot hit indication may also include a distance to the pin, an indication of the location of the scoring module 20 relative to the hole, or both.
As location data for the shot is collected by the one or more tracking systems, the shot locations may be plotted at corresponding locations on the hole graphic presentation 308. For example, as location data corresponding to the shot is received from the tracking system 11, the locations may be plotted in the hole graphic presentation 308. In one example, an indication of the source of the location data corresponding to each plot is also displayed. The source indication may be provided at the plot, e.g., with a distinguishable source symbol, plots may be color coded by source, plots may be connected by different source indicating line styles to the shot hit from location, or otherwise. In the example shown in FIG. 8B, shot locations collected by a shot prediction system 14, camera device 134 of an automated scoring system 12, a manual scoring system 15 set by personnel using a camera device 134, and the scoring module 20 via the object detection device 208, such as a laser rangefinder, or by plotting the shot location on the hole graphic representation 308, e.g., via interfacing with a touchscreen of the user interface 206. The plots include source indications to distinguish the sources, wherein the plot of the coordinates provided by the shot prediction system 14 is indicated by a “P”, the plot of the coordinates provided by the camera device 134 of the automated scoring system 12 is indicated by a “C”, the plot of the coordinates provided by the manual scoring system 15 is indicated by an “M”, and the plot of the coordinates provided by the scoring module 20 are indicated by an “S”. In some embodiments, the symbols may be further distinguished by color. Using the score management device 202 to interface with the score management operations provided by execution of the score management application 204, the user may select the location to be used as the final location and save the shot. This may update scores and related data in the score management tool 300, cause the finalizes shot data to be transmitted to the data management system 16, or both. In some embodiments, the hole graphic representation 308 may also provide an indication of the player associated with the shot hit, a stroke count, or both.
In one embodiment, when a player hits a shot, the score management application 204 may configure the score management device 202 to provide the shot hit indication 80. When a shot prediction system 14 is used, the location predictions may be imported into the scoring module 20 and be available for presentation on the hole graphic representation 308. The user may observe the shot plot and if it is determined to be good, the user may save the shot. As described above, the score management application 204 may configure the score management device 202 to provide the user an option to cancel the shot and manually create a shot using the object detection device 208 or plotting the shot location on the hole graphic representation 308 to set a final location. When plots from other or additional tracking systems 11 are present, the score management application 204 may similarly configure the score management device 202 to provide the user the option to save one of the location coordinates to set as final or cancel or otherwise manually create the shot location using the object detection device 208 or plotting the shot location on the hole graphic representation 308 and set as final. As described above the score management application 204 may configure the score management device 202 to enable user to one or more of enter shots (strokes), drops, or penalties, alter timestamps set by shot hit or other event related scoring data, correct shot from locations set by the tracking system 11, delete shots (strokes).
As described above, in some embodiments, the actions panel 310 may present action messages such as missing location data for a shot or one or more tracking systems of the tracking system 11 or sensors thereof being offline. In such instances, the score management tool 300 may be used to enter the missing data. For example, when shot location data is missing, the scoring module 20 may be used to collect the missing shot location data corresponding to the location the ball rests on the hole using the object detection device 208, such as a laser rangefinder. In another example, the user may collect the shot location data by plotting the shot location on the hole graphic representation 308, e.g., via interfacing with a touchscreen of the user interface 206. In another example, the user may collect the shot location data by positioning over the ball and triggering determination of the location of the location device 210. In one embodiment, the user may have an option to either collect the location data with the object detection device 208 or plot the location on the hole graphic representation 308, e.g., by interfacing with a touchscreen. The hole graphic representation 308 may associate a source identification with respect to the plot, which may be as described above. In one embodiment, the user may collect the shot location data on all shots, even if one or more tracking systems of the tracking system 11 also collect the shot location data.
In various embodiments, the program instructions provided by the score management application 204 configure the scoring module 20 to operate in conjunction with one or more tracking systems of the tracking system 11, such as the ones described herein and with respect to FIGS. 1A, 1B, & 8B. In one example operation, as a group arrives to the active hole, the group may populate the score management tool 300 blocks. As a team player addresses the ball, a scorer of a companion scoring system 12 may input this information into a companion device 122, which may execute a companion device application. This information may be received by the score management device 202 and displayed by the score management tool 300. When the player hits the ball, a scorer may enter this information into a companion device, and this information may be received by the score management device 202 and also displayed by the score management tool 300. For example, when a player is addressing a ball on the hole and/or the ball is hit, this information may be entered by provided by a tracking system 11 and presented in the hole graphic representation 308. In one configuration, once a stroke has been entered by the scorer, the score management application 204 may configure the score management device 202 to enable user to select the “Event” (e.g., stroke number), which, depending on configuration, may be from one or more of the group scorecard 304, player stroke detail 305, all groups on holes presentation 306, or hole graphic representation 308. This action may initiate location data collection using the object detection device 210 or hole graphic representation 308 to allow the user to capture the ball location. As noted above, the hole graphic representation 308 may include an icon or other symbol or indication of where the scoring module 20 is located based on location determination of the location device 208. Once a shot is taken, a dotted line may be displayed on the hole graphic representation 308 from the location of where the shot was taken to the pin. A distance to the pin may be provided. If the user determines the shot is good, the user may interface with score management tool 300 via the score management device 202 to save the shot. The user may also be provided with the option to manually create a shot or cancel a shot. The score management tool 300 may give the user the option to cancel or set shots collected by the available scoring systems 11 or the scoring module 20. Additionally, the score management application 204 may configure the score management device 202 to enable the user to manage other scoring data such as enter shots, drops, penalties, alter timestamps, correct from locations, and delete shots. In some embodiments, the score management tool 300 may include a player identification on the hole graphic representation 308 that identifies the player associated with the current shot.
In one embodiment, the scoring module 20 manages scoring data collected by an automated scoring system 13 including camera devices 134 positioned around holes configured to track ball locations of shots, a shot prediction system 12 including one or more of radar devices 132, camera devices 14, or laser devices configured to collect ball flight parameters of shots and generate predicted resting location, a manual scoring system 15 including camera devices 134 wherein producers set shot locations from the camera device images.
Scoring modules 20 may work with production personnel. For example, personnel utilizing scoring modules 20 may communicate with producers over radio. Scoring modules 20 may be used to collect shot location data of all shots in the fairway, regardless of collection by sensors, such as camera devices 134, to expand or fill gaps in collection of shot location data. In some embodiments, the scoring modules 20 may be used to monitor data input by scorers of a companion scoring system 12 and relay necessary information to producers regarding scorer mistakes and abnormal situations, e.g., via score management operations of the management device 202 configured for monitoring scoring data.
In some embodiments, scoring modules 20 may work closely with mobile spotters. Mobile spotters may assist users of scoring modules 20 with directional information, flagging balls the users cannot see due to deep rough, acting as a reference point for balls that are not in view, or relaying correct from locations to make sure all scoring module 20 and tracking system sensors, such as camera devices 134, entries are accurate. In some instances, mobile spotters work in teams, such as teams of 3 on par 3 holes, teams of 5 on par 4 holes, and teams of 7 on par 5 holes.
The present disclosure is intended to be read to encompass one or more systems or components thereof comprising one or more processors and one or more tangible, non-transitory computer-readable media comprising program instructions stored therein, wherein the program instructions are executable by the one or more processors such that the system is configured to perform the operations described herein with respect to any of the various embodiments, examples, configurations, or implementations of the golf data collection and management system 10 or components thereof. Such a system may comprise one or more computing devices, apparatuses, machines, or the like. As an example, the component devices of the scoring module 20, e.g., score management device 202, location device 210, or object detection device 208, may include one or more processors and memories storing program instructions that when executed by the one or more processors perform the score management operations described herein with respect to the component devices, e.g., monitoring scoring data, validating scoring data, collecting location data with respect to the scoring module 20 or objects, among others. The one or more processors may share processing operations described herein with respect to the scoring module 20 or component devices thereof. The one or more processors, memories, or program instructions may be local or distributed among the component devices or, otherwise, the scoring module 20. Thus, as an example, the score management device 202 may include a processor that executes program instructions that perform one or more score management operations, or portion thereof, of the object detection device 208, e.g., coordinate determination using a measured distance, or the location device 210, e.g., receiving or processing location data received from location services with respect to location of the location device and determine a location in a desired coordinate system. The score management device 202 may include memory that stores all or a portion of such program instructions.
While the present disclosure may reference particular applications executed on one or more electronic devices, it is to be understood that such applications, including any application services, may be provided within a single application, program, or platform, or may be divided, virtualized, distributed, or combined into or among any number of executable platforms and resources. Applications may refer to program instructions organized in any manner suitable to perform the operations described herein and that need not be limited to discrete units of code or other software package or program.
At least a portion of the methodologies and techniques described with respect to the exemplary embodiments may incorporate a machine, such as, but not limited to a computer system or other computing device within which a set of instructions, when executed, may cause the machine to perform any one or more of the methodologies or functions discussed above. The machine may be configured to facilitate various operations conducted by the systems. For example, the machine may be configured to, but is not limited to, assist the systems by providing processing power to assist with processing loads experienced in the systems, by providing storage capacity for storing instructions or data traversing the systems, or by assisting with any other operations conducted by or within the systems. As another example, the computer system may assist with enhancing accuracy coordinates and information gleaned therefrom in a reduced infrastructure environment by incorporating rules such as error and/or warning rules that automatically identify potential discrepancies.
In some embodiments, the machine may operate as a standalone device. In some embodiments, the machine may be connected via a communications network to perform and/or assist with system operations, such as, but not limited to, receiving requests, translating coordinates, calculating distances, analyzing map data, simulating shots, predicting coordinates, collecting sensor data, identifying players, detecting balls, transmitting responses, communicating with the various databases, associated system servers, any other system, application, API, program, and/or device, or any combination thereof. The machine may be connected with any component in the systems. In a networked deployment, the machine may operate in the capacity of a server or a client user machine in a server-client user network environment, or as a peer machine in a peer-to-peer (or distributed) network environment, for example. The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
The computer system may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory and a static memory, which communicate with each other via a bus. The computer system may further include a video display unit, which may be, but is not limited to, a liquid crystal display (LCD), a flat panel, a solid state display, or a cathode ray tube (CRT). The computer system may include an input device, such as, but not limited to, a keyboard, a cursor control device, such as, but not limited to, a mouse, a disk drive unit, a signal generation device, such as, but not limited to, a speaker or remote control, and a network interface device. The disk drive unit may include a machine-readable medium on which is stored one or more sets of instructions, such as, but not limited to, software embodying any one or more of the methodologies or functions described herein, including those methods illustrated above. The instructions may also reside, completely or at least partially, within the main memory, the static memory, or within the processor, or a combination thereof, during execution thereof by the computer system. The main memory and the processor also may constitute machine-readable media.
Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Applications that may include the machine and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.
In accordance with various embodiments of the present disclosure, methods described herein are intended for operation as software programs running on a computer processor. Furthermore, software implementations can include, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
In addition to or in alternative to the various embodiments and examples of the inventive concepts provided above, further non-limiting examples of the inventive concepts described herein are provided in the below clauses.
The present disclosure contemplates a machine-readable medium containing instructions so that a device, e.g., client device, coordinate translator, connected to a communications network, another network, or a combination thereof, can send or receive data, and communicate over the communications network, another network, or a combination thereof, using the instructions. The instructions may further be transmitted or received over the communications network, another network, or a combination thereof, via the network interface device. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present disclosure. The terms “machine-readable medium,” “machine-readable device,” or “computer-readable device” shall accordingly be taken to include, but not be limited to: memory devices, solid-state memories such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories; magneto-optical or optical medium such as a disk or tape; or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. The “machine-readable medium,” “machine-readable device,” or “computer-readable device” may be non-transitory, and, in certain embodiments, may not include a wave or signal per se. Accordingly, the disclosure is considered to include any one or more of a machine-readable medium or a distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.
The illustrations of arrangements described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Other arrangements may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Figures are also merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Thus, although specific arrangements have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific arrangement shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments and arrangements of the invention. Combinations of the above arrangements, and other arrangements not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. Therefore, it is intended that the disclosure not be limited to the particular arrangement(s) disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments and arrangements falling within the scope of the appended claims.
The foregoing is provided for purposes of illustrating, explaining, and describing embodiments of this invention. Modifications and adaptations to these embodiments will be apparent to those skilled in the art and may be made without departing from the scope or spirit of this invention. Upon reviewing the aforementioned embodiments, it would be evident to an artisan with ordinary skill in the art that said embodiments can be modified, reduced, or enhanced without departing from the scope and spirit of the claims described below.

Claims

What is claimed is:

1. A scoring module for managing golf tournament scoring data, comprising:

a score management device comprising a user interface including a display;

a location device configured to communicate with one or more location services;

an object detection device configured to detect ball locations from a location remote from the ball locations, wherein the scoring module is movable throughout a golf course during a golf event;

one or more processors;

one or more non-transitory computer readable media comprising program instructions that when executed by the one or more processors configure the scoring module to:

receive scoring data collected by one or more tracking systems during a golf tournament, wherein the scoring data comprises stroke data of players competing in the golf event and location data of golf balls hit by the players;

display the received scoring data on the display;

determine a current location of the scoring module relative to the golf course following each move using the location device; and

enable management operations with respect to the scoring data.

2. The scoring module of claim 1, wherein the program instructions further configure the scoring module to: plot location data on a hole graphic representation on the display of the score management device corresponding to a current shot of a player, wherein the location data was collected by one or more of the tracking systems.

3. The scoring module of claim 2, wherein the one or more tracking systems comprise two or more of:

a shot prediction system configured to predict ball flight and final resting positions using ball flight data collected by one or more radar devices;

an automated scoring system configured to track balls hit by players using at least a camera device employing computer vision to identify players and balls; or

a companion scoring system wherein a scorer enters stroke events into a companion device while accompanying players during play.

4. The scoring module of claim 3, wherein the program instructions further configure the scoring module to: display in the hole graphic representation source identifiers with respect to the plots that identify which tracking system is the source of the location data.

5. The scoring module of claim 2, wherein the program instructions further configure the scoring module to: provide a user option to verify location data corresponding to a location data plot or input new location data for the current shot.

6. The scoring module of claim 5, wherein the object detection device comprises a laser rangefinder and wherein the program instructions further configure the scoring module to:

determine a ball location on the golf course for input as new location data for the current shot utilizing a distance measurement captured by the laser rangefinder and the determined current location of the scoring module.

7. The scoring module of claim 6, wherein the program instructions further configure the scoring module to: with respect to input of new location data for the current shot, provide a user option to input the new ball location data via interaction with the hole graphic representation to plot the new ball location or utilization of the laser rangefinder.

8. The scoring module of claim 1, wherein the object detection device comprises a laser rangefinder and wherein the program instructions further configure the scoring module to:

determine a ball location on the golf course utilizing a distance measurement captured by the laser rangefinder and the determined current location of the scoring module.

9. The scoring module of claim 8, wherein the location device comprises a GNSS antenna, and wherein the GNSS antenna is configured to receive correction data from a GNSS antenna base station of a local location network positioned at a known location.

10. The scoring module of claim 1, wherein the program instructions further configure the scoring module to:

display a shot hit indication on the hole graphic representation when a shot is taken on a hole, wherein the shot hit indication comprises:

a line from where the shot was taken to a pin of the hole; and

a distance to the pin.

11. The scoring module of claim 1, wherein the program instructions further configure the scoring module to execute a score management tool configured to enable score management operations via interaction with the score management device comprising one or more of:

entering strokes, drops, or penalties;

altering timestamps with respect to scoring data captured by the one or more tracking systems;

correcting shot from locations set by the one or more tracking systems; or

deleting strokes collected by the one or more tracking systems.

12. The scoring module of claim 1, wherein the program instructions further configure the scoring module to: analyze the received scoring data to automatically identify anomalies; and display action messages corresponding to identified anomalies on the display for resolution.

13. The scoring module of claim 12, wherein the anomalies comprise at least one of: strokes without corresponding ball location coordinates; shot distances exceeding predetermined thresholds; multiple consecutive penalties or drops; tracking system offline conditions; non-sequential player stroke patterns within a group; multiple locations present for a particular stroke; multiple strokes present for a particular location; strokes present without corresponding locations; locations present without corresponding strokes; strokes or locations present without player identification; stroke coordinates not closer to a pin location than previous stroke coordinates; time gaps between strokes exceeding a predefined period; multiple strokes from tee location without penalties; or non-typical scores for a player.

14. The scoring module of claim 12, wherein the program instructions further configure the scoring module to: display a hole graphic representation responsive to selection of an action message; plot available location data from the one or more tracking systems on the hole graphic representation; and enable user verification or correction of the anomalous scoring data.

15. The scoring module of claim 12, wherein the program instructions further configure the score management device to: flag reviewed anomalies as completed; store validated scoring data; and transmit resolved anomaly data to a data management system.

16. The scoring module of claim 12, wherein the program instructions further configure the score management device to: compare zone locations determined by different tracking systems; translate coordinates between coordinate systems; and generate notifications when zone and coordinate determinations are inconsistent.

17. The scoring module of claim 12, wherein the program instructions further configure the score management device to: enable resolution of anomalies comprising: collection of new location data using an object detection device; modification of existing stroke scoring data; entering missing scoring data; or validating or canceling scoring data collected by tracking systems.

18. A method of managing golf tournament scoring data, comprising:

receiving, by a score management device of a scoring module, scoring data collected by one or more tracking systems during a golf tournament, wherein the scoring data comprises stroke data of players competing on a golf course and location data of golf balls hit by the players;

displaying the received scoring data on a display of the score management device;

determining a current location of the scoring module relative to the golf course following each move of the scoring module using a location device of the scoring module;

enabling management operations with respect to the scoring data.

19. The method of claim 18, further comprising:

plotting location data on a hole graphic representation on the display of the score management device corresponding to a current shot of a player, wherein the location data was collected by one or more of the tracking systems, the one or more tracking systems comprise two or more of:

a companion scoring system wherein a scorer enters stroke events into a companion device while accompanying players during play;

displaying in the hole graphic representation source identifiers with respect to the plots that identify which tracking system is the source of the location data;

providing a user option to verify location data corresponding to a location data plot or input new location data for the current shot;

determining a ball location on the golf course for input as new location data for the current shot utilizing a distance measurement captured by an object detection device of the scoring module and the determined current location of the scoring module.

20. The method of claim 18, further comprising:

analyzing the received scoring data to automatically identify anomalies;

displaying action messages corresponding to identified anomalies on the display for resolution;

plotting available location data from the one or more tracking systems in a hole graphic representation; and

enabling resolution of anomalies comprising:

collection of new location data using an object detection device;

modification of existing scoring data;

entering missing scoring data; or

validating or canceling scoring data collected by tracking systems,

wherein the anomalies comprise at least one of:

strokes without corresponding ball location coordinates; shot distances exceeding predetermined thresholds; multiple consecutive penalties or drops; tracking system offline conditions; non-sequential player stroke patterns within a group; multiple locations present for a particular stroke; multiple strokes present for a particular location; strokes present without corresponding locations; locations present without corresponding strokes; strokes or locations present without player identification; stroke coordinates not closer to a pin location than previous stroke coordinates; time gaps between strokes exceeding a predefined period; multiple strokes from tee location without penalties; or non-typical scores for a player.