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

[Feature request] GPS polling and file logging with different peroids #1115

Open
nckpln opened this issue Jan 13, 2024 · 2 comments
Open

[Feature request] GPS polling and file logging with different peroids #1115

nckpln opened this issue Jan 13, 2024 · 2 comments

Comments

@nckpln
Copy link

nckpln commented Jan 13, 2024

In some cases it would be very nice to have a good time resolution without creating a huge load on file system / network / battery.
I'm using GPSlogger in combination with Syncthing to track my family sport activities. If I decrease the logging interval bellow 10s in order to have a good resolution Syncthing goes crazy trying to keep up with monitoring changes and syncing it.
So the proposal is to optionally separate the GPS polling and file logging loops which can probably be useful for other logging methods as well.

@rekcodocker
Copy link

I would welcome this as well.

Increase scanning frequency (and possibly accuracy) when significant movement is detected, and lower them when it's detected that the logger remains in the same place.

@codethief
Copy link

@rekcodocker As noted in the ticket you linked, this issue here is not about the scanning frequency but about the frequency with which logs are written to the log file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants