Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BaseReader Proxy #4

Closed
marcelcaraciolo opened this issue Jun 24, 2020 · 2 comments · Fixed by #5
Closed

BaseReader Proxy #4

marcelcaraciolo opened this issue Jun 24, 2020 · 2 comments · Fixed by #5
Labels
enhancement New feature or request

Comments

@marcelcaraciolo
Copy link
Contributor

marcelcaraciolo commented Jun 24, 2020

  • what files does the tool must read for reading running tracking data ?

  • available formats: .TCX , .GPX, Cheetah , .Json, .fit

build the base reader proxy for reading/parsing the TCX, GPX and other GPS devices.

@marcelcaraciolo marcelcaraciolo added the enhancement New feature or request label Jun 24, 2020
@marcelcaraciolo
Copy link
Contributor Author

TCX and FIT are designed for fitness activities, so they can contain more fitness data than GPX.

eg TCX or FIT supports laps (splits). So your device could record a new lap whenever you press the lap button, or automatically after a set distance, eg every 1km. Also they support pauses, if you want to stop the activity at one point, then start again later. Whereas GPX is essentially just a series of points (with timestamps).

I am not sure whether Strava actually uses the laps or pauses recorded on the device, I suspect it will recalculate them anyway, based on the GPS points and time.

As standard, GPX does not support heart rate, cadence or power data. But this can be added with extensions. The most popular format for these extension was created by Garmin, it is also supported by a variety of other software/websites (including Strava). But some devices might record heart rate/cadence in a different format in the GPX file.

TCX or FIT can also contain summary data, for the whole activity. eg the total time, distance, calories, device used, type of sport. Some of this is used by Strava, eg to display the device, or automatically select the activity type.

TCX and GPX are both XML formats, which can be fairly inefficient in terms of file size. But this does mean they can be easily edited, eg in a text editor. FIT is a binary format, so is much smaller file size, typically about 1/10 of the size. File size is usually not a problem anyway - even if you are recording at 1 point per second, a 3 hour activity would be about 1MB in GPX format. So not really an issue, unless your device has very limited memory, or a slow internet connection for uploading.

So in general, you probably won't notice much difference between formats for uploading to Strava. Though TCX or FIT may give you a bit more data. And FIT would be a smaller file size.

@marcelcaraciolo
Copy link
Contributor Author

I will work only for now with the formats: TCX, FIT and GPX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant