Messages

I have a 2GB micro SD card with City navigator 2009 on it. It does not say Garmin, but I am guessing it is from garmin since it is so difficult to copy the map onto other cards. I was wondering if it will erase my map when I put some topo maps on it. When I put maps on my GPS it will usually erase my old maps on the card that are not highlighted, and I would hate for it to erase my city navigator.

I compared NW topo with Washington and Idaho. Idaho topo was spot on every time, and washington, I only had one spot that was one foot off. In NW, it was anywhere from two feet to nine feet. I compared Utah topo with SW topo and the Utah topo was accurate every time whereas SW topo was off about two to nine feet. I was just curious if they got their data from two different places, and if so where.

The USGS GNIS to GPX Converter is not working at all anymore for me. Everytime I try to convert a file it takes forever, then says "500 internal service error." Is this happening for anyone else, and can it be fixed?

As I have been using the topos from this site (all of them amazing, and very difficult to create), I have noticed some differences. In the Northwest and southwest topos, the contour lines are anywhere from two to 9 feet off of real elevation (to find this I make a waypoint on a contour line and then view it in google earth). When I do the same with the individual state topos, they have all been spot on, with the exception of one time when it was a foot off. I was wondering where each of them got there contour lines, and how they got off from each other. More of a curiosity question really.

I just bought a garmin gpsmap 60cs from someone today. It came with a 2 gb micro SD of city navigator NT 2009. It works great on the gps, and I think it is an original SD from Garmin since they are nigh impossible to copy over. What I wanted to know is if there is a way to unlock the map from my SD card onto mapsource. It would be junky not to be able to use mapsource for city navigator. 

I did select feet when it gave me the option - and it shows feet in the title (eg - Borah peak - 12,510ft) but in the properties of the POI it had over 41,000 ft in the elevation space. That is what is confusing.

I loaded the summit POI's into mapsource (opened it) after using the .GPX converter. Works great, but the elevation is off. I set it to show elevation on the title. The elevation on the title is correct (eg - Borah Peak - 12,510ft), but when I go to the properties, it says a different elevation (eg - Borah peak says around 41,000ft). I looked in the .CSV file to see if it was grabbing the number from elsewhere, but could not find any. Any reason why this may be happening?

Seems to work. Thanks much. Makes things a lot easier.

I went to the site, but could not find and .GPX files t download into POI loader. Am I not looking in the right place?

He John M., I think you kept the same ID number for MW as you have for NW, or else something is causing them not to work together like NW and SW topo use to be. I was wondering if that was fixable at all. Thanks.

The SW topo's ID was changed, and they both work together for Windows (it does on my computer). Try uninstalling what you have, downloading them again and installing them again. It should work just fine on Windows. If you have the Mac version, then you need to wait for Oz to fix it.

Looks like another job for John M. - He said in the NW/SW topo problem that he would fix the ID number for MW, but I guess he forgot. JOHN M. PLEASE HELP!

Now, when you say they were off, was the elevation off as well, or did it say (example) "12,000ft" at 9,000ft?

i looked on that site, and I am somewhat confused. On the topo maps (and even on the USGS website) it shows Borah Peak in Idaho at a 12510ft summit, but then it also says the highest point is 12662ft. Is there a reason that the summit is a different elevation from the highest points on some mountains? (Ex. -  http://geonames.usgs.gov/pls/gnispublic/f?p=116:3:1059039279243257::NO::P3_FID,P3_TITLE:378037%2CBorah%20Peak)

Is there a place that I could find summit point of interests that I could load with the POI loader. It would be nice to get summit POI's for the entire US, but Idaho and Utah could do.