Cgpsmapper Routable Cracked
Cgpsmapper Serial Serial Numbers. Convert Cgpsmapper Serial trail version to full software. CGpsMapper software - the only official place to get the cgpsmapper program, solution to make own maps. Maproute is a suggested tool for creating routable data from spatial data.
I've noticed it since MapSource 6.14.xx, 6.13.7 was the last version that didn't have the problem for me. These have all been from maps I've made myself, so I may be missing some command line switches that would clear them up. Some images and a discussion thread posted below. I think it has to do with the way the newer versions of MapSource cache imagery. Control-G hit twice will flush the cache and clean up the image with newer versions. The first Control-G may blank the screen. The second will bring back a cleaned up image.
I don't have that problem with maps I compile with cgpsmapper, but those are usually semi-transparent and non-routable, usually just topo, hydrography and woods. My mkgmap compiled maps are non-transparent and routable with a full range of data types. I don't notice the problem with Garmin's City Navigator products, but the level of detail on those is much lower than a comparable area with topo.
Last edited by Seldom (2010-05-28 18:33:58). Thanks for your comments. I used to run 6.15.11, I think, whatever the latest version before 6.16.1 was. This worked fine for me. I have tried Ctrl-G, but it only toggles 'Basic Map Only' display. In OSM maps the basic map shows nothing at all, so yes, I can zoom without problems, but it's not useful. As soon as I press Ctrl-G again it switches back to normal mode and the screen corruption occurs again.
I'm going to try this out on another PC with a fresh MS install and I'll report back. And don't expect any amazing discoveries.
Cheers, Peter. @beddhist: What kind of maps are you using? With my maps (compiled with mkgmap rev 1647) and Mapsource 6.16.1 (on a Windows Vista pc) I don't see any problems with rendering. @seldom I'm sorry, I didnt notice you mentioned it already No big deal about control-G. I'm running Win7-64bit. MapSource 6.16.1 NVidia GeForce GT220 1024MB Video RAM.
Samples of the MapSource rendering follow. Rendering is same in BaseCamp. Blurry OSM Image. Clean OSM Image after Control-G. Transparent or Non-transparent images generated with cgpsmapper don't render this way. See below: This cgpsmapper generated image cleanly at all zoom levels.
The image was of a non-transparent map. Transparent maps are identical. Note the difference in background color. Last edited by Seldom (2010-05-30 18:58:40). I suspect this may have to do with the Map Selection Area Polygon (0x004a) and/or the Map Coverage Polygon (0x004b). The OSM samples above were compiled as non-transparent maps, but the gray background is the same color as the NoMap color in MapSource 6.16.1.
So it looks like 6.16.1 may be treating the OSM maps as if they had no background. The light beige in the lower right of the following image is the standard background color. Also note the yellow map selection polygon highlight is offset from the actual map bounds. This is a routable map, so the actual limits of the map selected are the bottom of the horizontal contours and the right side of the vertical contours, but the gray background aligns with the map selection area. The selection polygon offset has no effect on the routing. I posted this on the mkgmap developers mailing list and got this reply: Peter Hendricks wrote: > > Hi, > > > > Sorry if this has been discussed before, but I did search the list and > > couldn't find any reference.
> > > > I'm using maps from OSM, downloaded from here: > > > > > > Ever since I upgraded Mapsource to the latest I'm getting the screen > > corrupted when zooming in. Details are currently discussed here: > > > > > > I would have thought that the developers would be aware of this problem, > > but can't find any reference to it.
> > > > Cheers, > > Peter. > > I also have MapSource 6.16.1 and I don't get this problem, so it's not universal. Laughing in the wind 2001 eng sub indo. When I have been messing around with self-generated maps in the past, I have seen this problem occur (with older versions of Mapsource) but that was due to the bounding box of my data not being converted to Garmin coordinates properly so the map 'border' was offset from the actual map data. -- Charlie ------------------------------------------------- Is the problem with how the tiles are split, then?
