Hoping there might be a few Memory-Map users here who can confirm my
interpretation of a few points please. (I've posted to the Memory-Map
internal forum, but typically it takes 4 days to get a response.)
I downloaded a tracklog of a UK walk from my Garmin GPS 12 and, using
other software, saved it as a GPX file. I imported that into
Memory-Map. If I move the mouse cursor over the map I can now see the
time I was at each trackpoint. Good, exactly what I want, as I'm
playing with geo-tagging my walk photos, and find I often need to know
when I was at a particular place, to match it with EXIF data from my
camera.
But the bad news is that I've just discovered that this time will
change, depending on whether I'm using Memory-Map in summer or winter!
IOW, if I were to view this same walk next winter, I think all the
times would be 1 hour behind?
As I understand it, this arises because of two factors:
1) GPX files have no knowledge of local times. So they will always use
the UTC (GMT) times recorded by the GPS unit. Regardless of what
software is used to save them. My walk was in summer, starting at
09:30, but the first trackpoint in the GPX files is 08:30, viewed in
my text editor. No information about offsets or zones is present in
the file.
2) But Memory-Map apparently adjusts this according to the time zone
set on my PC. So today, in British Summer Time (BST), the mouse cursor
shows the first trackpoint as 09:30, *apparently* the correct local
time. But if I re-open this overlay in December, it will show the
start as 08:30.
Seems very confusing. I'd have thought it would be much better to
avoid such ambiguity if Memory-Map consistently displayed the data
actually in the GPX file, i.e UTC (GMT). But maybe I'm missing
something?
--
Terry, West Sussex, UK
--
Terry, West Sussex, UK