Jump to content

How to edit cache coords on GPSMAP 62s?


Recommended Posts

Hey all this might be a stupid question but I'm having trouble figuring out how to do this.

 

Would like to be able to edit the coordinates that are saved for the geocache, for example if it is an unknown cache or there is coords are off and someone posted a note with updated ones. Would like to be able to do this without having to create a separate waypoint. Was easy on the etrex legend. Can't for the life of me figure it out on this one.

 

'Enter next stage' doesn't seem to do it...maybe I'm doing something wrong?

 

Thanks.

Link to comment

Use GSAK

HUH??? I think the OP wants to do it on the GPS.

 

@ieatcrayons

Enter next stage is exactly what you want. Maybe if you describe how you're trying to use it we can figure out what's going wrong.

 

As I said, GSAK. You cannot do what he wants on the GPS, you have to use GSAk to enter corrected cords and then send the caches to the GPS.

Link to comment

I agree with myotis.

 

There is no point loading unsolved puzzles onto the GPSr.

 

I have a custom filter that selects unfound, available cache s not owned by me, excluding unsolved puzzles.

 

MFILTER If=not($d_CacheType="U") and not($d_Found) and not(IsOwner()) and not ($d_Archived) and not ($d_TempDisabled)
MFILTER If=not($d_Found) and $d_HasCorrected and not(IsOwner()) and $d_CacheType="U" and not ($d_Archived) and not ($d_TempDisabled) Join=Or

 

For multistage, the "enter next stage" works great.

Link to comment

I agree with myotis.

 

There is no point loading unsolved puzzles onto the GPSr.

 

For multistage, the "enter next stage" works great.

 

Maybe I'm missing something . . or maybe there is a firmware difference between the 62 and an Oregon.

 

I have an Oregon 400T. I can load a mystery cache and use Enter next stage to enter the proper coordinates.

 

Sorry for the confusion.

Link to comment

Just out of curiosity (since I use a 60CSx and have never used a 62s)... I looked at the 62s owners manual and see very little different than the CSx in terms of waypoint/geocache management? So is it possible to just press 'find', select cache you want (which on a CSx brings up the cache screen showing name, coords, etc, with option to goto), and on that screen highlight the coords and change them there?

 

Just wondering if it'd work like that or not, as I'm considering upgrading to a 62s myself, eventually.

Link to comment

Just out of curiosity (since I use a 60CSx and have never used a 62s)... I looked at the 62s owners manual and see very little different than the CSx in terms of waypoint/geocache management? So is it possible to just press 'find', select cache you want (which on a CSx brings up the cache screen showing name, coords, etc, with option to goto), and on that screen highlight the coords and change them there?

You can edit a waypoint, but not a geocache.

 

Waypoints are stored differently from geocaches. From observation and discussion here (meaning not from Garmin), waypoints are stored internally, but geocaches are stored as index into a GPX file. The only way to edit the coordinates for a GPX is by editing the file, and the only way to do that is from another computer.

Link to comment

Just out of curiosity (since I use a 60CSx and have never used a 62s)... I looked at the 62s owners manual and see very little different than the CSx in terms of waypoint/geocache management? So is it possible to just press 'find', select cache you want (which on a CSx brings up the cache screen showing name, coords, etc, with option to goto), and on that screen highlight the coords and change them there?

You can edit a waypoint, but not a geocache.

 

Waypoints are stored differently from geocaches. From observation and discussion here (meaning not from Garmin), waypoints are stored internally, but geocaches are stored as index into a GPX file. The only way to edit the coordinates for a GPX is by editing the file, and the only way to do that is from another computer.

 

With the 62s there are different ways of doing things. The best way is to hookup your Garmin to a PC, pull out the GPX file and edit it directly using a basic text editor like Notepad in Windows. This will allow you to view the xml data which isn't too hard to figure out. Also, once you learn the basics of the xml format for the GPX file, you can create your own, drop it into the 62s and have multiple custom waypoints added in a few simple steps (this is good for example when you want to mark down several places of interest for an upcoming trip).

 

Now using just the GPS unit itself with no hookup to a PC is a little bit more lengthy and requires some patience.

 

For Waypoints:

 

Press Find->Waypoints->Select Waypoint->Press Enter->Press Menu->Review Point->Press Menu->Edit Waypoint

 

For Geocaches:

 

Press Find->Geocaches->Select Geocache->Press Enter->Press Menu->Review Point->Press Menu->Save as Waypoint->Go through steps above

 

