[mkgmap-dev] Holes in the Sea

Mon Mar 5 13:05:03 GMT 2012

On 02.03.2012 22:27, RheinSkipper wrote:
>> Betreff: Re: [mkgmap-dev] Holes in the Sea
>>
>> 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.
>>
> That would be perfect. But if it´s too difficult to implement, I could
> imagine a simple semi-automatic approach:
>
> Implement a mkgmap option "--seapoint-file=somefile.txt". In "somefile.txt"
> the user can put a list of coordinates (points) that are somewhere in the
> sea areas. If mkgmap processes a tile without coastline and there is a point
> from the list inside the tile, make it sea, otherwise land. So the user can
> "repair" seaholes easily by just adding one point within this area to the
> text file. People may share their seapoint lists. After some time there will
> be so many seapoints in the lists that holes in the sea will become
> extremely unlikely.
Well I don't think it can be so difficult. In principle on can already 
program it manually quite easy.
1. run generate map without address index
2. check if any tiles are missing. If no -- generate address 
index/gmapsupp If yes go to step 3.
3. Split all files with 60% of the previous max-nodes settings (could I 
use 50% or do I need to factor the overlap in??) and regenerate just 
hose tiles, using a new higher mapname number (highest one +1....)
4. check again, if now all tiles present, generate address 
index/gmapsupp, if not, redo for tiles not working like with 3.

... If it twice fails, then there is another error, and lowering 
max-nodes most likely won't give you a working map tile, hence just 
gerate map / gmapsupp. It doens't matter if the mapnames have holes, so 
if it is 63240000 then 63240002 and no 01 exist, it doesn't matter at 
all. Optionally mkgmap could just rename the generated files, so the 
mapname is continous...

All what would be needed for this, is that you also tell mkgmap where 
splitter.jar is to be found (default could be assumed that splitter is 
called splitter.jar, and placed in the working directory).