Dosido

Geocaching is the antithesis of the One Red Paperclip experiment.

It doesn't "move" the cache, it simply makes a note in the geocache_visits.txt file - the GPX file is unchanged. Well, they aren't intelligent, but you are given the option to filter out 'found' caches when creating the PQ.

This may be as designed. Did you 'uncheck' the "Ignore logs before..." box when uploading? If not, it will ignore logs before that date, and not upload them.

I've seen the 'drift' 3 times - once nearly 500' in error. However, I haven't seen it in quite some time - probably two months now. But it's frustrating to know it's a possibility, as whenever I'm out geocaching, and don't immediately find the cache, that's the big question that pops up - what's my accuracy here? So, while I would heartily recommend the Colorado for geocaching in most cases - I don't think I'd want to be on the hook for sending someone out where accuracy of position is potentially a matter of life and death using this unit.

This is the response I got via email when going back and forth with the location error/drift issue: So, not much help, but they did acknowledge that they know about the issue.

Links in logs now point to the cache page that the log is on, and no longer point to the linked page.

This was buried in another thread, and it doesn't appear to be available online, but it is via the web updater. Firmware 2.6 Not sure how much was already captured in 2.54, but they do say that they fixed the shutdown issue when deleting a waypoint from the map... Changes from version 2.50 to version 2.60: Added ability to turn elevation shading off, included in user profile settings Added ability to log a comment with geocaching Field Notes Added ability to save map selections to user profile settings Added compass setting to saved user profile settings Added tracback along current track Added ability to determine public land survey or USGS Quad name for Topo 24k HD cartography Added progress bar during software updates Added error message when the max number of geocache or gpx files is exceeded Added ability to search near a map point Added ability to use the map to add a point to a route Fixed shutdown when deleting a waypoint from the map Improved odometer distance calculation Improved Wherigo engine Improved backlight behavior Improved compass / GPS heading autoswitch behavior Improved keyboard behavior in address & intersection searches Improved behavior in low battery state Improved behavior of turn-by-turn route recalculations Improved map drawing to eliminate redraws when not necessary Improved map drawing to reduce partial map draws Improved map drawing to enhance appearance of trails Improved usability of WGS84 by listing as a datum rather than just a spheroid Improved automatic track archiving when archiving very lengthy activity segments Improved button behavior when logging geocache attempt Improved stopwatch timing Improved distance precision when reviewing a point and tracks. Improved inter-tidal color in non-marine colors Improved readability of geocache_visit.txt Increased maximum number of GPX files processed to 200 Corrected guidance text to not truncate streets when not necessary Corrected behavior of proximity alarms in custom points of interest Corrected potential issues that prevented user alarm from sounding Corrected map drawing above 75 degrees latitude Corrected potential issue when attempting to delete profiles Corrected issue that generated extra waypoints at poweron when 'Mark Waypoint' was the first listed shortcut Corrected potential issue preventing 'Waypoints' from being listed in 'Where to?' Corrected issue that prevented poor signal strength messages from disappearing if a fix was achieved Corrected calculated issue that prevented complete display of large numbers Corrected specified schema path for GPX files Corrected Dutch keyboard to include 'Z' for address searches Corrected User Grid to retain settings between power cycles Corrected User Grid to allow 'E' and 'W' for longitude origin entry Corrected shutdown issue when unit has empty Saved.gpx file Corrected issue of missing active route when you select 'GO' from the full screen map in geocache mode Corrected issue when selecting a custom poi from the recent found list after it is removed from the system. Corrected issue when selecting units on the stopwatch page using non-English languages. Corrected issue when you spell a geocache and the list doesn't reduce when the keyboard auto-pops Corrected issue where you can't get to a hint for a geocache once you set it to found then back to unfound Corrected issue where the chart information option would show up incorrectly Corrected duplicate entries in the other menu when in page loop mode. Corrected external power lost message in non-English languages Corrected issue with waypoint symbol selection shutdown Corrected issue where the unit will hang when you try to restore a Wherigo cartridge. Corrected potential shutdown going to mass storage mode when you have custom POI's loaded Corrected issues with Cyrillic characters

I was trying to get nRoute up and running with my Colorado on the laptop. So far, while Spanner is working (albeit with tons of drops), both nRoute and Streets & Trips 2006 have no problem connecting. (Edit to say that nRoute is finally working too...)

Check out this thread on the C230 for a sample POI file to upload, and info on exporting POIs with GSAK:

Good point! The work around now, I guess, is to show found caches, mark the cache as unfound, and then mark it found, writing a new comment. Both caches will show up in the 'finds' file, but at least you'd have the correct number on the 2nd one...

I don't really mind not being able to edit/see the note - I actually use it the same way I used my Palm - I'd screw up the graffiti on occasion, but I didn't care as it wasn't going right onto gc.com - it was just to remind me what I did - left TB, etc. So, not a deal breaker for me. I write much longer online logs than I'm willing to plug in on either the palm or the Colorado.

The dumb thing with the CO is, however, that you can only put one decimal place in, regardless of whether you're entering miles or feet. So, to get the projection accurate enough to easily find a cache, you need to convert any miles given to feet, otherwise, we're off by a considerable amount! Fortunately, the recent cache I did with a projection requirement gave both miles and feet, making the job easy.

Is there a place on the Colorado that I can view how many waypoints are stored on the unit? Something like xx of 1000 waypoints used? A status page of sorts?

I don't see how this is a bug - there's a 2000 cache limit for the unit, so I wouldn't expect that a 6000 cache file would work.

Scott, That was the difference - Guidance was 'on road' in my geocaching profile. Not sure how I missed that!

Hmm...not what I see at all... I setup automotive mode with both CN and Topo selected. Geocaching mode with only Topo selected. In automotive mode, I then went to Geocache->Select Cache-> (gives me a geocaching screen with CN map and straight line to dest.) Now I select Options->Goto Location and it autoroutes. I then change to geocaching mode (profile change->geocaching), and I get an autoroute shown a Topo map.

Ditto here, but if you click 'done' before you hit the next letter that brings you to less than a full page, you'll still get the filtered results. A less than elegant solution, but a workaround for now... Interestingly, this doesn't seem to happen when search/spelling out waypoints - only geocaches.

I have no problem viewing cache descriptions, etc as webscouter does in 2.54. Seems to me that the ability to save the map preference to a profile doesn't help much, if the unit still won't auto-route to a geocache unless I specifically select the CN maps in geocaching mode. It still continues to auto-route if I deselect the CN maps once the route has been calculated, however.

Ahh...you are correct! Too late to edit my post though.

I like Option 3, and then goto the compass screen, which will show you distance to 0.01m

I came over from a Magellan Explorist 500. Interestingly enough, I had no real drive to get a 60csx, even though a frequent caching buddy had one. Both the Explorist and 60cs had nice features, the custom POIs on the 60 series was nice, but not nearly enough to tear me away from the Explorist, which had some better features than the 60 - faster text input, could hold unlimited 200 cache files, unlimited maps. However, once the Triton came out, I lusted after that - until it was released. Utter garbage, and that from a company whose customer service went from excellent (when I first got a GPSr in 2000) to horrible after the Explorist release. So, when the Colorado was announced, I was ready to jump ship. I got my Colorado 400t about 5 weeks ago, and haven't turned my Explorist on again! I added CN 2009, to autoroute, and use it primarily for geocaching. I've got a few minor quibbles here and there, but I had them with the Explorist too. The 60 series has limitations, as did the Explorist, as does the Colorado, they're just different animals. However, the added features on the Colorado: larger screen, geocache data onboard, GPX drag and drop make it a clear winner for me.

I'm not sure if this is typical of the Garmin line, so perhaps it's the same as the 60 series and not a bug. I uploaded a track, set it to display on the unit, and when I power cycled, it was turned off again. I would've expected it to remain displayed until I chose to turn it off. On the same topic, while it is mentioned in the issues list, why in the world is the show track option under 'where to?' ?!?

There have been two caches put out for me to be the 'ceremonial' FTF. Both times it was requested that people wait until I find the cache before they hunt it. Both times, while I was away, my daughter went out with a good friend and placed a cache. I then went to find the cache with the kids in tow, so they could have fun watching me find 'their' cache. I appreciated the gesture, and the cache, but there is a little bit of pressure to get out and find the cache quickly, so that others could go find it without feeling that they were doing something wrong. We found both caches within a couple of days, and both times, others had logged them before us, so while the request was put out to allow a 'reserved' FTF, others had already been there. In no way, to me, did that reduce the fun I had finding the cache with the kids. All that said, I think it'd be better if the 'reserved' FTF caches were simply written up on gc.com, printed out, and given to the honoree, and only published after the ceremonial FTF thus eliminating any possibility of bad feelings on either side of the isle.

That'd be yesterday's Woot. You're a day late!

You didn't say which Mio you have, but there are skins for geocaching that you can add to some Mio portable units - adding a compass pointer, etc. However, barring a skinned unit, set the vehicle to 'pedestrian' under the "Route" menu, and make sure that 'keep position on road' is unchecked (find on the advanced settings screen). That ought to help out quite a bit!