Or alternatively, while you're in map view going for the Geocache, you can go to the Geocache menu options and just enter a next stage to add a waypoint to next stage coords. Either way, the 62s preserves all Geocache waypoint coordinates as is and will not allow them to be edited. Creating new waypoints associated with the cache name is the only way to edit the coordinates. That is unless Garmin is nice enough to provide us with a firmware update that fixes this.

 

Reference http://www.topografix.com/gpx.asp

Link to comment

Just out of curiosity (since I use a 60CSx and have never used a 62s)... I looked at the 62s owners manual and see very little different than the CSx in terms of waypoint/geocache management? So is it possible to just press 'find', select cache you want (which on a CSx brings up the cache screen showing name, coords, etc, with option to goto), and on that screen highlight the coords and change them there?

 

Just wondering if it'd work like that or not, as I'm considering upgrading to a 62s myself, eventually.

 

The 60CSX does not have paperless geocaching. The way geocaches are handled in the 60csx and a paperless GPS is completely different.

Link to comment

The "closed" file system of the 62/Oregon/Dakota make for a great way to keep track of your finds (import new PQs, mark as found / DNF, export field notes, reload new PQs etc) but can be jarring if you are used to the older units.

 

Multis are easier nowadays with the Enter Next Stage option, or you can still mark waypoints (if you make a new waypoint from within the geocache view, it will have the same name as the cache).

 

To manage puzzle caches you really do need a strategy. Easier ones:

 

1. You can solve at home and set a waypoint for the final on the unit.

 

2. You use a 3rd party geocache management program (like gsak.net). Solve the puzzle and edit the co-ordinates in the program, which will substitute the corrected co-ordinates into the gpx file that you then dump onto the unit.

Link to comment

Just out of curiosity (since I use a 60CSx and have never used a 62s)... I looked at the 62s owners manual and see very little different than the CSx in terms of waypoint/geocache management? So is it possible to just press 'find', select cache you want (which on a CSx brings up the cache screen showing name, coords, etc, with option to goto), and on that screen highlight the coords and change them there?

You can edit a waypoint, but not a geocache.

 

Waypoints are stored differently from geocaches. From observation and discussion here (meaning not from Garmin), waypoints are stored internally, but geocaches are stored as index into a GPX file. The only way to edit the coordinates for a GPX is by editing the file, and the only way to do that is from another computer.

 

With the 62s there are different ways of doing things. The best way is to hookup your Garmin to a PC, pull out the GPX file and edit it directly using a basic text editor like Notepad in Windows. This will allow you to view the xml data which isn't too hard to figure out. Also, once you learn the basics of the xml format for the GPX file, you can create your own, drop it into the 62s and have multiple custom waypoints added in a few simple steps (this is good for example when you want to mark down several places of interest for an upcoming trip).

 

Now using just the GPS unit itself with no hookup to a PC is a little bit more lengthy and requires some patience.

 

For Waypoints:

 

Press Find->Waypoints->Select Waypoint->Press Enter->Press Menu->Review Point->Press Menu->Edit Waypoint

 

For Geocaches:

 

Press Find->Geocaches->Select Geocache->Press Enter->Press Menu->Review Point->Press Menu->Save as Waypoint->Go through steps above

 

Or alternatively, while you're in map view going for the Geocache, you can go to the Geocache menu options and just enter a next stage to add a waypoint to next stage coords. Either way, the 62s preserves all Geocache waypoint coordinates as is and will not allow them to be edited. Creating new waypoints associated with the cache name is the only way to edit the coordinates. That is unless Garmin is nice enough to provide us with a firmware update that fixes this.

 

Reference http://www.topografix.com/gpx.asp

Link to comment

Not to mention that it's been several generations since one could directly edit a cache on a unit.

 

@Maingray

I think your terminology may be a bit backward there. It's the more recent offerings (Colorado forward) that have a more OPEN file system, not 'closed'.

 

When I need to deal with this issue (e.g., a field puzzle), I just create and edit a new waypoint. Once the deed is done, I re-open the original geocache listing and add found/not and field notes.

Link to comment

It's only worthless if you refuse to learn how to use it. :-)

 

My 60CSx was simple and easy to learn. I used it, along with a palm m500 for a long time, and it worked perfectly for the way I cache.

 

The palm doesn't talk with my windows 7 or windows vista computer, and I lost the cachemate program. So figured it was time to get a new GPS that was paperless.

 

Maybe I'm just not tech smart, but this thing is not user friendly.

 

