Thread: City Navigator Singapore/Malaysia NT 2011.40

Originally Posted by malebum

I put the map in SD card under Garmin folder and jcv file in JCV sub-folder. Both map and JCV ppears to work but I had to change the image file to gmapsupp.img. I did this using the MSM 2011 40 map though, not this CN 2011 map.....

Yes, only gmapsupp.img will work in the Garmin folder in SD. You can create a 'Map' folder (no quotes) in the sd root and put many maps in there and use 'anyname'.img eg CNNT_SG/MY_2012.40.img or anything else convenient.

Originally Posted by malebum

Is this the info you wanted?.........
Header: 11.01.2012 16:34:38, DSKIMG, XOR 00, V 11.40, Ms 0
Mapset: CN SGM NT 2011.40 ALL

Yes, thanks. I see from your post yesterday that you downloaded the Type3 pack. Same map info as my last Type2 dl, makes sense. Robinang reported a header date of 10.02.2012 which must mean different map info in at least one other pack type (1,4 or 5) for some reason.

Originally Posted by malebum

I find that this City Navigator NT 2011.40 map (both img and jcv files) is more than twice the size of the equivalent Malsingmaps NT 2011.40 but the Malsingmaps map seems better. At least for my home area, the Malsingmaps map displays more junction views. Although searching for POIs on this City Navigator map takes much longer time than searching on the Malsingmaps map.

Anybody has the same experience? Any reason for the great difference in map sizes?

City Navigator 85,680 kb for map, 358,046 kb for jcv
Malsingmaps 39,800 kb for map, 167,984 kb for jcv

Comparison is not always subjective when only one area is examined as you realize i'm sure. Simple answer, have both and use whichever seems best where you are at the time. Don't select both maps together of course or there will be problems. (Go to: Tools>Settings>Map>Info>Check or Un-check as req'd). On the other hand, the two different jcv files in the 'JCV' folder should not cause any problems.

Size could be also to do with differing compression rates used by the mapmakers, not just the map data. Higher compression rates may also explain slower drawing and/or searching.