From 4a6b1572eee73a7bde888f1fcff66b81b7a030e4 Mon Sep 17 00:00:00 2001
From: Jaap van Ekris <82339657+JaapvanEkris@users.noreply.github.com>
Date: Tue, 15 Sep 2026 11:49:50 +0200
Subject: [PATCH] Improved consistency of 'HANDLE_DISTANCE_UNIFORM_M'
 calculation placement

---
 spec/FIT_STANDARD.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/spec/FIT_STANDARD.md b/spec/FIT_STANDARD.md
index 9c1e402..9c2207a 100644
--- a/spec/FIT_STANDARD.md
+++ b/spec/FIT_STANDARD.md
@@ -282,6 +282,7 @@ These fields define the X-axis interpretation for curve data on each Record:
 
 - Axis metadata fields MUST appear together on each Record containing curve data
 - For Type=TIME_UNIFORM_MS with known drive time: `InstrokeSampleInterval = drive_time_ms / (point_count - 1)`
+- For Type=HANDLE_DISTANCE_UNIFORM_M with known drive length, `InstrokeSampleInterval = DriveLength / (point_count - 1)`
 - For Type=OAR_ANGLE_UNIFORM_DEG: Domain is [Catch, Finish] angles (from fields 11-12)
 - Type=UNKNOWN indicates shape-only data (for pattern analysis, not absolute plotting)
 - Producers SHOULD strive for consistency between axis metadata and stroke scalars, but consumers SHOULD NOT enforce strict validation
@@ -299,8 +300,6 @@ Recommended curve type names and encoding (Y-axis scale in developer field descr
 
 Curve samples are **uniformly spaced** along the declared abscissa (fields 90-92). Non-uniform source data MUST be resampled before export or stored in a companion JSON file.
 
-For **HANDLE_DISTANCE_UNIFORM_M**, sample index `k` maps to handle position `k × Δm` from catch, with Δm = `DriveLength / (point_count - 1)` when drive length is known.
-
 ### 6.5 Curve Array Format
 
 Curve data MUST be encoded as **UINT16** arrays (developer fields with array size > 1):