By coming on this forum, and playing around with the thing I have it working, but there are several things the 60CSx would do this won't. I really don't like it.

 

I'm sure for the way most people cache it might be great, but some of the things it does doesn't fit my way of caching.

Link to comment

What is it that the 60CSx does that the 62 won't? Aside from directly changing cache data, that is.

 

If I have a few caches in the unit, and want to keep them there for a future trip, but want to add a couple for today, the new ones delete the old ones. I've been told I can avoid that by putting the caches into a file before loading them? I haven't figured that out yet.

 

If I want to delete individual caches, after finding them, or for any reason. Can't do that without connecting to computer.

 

Playing with the two GPS unit in the yard, I have found the 60CSx to be more accurate. (however, this might have to do with the way I have the 62s set up)

 

Seems like every time I have some problem, and work like crazy to figure it out, something else comes up. NEVER had that problem with the 60CSx. With the 60 I was out and finding caches in one day.

 

Even the Magellan explorist 210 I started out with was easier to use then this thing.(in fact, if the explorist had point to point mapping and a lot easier to load caches, I might still be using it. B) )

 

I'm sure that when everything is figured out on this thing, I will find it is OK. It is just frustrating that it is so clunky.

Link to comment

It's only worthless if you refuse to learn how to use it. :-)

 

Thanks for that, I find that comment to be extremely insulting.

 

I'm working hard on learning how to use it, that's one reason I don't like it, it shouldn't be that hard to learn. No other GPSr I've used was as user unfriendly.

Link to comment

What is it that the 60CSx does that the 62 won't? Aside from directly changing cache data, that is.

 

If I have a few caches in the unit, and want to keep them there for a future trip, but want to add a couple for today, the new ones delete the old ones. I've been told I can avoid that by putting the caches into a file before loading them? I haven't figured that out yet.

 

If I want to delete individual caches, after finding them, or for any reason. Can't do that without connecting to computer.

 

Playing with the two GPS unit in the yard, I have found the 60CSx to be more accurate. (however, this might have to do with the way I have the 62s set up)

 

Seems like every time I have some problem, and work like crazy to figure it out, something else comes up. NEVER had that problem with the 60CSx. With the 60 I was out and finding caches in one day.

 

Even the Magellan explorist 210 I started out with was easier to use then this thing.(in fact, if the explorist had point to point mapping and a lot easier to load caches, I might still be using it. B) )

 

I'm sure that when everything is figured out on this thing, I will find it is OK. It is just frustrating that it is so clunky.

 

So, you're right. Some of these things you can't do, and that exists on all current and recent Garmin GPS's (and maybe even the same with Magellan, but I haven't used a Magellan in well over a decade, so I'm not sure how the new ones operate)

 

The first point, I'd like you to clarify, because loading new caches shouldn't overwrite old ones, unless you're referring to loading via Pocket Queries and your PQ only supplies you with cache listings that you have not found. In which case, your way around that is to either include found caches in your PQ, run your "my finds" PQ and load it on your GPS, or go to the specific cache you want to leave on there and load it as an individual file (either using the "send to GPS" function or downloading as a single .gpx file. The only way a cache listing will be overwritten is if you load a new .gpx file of the same file name.

 

Deleting caches from your device is much faster on a computer. I even prefer manage waypoints from the computer than on the device. Your found caches will be "hidden" - they'll appear as icons on the map, but they won't show up in the "find a geocache" list, or the "nearest cache" dashboard, so there's really no immediate reason to remove them from your device while in the field. You have to connect to a computer to load new caches, so use that time to also remove caches you don't want on there. I often have not need to keep my found caches on the device, so I simply have my PQs set to return only listings I have not found. Each time I load the new PQ file, it effectively removes found caches from my device. Remember, the reason you could do these things on your 60csx is that geocaches weren't differentiated from regular waypoints. Now, geocaches are categorized differently, and you get all of the information from the cache listing on your GPS with you, which you didn't get on the 60.

 

Accuracy is a much debated topic in these forums. I can't see any reason why older antenna technology should be more accurate than newer technology, so any accuracy issues are either perceived, or potentially software related. Truth is if you take two identical units out with you (say, two 62s's), you're going to get variations in location readings between the two units. I wouldn't be surprised if there's more accuracy variation within models than there is between models (within a brand anyway). Accuracy in geocaching is also subjective, as the accuracy of the coordinates supplied by a cache owner depends on their method of obtaining coordinates - a quick read from a cell phone will not be as good as a quick read from a GPS, which in turn is not as good as using the waypoint averaging feature. So if the CO's coordinates are off, your GPS won't bring you right on top of the cache. But that's not really the point of geocaching either... once you get within 30 feet, you should be putting the GPS down and searching landscape directly.

Link to comment

What is it that the 60CSx does that the 62 won't? Aside from directly changing cache data, that is.

 

If I have a few caches in the unit, and want to keep them there for a future trip, but want to add a couple for today, the new ones delete the old ones. I've been told I can avoid that by putting the caches into a file before loading them? I haven't figured that out yet.

 

If I want to delete individual caches, after finding them, or for any reason. Can't do that without connecting to computer.

 

Playing with the two GPS unit in the yard, I have found the 60CSx to be more accurate. (however, this might have to do with the way I have the 62s set up)

 

Seems like every time I have some problem, and work like crazy to figure it out, something else comes up. NEVER had that problem with the 60CSx. With the 60 I was out and finding caches in one day.

 

Even the Magellan explorist 210 I started out with was easier to use then this thing.(in fact, if the explorist had point to point mapping and a lot easier to load caches, I might still be using it. B) )

 

I'm sure that when everything is figured out on this thing, I will find it is OK. It is just frustrating that it is so clunky.

 

So, you're right. Some of these things you can't do, and that exists on all current and recent Garmin GPS's (and maybe even the same with Magellan, but I haven't used a Magellan in well over a decade, so I'm not sure how the new ones operate)

 

The first point, I'd like you to clarify, because loading new caches shouldn't overwrite old ones, unless you're referring to loading via Pocket Queries and your PQ only supplies you with cache listings that you have not found. In which case, your way around that is to either include found caches in your PQ, run your "my finds" PQ and load it on your GPS, or go to the specific cache you want to leave on there and load it as an individual file (either using the "send to GPS" function or downloading as a single .gpx file. The only way a cache listing will be overwritten is if you load a new .gpx file of the same file name.

 

Deleting caches from your device is much faster on a computer. I even prefer manage waypoints from the computer than on the device. Your found caches will be "hidden" - they'll appear as icons on the map, but they won't show up in the "find a geocache" list, or the "nearest cache" dashboard, so there's really no immediate reason to remove them from your device while in the field. You have to connect to a computer to load new caches, so use that time to also remove caches you don't want on there. I often have not need to keep my found caches on the device, so I simply have my PQs set to return only listings I have not found. Each time I load the new PQ file, it effectively removes found caches from my device. Remember, the reason you could do these things on your 60csx is that geocaches weren't differentiated from regular waypoints. Now, geocaches are categorized differently, and you get all of the information from the cache listing on your GPS with you, which you didn't get on the 60.

 

Accuracy is a much debated topic in these forums. I can't see any reason why older antenna technology should be more accurate than newer technology, so any accuracy issues are either perceived, or potentially software related. Truth is if you take two identical units out with you (say, two 62s's), you're going to get variations in location readings between the two units. I wouldn't be surprised if there's more accuracy variation within models than there is between models (within a brand anyway). Accuracy in geocaching is also subjective, as the accuracy of the coordinates supplied by a cache owner depends on their method of obtaining coordinates - a quick read from a cell phone will not be as good as a quick read from a GPS, which in turn is not as good as using the waypoint averaging feature. So if the CO's coordinates are off, your GPS won't bring you right on top of the cache. But that's not really the point of geocaching either... once you get within 30 feet, you should be putting the GPS down and searching landscape directly.

 

I load all my caches through GSAK. If I'm going to take a trip for the weekend I check out the caches in the area and load the ones I'm interested in into GSAK. If there are some caches in the GPS I plan on going for in a couple weeks, they disappear when I load the new ones.

 

I've only loaded a couple pocket queries over the years, but didn't think that worked for my caching style.

 

While I much prefer to delete caches as I find them, I guess I can live with having to delete them on the computer. That does have an advantage that I cannot accidentally delete a cache in the field. (been there done that. :P )

 

As for accuracy. Like I said, I do think it is how I have the thing set up. I've made some changes, after reading some tips here. Need to try it again. However, when using the two side by side, the difference is often more than 30ft. Sometimes as much as 50ft. With the 60CSx being very close, 5 to 15ft. When I got the 60CSx it didn't take several months and repeated trips to the forum to get it up and running right. <_<

 

As for your last point, I have been geocaching for 9 years, and am well aware you rarely get right on the cache. You get as close as it will get you, then put it away and start looking.

Link to comment

 

I load all my caches through GSAK. If I'm going to take a trip for the weekend I check out the caches in the area and load the ones I'm interested in into GSAK. If there are some caches in the GPS I plan on going for in a couple weeks, they disappear when I load the new ones.

 

Ok. I've not used GSAK (mac user), but I'm guessing that each time you export a set of caches to your 62, it's creating a file of the same file name each time, thus why your local caches are getting overwritten. See if there's a setting to let GSAK write your files with unique file names, that might solve your problem. Be mindful of the 5000 cache limit on the 62s, though.

Link to comment

 

I load all my caches through GSAK. If I'm going to take a trip for the weekend I check out the caches in the area and load the ones I'm interested in into GSAK. If there are some caches in the GPS I plan on going for in a couple weeks, they disappear when I load the new ones.

 

Ok. I've not used GSAK (mac user), but I'm guessing that each time you export a set of caches to your 62, it's creating a file of the same file name each time, thus why your local caches are getting overwritten. See if there's a setting to let GSAK write your files with unique file names, that might solve your problem. Be mindful of the 5000 cache limit on the 62s, though.

 

Yes, that's exactly what is happening. You should look at the output options in GSAK to save to a unique filename so it does not overwrite the previous data. You might try Garmin's BaseCamp software. While it's nowhere near as powerful as GSAK, it's pretty easy to use and lets you manage the caches on the device with a drag/drop/delete file browser sort of screen.

Link to comment

If I have a few caches in the unit, and want to keep them there for a future trip, but want to add a couple for today, the new ones delete the old ones. I've been told I can avoid that by putting the caches into a file before loading them? I haven't figured that out yet.

Let's start with this simple one. I noted below that you are using GSAK. If you look at the Send to GPS 'menu', you'll notice that it uses by default the name geocaches.gpx for your output. Yes, if you keep writing over that file, you will, er, keep writing over that file. Change the name, and you can stuff several different *.gpx files onto your unit just as you desire. Some of this isn't "It can't do it", it's an "OK, new paradigm that I need to understand. How do I do this now?"
Link to comment

If I have a few caches in the unit, and want to keep them there for a future trip, but want to add a couple for today, the new ones delete the old ones. I've been told I can avoid that by putting the caches into a file before loading them? I haven't figured that out yet.

Let's start with this simple one. I noted below that you are using GSAK. If you look at the Send to GPS 'menu', you'll notice that it uses by default the name geocaches.gpx for your output. Yes, if you keep writing over that file, you will, er, keep writing over that file. Change the name, and you can stuff several different *.gpx files onto your unit just as you desire. Some of this isn't "It can't do it", it's an "OK, new paradigm that I need to understand. How do I do this now?"

Actually that sounds like it's going to get messy later down the road.

 

I use GSAK. I maintain a database of geocaches on GSAK that I refresh about once a week, or just before I go geocaching.

 

Anything in my GSAK database that is available and not found gets uploaded to my GPS receiver. It always uses the same filename. It overwrites the old file, but since it includes everything in the old file that I haven't found, that doesn't matter.

 

If I want to add just a couple, without going through the hassle, I use the "Send to GPS" button on the website. That uses the GC code as the filename, so it won't overwrite anything other than itself.

Link to comment

If I have a few caches in the unit, and want to keep them there for a future trip, but want to add a couple for today, the new ones delete the old ones. I've been told I can avoid that by putting the caches into a file before loading them? I haven't figured that out yet.

Let's start with this simple one. I noted below that you are using GSAK. If you look at the Send to GPS 'menu', you'll notice that it uses by default the name geocaches.gpx for your output. Yes, if you keep writing over that file, you will, er, keep writing over that file. Change the name, and you can stuff several different *.gpx files onto your unit just as you desire. Some of this isn't "It can't do it", it's an "OK, new paradigm that I need to understand. How do I do this now?"

Actually that sounds like it's going to get messy later down the road.

 

It could, if the user does not do regular file maintenance when loading or updating his device. I use the 'unique name' method to identify the specific area that I'm visiting. ThatCity.gpx, ThisPark.gpx, ThatPark.gpx. If we go on a caching trip, I will usually build a separate database of caches in that city. Pretty easy later on to browse to the GPX folder after we come home and delete those one or two files off the device. It sounded to me like the OP was sort of doing something like that, but not giving his 'special trip' download it's own unique name.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...