ClydeE

To be honest, to get full use out of GSAK and this macro, you do need to be a premium member and load GPX files. A non premium member only has access to loc files, and this will severely limit the usefulness of GSAK and also render much of the data in the Findstatsgen3 rather useless.

Please see items 2 and 10 of the GSAK FAQ in the help file or online here http://gsak.net/help/hs1070.htm

Yes. For more information please see items 2 and 10 of the GSAK FAQ in the help file or online here http://gsak.net/help/hs1070.htm

Alternatively, just enter 200 in the "Maximum waypoints to send" box. GSAK will include child waypoints but do an "intelligent" calculation of the first 200 waypoints to send to your GPSr Form more information is this calculation please see http://gsak.net/help/hs38100.htm

Careful. That will replace everything in your GPX file that contains the letter combination of "GC" to nothing. You could be loosing that vital bit of information needed for a Puzzle cache or something. If you must go down that path then a better replacement might be "<name>GC" with "<name>" (without the double quotes)

From the main GSAK menu, try "GPS=>Export to Lowrance Usr..."

Try this:

Multiple finds for the same cache will only be counted correctly when: 1. Your GSAK database is being updated with GPX files from gc.com (not loc files) 2. You tell GSAK correctly how to match your found logs. To get item 2 correct make sure you have the "method for matching hidden and found" caches filled out correctly (Tools=>Options=>General). For more information see the help file or view this section online here http://www.gsak.net/help/hs7690.htm

Also another way can be found here http://forums.Groundspeak.com/GC/index.php...t&p=1444844

If you want to purge out some of your logs at any stage go "Database=>Purge logs"

And the 60csx, can even make this statement a fallacy. I don't think it is in the manual but the 60csx gets smart with us here. That is, if the name is the same but the coordinates are different it will actually add this as a new waypoint rather than replace - also changing the name of the waypoint behind your back to something unique. Bottom line: To keep your sanity, it is a good idea to delete all your waypoints in your GPSr before sending again.

Try this link

GSAK creates all exports in your current sort order. Just click on the any column heading to sort your data in that order before generating your LOC/GPX file.

Yep, we should be back up and running now.

For the latest status update please see this link

I have also set up a temporary board that you can use here

As a temporary measure I have set up a skeleton of the GSAK main page, so you download the latest version here

Update: Closer, but it must be the night shift over there (it is day time here in Australia). Looks like I need someone with more juice to sort this out.

Sorry for the inconvenience. I currently have a ticket open to try and find out why the account has been suspended. I did change plans just recently (needed more disk space and bandwidth), so perhaps there was a mix up with the account.

You can set a filter on only caches that have child waypoints via "Search=>Filter=>Other"

"File=>Print", and select the "Condensed HTML" option

The Nuvi natively supports GPX files, so you can just go "File=>Export=>GPX" to plonk data from GSAK to your Nuvi

Interesting! I've never tried that. You learn something new everyday! ... And if your GSAK database is up to date you can run this macro to generate and optimize the from and to dates for all your PQs that you need.

I was messing around with this and I noticed, when I export to mapsource. The waypoint id is the title of the cache and not the waypoint that gc.com suggests GCxxxx. Is there a way to change this? Please see item 3 of the GSAK FAQ in the help file or online here (It does refer to sending waypoints to the GPSr but it applies to all exports including MapSource)

It was the firewall - which is weird because it was working before I downloaded the latest update..... Thanks for all the suggestions tho' Nick This is a common problem when you update a program. Even though you may have authorized GSAK Internet access in the past, many Firewalls (software based mainly) see the update as a completely new program and therefor you must again grant it access to the Internet.