Thread: City Navigator North America NT 2012.30

Torrent of unlocked images...
[Only registered and activated users can see links. ]

Originally Posted by turboccc

D2656050A.sid 389MB External Point Addressing
D3406020A.sid 251,6MB trafficTrendsv3
D3157030A.sid 263,4MB InstaSearch
D3398020A.sid 152,3MB FastRouting

Is it in downloads of update?

Originally Posted by Frustated XT user

I have the 765T. Which .JCV works? I am guessing the largest version but if Garmin decided to do some serious compression with their images, that would be ideal. Please a thank you.

This is the smallest D3153040A.JCV 44,3MB LaneAssist and it will work as stated earlier in the thread. The largest should as well, and the difference has been reported to be a few more intersections shown in the larger jcv's, but more significantly, the image is more "photo real" in the largest file. I have experimented with several on an earlier version of NT2012 and all I tried seemed to work in a 1490(small 44, med 400, and large 700MB+). I see you did participate in the thread on the 2012.10, so suggest you try a small and bigger file (depending on what your needs are), simulate a route, and pick the one you like. I believe there is another thread that discusses that basically all the jcvs for a given map work, you just get different aspect ratio, resolution, etc....
I tried the D3060040A.JCV 757,3MB LaneAssistFull D3191030A.JCV 449,1MB LaneAssistPortrait, and D3153040A.JCV 44,3MB LaneAssist on an obscure interchange and saw two images in each, the full was higher resolution than the mid size, but both were full size and the showed trees in the background. The D3153040A.JCV 44,3MB LaneAssist was actually better resolution of the road and lanes than the 449MB file, but it did not show (blurred out) the background trees, etc. It appears the smaller file has the same utility, but focuses on the lane features not the background. In another post for an earlier version NT2012 it was reported the associated small jcv showed approximately 5 of 8 interchange pictures in the San Francisco area. Don't know if this would be true for this example.....Since there is lots of SD card space and the files don't seem to slow the unit loading it seems logical to use the big file.