apersson850

Yes, when there was a single drive letter gap available on the computer, then another free letter further down the alphabet. It wasn't the Colorado, but another dual-drive Garmin GPS, so I don't think that matters. This isn't likely to be a frequent problem, but it could occur.

Maybe it's an ability to display extended information that's not at the moment included in the POI data in the maps? Could be some "get ready for the future" thing.

To further clarify (also in relation to the post above the previous one): Which drive letter Windows assigns to the Colorado's internal drive(s) depends upon which other drives you have. On my computer, which has a diskette drive, four harddrives (one split in two logical drives), two DVD players, four flashdrives (card readers) in the computer, one card reader in a printer, one or more USB drives, one network drive in a router and some drives mounted on other computers in the network, the Colorado often shows up as P: and Q:. Look for the Garmin icon (blue triangle) in the list in Windows Explorer, and you'll find it.

Or rather you didn't understand the answer... The procedure RFtinkerer gave you is what you can do on the Colorado. The list of turns can't be modified on the newer Garmins. It's the same with the nüvis, for example. Unlike them, the Colorado does allow you to configure the map data fields. By opening the turn preview for a turn, you can see both distance and time to a turn.

How much free space do you have on the internal drive?

I assume you are just joking, as it's not even mentioned for any of the two units you linked to.

Being an electric systems designer, I say it's a signal timing problem. Sometimes, firmware changes can fix these, sometimes not. My unit changed its behavior after 2.40, but it didn't fix the problem. Perhaps units "slightly ill" are fixed, while those "really ill" aren't cured completely?

Yes, if not always.

Well, that I don't know if it does. What I know it does is that when the current log overflows, or rather soon will, then the oldest part is removed and archived automatically. But if you clear the active log, then it will not overflow, so then perhaps you don't get it archived either. I haven't checked this, as I normally never clear the active log. If I do, I can't see where I've been. The only reason I can see to clear the current log, is if you want to archive a specific activity by itself. As selecting a part from a full active log doesn't work properly, that requires either that you do it on a computer or that you clear the current log before you start the activity you want to archive. I find the first alternative to be better. It's more flexible.

I haven't tried, but someone said that it will list all cahces, that are listed in the file that summarizes your activities, as found. To me, it seems that the best thing is to not include found caches in your PQ, as they will then be listed as found as long as you have your log file in the Colorado, and the next time you install a new PQ, assuming you have logged on the net by then, they'll not be included.

You get parts of it from Setup -> Tracks, parts from Where to? -> Tracks. You don't get it all, though. Tracks are already archived automatically on the Colorado, but in internal memory. Works even if you don't have any card. Logging is done in a way which reduces the amount of files, instead of spending one single file for each and every day. The Colorado method is more based on location than date. Seems logical for a navigation device.

I've seen some such issues too. The sensible thing for a limited parser is of course to just disregard anything it doesn't understand. Sometimes it's tricky to understand what you don't understand.

Here's a snip from the data descriptor in the Colorado, showing that GPX data should go to the \Garmin\GPX folder. <Name>GPSData</Name> - <File> - <Specification> <Identifier>http://www.topografix.com/GPX/1/1</Identifier> <Documentation>http://www.topografix.com/GPX/1/1/gpx.xsd</Documentation> </Specification> - <Location> <Path>Garmin/gpx</Path> <FileExtension>GPX</FileExtension> </Location> <TransferDirection>InputToUnit</TransferDirection> </File>

More likely in a \Garmin\GPX folder on the card.

I hope I made it clear that I'm talking about two different situations: 1. Reading the map while moving through the terrain. 2. Panning the map while being elsewhere. Competing in orienteering since 1972 have taught me the benefit of item #1. When you desire efficiency, there's no option. But when panning, I want the same reference each time I do it. Then north up is the most logical one. That Garmin units revert to north up when you zoom out is just because when you do that, you are looking for an overview. You can't orient yourself relative to things you see around you anyway, as with these scales, they aren't visible on the map. Hence north up. Exactly what I suggest. For overview north up, but for checking your progress in the terrain track up.

OSGB = Ordnance Survey Great Britain France is a complex issue. Just look here. Garmin supports three different systems for Sweden. Their old definition for Rikets Nät, the improved definition (called RT90, which really is a map datum) and the new system, SWEREF 99TM. Garmin units not supporting this are the simple road navigation units, like a nüvi.

