Match Distance Covered km Calculator
Sum actual nonoverlapping tracked soccer segments, exposing missing tracking rather than extrapolating whole-match distance; no GPS processing/geodesy.
Description
Tracked match distance should preserve missing segment evidence.
Tracked match distance should preserve missing segment evidence. Unknown segments are excluded rather than extrapolated.1
The returned values include Known tracked match distance km, Unknown tracking segment count. The How section below explains the calculation, input rules and interpretation.
When to use Match Distance Covered km Calculator
Use Match Distance Covered km Calculator when you need to evaluate the supplied records under the calculation and evidence rules below. No GPS/geodesy processing or full-match extrapolation is supplied.
Prepare the observed race, match or training records and the stated units. Supply independently verified rule editions, calibration tables and targets where requested.
How to use Match Distance Covered km Calculator and understand its results
- Prepare the observed race, match or training records and the stated units. Supply independently verified rule editions, calibration tables and targets where requested.
- Enter observedNonoverlappingMatchSegmentMeters, segmentTrackingEvidenceFlags using the field table and calculation rules, then run the tool.
- Read knownTrackedMatchDistanceKm, unknownTrackingSegmentCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| observedNonoverlappingMatchSegmentMeters | Observed nonoverlapping match segment meters | list of number | Required |
| segmentTrackingEvidenceFlags | Segment tracking evidence flags | list of number | Required |
Enter aligned nonempty nonnegative nonoverlapping segment meters and binary evidence flags. Return known kilometers and unknown segment count.
knownKm=sum(distance where evidence1)/1000 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| knownTrackedMatchDistanceKm | Known tracked match distance km | number |
| unknownTrackingSegmentCount | Unknown tracking segment count | number |
{
"input": {
"observedNonoverlappingMatchSegmentMeters": [
1000,
1500,
500
],
"segmentTrackingEvidenceFlags": [
1,
0,
1
]
},
"output": {
"knownTrackedMatchDistanceKm": 1.5,
"unknownTrackingSegmentCount": 1
}
}Limitations and assumptions
No GPS/geodesy processing or full-match extrapolation is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Middle-Third Pass Completion %: Middle-third pass completion pools opportunities across records. Match percentages should not be averaged without exposure weights. For a complementary task, use Break Shot Ball Speed Estimate: Video travel windows estimate mean ball speed. Frame count describes the observation interval rather than impact timing.
References
-
Match Distance Covered km Calculator — tool.io
Similar or alternative tools
- Middle-Third Pass Completion %
Middle-third pass completion pools opportunities across records. Match percentages should not be averaged without exposure weights.
- Break Shot Ball Speed Estimate
Video travel windows estimate mean ball speed. Frame count describes the observation interval rather than impact timing.