[mkgmap-dev] Splitter Options for small files

Tue Jan 8 18:21:28 GMT 2013

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-tp5743455p5743464.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.