[mkgmap-dev] Should inter tile routing still work when splitting Splitter results again?

Tue Sep 29 21:03:30 BST 2009

On Tue, 29 Sep 2009 11:04:23 -0700, Apollinaris Schoell
<aschoell at gmail.com>
wrote:
> was able to render all of North America with 90000 nodes. But it's always
a
> bit of luck. splitter puts in only 50-70% of the limit in a majority of
the
> tiles. a small change can result  in a very different setup.
> 
Yes, I think I've seen things like this with previous splits as well.

>> The question:
>> Will routing be a problem because the result of recursively splitting
>> and rendering results in tiles that apparently do not line up perfectly?
>> I've done a few tests and it feels that routing has become worse, but I
>> don't have a definitive answer. If so, what can be done about this? I'm
>> curious if anyone (Chris?) has ideas about it.
>>
>>
> have tried it manually once, the tricky part is to split a tile from
> splitter again with splitter, because of the overlaps are required for
> mkgmap and can't be removed. but splitter will use the data and construct
a
> larger bounding box.
> You can do it this way. run splitter again on the tile. use area.list to
> get
> the new edge where the tile is split and combine it with the definition
of
> the large tile in the area.list from the first run to get the outer
> alignment with other tiles from the 1st run. run splitter again with this
> new aligned areas.list.
> to complicated for me to follow it systematically and went with lower
> max-nodes
> 
It sounds indeed like it's quite complicated to do. But maybe, if I lock
myself up for a week :p, this could be implemented in software. If the algo
works then this should work really well.