AthleticLIVE Generic XC CSV Format Specification

Updated 5 hours ago

General Format

The required data is composed of 3 parts: an event list, a roster of all competing athletes, and results. Some general requirements that apply to all files:

Files should use UNIX line endings, so a single character \n as opposed to CRLF
Text format should be UTF-8
Commas should be used a field separators
Date format should be MM/DD/YYYY like “07/15/2024”
Time of day format should be HH:MM:SS like “17:40:00”
Duration format (for result time and splits) should be H:MM:SS.s or H:MM:SS.ss like “16:07.3” or “1:05.58” or “9:57.0”, the hundredth can be included but will be displayed as provided, so if you would like results to the tenth, please provide them in that format
Event length unit can be one of: “km”, “m”, or “miles” corresponding to kilometers, meters, or miles
Gender can be one of: “M” or “F” corresponding to male or female
Place also accepts the codes: “DNS”, “DNF”, or “DQ” corresponding to did not start, did not finish, and disqualified

Data Retrieval Methods

All data can be provided in 1 of 2 formats, either local files that are automatically updated or a URL location that can be queried over HTTP for updates.

Files: should be a file called “alive_events.csv” for the event list, “alive_roster.csv” for the roster data, and either a file called “alive_results.csv” for all results in 1 file or results in separate files in the format “alive_results_<division_id>.csv” for each division still including the header row.
HTTP: should be 3 separate URLs for each events, roster, and results where each endpoint can be hit with an HTTP v1.1 GET request every 5 seconds to retrieve up to date data

Data Set Specifications

Event List: lists all events that are going to be run with a unique numerical division id and race details

<division_id>,<event_name>,<event_length>,<event_length_unit>,<event_start_date>,<event_start_time>

Roster List: lists all athletes with personal information and unique numerical bib numbers

<bib_number>,<last_name>,<first_name>,<gender>,<grade>,<team>

Result Lists: lists all of the results for all races (or separate files for each race) where each race begins with a header row followed by several result rows. Place is required once an athlete has a finish time, but is not required if they only have splits so far. The end of each result row includes as many or as few (including 0) splits for the athlete in order.

%<division_id>,<event_name>

<place>,<bib_number>,<last_name>,<first_name>,<gender>,<grade>,<team>,<time>,<split_1>,<split_2>,<split_3>...

Examples

Event List

1,Boys Varsity,5000,m,10/06/2025,16:00:00
2,Elementary Girls,1,mile,10/06/2025,16:35:00

Roster List

4546,Eastlund,Cole,M,10,Pekin
4547,Carrizales,Kyle,M,9,Pekin
4548,Johnson,Owen,M,11,Pekin
4549,Miller,Jonah,M,10,Pleasant Valley
4550,Whitson,Jack,M,12,Pleasant Valley
4551,Kirman,Sammy,M,12,Wilton
4552,Lange,Leif,M,10,Wilton
107,Faul,Claire,F,6,Durant
108,LeClair,Ella,F,6,Durant
109,Yoder,Nadia,F,5,Durant
110,Cummings,Mairie,F,6,Wilton
111,Kay,Audrey,F,4,Wilton
112,Locher,Addison,F,5,Wilton

Result Lists

%1,Boys Varsity
1,4549,Miller,Jonah,M,10,Pleasant Valley,19:45.7,6:37.9
2,4546,Eastlund,Cole,M,10,Pekin,19:52.8,6:44.5
3,4551,Kirman,Sammy,M,12,Wilton,20:16.1,6:33.2
4,4548,Johnson,Owen,M,11,Pekin,20:24.0,6:58.0
5,4550,Whitson,Jack,M,12,Pleasant Valley,21.07.3,7:03.1
,4547,Carrizales,Kyle,M,9,Pekin,,8:44.6
DNS,4552,Lange,Leif,M,10,Wilton,
%2,Elementary Girls
1,111,Kay,Audrey,F,4,Wilton,7:04.3
2,112,Locher,Addison,F,5,Wilton,7:09.1
3,107,Faul,Claire,F,6,Durant,7:10.5
4,108,LeClair,Ella,F,6,Durant,7:26.8
5,109,Yoder,Nadia,F,5,Durant,7:52.0
6,110,Cummings,Mairie,F,6,Wilton,8:09.4