Is it possible that your Garmin only has icons for 3-6-9-12 o'clock and is "rounding off" the angle in a funny way? It may be a fraction over 180 degrees and so getting "rounded up" (wrongly) to what you see. I have looked at the OSM data for that roundabout and there is nothing wierd there as far as I can see.
Also you say you are using r1919 of mkgmap. As from r3116 the internal calculations are being done in a higher resolution, to mitigate problems which can have symptoms like you are seeing. Can you try a later version(>=3116) , to see if that is any better? Colin On 2014-09-30 16:08, SPA wrote: > Greetings Andy > > All roundabouts... mmm did I say so? > ;) > > Ok here is an example of a roundabout: > Round about position: > 55.586085, 11.857095 > > Roundabout approach direction: > MY 6 o'clock > > To complete my journey I need to exit the roundabout at: > MY 12 o'clock > > The voice in Danish guides me correctly by telling me to take the second > exit. > > ****************************************** > The icon on the navigations window of my GPS (top left) > indicates that I have to exit the roundabout at: > MY 9 o'clock > ****************************************** > > Screenshot of my GARMIN: > http://thecyberinn.com/garmin/22060.png [1] > > Greetings > Johan > > P.S. Remember... life is not about the destination, but the amazing journey. > :) > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of SomeoneElse > Sent: 30. september 2014 15:27 > To: [email protected] > Subject: Re: [mkgmap-dev] Incorrect runabout exit indication > > On 29/09/2014 23:31, Peter Hendricks wrote: > >> Hi Andy, Johan has this problem on ALL roundabouts in OSM maps. > > Well "all" is quite a lot. He must have driven around lots of roundabouts > to test that :-) > > Seriously, an example would still help - specifically to see if the > roundabouts concerned have a node shared between one road's exit flare and > another's entrance. It would also allow other who use mkgmap themselves to > chip in and say "_my_ map does/does not have the problem at that > roundabout", to get a few more data values than 2, to try and figure out > what might be the difference that is causing the problem. > > I've just tried simulating a route through a bunch of nearby roundabouts (on > an eTrex Vista HCx and a Nuvi 265W) and I'm not seeing the problem as > described - in each case the on-screen pictures (including the small one on > the Nuvi) matches the verbal direction. > > I'm using "mkgmap-r1919" (quite old) and the options "--add-pois-to-areas > --remove-short-arcs --levels="0=24, 1=22, 2=21, 3=19, 4=18, 5=16" --route > --gmapsupp". > > Cheers, > > Andy > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [2] > > ----- > No virus found in this message. > Checked by AVG - www.avg.com [3] > Version: 2014.0.4765 / Virus Database: 4025/8297 - Release Date: 09/30/14 > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [2] Links: ------ [1] http://thecyberinn.com/garmin/22060.png [2] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [3] http://www.avg.com
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
