Field catalog
Every dotted data name the standard defines: what it carries, in which units, and where it is specified. Filtering is instant and the URL keeps your query, so a link to a search is a link you can send somebody.
This is a dictionary, not a to-do list
Four fields make a launch monitor conformant. ball.speed_mps, ball.launch_angle_deg, ball.launch_direction_deg and ball.spin_rpm. A simulator needs five. An accessory can be one.
Everything else on this page exists so that a device which measures something unusual has a standard name for it — a pressure mat, a putting sensor, a moving lie platform. Send what you measure and omit the rest. Nothing here is required because it is listed, and no device is expected to implement a whole namespace.
204 fields in the catalog
ball. How it left the face and where it went.#
The backspin component of the ball's spin.
Distance the ball flew before its first contact with the ground.
Side movement perpendicular to the launch direction, as distinct from lateral offset measured against the target line.
Angle at which the ball first returns to launch elevation, the same quantity as trajectory.descent_angle_deg.
Vertical launch angle of the ball relative to the ground.
Horizontal launch direction relative to the target line, positive to the right.
Distance the ball traveled along the ground after landing.
Lateral offset from the target line at the point of first landing, positive to the right.
The sidespin component, carried only where a device measures the spin components directly.
Lateral offset from the target line where the ball came to rest, positive to the right.
Ball speed divided by club head speed, a derived rather than measured quantity.
The physical specification of the ball that was struck — manufacturer, model, construction and condition.
Ball speed immediately after impact.
Tilt of the ball's spin axis, positive tilted right; a geometric quantity, never a shot-shape label.
Total spin rate of the ball off the face.
Which physical ball this is, from an embedded marker, carried verbatim. Nothing on the market reports it yet.
Distance from the ball's start to where it came to rest, carry and roll together.
club. What was swung, and what it was doing at impact.#
Vertical angle of the club head's approach into the ball, positive upward.
How fast the club face was rotating through impact.
Which club was used, carrying no confidence of its own — how it was determined lives in club.identification.
Lie angle actually delivered at impact, positive toe up.
Loft actually delivered at impact, as opposed to the loft stamped on the club.
Orientation of the club face at impact relative to the target line, positive open.
Face angle relative to the swing path, positive when the face is open to the path. Carried directly because it is the strongest predictor of curvature.
How club_id was arrived at — method, confidence, asserting participant and any disagreement between sources.
Where the club reached the bottom of its arc relative to the ball, positive meaning after the ball.
Direction of the club head path through impact relative to the target line, positive in-to-out.
The physical specification of the club that was swung — head, shaft and grip details as manufactured or fitted.
Club head speed at the moment of impact specifically, for devices that distinguish it from peak speed.
Club head speed.
Angle between the dynamic loft and the angle of attack, which largely determines how much spin the impact generates.
Impact position across the face from its center, positive toward the toe.
Impact position up the face from its center, positive above center.
Direction of the club head's travel through impact measured on the swing plane, positive in-to-out.
Horizontal orientation of the swing plane.
Vertical angle of the club head path relative to the ground, reported separately from the horizontal swing plane.
Which PHYSICAL club this is — an RFID or NFC serial, or any other marking unique to the one club — carried verbatim and never parsed. The specification is resolved from it afterwards.
The vendor's own opaque club identifier, passed through verbatim and unmapped.
origin. The state the shot started from.#
Distance from the ball to the pin at address.
Elevation of the target relative to the ball, positive meaning the pin is above the player. Part of the state of the shot, not a modifier of it.
Cross-slope of the lie, positive when the ground rises to the player's right regardless of handedness.
Slope of the lie along the line of play, positive uphill toward the target.
What the ball was sitting on before the stroke, from the registered surface vocabulary such as tee, fairway, rough, sand_bunker or green.
Absolute elevation of the ball's position in course coordinates, so origin and outcome elevations are directly comparable.
Course-local coordinates of the ball before the stroke, where the simulator exposes them.
The club the simulator suggested, which is a suggestion and never evidence of what was actually swung.
Flag that the player could not take a normal stance, recorded because it explains poor contact that would otherwise look like a bad swing.
outcome. Where it finished, and what it cost.#
Who added this stroke — the player, an operator or an official — since a human adjusting a score is exactly what an audit trail exists to capture.
Whether this stroke entered the score. Everything is recorded; only some things count.
Elevation of the resting position relative to the origin, positive meaning the ball finished above where it started.
Distance from the pin where the ball came to rest, which together with the origin distance is the whole of what a strokes-gained calculation needs.
Absolute elevation of the ball's resting position.
What the ball came to rest on, from the same registered surface vocabulary as origin.lie_surface.
Course-local coordinates of where the ball came to rest.
Whether the ball went in, which ends the hole regardless of what any other field says.
Free text about the outcome for a human reader. Never parsed and never load-bearing.
Why a penalty was assessed, coded so scoring and player rating can treat the categories differently.
Penalty strokes added as a result of this stroke.
For a drop, where the ball was before it was moved; the origin block carries where it was then played from.
The coded rule under which a penalty or adjustment was applied.
What kind of stroke this record represents. Kinds other than stroke, whiff, provisional, mulligan and practice involve no swing and carry no ball, club or trajectory data.
How many strokes this record adds to the score, normally 1, allowing a conceded two-putt to be reported as one record adding 2.
trajectory. The path between those two, as events.#
Peak height of the ball above the origin, not above the ground beneath it.
Angle at which the ball came down, which determines how much a shot will stop.
The ordered sequence of things that happened to the ball, whose minimum conformant form is launch, landing and rest.
Time from launch to first landing.
Where the ball finished relative to where it started, which should agree with outcome.elevation_change_m.
round. The round in progress: who is playing, whose turn, which hole.#
Engine-provided strokes received per slot for the course, tee set and format about to be played, with a completeness gate and the source of the numbers.
Which hole is being played, as one object: number, par, length, and the course it belongs to. The engine spreads it across every shot record it composes.
Who is at the ball now, given as a slot and a display label. Provided by the simulator and requestable by any participant.
Who the engine attributed the last stroke to, so a device whose data completes late can still be attributed correctly after the group has rotated.
Every player in the round as slot, display label and optional check-in reference, supplied by the simulator so displays can name the group and a scanning member can pick which name is theirs.
What the simulator has in force for the round: its assists, each classified by what it does to the evidence, its conditions, course and swing inputs. Simulator-provided and standing; in an event the engine compares it with the rules package.
player. The person at the ball.#
The handedness a launch monitor observed — which side of the ball armed, or the swing itself — and therefore measured rather than configured.
The handedness the simulator was configured for, which decides how the shot was rendered and where the ball was teed.
status. A participant reporting on its own condition.#
The launch monitor's own report that it can see the ball and record a stroke now.
The simulator's own report that the round can accept a stroke now.
bay. This installation: check-in, claim, and who has scanned in.#
The members who have scanned in at this bay and not yet left, each with an opaque check-in reference, display label and expiry. Published by the engine before any round exists.
The engine-minted check-in payload for this bay — QR payload, short code, expiry and whether it rotates — so a device with a screen can render it instead of sending players to a wall placard.
The payload an operator scans to claim this bay and vouch for its equipment. A different code for a different act from the check-in code, and the two must never be confused.
course. The course being played, by reference rather than by value.#
Opaque identifier for the course this stroke was played on.
Content hash of the course file, which is the course's real identity where name and version are only labels. It is what answers whether two bays are playing the same golf course.
True only when the engine computed the course hash itself; false means it is relaying the simulator's claim.
The single transform mapping this course file onto the real world — datum, epoch, the real-world location of local (0,0), the bearing of the local +y axis and the accuracy of the transform — declared once rather than repeated per position.
Length of this hole from the tees in play.
Par for this hole as the course file states it.
Course name as the simulator presents it, a label for humans rather than an identity.
Where the hole was actually cut for this round, so two rounds on the same course file with different cuts can be told apart.
The facility's own human-readable label for the day's pin setup, a companion to pin_position and never a substitute for it.
Where the course file came from — the simulator's own library, a marketplace, a community pack.
Which tees were played, which sets both the yardage and the rating the score is judged against.
The vendor's own identifier for the course file, so support can name the same file the vendor names.
Course file version, since a layout can be revised without being renamed.
environment. The air the shot was played in — a game setting, or real weather outdoors.#
Course altitude the flight model used, which materially changes carry.
Whether the environment values were a simulator setting or came from a real sensor, since a wind value that is a game setting and one that is the weather are not the same fact.
Ground firmness the simulator applied, on the standard coarse scale.
Green speed the simulator applied, on the stimpmeter scale.
Relative humidity the flight model used.
Barometric pressure the flight model used.
Air temperature the flight model used.
Bearing the simulated wind blows toward, 0 being north — not the meteorological from-convention.
Peak gust the simulator applied, where its model varies the wind.
Wind speed the simulator applied to this shot.
ambient. The room, not the game: what was physically measured where the player stands.#
Air density measured in the bay, or derived from the measured pressure, temperature and humidity.
Altitude of the bay itself, as measured or configured, distinct from the course altitude the simulator applied.
Temperature of the ball itself where a sensor reports it, since a cold ball travels measurably shorter.
Relative humidity physically measured in the bay.
Light level measured in the bay, which is how a bay evidences the lighting a camera-based system declares it requires.
Identifier of the device that took the ambient measurements.
Barometric pressure physically measured in the bay.
Air temperature physically measured where the player is standing, which is the field the ambient block exists for indoors.
Compass bearing the air measured in the bay is moving toward, 0 being north.
Wind speed actually measured at the bay, for outdoor and hybrid play only; indoors it should be absent rather than zero.
conditions. What a competition requires a simulator to put in force.#
Course altitude the simulator's flight model must assume, fixed by the event rather than taken from the bay's location.
Ground firmness the event requires, on the standard coarse scale.
Green speed the event requires, on the stimpmeter scale.
Whether the event's playing conditions are fixed for the whole round or specified per hole.
The same condition keys nested under hole numbers, present when mode is per_hole.
Which pin placement set the event puts in force.
Barometric pressure the simulator's flight model must assume.
Air temperature the simulator's flight model must assume.
Compass bearing the event's wind blows toward, 0 being north.
Wind speed the simulator must apply for the event.
How much the wind is permitted to vary during play, zero being a steady wind.
swing. The motion itself, where a device can see it.#
Body segment measurements captured at each named swing event.
The offset of each named moment of the swing — address, takeaway, top, transition, impact, finish — relative to impact, negative before it.
The order and timing in which body segments reached peak angular speed, and whether that order was proximal-to-distal.
The peak value of each body measurement across the swing, whenever it occurred.
Pointers to the sampled biomechanical traces for this swing, held on the bulk path rather than inlined in the latency-critical record.
Backswing time divided by downswing time.
putt. The stroke on the green, which is a different measurement problem.#
Where the putter was aimed at address relative to the target line, distinct from face angle at impact.
Duration of the backswing, from takeaway to the top of the stroke.
Total side movement of the putt from its launch direction.
Green speed inferred from this putt's roll deceleration, distinct from the configured environment.green_speed_stimp.
How far past the hole the ball would have finished at its entry speed.
Ball speed at the hole.
Duration of the forward stroke, from the top to impact.
Contact position across the putter face, positive toward the toe.
Ball speed as it leaves the putter face.
Angle of attack of the putter head, positive upward.
Putter face orientation at impact, positive open and pointing right of the target line.
Putter lie angle at impact, positive toe up.
Loft delivered at impact by the putter; negative means the ball was pressed into the green.
Path of the putter head through impact, positive in-to-out.
Launch angle of the ball off the putter face.
Share of the putt spent in true roll rather than skid.
Speed at which the ball begins rolling.
Total putter face rotation through the stroke.
Distance the ball skids or bounces before true roll begins.
Slope across the putt's line, as a percentage grade.
Slope along the putt's line as a percentage grade, positive uphill toward the hole.
How much speed the ball lost before beginning true roll.
How far the putter was taken back.
Backswing time divided by forward swing time.
Distance at which the ball begins true forward roll.
pressure. What the player did against the ground.#
Pressure measurements captured at each named swing event.
Center of pressure along the target line, positive toward the target and zero at address.
Share of the center of pressure carried on the lead foot.
Center of pressure perpendicular to the target line, positive toward the ball.
Share of the center of pressure carried on the trail foot.
Peak horizontal ground reaction force, the one that drives rotation.
Pointer to the full pressure trace held on the bulk path, of which the pressure scalars are the summary.
Width of the player's stance, measured between the feet.
Peak torque applied against the ground.
Peak vertical force as a multiple of the player's body weight, which is the comparable form.
Peak vertical ground reaction force through the swing.
platform. A moving hitting surface: what it was asked for, and what it reached.#
Pitch the lie platform actually reached, as distinct from what it was asked for.
Pitch the simulator commanded the lie platform to, positive uphill toward the target.
Roll the lie platform actually reached, as distinct from what it was asked for.
Roll the simulator commanded the lie platform to, positive meaning the surface rises to the player's right.
Whether the platform reached its commanded state before the stroke.
The surface the hitting platform actually presented, from the registered lie-surface vocabulary.
The surface the simulator asked the hitting platform to present, from the registered lie-surface vocabulary.
identification. How the club in the player’s hands was worked out.#
The stated reliability of an imaged, marker or inferred club identification; a ui_selected club has no meaningful confidence.
The record that two sources named different clubs, carrying both values rather than resolving between them.
How the club in the player's hands was identified — RFID, marker, imaging, holder absence, impact inference, bag sequence or UI selection.
Whether the player was shown the detected club and accepted it.
Which participant asserted the club, often the simulator rather than the launch monitor.
identity. What a device says it is, at handshake.#
The device's signature over its identity, capability descriptor and the engine's session nonce together, which is what prevents a descriptor being forged or replayed from another session.
The strength of key custody the device claims, from unattested through software-held, device-held and hardware-rooted.
When the device was last calibrated.
When the device's current calibration lapses.
The device's own identifier within the bay. An identifier, never a credential.
Firmware revision as the vendor names it; a device that omits it cannot be matched by a firmware-specific rule.
Hash of the firmware build the device is actually running, which is what makes an approved-software-version requirement enforceable rather than self-reported.
Hardware revision, for vendors who ship more than one under a single model name.
Model name of the device, which together with vendor is what deny rules, certificates and certified-model lists match on.
Every sensing modality present on this unit, since real devices routinely combine radar, camera and infrared technologies.
The unit's serial number. It travels to SGA for certification and audit, is not redistributed to other participants, and is what distinguishes two units that were given the same device id.
Manufacturer name of the device.
integrity. What the engine knows about how good this record is.#
Flag that the shot was queued against the previous player because the swing landed before any sample said the turn had moved.
Flag that the contributing device was not bound to this bay when it sent the record, so the data lacks proof of where it came from.
Whether every flight-critical contribution was in when the record was composed — a fact about the composition rather than about the ball.
Flag that no launch monitor measured this stroke — it was entered, conceded or reconstructed — so it counts but is not evidence of how the ball was struck.
The devices that were expected to contribute to this record and did not, named rather than merely counted.
How the correlation window ended — complete, on a deadline, declined or forced — which distinguishes a record composed because everyone answered from one composed because the engine stopped waiting.
model. The named model behind a calculated or inferred value.#
Vendor-namespaced name of the model that produced a calculated or inferred value. The model need not be published, but it must be named.
Version of the named model, so a change in results across a season can be attributed to a model change rather than to a player.
position. A point, in course-local coordinates.#
Radius within which the ball is actually expected to be, required in practice whenever the position's provenance is inferred.
The same point expressed in real-world coordinates with its datum, epoch, height reference and accuracy. Optional and additive: the local frame remains authoritative for everything the standard computes.
Course-local position across the target line, positive to the right of it.
Course-local position along the target line, positive toward the target.
Height above the reference surface.
sga. Reserved by the association.#
The pseudo-field a participant puts in its wants in order to receive notices, reusing the ordinary subscription model rather than a separate transport.