If I were you, I would use the TRACK and POINT table.
The TRACK table will contain a row for each individual track.
TRACK_ID int not null (PK) NAME varchar(40) DESCRIPTION varchar(255) other identifying information
The POINT table will contain several lines per track, one for each point in the track.
POINT_ID int not null (PK) TRACK_ID int not null (FK to TRACK) LAT float degrees .. positive means north LONG float degrees .. positive means east, negative means west ALT float (elevation if you have it) TS timestamp of point
A few notes about this. Keep an eye on the rows of the POINT table; you will have a lot of them, and you want to crunch them quickly. Also, resist the temptation to use double instead of float; the floating-point data format has greater accuracy for a typical point (unless you are a land surveyor and you are not aware of materials such as universal transverse projections of the Mercator).
source share