[mkgmap-dev] Splitter Options for small files

Tue Jan 8 19:07:22 GMT 2013

Hmm, sorry, I was wrong again :-(

If splitter finds a bbox in the input file, this bbox is used and all data
outside of the bbox is 
ignored (maybe not with --keep-complete=true ). Typically, nodes outside of
the bbox belong to
ways that have also nodes inside of the bbox.

So, the question is if we solve the problem if we ignore the bbox of the
input file or if we simply
copy the input file when it is small. 
Do you have the problem with --keep-complete=true?

Gerd

GerdP wrote
> 
> GerdP wrote
>> I see two possible reasons:
>> 1) splitter creates a new bounding box which is aligned to 2048 garmin
>> units, it will 
>> "blow up" the original bbox if needed.
>> 2) If the input file contains a bounding box, splitter doesn't copy data
>> that lies 
>> outside of this bbox. 
> Sorry, forget 2) 
> Splitter calculates the bounding box in this way:
> it starts with an empty bbox. 
> if a bounding box is found in the input file, this is used to enlarge
> splitters bbox
> it enlarges the bbox for each node in the input file that lies outside of
> the bbox
> 
> The result is reported in the line starting "Exact map coverage is "
> The next line begiining with ""Rounded map coverage is " shows the bbox 
> that is written to the output file.
> 
> If I got this right, mkgmap should not have a problem with that. If it
> does, the 
> problem should be fixed in mkgmap.
> 
> Gerd

--
View this message in context: http://gis.19327.n5.nabble.com/Splitter-Options-for-small-files-tp5743455p5743469.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.