On 14/06/2010 13:16, Peter Hendricks wrote:
Thanks for your comment, Charlie. I will pass this back to the people who make the maps.
I also have MapSource 6.16.1 and I don't get this problem, so it's not universal. 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.
FWIW, I was able to recreate this problem by using the multipolygon version of generate-sea in mkgmap. I normally use the no multipolygon version of generate-sea because this creates a nice land polygon that covers the default Garmin yellow on my GPS (my GPS ignores any attempt to change the 0x4b polygon using a typ file). With generate-sea:no-mp, I have no problems. But with generate-sea multipolygon version, and MapSource 6.16.1, I get similar problems to those shown above, with blurry images when zooming in and out that are only resolved by refreshing the cache.
To summarise. 1) No problems with blurry images, compiled using: generate-sea:no-mp,no-sea-sectors,extend-sea-sectors,close-gaps=1000 2) Blurry images when zooming in & out, only solved by refreshing tile cache: generate-sea:extend-sea-sectors,close-gaps=1000