Hi, I use my GoPro 6 to capture for mapillary seamlessly. Unfortunatly I noticed that the internal date was missed up, which results in wrong date (1.1.2016) also here at mappilary.
I was wondering why the platform doesn’t make use of the GPS date if available? Isn’t it a much more reliable source a unique timestamp for a global community?
AFAIK mapillary_tools uses GPS EXIF data if it it is already there. ie Date/Time and co-ordinates. No need to geo-encode from a separate GPX etc file.
I thought that, too. Unfortunatly it uploades this unplausible timestamps and I’m unable to fix it 
I was wondering why the platform doesn’t make use of the GPS date if available? Isn’t it a much more reliable source a unique timestamp for a global community?
I have been mentioning and asking for this a long time ago. In other words, the order of precedence throughout the platform should be:
| Exif tags |
|---|
GPSDateStamp, GPSTimeStamp |
DateTimeOriginal, SubSecTimeOriginal, OffsetTimeOriginal |
DateTimeDigitized, SubSecTimeDigitized, OffsetTimeDigitized |
DateTime, SubSecTime, OffsetTime |
DateTimeOriginal , OffsetTimeOriginal |
DateTimeDigitized, OffsetTimeDigitized |
DateTime, OffsetTime |
DateTimeOriginal potentially assume UTC here |
DateTimeDigitized potentially assume UTC here |
DateTime potentially assume UTC here |
But hey, who am I to know? 
We do read GPS timestamps but it’s not the preferred one yet. Will fix it in new mapillary_tools and DU.