allory

With a 2gb card you can load all of CityNav and then the topo maps you are most likely to want on a regular basis till you run out of room. An additional smaller card can be used to load up a smaller area when a particular trip requires it.

On the Venture Cx the profile option only works if you have Topo 2008 maps loaded. It uses elevation info from the maps to create a profile of a route.

In DLGV32V37 you can check the lat/lon of the corners of the image. Its not difficult to create a .kml file which will open Google Earth with the image superimposed in the correct location using that information. At that point you could continue with the instructions you have for using GE. Replace the lat-lon info and the file names in the example below with your info and name the file doc.kml. The 'LookAt' values should be approximately in the center of your image. It should work. <?xml version="1.0" encoding="UTF-8"?> <kml xmlns="http://earth.google.com/kml/2.1"> <Folder> <name>doc.kml</name> <LookAt> <longitude>-106.7660</longitude> <latitude>42.53275</latitude> <range>15000.0</range> <tilt>0.0</tilt> <heading>0</heading> </LookAt> <open>1</open> <Folder> <name>Layers</name> <open>0</open> <GroundOverlay> <name>Alcova Geology</name> <color>5fffffff</color> <Icon> <href>geology.jpg</href> <viewBoundScale>1.0</viewBoundScale> </Icon> <LatLonBox> <north>42.60518333333334</north> <south>42.46085</south> <east>-106.6585</east> <west>-106.8739166666667</west> </LatLonBox> </GroundOverlay> </Folder> </Folder> </kml>

The H series has an improved chipset for gps reception. It has nothing to do with the radio portion. The H series does only show up in the 5x0 models, however, and all the 5x0 models do have higher wattage on the radio than the 1x0 models.

The Edge does do navigation. You can save or load waypoints and do goto's. You can create routes connecting waypoints. Tracks are displayed and can be off-loaded to the computer to see where you've been. No downloadable maps, but a small map page which displays the points and tracks. See the owners manual: http://www8.garmin.com/manuals/967_OwnersManual.pdf It would not be the best geocaching unit, but it has all the capability of the old yellow eTrex plus a SiRF chipset.

I know that. The header for this discussion says ONIX 200CR

I know that. The header for this discussion says ONIX 200CR

I can't say anything about performance, but according to http://bushnell.com/gps/gps_onix200CR.cfm # Runs on two AA batteries (not included) # Dimensions: 108mm (h) x 44mm (w) x 18mm (d) and any GPS that has maps uses proprietary, somewhat expensive maps.

Previous firmware versions are available at: http://gpsinformation.org/perry/etrex/venture/

If you don't mind playing the rebate game: http://www.buy.com/retail/product.asp?sku=...amp;dcaid=17653 or http://www.ecost.com/detail.aspx?EDP=34400...urce=EWB062607A

Elevation being off is a difficult thing to quantify. Elevations are certainly different than those in the older Topo for a lot of mountain peaks, but if you go to the USGS gnis site you will find that the elevations listed there are not the same as either product in some cases. If you look at paper copies of the maps the 1:24,000 series often lists a different number than the 1:100,000 series. There are differences/problems to be sure, but I'm not sure Garmin is to blame.

I used to order from them quite a bit without any problems. I'm no longer the one who orders computer supplies for our department so haven't dealt with them in a couple of years. I would, however, order from TVNAV.com. I've purchased several gps from them without problems and their price is only $215 plus ~10 for shipping.

http://gpsinformation.org/perry/etrex/vista/

There is no calibration, you are stuck with the discrepancy. There are several reasons why they are different. Your GPS elevation is the least accurate of the information it will give you, typically 50% more than the lat/lon error. The elevation on Google Earth is based on a digital elevation model which will return the average elevation for a cell, probably a 30 meter square. The precision of alignment between your GPS info and Google Earth is not always precise (regardless of datum settings), and you may be comparing a GPS elevation to a GE elevation which is not only an average, but from up to 200 meters distant (based on my efforts). So, while you might prefer to be closer than 84 feet of difference, you can't count on it.

The thin horizontal lines on mine will alway clear up if I toggle the backlight on and off.

There is also a significant size difference between 2.53 (1.44 mb) and 2.57 (8.29 mb), which would make me nervous about what it might do to the basemap. The XL update v. 2.10 is also large and claims to update the basemap. While Magellan has not made it easy to get firmware for units unless you have a serial number, there are a few updates archived at http://gpsinformation.org/perry/magellan/, including eX210 v. 2.53.

Only off a bit, they're called the 520HCx and 530HCx and still have the lithium ion battery. (press release)

Case in point. This afternoon Garmin posted v. 4.20 for the 60C, 60CS, 76C and 76CS and 2.70 for the Legend C and Vista C. For some reason the daylight savings time issue is not addressed. https://buy.garmin.com/shop/store/downloads...167&pID=263 Changes made from version 2.60 to 2.70: * Improved support for Macintosh USB. * Corrected support for certain carpool/toll roads types in Austria and Switzerland.

Actually, just last week Garmin posted updates for the Streetpilot i2, i3 and i5. They have been discontinued for a while. They do it, but you shouldn't count on it being a high priority.

Garmin has only posted the Vista version but the others are available via WebUpdater. I was even able to update mine from a mac. http://www8.garmin.com/support/agree.jsp?id=1393 Changes made from version 2.60 to 2.70: * Updated daylight saving time dates. * Add capability for 2 wide data fields on map, compass, and highway pages. * Add capability for 1 wide data fields on map page. * Add data card information page. * Add selectable alarms for proximity waypoints and custom POI. * Improve labeling and scanning of custom POI on the map page. * Add capability to see vertical profile of an autoroute using DEM topo data. * Fixed issue with incorrect dates showing when editing the data field for Sun & Moon page and Hunt & Fish page. * Fixed issue where invalid find menu options could show when using the Auto Order feature. * Fixed issue where route names would be converted to upper case during editing. * Fixed issue where invalid related software can be selected when using the WebUpdater. * Fixed issue where keyboard characters won't update when editing the Welcome message.

If you go with CityNav you can fit all of Oregon on a 32mb card. If you have a 64mb card you can fit all of Oregon and Washington, or do Oregon with both CityNav and Topo. If you spring for a 1gb card (not too hard to find under $20) you can do just about anything most people would need. Salem coverage looks pretty good, check out the Garmin's map viewer to see what's available.

Actually, the last press release said that Training Center would be available by the end of the year, and that at that time they would have info about other products. When they did release Training Center they said that WebUpdater and POI Downloader should be available in 2007Q1. No word yet on MapSource, except that they aren't giving up.

I've had a problem with a date bar up near the top of the screen. For some reason it often defaults to Sept. 2004 and won't show tracks or points which are newer than that. Click the slider and drag it to the right and everything should show up.

Its a pain, but I have taken the data from the kml file into excel and subtracted a certain amount from both lat and lon to get the track log lined up with what shows on Google Earth. When you're creating a geologic road log for educational purposes its handy to have things look correct.

Sorry I wasn't clear. You do get to enable or disable whole sets, not just individual segments.