Well, I have at least not got it to work, with custom POI files. I installed the same file as I use in the nüvis, for example, and it gives camera alerts with the Zumo 550 and the nüvi 760, but the Colorado was silent. It can find the cameras, though, if you want that.

I think everyone who assumed it was just a GPSmap 60 CSx+ were disappointed. I looked at it as a fresh restart for a hiking/all purpose GPS, and liked the idea. I didn't like everything in the implementation, but frankly, there are several features in the 60 CSx I've only used once: To test that they worked. But I didn't read any advertisements (there weren't any, as I got it before it was officially announced), so I was never tricked by something that seemed to promise something I could interpret as something it really was not.

All right, now I see what you mean. As geocaches are a different kind of animal in a Colorado, compared to waypoints, I doubt we'll see any ability for the Colorado to edit the GPX file the geocaches came from, or the cache database that's built from these GPX files. Maybe, but I doubt it. It probably depends upon how they've structured their database, and its relation to the GPX file, if this is easy or tricky to implement. Waypoints are something else, and for them, I can't really see a very much more efficient way of modifying the coordinates than the present one. Which also was what I responded to, as I thought that was what you were asking. As it is now, you have to create a new waypoint, with the next step of that multi, and head for the waypoint, but read the hints and description for something elsewhere, as the original location of such a multi isn't where it really is. I understand this 100% now, but didn't at first. There aren't many multi caches around here. No wonder if the stupid change to panning in track up also ruined the smooth panning, in addition to wrecking the whole idea of panning all together. Wouldn't that be typical? The beauty of track up is that you can easily compare the map view with the surrounding terrain, as you move through it. But as soon as you start panning, that reason for track up disappears, as you no longer can see the terrain around the point you've panned to. If you could, you wouldn't need to pan. So, when panning, it's much better to have a consistent reference, and then the old map book principle of having north up is just as good, or really better, than anything else. It's especially significantly better than having a new direction upwards on the display each and every time you enter panning. This used to work well on the Colorado, but constant whining about it, from users who probably hadn't thought all the way about this, made them destroy it. Or whatever the reason was. But it feels like "you asked for them to ruin it, and they did". Fortunately, if you use the perspective mode instead of the vertical projection track up mode, it will all the time pan in north up. As long as they don't ruin that too, at Garmin, it works pretty well anyway.

Proximity alert is an alert that sounds when you come within a certain radius from a user defined waypoint. A speedcam alert is when you come within a certain radius from a custom POI, and also are above a certain speed (for a camera). The Colorado doesn't support any of these. The 60 CSx supports both. nüvis support alerts for custom POI. Trackback is the option to be guided along a recorded track, in any direction (either back to where you came from, or once again along the track). The Colorado supports this in the context of redoing the recorded journey once again, not going in the opposite direction. If you want to follow a track backwards, to get you out of wherever you went in, you have to follow the graphical representation of the track on the screen. If there are roads available, you can let the unit compute an autorotue to your origin, if you have the maps supporting autoroutes.

Even if the chips aren't the same, they are working according to the same principle.

Provided the detailed map you've installed supports autorouting, the GPS will indeed use all roads on it. But for longer stretches, it will try to stay out of the smallest roads, of course. Particularily if you selected shorter time as your preference. The Zumo is the only Garmin GPS that interacts with Mapsource in such a way, that you get an identical route, when you transfer it to the GPS. If that's important, that's the unit to get.

Only with DEM maps. City Navigator does not support 3D view.

Are you serious? The current method takes two presses on the Enter key, as well as a few clicks of wheel turning, but that's so easy to do that I don't count it. Then you are at the coordinate entry screen. How much simpler do you think it could get, without getting in the way of the most common thing, i.e. store a point here? Regarding the USB cable, I don't really see the benefit? The only thing it will do is that you don't need to remove the cable. Pulling a USB cable out is about as much work as flipping a switch. The rest would be the same anyway. You could loose millions...

Trackback exists, or rather track forward, as it will guide you along the track, the same way as you did the trip when the track was recorded. If Garmin intended the Colorado to be just an upgrade from the 60 CSx, not a different development route, then it would probably have everything the 60 CSx has from the beginning. From that, one can guess that they don't intend to include everything the 60 CSx has, but support some of it and add a few other new things, that aren't on the 60 CSx at all. As far as I know, the 60 CSx doesn't switch to the map page just because you reach a waypoint? Or are you referring to the turn previews? Or maybe it does, but I've never noticed.