Topics

A few days ago I downloaded the NLCD 2006 landcover database from this site:
http://www.mrlc.gov/nlcd06_data.php

I was able to view an image of the data in GM, but couldn't extract any of the data.  When I dragged my cursor over the colored portion of the image, GM reported PAL IDX 0, and RGB(0,0,0).  Also, when I zoomed in to the image eventually it went black, but I could zoom out and the color returned.

I reported this to Mike, who tested it at GM and who had no problem opening the file, but couldn't suggest any reason I couldn't open it.  From this I conclude there must be something weird on my local PC.

Later I obtained the same file as a GeoTIFF and GM opened it fine (using only 36% of my available memory), so I don't think my available memory was the problem.

My system is has an  i7 processor and 8 GB RAM, and I'm running Win7-64.

I'd appreciate any suggestions.

I have a large number of files I'd like to modify with GPSmapedit overnight.  To do that I'll need a way to pass commands from a batch file to the program.  I'd appreciate any tips.
Thanks.

This is becoming a hijack.  Should move to map making.

I learn something new every day.  I use color/no color patterns in the TYP files for land cover in Desert Southwest, but I thought you had to compile them with "Transparent=Y(or S)" to get them to read through to another map.

I just took my 62s to the Grand Canyon and walked down the North Kaibab trail to Phantom Ranch and up Bright Angel the next day. (Not 1 day RimtoRim like the fanatics do it.)

Track recording method was set to Auto and recording interval was set to Normal. 

The hike from North Rim to Phantom is listed as 13.3, but the 62s showed 17.3.
The hike from Phantom up Bright Angel is listed as 10, but the 62s shows 11.

The added mileage can be seen on  the track as series of spurious track points, some hundreds of feet off.

Anybody here found settings to minimize these errors?

The Beta's out:
http://tech.groups.yahoo.com/group/global_mapper/message/12579

I'm trying to generate a hillshade map of the continental US.  The grid could be about somewhere between 6" (finest) and 30" (coarsest).  The coarsest I can find on GM is the SRTM is 3".  I could live with that, but the download is taking forever.  (An hour with 0% progress.)

I uploaded a Mac version of Desert Southwest about a month after I uploaded the PC version, but the Mac doesn't show up on the download dialog.  I recall having a PC/Mac choice in the original map upload dialog, but it doesn't appear to be there now.

Desert Southwest has more National Parks in UT than AZ or NV so I picked Utah during the upload dialog. But the AZ section contains the Grand Canyon, Petrified Forest, and Sunset Crater, and the NV section runs from Lake Meade to Great Basin.  Is there any way I can get this map to show in the NV and AZ lists?

When I hook either my OR or 62s to BaseCamp I can only pick the Basemap to show in BaseCamp.  The maps in the gmapsupp.img don't show at all.  OS is Win7-64.  BaseCamp is latest version.

IIRC, older versions would show maps that were on the GPSr.

Is there a way to specify a download area in the National Map Viewer by lat and lon rather than by quad or map extent?  I can't find it, and I'm going to miss the Seamless Server when it's decommissioned.

When I install Desert Southwest using MapSetToolKit the "Find Places" tab works.  When I install it using the map installer script I downloaded on 5/5/2010, "Find Places" is grayed out.

I started uploading a revised Desert Southwest last night about midnight and went to sleep.  When I woke up this morning it appeared to be uploaded, but with the number of fails I had when I uploaded it Sunday, I can't be sure.  Is there any way to check the file date of the uploaded map?

I've just finished a routable topo with 40' contours, land ownership and wooded areas that extends from 40 N to 34 N and 116 W to 109 W.  It's handy as a single map, but the installer works out to be 400 MB.

Is that too big?  If so, please recommend sizes I should reduce it to.

So far, I've figured it out by experimentation, but some things are hard to figure, like "Map Skins".  I believe these are to make the GPSMapedit screen resemble MapSource more closely, but I don't know how to generate one.

I'm working on a routable map of Northern Arizona.  It includes South Kaibab trail, Bright Angel trail, and North Kaibab trail, connecting North Rim and Grand Canyon Village.  So I've got a reasonably straight pedestrian path from Kanab, UT to Grand Canyon Village.

If I make a route that's less than about 40 miles long from some point on highway 67 to Grand Canyon Village the route takes me down into and across the Canyon.  However, if I increase the travel distance to 50 miles, the route takes me north on 67  to US89Alt, south on US89 and east on AZ64, as if I were hitch hiking.

If anyone can test this behavior on a genuine Garmin routable trail product, or is familiar with this behavior, I'd appreciate hearing from you.

This error shows up just before the end of a map compile. 

Anybody here besides me ever gotten it, and, if so, were you able to fix it? 

Running a search on this site I see that the only other mention of it was by me, in conjunction with vectorized tree graphics.

Thanks in advance.

None of my links have worked all weekend. I'm looking for California Land Status shapefiles and abbreviations for New Mexico and California.

Thanks in advance.

Now that REI's selling a 62S for 279.99 I'm wondering whether to buy it or not.

Features I miss on my OR300 that I had on my 60 CSX are the external antenna port and the round Garmin serial port.  From what I can see on the Garmin's 62S page the 62S has neither of those ports.

Can a 62S owner please confirm that?

If I'm right, since I don't geocache, the only benefits of a 62S over my OR300 would be the 3 axis compass, an easier to read screen, and, perhaps, the buttons.

Thanks, in advance.

I've got BLM set to all CAPs in my GM package file and it shows correctly in GPSmapEdit.  The KFC POI is also set to all CAPs.  KFC shows up correctly, but Blm shows up with only the first letter capitalized.  Anybody figured a way around this?  Or better yet, why KFC works and Blm doesn't.  The last Western Ownership map I downloaded also had this problem.

Does the Data Level matter for an 0x4b polygon?  I suspect it doesn't, but if anybody's had problems with it, I'd appreciate your comments.