You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: