GSAK?

[+Kiwi Nomad]

Another thing that you can do is change the format of the cache name before down loading it to your GPS.

A friend of mine puts an X at the beginning of the name of any cache that he has loaded corrected coordinates for.

Back when most GPS's only allowed around 8 or 10 characters in the name he used to drop the GC at the beginning of the GC code and add extra letters at the end telling him what size and type of cache it was.

 

He also created a macro that shows how many caches you have found in each part of New Zealand and maps it. Which comes in useful when trying to find out if you qualify for the challenge cache I placed.

 

I love working out which caches I want to find and then opening a map of just those caches. It means I can have it show just the ones I'm interested in, some puzzles showing, some not. Flag ones to be solved at home so they don't show up, but include the others and the ones I have solved.

 

Also there is usually more than one way to achieve the same outcome depending on how you prefer to use the program.

[+Jeepster]

How do you guys handle this "problem" with corrected coordinates?

 

One can change the coordinates for a puzzle cache, on Geocaching.com, to show the solved location - there's an edit pencil right next to the coordinates on the cache page. Changing the coordinates yields these results when I'm logged in:

 

1) The corrected coordinates show up on the cache page.

 

2) The corrected coordinates show up in any pocket query that includes that cache.

 

3) A download of the pocket query and a subsequent upload into GSAK shows the corrected coordinates.

 

4) A direct download of the pocket query into GSAK - using the "Download pocket queries" option - shows the corrected coordinates.

 

Now the problem:

 

When using the "Refresh cache data" option in GSAK, the corrected coordinates are replaced with the original "incorrect" coordinates. That problem caught me recently on a puzzle cache. Luckily, I'd checked the location via Google Earth and knew where to look without having to return home to get the solved coordinates.

 

My work-a-round now is to keep puzzle caches in a separate database and use the "Get recent logs ..." option instead of "Refresh cache data" option.

[+Beach_hut]

How do you guys handle this "problem" with corrected coordinates?

 

One can change the coordinates for a puzzle cache, on Geocaching.com, to show the solved location - there's an edit pencil right next to the coordinates on the cache page. Changing the coordinates yields these results when I'm logged in:

 

1) The corrected coordinates show up on the cache page.

 

2) The corrected coordinates show up in any pocket query that includes that cache.

 

3) A download of the pocket query and a subsequent upload into GSAK shows the corrected coordinates.

 

4) A direct download of the pocket query into GSAK - using the "Download pocket queries" option - shows the corrected coordinates.

 

Now the problem:

 

When using the "Refresh cache data" option in GSAK, the corrected coordinates are replaced with the original "incorrect" coordinates. That problem caught me recently on a puzzle cache. Luckily, I'd checked the location via Google Earth and knew where to look without having to return home to get the solved coordinates.

 

My work-a-round now is to keep puzzle caches in a separate database and use the "Get recent logs ..." option instead of "Refresh cache data" option.

 

I do all of my co-ordinate correcting in GSAK itself, never had the problem you're describing? I've just tried it on a random cache in my solved list, and it retained the corrected co-ords.

[+Walts Hunting]

I enthusiastically pay 100% of full price to be able to use the 5% of GSAK that I actually understand.

 

+1

[+Walts Hunting]

How do you guys handle this "problem" with corrected coordinates?

 

One can change the coordinates for a puzzle cache, on Geocaching.com, to show the solved location - there's an edit pencil right next to the coordinates on the cache page. Changing the coordinates yields these results when I'm logged in:

 

1) The corrected coordinates show up on the cache page.

 

2) The corrected coordinates show up in any pocket query that includes that cache.

 

3) A download of the pocket query and a subsequent upload into GSAK shows the corrected coordinates.

 

4) A direct download of the pocket query into GSAK - using the "Download pocket queries" option - shows the corrected coordinates.

 

Now the problem:

 

When using the "Refresh cache data" option in GSAK, the corrected coordinates are replaced with the original "incorrect" coordinates. That problem caught me recently on a puzzle cache. Luckily, I'd checked the location via Google Earth and knew where to look without having to return home to get the solved coordinates.

 

My work-a-round now is to keep puzzle caches in a separate database and use the "Get recent logs ..." option instead of "Refresh cache data" option.

 

I do all of my co-ordinate correcting in GSAK itself, never had the problem you're describing? I've just tried it on a random cache in my solved list, and it retained the corrected co-ords.

 

Actually this cane up on the GSAK forums (which BTW is a better place to ask GSAK questions) and the answer was to lock those caches in the DB.

[+Dgwphotos]

How do you guys handle this "problem" with corrected coordinates?

 

One can change the coordinates for a puzzle cache, on Geocaching.com, to show the solved location - there's an edit pencil right next to the coordinates on the cache page. Changing the coordinates yields these results when I'm logged in:

 

1) The corrected coordinates show up on the cache page.

 

2) The corrected coordinates show up in any pocket query that includes that cache.

 

3) A download of the pocket query and a subsequent upload into GSAK shows the corrected coordinates.

 

4) A direct download of the pocket query into GSAK - using the "Download pocket queries" option - shows the corrected coordinates.

 

Now the problem:

 

When using the "Refresh cache data" option in GSAK, the corrected coordinates are replaced with the original "incorrect" coordinates. That problem caught me recently on a puzzle cache. Luckily, I'd checked the location via Google Earth and knew where to look without having to return home to get the solved coordinates.

 

My work-a-round now is to keep puzzle caches in a separate database and use the "Get recent logs ..." option instead of "Refresh cache data" option.

I discovered this is happening recently, as well.

[+Don_J]

How do you guys handle this "problem" with corrected coordinates?

 

One can change the coordinates for a puzzle cache, on Geocaching.com, to show the solved location - there's an edit pencil right next to the coordinates on the cache page. Changing the coordinates yields these results when I'm logged in:

 

1) The corrected coordinates show up on the cache page.

 

2) The corrected coordinates show up in any pocket query that includes that cache.

 

3) A download of the pocket query and a subsequent upload into GSAK shows the corrected coordinates.

 

4) A direct download of the pocket query into GSAK - using the "Download pocket queries" option - shows the corrected coordinates.

 

Now the problem:

 

When using the "Refresh cache data" option in GSAK, the corrected coordinates are replaced with the original "incorrect" coordinates. That problem caught me recently on a puzzle cache. Luckily, I'd checked the location via Google Earth and knew where to look without having to return home to get the solved coordinates.

 

My work-a-round now is to keep puzzle caches in a separate database and use the "Get recent logs ..." option instead of "Refresh cache data" option.

 

I do all of my co-ordinate correcting in GSAK itself, never had the problem you're describing? I've just tried it on a random cache in my solved list, and it retained the corrected co-ords.

 

Actually this cane up on the GSAK forums (which BTW is a better place to ask GSAK questions) and the answer was to lock those caches in the DB.

 

Actually, the better solution is to use the Corrected Coordinates feature in GSAK. Right click the cache in the grid and select Corrected Coordinates. This allows you to continue to refresh the cache and get any changes that may have been made to it. If you lock the entire waypoint, it will never get updated. Once you set Corrected Coordinates, the coordinates are locked regardless of the method you use to update the cache.

 

This is a well known problem that the api refresh always contains the original coordinates. The GPX contains corrected coordinates, but it has no indicator in it that GSAK can queue off of to lock the field. This is something that Groundspeak will have to address, not GSAK.

[+Jeepster]

Actually, the better solution is to use the Corrected Coordinates feature in GSAK. Right click the cache in the grid and select Corrected Coordinates. This allows you to continue to refresh the cache and get any changes that may have been made to it. If you lock the entire waypoint, it will never get updated. Once you set Corrected Coordinates, the coordinates are locked regardless of the method you use to update the cache.

 

This is a well known problem that the api refresh always contains the original coordinates. The GPX contains corrected coordinates, but it has no indicator in it that GSAK can queue off of to lock the field. This is something that Groundspeak will have to address, not GSAK.

 

Thank you ... that's the perfect answer to the problem. I was changing the coordinates via the right click "Edit..." function and not the right click "Corrected Coordinates" function. That difference probably explains why some folks also had the problem and others didn't ... editing via two different functions.

[+Chrysalides]

Using Corrected Coordinates has the added advantage of being able to easily distinguish my solved puzzles from those I haven't / cannot solved. If it is a challenge cache or field puzzle, I set the corrected coordinates to the posted coordinates. It'll still flag it as "corrected".

[+Jeepster]

Using Corrected Coordinates has the added advantage of being able to easily distinguish my solved puzzles from those I haven't / cannot solved. If it is a challenge cache or field puzzle, I set the corrected coordinates to the posted coordinates. It'll still flag it as "corrected".

 

Didn't understand what you were saying until I noticed the red "(Corrected)" note on the coordinate line in the cache write-up. Thanks, that answered the question of how to tell if the coordinates were really locked.

 

A apologize in advance for maybe wondering off topic a little, but this is also a very neat feature of GSAK that I've just discovered. I've added a column called "User Data" to the grid. The data for that column is added in the "User data" field of the edit screen. In that column is where the data you suggested resides ... "Night Cache Hunt", "Solved - N 45° 45.714 W 42° 42.645", "Need Ladder", "GZ Start", "Chirp Unit", etc. That allows me to see and sort on which caches to upload for the next cache run.

 

Of course it only works if you maintain the database through refreshing (and adding new caches) rather than starting over with a fresh download each time. Refreshing the database doesn't affect the information in the "User Data" column.

Edited February 2, 2013 by Jeepster

[+The Jester]

Using Corrected Coordinates has the added advantage of being able to easily distinguish my solved puzzles from those I haven't / cannot solved. If it is a challenge cache or field puzzle, I set the corrected coordinates to the posted coordinates. It'll still flag it as "corrected".

 

Didn't understand what you were saying until I noticed the red "(Corrected)" note on the coordinate line in the cache write-up. Thanks, that answered the question of how to tell if the coordinates were really locked.

You can also add the corrected co-ord column to the grid and see the marker for those caches. Also, if you look at Waypoints=>Highlight, you can set a color indicator for the status of CC - I have one for puzzle caches without CC's so I can easily see unsloved puzzles in my grid.

 

A apologize in advance for maybe wondering off topic a little, but this is also a very neat feature of GSAK that I've just discovered. I've added a column called "User Data" to the grid. The data for that column is added in the "User data" field of the edit screen. In that column is where the data you suggested resides ... "Night Cache Hunt", "Solved - N 45° 45.714 W 42° 42.645", "Need Ladder", "GZ Start", "Chirp Unit", etc. That allows me to see and sort on which caches to upload for the next cache run.

 

Of course it only works if you maintain the database through refreshing (and adding new caches) rather than starting over with a fresh download each time. Refreshing the database doesn't affect the information in the "User Data" column.

There are actually 4 User Data columns available (and more can be added with Custom fields). User Note is even more flexible, you can add links to websites, pictures and such. The data from these can be exported as the first log on GPX exports.