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

Reject empty tracks #39

Open
opatut opened this issue Feb 19, 2021 · 2 comments
Open

Reject empty tracks #39

opatut opened this issue Feb 19, 2021 · 2 comments
Labels
data processing enhancement New feature or request

Comments

@opatut
Copy link
Member

opatut commented Feb 19, 2021

One part of openbikesensor/obsApp#14 that I overlooked is where empty tracks should not show up at all. Those happen quite often when the OBS is switched on, but turned off again before starting the recording (i.e. no GPS found yet).

I'd say the API should just detect and reject empty tracks on upload. Maybe in addition we can teach the firmware not to produce these files (or detect and delete them), @amandel?

@amandel
Copy link
Member

amandel commented Feb 19, 2021

Empty files with no data or header data only should not be generated any more since a while now. You might get files with a low number of lines or with no line with location information.

@opatut opatut added enhancement New feature or request data processing labels Feb 24, 2021
@opatut
Copy link
Member Author

opatut commented May 15, 2021

The importer should reject those. Then we can mark the track as invalid, and delete or at least hide it.

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

No branches or pull requests

2 participants