[mkgmap-dev] Inter-tile routing failures - not all our fault?

Fri Aug 14 21:25:26 BST 2009

did some experiments in Mapsource and Garmin maps don't suffer from this
problem.found a place where the direction of the route defines which way
is chosen. makes perfect sense because right turns are faster and easier
than left turns.
Mapsource will even choose the longer way across the tile boundary to avoid
the left turns.

Is there anything I can check for? map is not protected and should be
possible to load in Gpsmapedit.

On Fri, Aug 14, 2009 at 3:34 AM, Mark Burton <markb at ordern.com> wrote:

>
> Using a recent GB tiled map on my eTrex, I have found that it performs
> differently (better?) to mapsource with regard to the problem of not
> routing across a boundary and back to the source tile.
>
> An example route I tried used a road that snaked across a boundary.
> Mapsource failed miserably in the manner previously described. The
> eTrex faired better in that it could manage to route across the
> boundary and back again for at least one crossing pair but when I tried
> to cross and back again for the second time, it took a really long time
> to calculate the route and the result was very silly.
>
> On another example route, that crossed the boundary to a fork and then
> crossed back to the original tile, mapsource failed but the eTrex was
> quite happy.
>
> So I remain far from convinced that the problem is due to buggy map
> data generated by mkgmap. However, it may be that we have to generate
> map data that is in some way "more sympathetic" to the needs of the
> Garmin routing engines.
>
> Mark
>
>
>
>
>
> _______________________________________________
> 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/20090814/ee7ce6c4/attachment.html 