Clock settings?

I've got myself a bit muddled over my iPAQ 2210 (OS = WM 2003) clock
settings. I'm in UK. Clock is set to 'GMT: London, Dublin'. Time right
now is about 17:15, Summer Time, i.e GMT + 1. The Today screen is
showing 17:15. So it seems all is well, given that I recall the PPC
takes care of Summer Time (DST).

But I can't make sense of the GPS times recorded during a walk I just
made. I used Memory-Map on the PPC linked by Bluetooth to my QStarz
GPS receiver. The walk started after a pub lunch at 12:50 local time.
But in the GPX file I've just downloaded from the PPC, the first entry
is 09:50. I would expect it to be showing GMT, i.e. 11:50.

So what can account for that 2 hour difference?

If it's relevant, I did have the clock set to GMT+2 in the 'Visiting'
section for a holiday in Italy, but I switched back to 'Home' on my
return last weekend. And that's how it was set when the walk occurred.

It's probably something glaringly obvious I've missed!

--
Terry, East Grinstead, UK

Jaap
Sat Apr 26 11:28:08 PDT 2008

GPS clocks are in UTC, which is without summertime. The other hour I can't
explain....

--
Jaap van Ekris
owner ModernNomads.info
www.modernnomads.info, Windows Mobile Wiki and blog

Sven
Sat Apr 26 17:48:29 PDT 2008

There isn't per chance a time zone setting buried in Memory Map somewhere?
It gets normalized time from the GPS system and has to use something to
correct for your position and DST periods. Could use the device default, but
maybe not.

"Terry Pinnell" <terrypinDELETE@THESEdial.pipex.com> wrote in message
news:e5l614tk9pagv60f02nru9dflv3k7k52ec@4ax.com...
> I've got myself a bit muddled over my iPAQ 2210 (OS = WM 2003) clock
> settings. I'm in UK. Clock is set to 'GMT: London, Dublin'. Time right
> now is about 17:15, Summer Time, i.e GMT + 1. The Today screen is
> showing 17:15. So it seems all is well, given that I recall the PPC
> takes care of Summer Time (DST).
>
> But I can't make sense of the GPS times recorded during a walk I just
> made. I used Memory-Map on the PPC linked by Bluetooth to my QStarz
> GPS receiver. The walk started after a pub lunch at 12:50 local time.
> But in the GPX file I've just downloaded from the PPC, the first entry
> is 09:50. I would expect it to be showing GMT, i.e. 11:50.
>
> So what can account for that 2 hour difference?
>
> If it's relevant, I did have the clock set to GMT+2 in the 'Visiting'
> section for a holiday in Italy, but I switched back to 'Home' on my
> return last weekend. And that's how it was set when the walk occurred.
>
> It's probably something glaringly obvious I've missed!
>
> --
> Terry, East Grinstead, UK

Terry
Sun Apr 27 00:14:43 PDT 2008

"Sven" <sejohannsen@hotmail.com> wrote:

>There isn't per chance a time zone setting buried in Memory Map somewhere?
>It gets normalized time from the GPS system and has to use something to
>correct for your position and DST periods. Could use the device default, but
>maybe not.
>
>"Terry Pinnell" <terrypinDELETE@THESEdial.pipex.com> wrote in message
>news:e5l614tk9pagv60f02nru9dflv3k7k52ec@4ax.com...
>> I've got myself a bit muddled over my iPAQ 2210 (OS = WM 2003) clock
>> settings. I'm in UK. Clock is set to 'GMT: London, Dublin'. Time right
>> now is about 17:15, Summer Time, i.e GMT + 1. The Today screen is
>> showing 17:15. So it seems all is well, given that I recall the PPC
>> takes care of Summer Time (DST).
>>
>> But I can't make sense of the GPS times recorded during a walk I just
>> made. I used Memory-Map on the PPC linked by Bluetooth to my QStarz
>> GPS receiver. The walk started after a pub lunch at 12:50 local time.
>> But in the GPX file I've just downloaded from the PPC, the first entry
>> is 09:50. I would expect it to be showing GMT, i.e. 11:50.
>>
>> So what can account for that 2 hour difference?
>>
>> If it's relevant, I did have the clock set to GMT+2 in the 'Visiting'
>> section for a holiday in Italy, but I switched back to 'Home' on my
>> return last weekend. And that's how it was set when the walk occurred.
>>
>> It's probably something glaringly obvious I've missed!
>>
>> --
>> Terry, East Grinstead, UK

Thanks both.

Jaap: It's a 2 hour difference, as explained. 11:50 -09:50

Sven: I think you're right, and somehow I think MM may have got
'stuck' with that 'Visiting' setting of a week or so earlier. Because
after posting I did another 'walk' from the PC to my garden and back.
As luck would have it, there was a widespread power cut during those 2
mins, so I got back to a PC powering down! But eventually, when I was
able to look at the new GPX, it was now correct.

--
Terry, East Grinstead, UK

Doug
Mon Apr 28 20:26:57 PDT 2008


> There isn't per chance a time zone setting buried in Memory Map somewhere?
> It gets normalized time from the GPS system and has to use something to
> correct for your position and DST periods. Could use the device default,
> but maybe not.

That may well be what is happening but if so its a bug in Memory Map. The
gpx standard http://www.topografix.com/gpx.asp most emphatically specifies
UTC time always.

Cheers
Doug Forster

Sven
Tue Apr 29 19:04:09 PDT 2008

That's nice, but we aren't really talking about transferring GPS data, we
are talking about displaying it for the user. The time calculated by the GPS
software, is going to be in UTC. The question is how is that normalized for
the user, i.e. using what offset?, system, program setup, calculated based
on discovered position and knowledge of time, time zones and DST periods?
Even MS can't seem to get the latter right, with everyone screwing with when
DST starts and stops. A bug, BTW, is a piece of software not doing what it
was intended to do, not, it not doing what you think it should.


"Doug Forster" <nobody@nowhere.com> wrote in message
news:DF9453A5-8CE2-4180-934F-933A44C3DB46@microsoft.com...
>
>> There isn't per chance a time zone setting buried in Memory Map
>> somewhere?
>> It gets normalized time from the GPS system and has to use something to
>> correct for your position and DST periods. Could use the device default,
>> but maybe not.
>
> That may well be what is happening but if so its a bug in Memory Map. The
> gpx standard http://www.topografix.com/gpx.asp most emphatically specifies
> UTC time always.
>
> Cheers
> Doug Forster

Doug
Tue Apr 29 21:32:34 PDT 2008

> That's nice, but we aren't really talking about transferring GPS data, we
> are talking about displaying it for the user. The time calculated by the
> GPS software, is going to be in UTC. The question is how is that
> normalized for the user, i.e. using what offset?, system, program setup,
> calculated based on discovered position and knowledge of time, time zones
> and DST periods?

Well no the OP was talking about the content of a GPX file. This is an xml
GPS data interchange file that is formatted to a well defined standard that
specifies UTC time for its contents regardless of the source of the data.
That file format is used by a wide variety of GPS software (including my
own) that assumes it is correctly specified.

>>A bug, BTW, is a piece of software not doing what it
> was intended to do, not, it not doing what you think it should.

Not what it was intended to do but what it says it intended to do and if it
says it intends to export a GPX file and the file isn't a GPX file because
it doesn't comply with the standard then that would be a bug. Thats what
standards are all about.

Cheers
Doug Forster

Terry
Thu May 01 00:54:20 PDT 2008

"Doug Forster" <nobody@nowhere.com> wrote:

>> That's nice, but we aren't really talking about transferring GPS data, we
>> are talking about displaying it for the user. The time calculated by the
>> GPS software, is going to be in UTC. The question is how is that
>> normalized for the user, i.e. using what offset?, system, program setup,
>> calculated based on discovered position and knowledge of time, time zones
>> and DST periods?
>
>Well no the OP was talking about the content of a GPX file. This is an xml
>GPS data interchange file that is formatted to a well defined standard that
>specifies UTC time for its contents regardless of the source of the data.
>That file format is used by a wide variety of GPS software (including my
>own) that assumes it is correctly specified.
>
>>>A bug, BTW, is a piece of software not doing what it
>> was intended to do, not, it not doing what you think it should.
>
>Not what it was intended to do but what it says it intended to do and if it
>says it intends to export a GPX file and the file isn't a GPX file because
>it doesn't comply with the standard then that would be a bug. Thats what
>standards are all about.
>
>Cheers
>Doug Forster

Doug,

As you see from my earlier reply, I reckon Sven's diagnosis was
probably correct. Don't lose sight of the chain of processing:

Satellite --> QStarz GPS Receiver --> PPC running Memory-Map -->
Export Overlay File (.MMO) --(later)--> Import Overlay File on PC
running Memory-Map --> Save it as GPX.

I strongly suspect that it was at one (or both, compounded?) of the
Mem-Map stages that the error was introduced. I'll watch out carefully
and report back more rigorously on any reoccurrence.

--
Terry, East Grinstead, UK