GPS import

GPS import

ForCoachesClub admins

If your team trains with GPS vests, bring in the file the vest software exports. Distances and sprints then show up next to the survey answers: in the week view, the charts, the player page and the load ratio.

Where to find it
Where
GPS import in the menu.
Who
Coaches (for the teams they coach) and admins. Viewers and players don't see it.
  1. 1

    Export the session from the vest software

    As a CSV file with one row per player and a header row. Most vest software has this export.

  2. 2

    Pick the team and choose the file

    Choose CSV file. The file can be up to 2 MB. Nothing is saved yet: you see a preview first.

  3. 3

    Check the columns

    The app recognises the usual column names. Fix any that are wrong, or set one to "Not in the file".

  4. 4

    Pick anyone not recognised

    For each name the app could not place, choose who it is, or leave it on "Skip these rows".

  5. 5

    Save

    Save N rows saves every row that has a player and a date. A note says how many were saved and how many skipped.

GPS import Try it — nothing is saved

Import a vest export

Choose the file, tell the app who “Oskari N.” is, and save. Leave him on “Skip these rows” to see the count drop.

Columns

These are the columns the app looks for. It ignores case, units in brackets and punctuation, so "Total Distance (m)" is the same as "total distance". Finnish column names work too.

ColumnRecognised names, for example
Player namePlayer, Player Name, Name, Athlete
Jersey numberJersey, Shirt Number, Number, No
DateDate, Session Date, Start Date, Day
SessionSession, Session Title, Activity, Drill
DurationDuration, Total Duration, Total Time, Minutes
Distance (m)Total Distance, Distance
High-speed running (m)HSR, HSR Distance, High Speed Running
Sprint distance (m)Sprint Distance
SprintsSprints, Sprint Count, Number of Sprints, Sprint Efforts
Top speedMax Speed, Top Speed, Max Velocity
Accelerations, DecelerationsAccelerations, Accels; Decelerations, Decels
Strain pointsPlayer Load, Total Player Load, Load
  • The file needs a player name or a jersey number column, and a date column. Everything else is optional.
  • Strain points are the vest's own total of movement in every direction — running, jumps, turns and contacts — counted by its motion sensor. The number has no unit: compare a player with their own earlier sessions.
  • Dates can be written 2026-10-29, 29.10.2026, 29/10/2026 or 29.10.26 (day first). A time after the date is ignored.
  • Numbers can use a decimal comma or point, with or without thousands separators.
  • Durations can be minutes (75), or hours, minutes and seconds (01:15:00).
  • A top speed in m/s (when the column name says so) is turned into km/h.
  • Distances in kilometres (when the column name says km, as in "Total_km" or "Distance (km)") are turned into metres, and the preview says which columns it read that way.
  • Separators can be commas, semicolons or tabs.

Rows to check

Some values are probably in the wrong column or unit, especially in a file kept by hand. The preview marks those rows and says why:

  • Strain points under 10 for a session over 1 km: usually a high-speed running value typed into the load column.
  • More high-speed running than distance in total.
  • A total distance under 50 m: kilometres in a column the file calls metres.

Marked rows are saved like the others: it is your data. Fix them in the file and import it again; the new rows replace the old ones for the same player, day and session.

A spreadsheet you keep yourself

If you have typed the numbers into a spreadsheet, download it as CSV and import that file: one row per player per session, with a player and a date column. Earlier sessions come in the same way as new ones.

How players are matched

For each row, the app tries in this order, among the players on the chosen team:

  1. the jersey number, if exactly one player has it;
  2. the name exactly, ignoring accents and case;
  3. the name the other way round ("Lehtinen Joona", "Lehtinen, Joona");
  4. the last name alone, if only one player has it.

Rows still without a player are listed under Players not recognised. Pick the right player for each name once; every row with that name follows. Rows you leave on "Skip these rows" are not saved.

Keep the jersey numbers on the roster up to date. Matching by number is the most reliable, and it also works when the vest software spells a name differently.

Importing again replaces

Saving a row replaces that player's earlier GPS row for the same day and the same session name. Importing a corrected file again is safe: nothing is counted twice. Two different sessions on one day (with different session names) are kept apart.

Earlier imports

Earlier imports lists the files, who imported them and how many rows were saved. The bin deletes an import and every row it saved, for when the wrong file went in. Admins can delete any import; a coach can delete their own.

Where GPS shows up

  • Week view: a GPS line under the day's sessions, and the week's distance in the total.
  • Team charts and the player page: distance and high-speed running.
  • Season view: distance, high-speed running and sprint distance per week.
  • Load ratio: every GPS measure, compared like load.

GPS does not change the survey load (RPE × minutes). The two are shown side by side.