logo separator

[mkgmap-dev] Holes in the Sea

From RheinSkipper rheinskipper1000 at gmx.de on Sun Feb 26 18:17:39 GMT 2012

Still holes in the sea

First I bought some more memory to make sure, the holes in the sea are no
memory issue. But even with 8 GB the empty sea tiles are still there.

The empty tile south of Monaco is attached here. I converted it to XML and
there are 28 occurrences of natural=coastline in it.

After increasing --max-nodes from 1000000 to 1200000 this hole is also still
there (tile number changes off course).

I use --no-trim --overlap=5000. Higher overlap makes no difference.


> -----Ursprüngliche Nachricht-----
> Von: mkgmap-dev-bounces at lists.mkgmap.org.uk [mailto:mkgmap-dev-
> bounces at lists.mkgmap.org.uk] Im Auftrag von Marko Mäkelä
> Gesendet: Freitag, 17. Februar 2012 22:29
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Holes in the Sea
> On Fri, Feb 17, 2012 at 05:14:53PM +0100, RheinSkipper wrote:
> >Also attached is a screenshot of those terrible holes in the sea.
> I do not have idea about the max-nodes in the splitter, but the holes are
> regular that they should be relatively easy to figure out.
> Can you determine the tiles corresponding to the holes? Are there any
> natural=coastline ways in the tiles? If not, mkgmap should assume that the
> whole tile is land. I would start by checking the hole south of Nizza, as
it is
> smaller. Try to convert the tile.osm.pbf to XML format with Osmosis and
> do grep 'natural.*coastline' tile.osm. If there is no match, then my guess
> should be right.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 63240790.osm.pbf
Type: application/octet-stream
Size: 14761 bytes
Desc: not available
Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20120226/8228f8b5/attachment.obj 

More information about the mkgmap-dev mailing list