Time, Distance and Input Errors
Find accepted time and distance formats, input limits and fixes for common errors. See examples for decimal values, 90-minute runs and invalid fields.
Read the time fields separately
Duration inputs use separate hours, minutes and seconds fields. Hours and minutes are whole-number values. Minutes and seconds must be less than 60. Seconds may include a fractional value down to one millisecond; a value requiring finer precision is rejected. Every displayed time field needs a value, including zero where appropriate.
The complete duration must be at least one second and no more than 48 hours. That means 48 / 0 / 0 is valid, while 48 / 0 / 1 is outside the range. A 50-minute duration is 0 / 50 / 0, not 0 / 0 / 50. In pace inputs, the minutes component may be 60 or more because it expresses time per kilometre or mile, not an hour component.
Use an English decimal point and an explicit unit
Distances accept a non-negative decimal number with an English decimal point. Surrounding spaces are trimmed. Examples such as 10, 10.5, .5 and 10. are parsed as decimal values. Scientific notation, comma grouping, a plus or minus sign, and words such as Infinity are not accepted.
After conversion to millimetres, a total distance must be from 100 m to 100 km. Zero is outside that total-distance range even though zero is useful in a time component. The named race presets use exact distance constants. Custom decimal distances are rounded to the nearest millimetre after unit conversion.
Accepted and rejected examples
The table below is generated by running these inputs through the application’s validators. Rejected rows show the same English messages used by the tool interface.
| Field(s) | Input | Result or message |
|---|---|---|
| Distance · km | 10 | Accepted · 10 km |
| Distance · km | .5 | Accepted · 0.5 km |
| Distance · km | 10. | Accepted · 10 km |
| Distance · km | 10 (surrounding spaces) | Accepted · 10 km |
| Distance · km | Empty field | Enter a value in the highlighted field. |
| Distance · m | 1e3 | Use a positive English-format number, for example 10 or 10.5. |
| Distance · m | 1,000 | Use a positive English-format number, for example 10 or 10.5. |
| Distance · km | -1 | Use a positive English-format number, for example 10 or 10.5. |
| Distance · km | 0 | Choose a total distance from 100 m to 100 km. |
| Distance · km | 0.05 | Choose a total distance from 100 m to 100 km. |
| Distance · km | 101 | Choose a total distance from 100 m to 100 km. |
| Time · h / min / sec | 0 / 50 / 00 | Accepted · 0:50:00 |
| Time · h / min / sec | 0 / 60 / 00 | Use separate hours, minutes and seconds. Minutes and seconds must be below 60. |
| Time · h / min / sec | 0 / 0 / 0.5 | Choose a total time from 1 second to 48 hours. |
| Time · h / min / sec | 0 / 0 / 1.125 | Accepted · 1.125 seconds total |
| Time · h / min / sec | 0 / 0 / 1.1234 | Use separate hours, minutes and seconds. Minutes and seconds must be below 60. |
| Time · h / min / sec | 48 / 0 / 0 | Accepted · 48:00:00 |
| Time · h / min / sec | 48 / 0 / 1 | Choose a total time from 1 second to 48 hours. |
Correct one value without losing the others
- Read the message and identify the highlighted field.
- Keep valid entries in the other fields.
- Remove unsupported separators or correct the component range.
- Update the result after the field becomes valid.
- Confirm the distance and terminal time before exporting.
If a small interval would produce more than 240 split markers, choose a larger interval. A finish-time grid is limited to 60 rows. These limits control the size of the output; they do not assess whether a chosen running target is sensible or achievable.