I have now submitted all sequences for 2018-08 (date range for uploading) that normally would have been cut (some because of these errors) for reprocessing. This should re-insert the orginal date into our backend, and re-calculate the spikes in the places where this date bug was the cause of the confusion. The results should be visible within 1-2 days.
@filipc for the old 2017 spiky sequences- that is an Android bug where the date was submitted wrongly in the EXIF. I am planning to pull this data out of Postgresql into Elasticsearch, since we have the Android App version number, and then reprocess and fix the EXIF harvesting code so we can re-calculate these seqeunces, too. It’s on my radar.