[mkgmap-dev] Holes in the Sea

Fri Mar 2 20:57:33 GMT 2012

The problem is that splitter and mkgmap don't work together at all. The 
solution would be that splitter does more checking against the 
possibility of such empty tiles, or other way around - an improvement on 
how max-nodes are counted. The other possibility would be, if there was 
an automatic mechanism (mapid is important here why it needs to be 
somehow integrated) how too big tiles could be split again and 
reprocessed once more by mkgmap.

On 02.03.2012 21:54, Minko wrote:
> I think that it has to do with the negative node-id's when you draw an island
> that isn't in the OSM database. Probably it will not merge with the osm data.
>
> Well, either way it will be an inconvenient workaround, I agree.
>
> Maybe Wanmil's floodblocker can do something like this, but then
> the opposite way?
>
> 1) If a tile has no info at all ->  sea
> 2) only ferry-lines or territorial water boundaries (or with marine=yes) ->  sea
>
> The problem is the first case, it can also be an empty land tile somewhere in Siberia.
>
>
> RheinSkipper wrote:
>> This workaround is inconvenient. So I hope the mkgmap developers will find a
>> way how to recognize the offshore tiles as sea instead of land
>> automatically, someday.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev