> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/glossary.md). # Glossary Common terms used across Racemap live tracking — with their synonyms. This list is intended to help users find documentation no matter which term they search for, and to guide AI-assisted documentation tooling toward the preferred vocabulary. *** ## Read **Preferred term:** read\ **Synonyms:** detection, passing, ping, trackping, timestamp\ **Context:** prediction feature, timing integrations A single data point recorded when a participant is observed by a timing reader or GPS device. In the prediction and timing context, **read** is the preferred term. The word **detection** is common in integrations with external timing systems (e.g. ChronoTrack, RACE RESULT). **Passing** appears in some timing-system UIs and older documentation. **Ping** and **Trackping** are RACE RESULT specific for Mobile Trackbox detections. *** ## Auto-pausation **Preferred term:** auto-pausation\ **Synonyms:** auto-deactivation, automatic shutdown, automatic pause The automatic pausing of the Data Feed API module that occurs on the first API request arriving more than 2 hours after an event's end time. Auto-pausation prevents unexpected billing costs when a feed is left active after the event finishes. Repeating (live loop) events are excluded. See [Auto-pausation](/api/auto-pausation.md). *** ## Billing cycle **Preferred term:** billing cycle\ **Synonyms:** event cycle, billing period\ **Context:** billing A 7-day period that live tracking is billed against. A cycle is counted in **whole UTC calendar days** and is anchored to the first UTC day the event is active; it covers that day plus the following 6 UTC dates and is billed once. Because days are counted in UTC — not local time — a long event that starts shortly before 00:00 UTC can touch an 8th UTC date and roll into a second cycle. See [Billing cycles](/billing.md) and the related [Auto-pausation](#auto-pausation). *** ## Timekeeping Point **Preferred term:** timekeeping point\ **Synonyms:** split, checkpoint, geofence, virtual checkpoint, timing point, reader location A virtual location defined on the course at which reads are recorded for timing or ranking purposes. The API field name is `timekeepings` (plural). In the UI and documentation the terms *split*, *checkpoint*, and *geofence* appear interchangeably — all refer to the same concept. *** ## Timing Reader **Preferred term:** reader\ **Synonyms:** decoder, timing system, Track Box, antenna Hardware or software positioned at a timekeeping point that records reads as participants pass. Different vendors use different names: RACE RESULT uses *decoder*, Racemap's own hardware is the *Track Box*, and the general abstraction in the API and documentation is *reader*. *** ## Data Feed **Preferred term:** Data Feed\ **Synonyms:** Data API, live API, datafeed, data feed module The real-time HTTP API that serves current event data — participant locations, ranks, times — to external consumers such as TV graphics, custom dashboards, or result systems. Enabled per event via the Data API settings. See [Data API overview](/api.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.racemap.com/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.