Ignore the “distance filter” setting once at the start of every hour and/or at the start of any new log file

As it is now, when using the “distance filter” setting, if a person stays for an hour or more at the same place, it’s really easy to end up with an incomplete registry, with no new files for hours. I’m creating a new file for every hour (%YEAR-%MONTH-%DAY-%HOUR) and constantly facing this issue. The solution is simple, though: just, as the title says, have the app ignore the “distance filter” setting once at the start of every hour and/or at the start of any new log file and register the location even if it is the same as previously seen. This way, as long as the user is not using some crazy setup (a new file for every minute or second, let’s say), the app would write a consistent registry, with no missing hours, while, at the same time, not spamming the registry with the same location (so, respecting the filter). This could be a setting by itself to be activated by the user, of course.

The issue names no files or tests. Trace the distance-filter decision together with hourly and new-log-file creation, then verify that the location is recorded at each hour or new file while the filter still suppresses other duplicate locations.