Back to this long running but (for me) still inconclusive discussion.Richard (rgphilpott):
You seemed to provide the definitive answer I'd been seeking. If I understood correctly you said that I could change Mem-Map's behaviour by editing the GPX file, replacing all lines like "2011-10-05T08:46:54Z" with "2011-10-05T09:46:54+01:00".Richard (USmmtech):
You appeared to confirm that.
However, I just made that global replacement to a sample GPX file, but hovering over the track still shows the original times, not one hour later.
If it helps, here's the start of the revised GPX file:
<?xml version="1.0" encoding="ISO-8859-1"?>
creator="Memory-Map 184.108.40.2069 http://www.memory-map.com
<type>C2C ALL:C2C Actual</type>
<trkpt lat="54.5554591497" lon="-2.7412378311"><ele>192</ele><time>2011-07-30T08:11:27+01:00</time></trkpt>
<trkpt lat="54.5550938288" lon="-2.7407826742"><ele>182</ele><time>2011-07-30T08:17:13+01:00</time></trkpt>
I was mistaken. The current PC time factor must have confused me. I've now repeated several tests and summarise the results as follows:
GPX #1, walk in winter, start = 09:12 local time. Actual 1st trackpoint time in file = 09:12. Displayed by MM as 10:12 (incorrect). After global replacement = 09:12 (correct).
GPX #2, walk in summer, start 09:25 local time. Actual 1st trackpoint time in file = 08:25. Displayed by MM as 09:25 (correct). After global replacement = 08:25 (incorrect).
If I was doing this test late in the year (back on GMT instead of BST) then those results would be reversed.
On balance, reckon I'll stick with taking photo of a clock or my watch near the start of every walk. The combinations of walk date (winter, summer), location (UK, Europe, USA, etc) and the current PC Date/Time make it all too much of a PITA!
A wizard in MM might sort it, but I won't hold my breath.
Terry, East Grinstead, UK