Re: Worldwide routable Garmin maps: URL REMOVED

ligfietser wrote:

Yeah it takes the same tile as Brussels
http://osm.pleiades.uni-wuppertal.de/ga … 241989.img

In the OFM Lite it looks ok:
Paris tile http://osm.pleiades.uni-wuppertal.de/ga … 240194.img
Brussels: http://osm.pleiades.uni-wuppertal.de/ga … 240196.img

Since the generic and OFM use the same splitted files, why is then the Generic map corrupt?

Almost. The base split is the same for both maps. I.e. the first run of splitter is splitting the planet using the max-nodes=1400000 parameter. The generic map and the OpenFietsMap render scripts then render and split these initial splitted tiles with every decreasing max-nodes parameters until everything is successfully rendered and the resulting tile is smaller then 8 MB. So some of the initial tiles are rendered only once for each map and some tiles are splitted/rendered many times before the result is accepted. This can (but doesn't have to) result in a different final tile layout for each map type.

Is the generic map containing too many nodes, more than the OFM lite? Is there a diferrence in mkgmap settings that is causing this?

There are differences in Mkgmap settings between both map types.

Two more remarks:
-I notice that the one OFM Brussels map is split in two tiles in the generic map

Yes, this is probably a result of what the Mkgmap styles include or exclude.

-I have noticed that using -ea (enable assertions) sometimes generates an empty tile when only one road was corrupt in my maps, and therefore i dont use this option anymore. Maybe this is causing trouble too in the Paris area?

I'm using the -ea option to ensure that Mkgmap doesn't produce a tile when it's not correct. Tiles that are 0 bytes are detected and automatically deleted. The smallest tile in both maps is 14kB in size.

Plan of action:
Find the initial tile that contains Paris
Enable as much logging as possible
Execute the rendering/splitting on that tile only
Analyze, analyze, analyze