Anquet upgrade.

d hill said:

I note from their Web site that i can upgrade my discs at a discount.
Question panel is it worth it to upgrade from version 1.2.9 to current
whatever version.
I have York dales. and peak at 1:25000 and peak at 1:50000
I note that the later isn't supported in the 'version'.

It's worth getting the free demo and exploring that first. The route
handling is now way more powerful than before, there's an improved
Pocket PC program and Smartphone support too. I guess it depends if any
of these things are meaningful changes for you.

Bear in mind that extending your Anquet coverage will almost certainyl
mean having to install the newer version and the two cannot interface
"seamlessly". On the other hand, do you want to pay again for mapping
you've already bought?

druidh

d hill said:

I note from their Web site that i can upgrade my discs at a discount.
Question panel is it worth it to upgrade from version 1.2.9 to current
whatever version.
I have York dales. and peak at 1:25000 and peak at 1:50000
I note that the later isn't supported in the 'version'.

I have Lake District and Glen Coe (etc) at 1:25k in the older version.
I recently bought packs covering my local area in Lanarkshire.

I was annoyed to find that I had to have both Anquet and Anquet v6
installed as the newer software did not work with the older map data.
Effectively, they are two separate mapping applications. I emailed
Anquet, expressing reluctance to fork out again to re-buy software that
I had already, legitimately bought, so that all my mapping could be
operated through a single application. Even Microsoft products are
reasonably backwards-compatible.

The reply merely re-iterated the offer of a 50% discount on the purchase
price of a v6 version of my existing software. Alternatively, I could
buy the older version of my new software. Not very customer-friendly, I
thought.

The new software has pros and cons over the old. I haven't used the new
stuff much yet, but I am getting to grips with the database manager
aspect, which is possibly a plus. It is slower to start up than the old
version. The pocket PC utility has more functionality (if that is a
significant point). But it still does not upload times in the track
record from my Garmin eTRex.

Having said all that, I will probably upgrade my Lakes pack just so that
I'm not having to remember how to work two different applications.

George

George Reid said:

d hill said:

I note from their Web site that i can upgrade my discs at a discount.
Question panel is it worth it to upgrade from version 1.2.9 to current
whatever version.
I have York dales. and peak at 1:25000 and peak at 1:50000
I note that the later isn't supported in the 'version'.

I have Lake District and Glen Coe (etc) at 1:25k in the older version. I
recently bought packs covering my local area in Lanarkshire.

I was annoyed to find that I had to have both Anquet and Anquet v6
installed as the newer software did not work with the older map data.
Effectively, they are two separate mapping applications. I emailed
Anquet, expressing reluctance to fork out again to re-buy software that
I had already, legitimately bought, so that all my mapping could be
operated through a single application. Even Microsoft products are
reasonably backwards-compatible.

The reply merely re-iterated the offer of a 50% discount on the purchase
price of a v6 version of my existing software. Alternatively, I could
buy the older version of my new software. Not very customer-friendly, I
thought.

These licensing restrictions are actually imposed by the Ordnance
Survey. I doubt Anquet would wish this as it obviously gives an
opportunity for customers to seriously consider alternative products.

Having said that, I think it's fair to say that Anquet have applied the
"rules" more vigorously than their competitors have. I know that there
is a well known "hack" for Memory Map to get around this problem.

Quoted message said:

The new software has pros and cons over the old. I haven't used the new
stuff much yet, but I am getting to grips with the database manager
aspect, which is possibly a plus. It is slower to start up than the old
version. The pocket PC utility has more functionality (if that is a
significant point). But it still does not upload times in the track
record from my Garmin eTRex.

That's weird - I'm now getting timestamps in the uploads from my Geko.
have you applied any of the software updates?

Quoted message said:

Having said all that, I will probably upgrade my Lakes pack just so that
I'm not having to remember how to work two different applications.

I had the whole country at 1:50k, so did the full upgrade. However, I've
got the Harveys 1:25k of Scotland and there is no equivalent in the new
version which means I'm a bit stuck!

druidh

druidh said:

George Reid wrote:

Quoted message said:

Quoted message said:

The new software has pros and cons over the old. I haven't used the
new stuff much yet, but I am getting to grips with the database
manager aspect, which is possibly a plus. It is slower to start up
than the old version. The pocket PC utility has more functionality
(if that is a significant point). But it still does not upload times
in the track record from my Garmin eTRex.

Quoted message said:

That's weird - I'm now getting timestamps in the uploads from my Geko.
have you applied any of the software updates?

I haven't had an opportunity to try it out since I updated a month or so
ago. Just noticed another update (6.0.8) and have downloaded it. Will
be in the Lakes next weekend, but with old Anquet )-:

George

George Reid said:

I haven't had an opportunity to try it out since I updated a month or so
ago. Just noticed another update (6.0.8) and have downloaded it. Will
be in the Lakes next weekend, but with old Anquet )-:

....just went out for a cycle this afternoon with my Etrex. Uploaded
Tracklogs to Anquet v6 (2.0.8) when I got home. Although the saved
tracklogs have all track points timestamped 30/12/1989 23:59 (presumably
a default), the ACTIVE LOG shows correct date but time is GMT not BST.

I guess this must be a problem with the Etrex output, as it shows the
time correctly.

Don't know why the time data is lost in saved tracklogs, though. My
Etrex is a few years old running software version 2.14 (newer models
have a hardware upgrade and newer software upgrades are not compatible).
I will email Garmin support.

George

George Reid said:

George Reid said:

I haven't had an opportunity to try it out since I updated a month or
so ago. Just noticed another update (6.0.8) and have downloaded it.
Will be in the Lakes next weekend, but with old Anquet )-:

...just went out for a cycle this afternoon with my Etrex. Uploaded
Tracklogs to Anquet v6 (2.0.8) when I got home. Although the saved
tracklogs have all track points timestamped 30/12/1989 23:59 (presumably
a default), the ACTIVE LOG shows correct date but time is GMT not BST.

I guess this must be a problem with the Etrex output, as it shows the
time correctly.

Coincidently, I've been out playing with my Etrex (Vista) this
afternoon, recording a few paragliding flights. I also get the default
tracklogs from 30/12/89 23:59, but the ones I'm interested in have the
correct date/time. There is a setting under:-
"main Menu"==>"Setup"==>"time" called 'Daylight Savings Time', which is
set to 'Auto' on my GPS. Have you checked this?

HTH

--
Dave McLaughlin

[censored] Sapiens Non Urinat In Ventum

In article <[email hidden]>, George Reid
<[email hidden]> writes

Quoted message said:

...just went out for a cycle this afternoon with my Etrex. Uploaded
Tracklogs to Anquet v6 (2.0.8) when I got home. Although the saved
tracklogs have all track points timestamped 30/12/1989 23:59
(presumably a default), the ACTIVE LOG shows correct date but time is
GMT not BST.

I guess this must be a problem with the Etrex output, as it shows the
time correctly.

When asked for track data Garmins output the time as seconds since
midnight at the end of 30/12/1989 UTC (GMT). What the program that
receives that data does with the time is up to it - it seems Anquet is
not dealing with the unavailable time data very well and defaulting to
GMT in your case. Is your computer timezone set properly and do you have
"Automatically adjust for daylight saving changes" selected? Both can be
checked by double clicking on the clock. Anquet might be trying to
adjust the times based on your computer's settings so if the setting are
not correct it may have unexpected results.

Quoted message said:

Don't know why the time data is lost in saved tracklogs, though.

Saving a track log also squashes it to save space. Part of the space
saving squash is reducing the points in the track and part is removing
the trackpoint times.

--

Dominic Sexton

Dave McLaughlin said:

George Reid said:

George Reid said:

I haven't had an opportunity to try it out since I updated a month or
so ago. Just noticed another update (6.0.8) and have downloaded it.
Will be in the Lakes next weekend, but with old Anquet )-:

...just went out for a cycle this afternoon with my Etrex. Uploaded
Tracklogs to Anquet v6 (2.0.8) when I got home. Although the saved
tracklogs have all track points timestamped 30/12/1989 23:59
(presumably a default), the ACTIVE LOG shows correct date but time is
GMT not BST.

I guess this must be a problem with the Etrex output, as it shows the
time correctly.

Coincidently, I've been out playing with my Etrex (Vista) this
afternoon, recording a few paragliding flights. I also get the default
tracklogs from 30/12/89 23:59, but the ones I'm interested in have the
correct date/time. There is a setting under:-
"main Menu"==>"Setup"==>"time" called 'Daylight Savings Time', which is
set to 'Auto' on my GPS. Have you checked this?

....yup. It's on auto. And as I said, the screen time on the etrex
shows correctly. It must be something in the download process...

George

Dominic Sexton said:

In article <[email hidden]>, George Reid
<[email hidden]> writes

Quoted message said:

...just went out for a cycle this afternoon with my Etrex. Uploaded
Tracklogs to Anquet v6 (2.0.8) when I got home. Although the saved
tracklogs have all track points timestamped 30/12/1989 23:59
(presumably a default), the ACTIVE LOG shows correct date but time is
GMT not BST.

I guess this must be a problem with the Etrex output, as it shows the
time correctly.

When asked for track data Garmins output the time as seconds since
midnight at the end of 30/12/1989 UTC (GMT). What the program that
receives that data does with the time is up to it - it seems Anquet is
not dealing with the unavailable time data very well and defaulting to
GMT in your case. Is your computer timezone set properly and do you have
"Automatically adjust for daylight saving changes" selected? Both can be
checked by double clicking on the clock. Anquet might be trying to
adjust the times based on your computer's settings so if the setting are
not correct it may have unexpected results.

Quoted message said:

Don't know why the time data is lost in saved tracklogs, though.

Saving a track log also squashes it to save space. Part of the space
saving squash is reducing the points in the track and part is removing
the trackpoint times.

I've just uploaded both the Active Tracklog and a saved Tracklog from my
Geko to Anquet. Both have timestamp information. Both are still
presenting time in GMT format. I suspect that the data is all saved this
way and that changing the setting in the GPS is merely changing how it
is presented on the GPS itself - not changing the underlying data.

druidh

druidh said:

Dominic Sexton wrote:

Quoted message said:

Quoted message said:

Is your computer timezone set properly and do you
have "Automatically adjust for daylight saving changes" selected?

....yes, and yes.

Quoted message said:

I've just uploaded both the Active Tracklog and a saved Tracklog from my
Geko to Anquet. Both have timestamp information. Both are still
presenting time in GMT format. I suspect that the data is all saved this
way and that changing the setting in the GPS is merely changing how it
is presented on the GPS itself - not changing the underlying data.

....that would explain the hour's difference I notice in my Active Log
upload. Maybe the Etrex is not quite the same as the Geko when
outputting data?

George