Messages

It seems, the new version 4.2.1 MapInstall (October 30, 2019) in Basecamp  4.7.1 works correctly.

http://www.gawisp.com/perry/mapsource/BaseCamp_462.exe

As I know, the GPSMapEdit can't read the TYP file. You have to use the source text file.

You can find the documentation about types in chapter 12.3 of the manual. The reason of different view in Basecamp and Mapedit could be in the TYP file. Try to choose the same TYP in the Mapedit (View, Map skin) as you use for your map.

I think the best information is in the manual for cgpsmapper http://www.cgpsmapper.com/manual.htm.
@Red90  You right, level0 has to be 24 bits only for routeble maps.

Level0 has to be 24 bits.

I am missing the command POIIndex=Y in the file GuamMap2015.mp in the section [IMG ID]. See cgpsmapper manual:

POIIndex=
N - objects will be indexed only if POI index info is explicitly provided
Y - all POI objects will automatically be indexed (may be searched by the Find function in the GPS)
Default = N

I have used the Insight Map Creator to create a map of USA inland waterways - see waterways.cz/lowrance.php. I hope, it will help all people on the water.

I read the post from Popej and it is obvious not only from this post, that Popej knows about creating of maps much more than me. But ...

What does exactly mean "cgpsmapper only supports to 24-bit"? When I use level0=26, the is no error at the compilation and I can read in the log, that all object were succesfully imported into layer 0. And, as I wrote, the result in Mapsource is better than by using 24 bit (you can see isobaths in the same place with 24 bit and 26 bit in attachments).

Of course, the discussion about this is useless, because the map with 26 bit is not visible under ceartain zoom. Discussion is, how prevent cgpsmapper from distortion the lines.

SimplifyLevel doesn't help, because input data are correct and therefore I use Preprocess=N. Even when I used Preprocess=Y and SimplifyLevel=3, the picture was the same - distorted.

May be there is no way (see discusssion  at page tech.dir.groups.yahoo.com/neo/groups/map_authors/conversations/topics/2495).

I understand that the precisison 2.4m is enough for GPS unit, but I don't think, that inaccuracy GPS unit is reason for making inaccurate maps.

Has anybody solved the problem with "loss of detail" after compiling by cgpsmapper?

I am asking, because I am facing the same problem with isobaths in waterways maps (web: waterways.cz).

I thought, I solved the problem by using level0=26 instead of level0=24. The picture has been very nice in Mapsource, but the polygons and polylines haven't been visible (under certain zoom) in marine plotters.  So, this solution is unusable.