-
Notifications
You must be signed in to change notification settings - Fork 211
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
Compress GXP files #504
Comments
bpatrik
added a commit
that referenced
this issue
Jun 24, 2022
Its a lossy compression that can be finetuned in the config. #504
bpatrik
added a commit
that referenced
this issue
Jun 24, 2022
Made some tweaks and tested on my walks, hikes that I recorded with my watch. With this lossy compression a 6x improvement can be achieved. |
bpatrik
added a commit
that referenced
this issue
Jun 24, 2022
bpatrik
added a commit
that referenced
this issue
Jun 25, 2022
bpatrik
added a commit
that referenced
this issue
Jun 25, 2022
Running the compression on my full gallery (265 gpx files) |
bpatrik
added a commit
that referenced
this issue
Mar 11, 2023
bpatrik
added a commit
that referenced
this issue
Mar 18, 2023
bpatrik
added a commit
that referenced
this issue
Mar 23, 2023
bpatrik
added a commit
that referenced
this issue
Jul 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I checked my GPX files that I logged with my Garmin watch and it seems to contain too much information. GPS entry logs are every 2 meter, every 2-3 sec. It also contains altitude and hearth rate. The app can only use the
lat
andlon
part of the data, so no need to send all of them to the client side. Also data can be more sparse.Lest implement a lossy gpx compressor: It would remove all not used data and make the entry more sparse.
The text was updated successfully, but these errors were encountered: