[mkgmap-dev] It's clearly a bug in the splitter
From Gerd Petermann gpetermann_muenchen at hotmail.com on Thu Oct 18 09:15:30 BST 2012
Hi, I'll take a look at it. Gerd > Date: Wed, 17 Oct 2012 23:00:54 +0100 > From: steve at parabola.me.uk > To: extremecarver at gmail.com; mkgmap-dev at lists.mkgmap.org.uk > Subject: Re: [mkgmap-dev] It's clearly a bug in the splitter > > On 17/10/12 19:44, Felix Hartmann wrote: > > However actually now that I think about it - I can only come up with one > > explication why rev 105 on splitter was done - that is so that tiles > > don't overlap. Because the current hack means all tiles will be expanded. > > Yes, that is exactly right, the tiles will overlap and routing will fail > across boundaries. > > > What we really need is to have the splitter identify ALL outside edges. > > Yes. > > I'm not really sure how splitter works now, but it looks to me like all > we need to do is alter > > SplittableArea splittableArea = nodes.getRoundedArea(resolution); > > in Main.calculateAreas() so that it doesn't round at all. > > ..Steve > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20121018/ee612cf1/attachment.html
- Previous message: [mkgmap-dev] It's clearly a bug in the splitter
- Next message: [mkgmap-dev] It's clearly a bug in the splitter
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list