GPX Import + Extract Brief Visits - possible timezone problem

Arc App Support
1

I imported a GPX file and used Extract Brief Visits to begin cleaning up the data. It appears that the visit was extracted successfully, but it was saved to the timeline with its timestamps converted to my phone’s local timezone instead of preserving the original GPX timestamps.

I’ve emailed the debug information, the original GPX file, and a screenshot of the extracted visit.

During my testing, I believe BIG-645 occurred, so the debug logs may contain unrelated information.

From what I can tell, the GPX itself imported correctly. The track starts at 10:01 in the location’s local timezone, as expected. However, after running Extract Brief Visits, the extracted visit appeared starting at 6:01, which corresponds to 10:01 converted to my phone’s local timezone. This suggests that the extraction process is incorrectly interpreting or converting the timestamps, even though the initial GPX import preserves them correctly.

Thanks,

2

Good news on this one: your data is fine. The GPX import stored the recording timezone against every sample, and it’s still there — nothing was converted or lost on the way in.

What you hit is a display bug confined to that screen. The Extract Brief Visits list formats its times using your phone’s current timezone rather than the timezone the data was recorded in, so a 10:01 stop reads as 6:01. The extracted visit itself keeps its true times — if you view it in the timeline day view it should show 10:01, as expected.

Your report also widened an existing ticket. We already had this filed against the segments view (BIG-535), and checking your case against the code turned up the same oversight on several other screens, so it’s now one fix across all of them rather than a one-off.

And you were right that BIG-645 showed up during your testing — that one’s fixed and will be in the next release.