
On 25.01.2010 23:38, Mark Burton wrote:
Felix,
The fix to the splitter plus the patches DID it. However why is the map flooded if I don't put an natural=land all around it. I'm using "=polygons" Have you got any idea on this?
I should think that your little natural=coastline poly on the RHS just below the middle is causing the problem because what you have there is an anti-island (sea surrounded by land) and I don't think the sea generation code knows about anti-islands.
No I put that natural=land to stop flooding. If it is removed everything gets flooded. Sorry should have noted this. There is one big big reason why I really don't want to drop --geneerate-sea=polygons (and also would like to have the option to create natural=land for all maps where I have to disable --generate-sea to avoid flooding), and that is that I need natural=land to change background color (so there is no nasty nasty yellow).
I think if there is no sea polygon at all, the =polygons code should still create a natural=land on top of the blue background (I already noticed this, so bug is not new, but I assumed it to happen somehow due to the wrong overview map) - Should I open another thread for this?
Well, it does generate a land poly when there's no sea but your legend map has sea.
It does, sadly.
I'll think about this and see if I can fix the problem.
No problem to make it complicated. But I don't understand why it is flooded 100% without natural=land polygon.
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev