[talk-au] re Coastline rendering in Garmins Mapsource

[Matt White]

Coastlines (and the "inverse islands" issues) have been onging for ages 
for the mkgmap produced garmin files. There's a --generate-sea switch 
for mkgmap that sometimes works fine, other times, not so good. It's hit 
and miss enough that I've mever enabled it for the maps I generate

Problem seems to come from a few different things - non-closed coasline 
polygons, coastline direction changes, points where rivers join 
sea/coastline etc.

There's a lot of chat on the mkg-map dev list over the last 6 months or 
so regarding this

Matt

John Henderson wrote:
> John Kitchener wrote:
>   
>> Here's how it renders on an Oregon 300
>> http://img695.imageshack.us/img695/2718/oregon300.jpg
>>     
>
> Using a different mkgmap "style file" and "TYP file" presumably to 
> generate the gmapsupp.img file.  They're highly configurable.  I've 
> started experimenting with them for the routable cycle maps I'm producing.
>
> We've still got that underlying problem with the coastline though.
>
> John H
>
> _______________________________________________
> Talk-au mailing list
> Talk-au at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-au
>
>