Incorrect runabout exit indication
Greetings First of all, Im not sure if I am following the correct procedure by wring to this email address I found here on the mkgmap site? I use a Garmin Nüvi 55 with primarily maps of Denmark from OpenStreetMap (Lambertus) compiled with mkgmap. I have the latest revision of the Denmark map 09-09-2014. All other maps on my GPS are disabled. There is an error: For example, my journey takes me though a roundabout. It is a straight forward roundabout with 4 exists, 3, 6, 9 & 12 oclock. I enter the roundabout at 6 oclock and should exit it at 9 oclock to reach my destination. The voice prompt of my GPS navigates me though the roundabout correctly take exit number three, bla bla bla HOWEVER, the small icon to the top left of the navigation window on my Garmin, indicating the specific roundabout exit position, incorrectly indicates that I should exit the roundabout at 6 oclock. I find this to be the matter with all roundabouts the small icon to the top left of the navigation window, indicating the specific roundabout exit position, displays an exit later that the actual exit that I need to take. When I use a map from for example NZ Open GPS (http://gwprojects.org/) that compiles maps with cgpsmapper both the voice prompt and the icon indicating the specific roundabout exit position (top left of navigation screen) of my GPS is correct. I am not sure if this is a mkgmap compiler issue or a Garmin device firmware issue? Kind regards Johan
On 16/09/2014 04:05, SPA wrote:
For example, my journey takes me though a*roundabout*. It is
a straight forward roundabout with 4 exists, 3, 6, 9 & 12 o'clock.
I *enter*the roundabout at*6 o'clock*and should*exit*it at*9 o'clock*
to reach my destination.
The*voice prompt* of my GPS navigates me though the roundabout
*correctly*... "/take exit number three, bla bla bla/"...
*HOWEVER*, the*_small icon_**to the top left of the navigation*
window on my Garmin, indicating the specific roundabout exit
position,*incorrectly indicates*that I should*exit*the roundabout
at 6 o'clock.
Can you provide a link to the roundabout on the OpenStreetMap website? That would help people to see if, for example, someone's incorrectly joined the "exit" of one roundabout flare to the "entrance" of the next one (which would suggest, incorrectly, that you had to get off the roundabout after one fewer exit. Cheers, Andy
Hi Andy, Johan has this problem on ALL roundabouts in OSM maps. I asked him to test this with the NZOGPS map in simulation mode and there it doesn't happen. Kind regards, Peter. On 16/09/2014 20:50, SomeoneElse wrote:
On 16/09/2014 04:05, SPA wrote:
For example, my journey takes me though a *roundabout*. It is
a straight forward roundabout with 4 exists, 3, 6, 9 & 12 o’clock.
I *enter* the roundabout at *6 o’clock* and should *exit* it at *9 o’clock*
to reach my destination.
The *voice prompt* of my GPS navigates me though the roundabout
*correctly*… “/take exit number three, bla bla bla/”…
*HOWEVER*, the *_small icon_**to the top left of the navigation*
window on my Garmin, indicating the specific roundabout exit
position, *incorrectly indicates* that I should *exit* the roundabout
at 6 o’clock.
Can you provide a link to the roundabout on the OpenStreetMap website? That would help people to see if, for example, someone's incorrectly joined the "exit" of one roundabout flare to the "entrance" of the next one (which would suggest, incorrectly, that you had to get off the roundabout after one fewer exit.
Cheers,
Andy
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
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
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 Greetings Johan P.S. Remember... life is not about the destination, but the amazing journey. :) -----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of SomeoneElse Sent: 30. september 2014 15:27 To: mkgmap-dev@lists.mkgmap.org.uk 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 mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4025/8297 - Release Date: 09/30/14
On 30/09/2014 15:08, SPA wrote:
Ok here is an example of a roundabout: Round about position: 55.586085, 11.857095
That's this one then: http://www.openstreetmap.org/way/207339216
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.
So presumably your coming from the northeast here: http://www.openstreetmap.org/way/290451039 and exiting at the southwest here: http://www.openstreetmap.org/way/42685063
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
I wonder if it's doing that because the angle between entry and exit roads is just a little more than 180 degrees (i.e. a little more than "straight on"), or because it's a road with (in that direction) no exit at 9 o'clock? What does it say if you try and go in the other direction - i.e. from http://www.openstreetmap.org/way/42685063 to http://www.openstreetmap.org/way/290451040 ? I'll have a think and see if I can find any similar ones locally. Cheers, Andy
Hi Andy It's the correct roundabout we are talking about. the entry/exit directions are correct too.
I wonder if it's doing that because the angle between entry and exit roads is just a little more than 180 degrees (i.e. a little more than "straight on"), or because it's a road with (in that direction) no exit at 9 o'clock? I have no idea. I have not experience with map drawing or editing.
What does it say if you try and go in the other direction - i.e. from I get the same result when driving from the opposite direction of the roundabout.
Here is a new example with a different roundabout with 5 entry/exit points: (for all practical purposes we ignore the Danish voice guidance that seems to be in order) Circle coordination: N55.63893° E12.06860° (same roundabout for all 3 examples same entry direction/deferent exit directions) route enter circle at 000 degrees should circle at ***290*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***225*** degrees Screenshot: http://thecyberinn.com/garmin/20898.png route enter circle at 000 degrees should circle at ***165*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***080*** degrees Screenshot: http://thecyberinn.com/garmin/26841.png route enter circle at 000 degrees should circle at ***290*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***080*** degrees Screenshot: http://thecyberinn.com/garmin/32308.png Regards Johan -----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of SomeoneElse Sent: 30. september 2014 16:29 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication On 30/09/2014 15:08, SPA wrote:
Ok here is an example of a roundabout: Round about position: 55.586085, 11.857095
That's this one then: http://www.openstreetmap.org/way/207339216
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.
So presumably your coming from the northeast here: http://www.openstreetmap.org/way/290451039 and exiting at the southwest here: http://www.openstreetmap.org/way/42685063
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
http://www.openstreetmap.org/way/42685063 to http://www.openstreetmap.org/way/290451040 ? I'll have a think and see if I can find any similar ones locally. Cheers, Andy _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4025/8297 - Release Date: 09/30/14
Hi Johan, if I got you right, the device shows conflicting information. I think this is likely to be a firmware problem. Did you try to update your device? Gerd
From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 2 Oct 2014 05:08:54 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Hi Andy
It's the correct roundabout we are talking about. the entry/exit directions are correct too.
I wonder if it's doing that because the angle between entry and exit roads is just a little more than 180 degrees (i.e. a little more than "straight on"), or because it's a road with (in that direction) no exit at 9 o'clock? I have no idea. I have not experience with map drawing or editing.
What does it say if you try and go in the other direction - i.e. from I get the same result when driving from the opposite direction of the roundabout.
Here is a new example with a different roundabout with 5 entry/exit points: (for all practical purposes we ignore the Danish voice guidance that seems to be in order)
Circle coordination: N55.63893° E12.06860° (same roundabout for all 3 examples… same entry direction/deferent exit directions)
route… enter circle at 000 degrees… should circle at ***290*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***225*** degrees Screenshot: http://thecyberinn.com/garmin/20898.png
route… enter circle at 000 degrees… should circle at ***165*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***080*** degrees Screenshot: http://thecyberinn.com/garmin/26841.png
route… enter circle at 000 degrees… should circle at ***290*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***080*** degrees Screenshot: http://thecyberinn.com/garmin/32308.png
Regards Johan
-----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of SomeoneElse Sent: 30. september 2014 16:29 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
On 30/09/2014 15:08, SPA wrote:
Ok here is an example of a roundabout: Round about position: 55.586085, 11.857095
That's this one then:
http://www.openstreetmap.org/way/207339216
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.
So presumably your coming from the northeast here: http://www.openstreetmap.org/way/290451039
and exiting at the southwest here: http://www.openstreetmap.org/way/42685063
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
http://www.openstreetmap.org/way/42685063 to http://www.openstreetmap.org/way/290451040 ?
I'll have a think and see if I can find any similar ones locally.
Cheers,
Andy
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4025/8297 - Release Date: 09/30/14
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd I have indeed updated the firmware as the first thing after I unpacked the device from the box it was purchased in. And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... Regards Johan
On 02 Oct 2014, at 08:58, Gerd Petermann <gpetermann_muenchen@hotmail.com> wrote:
Hi Johan,
if I got you right, the device shows conflicting information. I think this is likely to be a firmware problem. Did you try to update your device?
Gerd
From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Thu, 2 Oct 2014 05:08:54 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Hi Andy
It's the correct roundabout we are talking about. the entry/exit directions are correct too.
I wonder if it's doing that because the angle between entry and exit roads is just a little more than 180 degrees (i.e. a little more than "straight on"), or because it's a road with (in that direction) no exit at 9 o'clock? I have no idea. I have not experience with map drawing or editing.
What does it say if you try and go in the other direction - i.e. from I get the same result when driving from the opposite direction of the roundabout.
Here is a new example with a different roundabout with 5 entry/exit points: (for all practical purposes we ignore the Danish voice guidance that seems to be in order)
Circle coordination: N55.63893° E12.06860° (same roundabout for all 3 examples… same entry direction/deferent exit directions)
route… enter circle at 000 degrees… should circle at ***290*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***225*** degrees Screenshot: http://thecyberinn.com/garmin/20898.png
route… enter circle at 000 degrees… should circle at ***165*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***080*** degrees Screenshot: http://thecyberinn.com/garmin/26841.png
route… enter circle at 000 degrees… should circle at ***290*** degrees to complete journey icon at top left of navigational window indicates that I should leave circle at position ***080*** degrees Screenshot: http://thecyberinn.com/garmin/32308.png
Regards Johan
-----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of SomeoneElse Sent: 30. september 2014 16:29 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
On 30/09/2014 15:08, SPA wrote:
Ok here is an example of a roundabout: Round about position: 55.586085, 11.857095
That's this one then:
http://www.openstreetmap.org/way/207339216
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.
So presumably your coming from the northeast here: http://www.openstreetmap.org/way/290451039
and exiting at the southwest here: http://www.openstreetmap.org/way/42685063
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
http://www.openstreetmap.org/way/42685063 to http://www.openstreetmap.org/way/290451040 ?
I'll have a think and see if I can find any similar ones locally.
Cheers,
Andy
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4025/8297 - Release Date: 09/30/14
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Johan, And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd
Hi Gerd I just want to let you know that I do not compile and/or edit any OSM maps. I do not have any experience in the area. I therefore have no idea what "mkgmap r3336" is. The way I get OSM maps onto my PGS is by visiting http://garmin.openstreetmap.nl/, selecting the desired tiles "Generic Routable (new style)" and then clicking on "Build my map". I then run the *.exe file that will extract the tiles and see to it that I have the correct imported map into BaseCamp. From there load the maps onto my GPS. Your two *.img files (V1 & V2) I just copied directly onto my GPS for the testing purposes. BO TH work perfectly when I simulate a route. the Danish voice prompt guides me to take the correct exit & and the icon indication the relive position for exiting the roundabout is correct. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 07:55 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, _____ And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd
Johan, Did you experience this issue also in the Generic Routable (old style) or only in the new style? BTW Lambertus produces his maps with mkgmap, r3336 is the version he also used in the latest release.
Hello again Gerd I quickly downloaded the latest version of Lambertus's OSM for Denmark, Generic Routable (old style), date: 01-10-2014. It works fine. the Danish voice prompt guides me to take the correct exit & and the icon indication the relative roundabout position for exiting the roundabout is correct. Kind regards Johan -----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Minko Sent: 3. oktober 2014 11:07 To: Development list for mkgmap Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Johan, Did you experience this issue also in the Generic Routable (old style) or only in the new style? BTW Lambertus produces his maps with mkgmap, r3336 is the version he also used in the latest release. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4037/8316 - Release Date: 10/03/14
Hi Johan, can you still reproduce the problem with new style map for 01-10-2014? Gerd
From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 11:33:35 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Hello again Gerd
I quickly downloaded the latest version of Lambertus's OSM for Denmark, Generic Routable (old style), date: 01-10-2014. It works fine. the Danish voice prompt guides me to take the correct exit & and the icon indication the relative roundabout position for exiting the roundabout is correct.
Kind regards Johan
-----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Minko Sent: 3. oktober 2014 11:07 To: Development list for mkgmap Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Johan, Did you experience this issue also in the Generic Routable (old style) or only in the new style? BTW Lambertus produces his maps with mkgmap, r3336 is the version he also used in the latest release.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4037/8316 - Release Date: 10/03/14
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd Pls give me some time. There is a queue. "This request is #20 in the queue. The delay is approximately 2 hours." Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:47 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, can you still reproduce the problem with new style map for 01-10-2014? Gerd
From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 11:33:35 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Hello again Gerd
I quickly downloaded the latest version of Lambertus's OSM for Denmark, Generic Routable (old style), date: 01-10-2014. It works fine. the Danish voice prompt guides me to take the correct exit & and the icon indication the relative roundabout position for exiting the roundabout is correct.
Kind regards Johan
-----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Minko Sent: 3. oktober 2014 11:07 To: Development list for mkgmap Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Johan, Did you experience this issue also in the Generic Routable (old style) or only in the new style? BTW Lambertus produces his maps with mkgmap, r3336 is the version he also used in the latest release.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4037/8316 - Release Date: 10/03/14
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd
can you still reproduce the problem with new style map for 01-10-2014?
Yes, I get the same error when using new style map for 01-10-2014. indication for the relative roundabout position for exiting the roundabout that is. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:47 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, can you still reproduce the problem with new style map for 01-10-2014? Gerd
From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 11:33:35 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Hello again Gerd
I quickly downloaded the latest version of Lambertus's OSM for Denmark, Generic Routable (old style), date: 01-10-2014. It works fine. the Danish voice prompt guides me to take the correct exit & and the icon indication the relative roundabout position for exiting the roundabout is correct.
Kind regards Johan
-----Original Message----- From: <mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk> mkgmap-dev-bounces@lists.mkgmap.org.uk <mailto:[mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk]> [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Minko Sent: 3. oktober 2014 11:07 To: Development list for mkgmap Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Johan, Did you experience this issue also in the Generic Routable (old style) or only in the new style? BTW Lambertus produces his maps with mkgmap, r3336 is the version he also used in the latest release.
_______________________________________________ mkgmap-dev mailing list <mailto:mkgmap-dev@lists.mkgmap.org.uk> mkgmap-dev@lists.mkgmap.org.uk <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
----- No virus found in this message. Checked by AVG - <http://www.avg.com> www.avg.com Version: 2014.0.4765 / Virus Database: 4037/8316 - Release Date: 10/03/14
_______________________________________________ mkgmap-dev mailing list <mailto:mkgmap-dev@lists.mkgmap.org.uk> mkgmap-dev@lists.mkgmap.org.uk <http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Johan, okay, mkgmap r3336 is the current version of the map compiler mkgmap, which is used by Lambertus who offers the service at http://garmin.openstreetmap.nl/. The r3336 simply means it is based on the revision 3336 in the Subversion repository. You can download this program here: http://www.mkgmap.org.uk/download/mkgmap.html If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. You may also try if the "Routable Bicycle (Openfietsmap Lite)" shows the same problem. @Lambertus: Do you publish the style and the options that are used for your service anywhere? Ciao, Gerd From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 10:54:47 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Gerd I just want to let you know that I do not compile and/or edit any OSM maps. I do not have any experience in the area. I therefore have no idea what “mkgmap r3336” is. The way I get OSM maps onto my PGS is by visiting http://garmin.openstreetmap.nl/, selecting the desired tiles “Generic Routable (new style)” and then clicking on “Build my map”. I then run the *.exe file that will extract the tiles and see to it that I have the correct imported map into BaseCamp. From there load the maps onto my GPS. Your two *.img files (V1 & V2) I just copied directly onto my GPS for the testing purposes. BO TH work perfectly when I simulate a route… the Danish voice prompt guides me to take the correct exit & and the icon indication the relive position for exiting the roundabout is correct. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 07:55 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. Mmmmm, is this not what I have been doing here? Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:17 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, okay, mkgmap r3336 is the current version of the map compiler mkgmap, which is used by Lambertus who offers the service at http://garmin.openstreetmap.nl/. The r3336 simply means it is based on the revision 3336 in the Subversion repository. You can download this program here: http://www.mkgmap.org.uk/download/mkgmap.html If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. You may also try if the "Routable Bicycle (Openfietsmap Lite)" shows the same problem. @Lambertus: Do you publish the style and the options that are used for your service anywhere? Ciao, Gerd _____ From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 10:54:47 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Gerd I just want to let you know that I do not compile and/or edit any OSM maps. I do not have any experience in the area. I therefore have no idea what "mkgmap r3336" is. The way I get OSM maps onto my PGS is by visiting http://garmin.openstreetmap.nl/, selecting the desired tiles "Generic Routable (new style)" and then clicking on "Build my map". I then run the *.exe file that will extract the tiles and see to it that I have the correct imported map into BaseCamp. From there load the maps onto my GPS. Your two *.img files (V1 & V2) I just copied directly onto my GPS for the testing purposes. BO TH work perfectly when I simulate a route. the Danish voice prompt guides me to take the correct exit & and the icon indication the relive position for exiting the roundabout is correct. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 07:55 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, _____ And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Johan, you are downloading the files produced by the server. These files depend on several input files, program parameters, the mkgmap release and - of course- the OSM data. If an error occurs or disappears, we never know exactly why, and - to me - the server is a black box. For the programmer, the best situation is a fixed set of input files and parms that allows him to reproduce the problem on his own machine. Gerd From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 11:35:16 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Gerd If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. Mmmmm, is this not what I have been doing here? Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:17 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, okay, mkgmap r3336 is the current version of the map compiler mkgmap, which is used by Lambertus who offers the service at http://garmin.openstreetmap.nl/. The r3336 simply means it is based on the revision 3336 in the Subversion repository. You can download this program here: http://www.mkgmap.org.uk/download/mkgmap.html If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. You may also try if the "Routable Bicycle (Openfietsmap Lite)" shows the same problem. @Lambertus: Do you publish the style and the options that are used for your service anywhere? Ciao, GerdFrom: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 10:54:47 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indicationHi Gerd I just want to let you know that I do not compile and/or edit any OSM maps. I do not have any experience in the area. I therefore have no idea what “mkgmap r3336” is. The way I get OSM maps onto my PGS is by visiting http://garmin.openstreetmap.nl/, selecting the desired tiles “Generic Routable (new style)” and then clicking on “Build my map”. I then run the *.exe file that will extract the tiles and see to it that I have the correct imported map into BaseCamp. From there load the maps onto my GPS. Your two *.img files (V1 & V2) I just copied directly onto my GPS for the testing purposes. BO TH work perfectly when I simulate a route… the Danish voice prompt guides me to take the correct exit & and the icon indication the relive position for exiting the roundabout is correct. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 07:55 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd For the programmer, the best situation is a fixed set of input files and parms that allows him to reproduce the problem on his own machine. I agree. I have no idea how to do this, but I can imagine that for this I need OSM data and the mkgmap compiler, not true? Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:54 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, you are downloading the files produced by the server. These files depend on several input files, program parameters, the mkgmap release and - of course- the OSM data. If an error occurs or disappears, we never know exactly why, and - to me - the server is a black box. For the programmer, the best situation is a fixed set of input files and parms that allows him to reproduce the problem on his own machine. Gerd _____ From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 11:35:16 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Gerd If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. Mmmmm, is this not what I have been doing here? Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:17 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, okay, mkgmap r3336 is the current version of the map compiler mkgmap, which is used by Lambertus who offers the service at http://garmin.openstreetmap.nl/. The r3336 simply means it is based on the revision 3336 in the Subversion repository. You can download this program here: http://www.mkgmap.org.uk/download/mkgmap.html If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. You may also try if the "Routable Bicycle (Openfietsmap Lite)" shows the same problem. @Lambertus: Do you publish the style and the options that are used for your service anywhere? Ciao, Gerd _____ From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 10:54:47 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Gerd I just want to let you know that I do not compile and/or edit any OSM maps. I do not have any experience in the area. I therefore have no idea what "mkgmap r3336" is. The way I get OSM maps onto my PGS is by visiting http://garmin.openstreetmap.nl/, selecting the desired tiles "Generic Routable (new style)" and then clicking on "Build my map". I then run the *.exe file that will extract the tiles and see to it that I have the correct imported map into BaseCamp. From there load the maps onto my GPS. Your two *.img files (V1 & V2) I just copied directly onto my GPS for the testing purposes. BO TH work perfectly when I simulate a route. the Danish voice prompt guides me to take the correct exit & and the icon indication the relive position for exiting the roundabout is correct. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 07:55 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, _____ And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Johan, if you are interested in the details see http://www.mkgmap.org.uk/ It contains links to the program, the manual etc. The program is rather for OSM experts, and although I am helping to maintain it I also like to use Lambertus service when I need a map for my cycle tours ;-) Gerd From: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 12:05:08 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Gerd For the programmer, the best situation is a fixed set of input files and parms that allows him to reproduce the problem on his own machine.I agree. I have no idea how to do this, but I can imagine that for this I need OSM data and the mkgmap compiler, not true? Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:54 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, you are downloading the files produced by the server. These files depend on several input files, program parameters, the mkgmap release and - of course- the OSM data. If an error occurs or disappears, we never know exactly why, and - to me - the server is a black box. For the programmer, the best situation is a fixed set of input files and parms that allows him to reproduce the problem on his own machine. GerdFrom: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 11:35:16 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indicationHi Gerd If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. Mmmmm, is this not what I have been doing here? Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 11:17 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, okay, mkgmap r3336 is the current version of the map compiler mkgmap, which is used by Lambertus who offers the service at http://garmin.openstreetmap.nl/. The r3336 simply means it is based on the revision 3336 in the Subversion repository. You can download this program here: http://www.mkgmap.org.uk/download/mkgmap.html If you think the problem is caused by mkgmap, it would be of great help if you could reproduce the problem with e.g. the wrong-exit.osm that I used. You may also try if the "Routable Bicycle (Openfietsmap Lite)" shows the same problem. @Lambertus: Do you publish the style and the options that are used for your service anywhere? Ciao, GerdFrom: spa@thecyberinn.com To: mkgmap-dev@lists.mkgmap.org.uk Date: Fri, 3 Oct 2014 10:54:47 +0200 Subject: Re: [mkgmap-dev] Incorrect runabout exit indicationHi Gerd I just want to let you know that I do not compile and/or edit any OSM maps. I do not have any experience in the area. I therefore have no idea what “mkgmap r3336” is. The way I get OSM maps onto my PGS is by visiting http://garmin.openstreetmap.nl/, selecting the desired tiles “Generic Routable (new style)” and then clicking on “Build my map”. I then run the *.exe file that will extract the tiles and see to it that I have the correct imported map into BaseCamp. From there load the maps onto my GPS. Your two *.img files (V1 & V2) I just copied directly onto my GPS for the testing purposes. BO TH work perfectly when I simulate a route… the Danish voice prompt guides me to take the correct exit & and the icon indication the relive position for exiting the roundabout is correct. Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 3. oktober 2014 07:55 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, And yes... I'm fearing the firmware as the culprit too, however, Garmin's maps and other third party maps complied with others compilers work perfectly.... okay, I did not get that before. There is a function in mkgmap that manipulates the values of angles to assure that Garmin gives correct advices at e.g. roundabouts: --adjust-turn-headings I think this might be the reason for the problem. I've compiled two gmapsupp files for the roundabout from your 2nd example, once with (v1), once without this option (v2) Please check if you see a difference. The attached file contains the input file and the different gmapsupp files produced with mkgmap r3336: v1: java -jar mkgmap.jar --route --index --gmapsupp wrong-exit.osm v2: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings wrong-exit.osm Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Gerd, The new styles for Lambertus you can find here: https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fs... The issue could be that there are two lines used for roundabouts: https://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/styles/wor... First step, an invisible routable line for the roundabouts 0x0c # Roundabouts junction=roundabout & highway=trunk [0x0c road_class=3 road_speed=2 resolution 18 continue with_actions] junction=roundabout & highway=primary [0x0c road_class=3 road_speed=2 resolution 19 continue with_actions] junction=roundabout & highway=secondary [0x0c road_class=2 road_speed=2 resolution 20 continue with_actions] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & !(highway=unclassified|highway=tertiary|highway=secondary|highway=primary| highway=trunk) [0x0c road_class=0 road_speed=1 resolution 22 continue with_actions] Second step, all roundabouts are made unaccessible after 0x0c is processed, in order to prevent two routable lines on top of each other: junction=roundabout {set access=no} Third step (continue with_actions) the highways are rendered, so you can see a difference in road classes on those roundabouts. The default mkgmap style (=Lambertus 'old style') renders all roundabouts the same. I think Johan's nuvi gets confused by those two routable types?
Hi Minko, thanks for the info. I am pretty sure that this "trick" is the cause of the problem, but I am not sure if mkgmap can be improved to handle it. If I got it right, the additional roads with access=no are also handled by the adjust-turn-headings option, so maybe they are only causing trouble here. I don't know if (or how) I can configure my Oregon to show the problem, so I've created more test maps for Johan: v3: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v4: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with the original style files . v5: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v6: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with a modified lines file (removed the "continue with_actions" for the roundabouts) @Johan: Please check all 4 versions Gerd
Date: Fri, 3 Oct 2014 17:56:44 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Gerd, The new styles for Lambertus you can find here: https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fs...
The issue could be that there are two lines used for roundabouts:
https://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/styles/wor...
First step, an invisible routable line for the roundabouts 0x0c
# Roundabouts junction=roundabout & highway=trunk [0x0c road_class=3 road_speed=2 resolution 18 continue with_actions] junction=roundabout & highway=primary [0x0c road_class=3 road_speed=2 resolution 19 continue with_actions] junction=roundabout & highway=secondary [0x0c road_class=2 road_speed=2 resolution 20 continue with_actions] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & !(highway=unclassified|highway=tertiary|highway=secondary|highway=primary| highway=trunk) [0x0c road_class=0 road_speed=1 resolution 22 continue with_actions]
Second step, all roundabouts are made unaccessible after 0x0c is processed, in order to prevent two routable lines on top of each other:
junction=roundabout {set access=no}
Third step (continue with_actions) the highways are rendered, so you can see a difference in road classes on those roundabouts. The default mkgmap style (=Lambertus 'old style') renders all roundabouts the same.
I think Johan's nuvi gets confused by those two routable types?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Good morning Gerd We know that Generic Routable (old style) maps compiled by Lambertus's site work correct. We know that Generic Routable (new style) maps compiled by Lambertus's site cause problems. The test maps you send me. are they all new style maps? Here are the results of the 4 maps samples you sent me: ********************************************** v3 - the icon indicating the relative position for exiting the roundabout is INCORRECT (a relative position indicating one roundabout exit LATER than the correct exit) v4 - the icon indicating the relative position for exiting the roundabout is INCORRECT (a relative position indicating one roundabout exit LATER than the correct exit) V5 - the icon indicating the relative position for exiting the roundabout is CORRECT V6 - the icon indicating the relative position for exiting the roundabout is CORRECT Greetings Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 4. oktober 2014 08:29 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Minko, thanks for the info. I am pretty sure that this "trick" is the cause of the problem, but I am not sure if mkgmap can be improved to handle it. If I got it right, the additional roads with access=no are also handled by the adjust-turn-headings option, so maybe they are only causing trouble here. I don't know if (or how) I can configure my Oregon to show the problem, so I've created more test maps for Johan: v3: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v4: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with the original style files . v5: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v6: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with a modified lines file (removed the "continue with_actions" for the roundabouts) @Johan: Please check all 4 versions Gerd
Date: Fri, 3 Oct 2014 17:56:44 +0200
From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Gerd, The new styles for Lambertus you can find here:
https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fs tyles%2Fworld
The issue could be that there are two lines used for roundabouts:
https://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/styles/wor ld/lines
First step, an invisible routable line for the roundabouts 0x0c
# Roundabouts junction=roundabout & highway=trunk [0x0c road_class=3 road_speed=2
resolution 18 continue with_actions]
junction=roundabout & highway=primary [0x0c road_class=3 road_speed=2 resolution 19 continue with_actions] junction=roundabout & highway=secondary [0x0c road_class=2 road_speed=2 resolution 20 continue with_actions] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & !(highway=unclassified|highway=tertiary|highway=secondary|highway=primary| highway=trunk) [0x0c road_class=0 road_speed=1 resolution 22 continue with_actions]
Second step, all roundabouts are made unaccessible after 0x0c is processed, in order to prevent two routable lines on top of each other:
junction=roundabout {set access=no}
Third step (continue with_actions) the highways are rendered, so you can see a difference in road classes on those roundabouts. The default mkgmap style (=Lambertus 'old style') renders all roundabouts the same.
I think Johan's nuvi gets confused by those two routable types?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Johan, v3 and v4 are new style with two different program options, v5 and v6 are slightly modified new style maps with the same options. More detailed: If you watch your map, you see that Garmin shows major roads with other colors and bitmaps compared to smaller roads. This is done because the img file contains information about the "type of road". The roundabouts are special, because Garmin only has one type "roundabout", so normally, it displays the roundabout for a major road with the same color and bitmap as one for a small road. The "new style" tried to use a "trick": It stores the roundabout once as roundabout, once as a normal street, so that the device shows the correct color and bitmap, but obviously this confuses the algo in your device. The v5 and v6 versions don't contain this trick. AFAIK Garmin maps never use this trick, so I fear we can't blame the Garmin algo for being confused. @Minko, Lambertus: I'd prefer the map without the trick, it is smaller and less likely to confuse the routing. Gerd We know that Generic Routable (old style) maps compiled by Lambertus’s site work correct. We know that Generic Routable (new style) maps compiled by Lambertus’s site cause problems. The test maps you send me… are they all new style maps? Here are the results of the 4 maps samples you sent me: ********************************************** v3 – the icon indicating the relative position for exiting the roundabout is INCORRECT(a relative position indicating one roundabout exit LATER than the correct exit) v4 – the icon indicating the relative position for exiting the roundabout is INCORRECT(a relative position indicating one roundabout exit LATER than the correct exit) V5 – the icon indicating the relative position for exiting the roundabout is CORRECT V6 – the icon indicating the relative position for exiting the roundabout is CORRECT Greetings Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 4. oktober 2014 08:29 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Minko, thanks for the info. I am pretty sure that this "trick" is the cause of the problem, but I am not sure if mkgmap can be improved to handle it. If I got it right, the additional roads with access=no are also handled by the adjust-turn-headings option, so maybe they are only causing trouble here. I don't know if (or how) I can configure my Oregon to show the problem, so I've created more test maps for Johan: v3: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v4: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with the original style files . v5: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v6: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with a modified lines file (removed the "continue with_actions" for the roundabouts) @Johan: Please check all 4 versions Gerd
Date: Fri, 3 Oct 2014 17:56:44 +0200> From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Gerd, The new styles for Lambertus you can find here: https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fs...
The issue could be that there are two lines used for roundabouts:
https://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/styles/wor...
First step, an invisible routable line for the roundabouts 0x0c
# Roundabouts junction=roundabout & highway=trunk [0x0c road_class=3 road_speed=2 resolution 18 continue with_actions] junction=roundabout & highway=primary [0x0c road_class=3 road_speed=2 resolution 19 continue with_actions] junction=roundabout & highway=secondary [0x0c road_class=2 road_speed=2 resolution 20 continue with_actions] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & !(highway=unclassified|highway=tertiary|highway=secondary|highway=primary| highway=trunk) [0x0c road_class=0 road_speed=1 resolution 22 continue with_actions]
Second step, all roundabouts are made unaccessible after 0x0c is processed, in order to prevent two routable lines on top of each other:
junction=roundabout {set access=no}
Third step (continue with_actions) the highways are rendered, so you can see a difference in road classes on those roundabouts. The default mkgmap style (=Lambertus 'old style') renders all roundabouts the same.
I think Johan's nuvi gets confused by those two routable types?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am Samstag, 4. Oktober 2014, 09:38:35 schrieb Gerd Petermann: Hi
It stores the roundabout once as roundabout, once as a normal street, so that the device shows the correct color and bitmap, but obviously this confuses the algo in your device. The v5 and v6 versions don't contain this trick.
I use roundabout in the following way, so i got the hints in the correct way and don't see the ugly orange rings ;-) #-------------------------------------------------------------------------------------- # secondary as example | highway=secondary [0x12004 resolution 21-20 continue] | highway=secondary [0x11004 resolution 24-22 continue] | highway=secondary & junction=roundabout | [0x0c resolution 24 road_class=2 road_speed=2] | highway=secondary [0x04 resolution 24 road_class=3 road_speed=4] | | highway=secondary_link [0x12004 resolution 22-22 continue] | highway=secondary_link [0x11004 resolution 24-23 continue] | highway=secondary_link [0x08 resolution 24 road_class=3 road_speed=3] Most of my routable ways are invisible and used on level 1 oder resolution 24. | [_line] | Type=0x0c | UseOrientation=N | Xpm="32 1 2 1" | "! c #FFFFFF" | " c none" | " " | ;12345678901234567890123456789012 | String1=0x02,Kreisverkehr | String2=0x04,Roundabout | ExtendedLabels=N | [end] You can find my style here https://github.com/berndw1960/aiostyles Bernd
Hi Gerd Thank you for all the information. I guess till further notice I will have to be satisfied with Generic Routable (old style) maps if I want to avoid the incorrect roundabout icon exit indication then. Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 4. oktober 2014 09:39 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Johan, v3 and v4 are new style with two different program options, v5 and v6 are slightly modified new style maps with the same options. More detailed: If you watch your map, you see that Garmin shows major roads with other colors and bitmaps compared to smaller roads. This is done because the img file contains information about the "type of road". The roundabouts are special, because Garmin only has one type "roundabout", so normally, it displays the roundabout for a major road with the same color and bitmap as one for a small road. The "new style" tried to use a "trick": It stores the roundabout once as roundabout, once as a normal street, so that the device shows the correct color and bitmap, but obviously this confuses the algo in your device. The v5 and v6 versions don't contain this trick. AFAIK Garmin maps never use this trick, so I fear we can't blame the Garmin algo for being confused. @Minko, Lambertus: I'd prefer the map without the trick, it is smaller and less likely to confuse the routing. Gerd _____ We know that Generic Routable (old style) maps compiled by Lambertus's site work correct. We know that Generic Routable (new style) maps compiled by Lambertus's site cause problems. The test maps you send me. are they all new style maps? Here are the results of the 4 maps samples you sent me: ********************************************** v3 - the icon indicating the relative position for exiting the roundabout is INCORRECT (a relative position indicating one roundabout exit LATER than the correct exit) v4 - the icon indicating the relative position for exiting the roundabout is INCORRECT (a relative position indicating one roundabout exit LATER than the correct exit) V5 - the icon indicating the relative position for exiting the roundabout is CORRECT V6 - the icon indicating the relative position for exiting the roundabout is CORRECT Greetings Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Gerd Petermann Sent: 4. oktober 2014 08:29 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication Hi Minko, thanks for the info. I am pretty sure that this "trick" is the cause of the problem, but I am not sure if mkgmap can be improved to handle it. If I got it right, the additional roads with access=no are also handled by the adjust-turn-headings option, so maybe they are only causing trouble here. I don't know if (or how) I can configure my Oregon to show the problem, so I've created more test maps for Johan: v3: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v4: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with the original style files . v5: java -jar mkgmap.jar --route --index --gmapsupp --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm v6: java -jar mkgmap.jar --route --index --gmapsupp --adjust-turn-headings --style-file=d:\mkgmap-style-sheets-read-only\styles\world wrong-exit.osm both with a modified lines file (removed the "continue with_actions" for the roundabouts) @Johan: Please check all 4 versions Gerd
Date: Fri, 3 Oct 2014 17:56:44 +0200
From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication
Gerd, The new styles for Lambertus you can find here:
https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fs tyles%2Fworld <https://code.google.com/p/mkgmap-style-sheets/source/browse/#svn/trunk/styl es/world>
The issue could be that there are two lines used for roundabouts:
https://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/styles/wor ld/lines
First step, an invisible routable line for the roundabouts 0x0c
# Roundabouts junction=roundabout & highway=trunk [0x0c road_class=3 road_speed=2
resolution 18 continue with_actions]
junction=roundabout & highway=primary [0x0c road_class=3 road_speed=2 resolution 19 continue with_actions] junction=roundabout & highway=secondary [0x0c road_class=2 road_speed=2 resolution 20 continue with_actions] junction=roundabout & highway=tertiary [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21 continue with_actions] junction=roundabout & !(highway=unclassified|highway=tertiary|highway=secondary|highway=primary| highway=trunk) [0x0c road_class=0 road_speed=1 resolution 22 continue with_actions]
Second step, all roundabouts are made unaccessible after 0x0c is processed, in order to prevent two routable lines on top of each other:
junction=roundabout {set access=no}
Third step (continue with_actions) the highways are rendered, so you can see a difference in road classes on those roundabouts. The default mkgmap style (=Lambertus 'old style') renders all roundabouts the same.
I think Johan's nuvi gets confused by those two routable types?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
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: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of SomeoneElse Sent: 30. september 2014 15:27 To: mkgmap-dev@lists.mkgmap.org.uk 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 mkgmap-dev@lists.mkgmap.org.uk 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 mkgmap-dev@lists.mkgmap.org.uk 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
On 30/09/2014 15:34, Colin Smale wrote:
Also you say you are using r1919 of mkgmap.
Just for the avoidance of doubt - it's me that's using the out-of-the-ark version of mkgmap - the person with the original problem was seeing the issue with Lambertus' maps (which I suspect will be created with a much newer version). Cheers, Andy
Hi Colin
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. No correct. My Gamin has more than the 3-6-9-12 o’clock icons.
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?
I have no idea what “r1919 of mkgmap” is??? I use Lambertus' maps from http://garmin.openstreetmap.nl/ Regards Johan From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Colin Smale Sent: 30. september 2014 16:34 To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Incorrect runabout exit indication 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 Greetings Johan P.S. Remember... life is not about the destination, but the amazing journey. :) -----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of SomeoneElse Sent: 30. september 2014 15:27 To: mkgmap-dev@lists.mkgmap.org.uk 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 mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4765 / Virus Database: 4025/8297 - Release Date: 09/30/14 _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (8)
-
Bernd Weigelt -
Colin Smale -
Gerd Petermann -
Minko -
Peter Hendricks -
SomeoneElse -
SPA -
spa＠thecyberinn.com