Current default style produces some estrange detours for a test route in a couple of places in my home town (blue circles 1 and 2 in attached screenshot). I've tracked the issue down and behavior has been changing with mkgmap versions, as detailed in the following chart, being current situation worst for this particular case: MapSource 6.16.3 BaseCamp 4.2.5 mkgmap version Car Truck Car Truck 1 2 1 2 1 2 1 2 <3081 OK OK OK OK OK OK OK OK 3088-3108 Suboptimal route OK Loop OK Loop OK Loop
=3111 Suboptimal route Bad Loop OK Loop OK Loop
Main changes were introduced with r3081 (merge from the high-prec-coord branch) and r3111 (merge from NOD127 branch). Perhaps those changes need a review. All test were done with the following command, only changing mkgmap jar file: java -Xmx600m -ea -jar mkgmap.jar --bounds=bounds.zip --route --latin1 --code-page=1252 --family-name="Test" --family-id=190 --product-id=1 --series-name="Test-default" --overview-mapname=55190000 --mapname=55190000 --index --add-pois-to-areas --link-pois-to-ways --location-autofill=is_in,nearest --style=default typ/EUR-190.TYP /home/carlos/tmp/test1.osm Files for test: http://alternativaslibres.org/files/detours.zip Note that first street after point 1 is tagged hgv=no, otherwise trucks would probably take the same suboptimal route than cars since r3081.
Hi Carlos, I have your example tested in BaseCamp and I don't see any problems at point 1. At point 2 weird routing appears only for track and camper. It could be due to angle at crossroad. I could get normal turn right after changing geometry of this crossroad, as in attached picture. I think there were some changes in mkgmap dealing with angels between roads. Maybe this code should be reviewed? -- Best regards, Andrzej
El 05/01/17 a las 19:05, Andrzej Popowski escribió:
Hi Carlos,
I have your example tested in BaseCamp and I don't see any problems at point 1. At point 2 weird routing appears only for track and camper. It could be due to angle at crossroad. I could get normal turn right after changing geometry of this crossroad, as in attached picture.
I think there were some changes in mkgmap dealing with angels between roads. Maybe this code should be reviewed? Hi Andrzej Your findings in BaseCamp match what I found. I guess the problem comes from the angle between crossing roads, but modifying it as in your picture would be "tagging for the render" I suspect;-). Current angle between those two streets is wider than 90º and it shouldn't be avoided for routing anyway. Attached is a picture with the correct chart
Hi, my understanding so far is that the Garmin algo doesn't like a rather sharp turn on a road with highway=trunk [0x02 road_class=4 road_speed=5 resolution 18] In Germany a trunk road is nearly like a motorway and it seems that the above rule is good for this. Maybe we should add country specific rules here? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 5. Januar 2017 21:01:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours El 05/01/17 a las 19:05, Andrzej Popowski escribió:
Hi Carlos,
I have your example tested in BaseCamp and I don't see any problems at point 1. At point 2 weird routing appears only for track and camper. It could be due to angle at crossroad. I could get normal turn right after changing geometry of this crossroad, as in attached picture.
I think there were some changes in mkgmap dealing with angels between roads. Maybe this code should be reviewed? Hi Andrzej Your findings in BaseCamp match what I found. I guess the problem comes from the angle between crossing roads, but modifying it as in your picture would be "tagging for the render" I suspect;-). Current angle between those two streets is wider than 90º and it shouldn't be avoided for routing anyway. Attached is a picture with the correct chart
That could explain detour at point 2, but I have tried downgrading implied roads up to tertiary with no routing change. Point 1 is a straight road, but MapSource prefers to turn right and then left instead. El 05/01/17 a las 21:13, Gerd Petermann escribió:
Hi,
my understanding so far is that the Garmin algo doesn't like a rather sharp turn on a road with highway=trunk [0x02 road_class=4 road_speed=5 resolution 18]
In Germany a trunk road is nearly like a motorway and it seems that the above rule is good for this. Maybe we should add country specific rules here?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 5. Januar 2017 21:01:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours
El 05/01/17 a las 19:05, Andrzej Popowski escribió:
Hi Carlos,
I have your example tested in BaseCamp and I don't see any problems at point 1. At point 2 weird routing appears only for track and camper. It could be due to angle at crossroad. I could get normal turn right after changing geometry of this crossroad, as in attached picture.
I think there were some changes in mkgmap dealing with angels between roads. Maybe this code should be reviewed? Hi Andrzej Your findings in BaseCamp match what I found. I guess the problem comes from the angle between crossing roads, but modifying it as in your picture would be "tagging for the render" I suspect;-). Current angle between those two streets is wider than 90º and it shouldn't be avoided for routing anyway. Attached is a picture with the correct chart
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale LibreOffice desde http://es.libreoffice.org/descarga/ LibreOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. LibreOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones.
OK, I'll have a closer look at the calculated angles tomorrow. Maybe problem at point 1 is related to the type=through_route relation. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 5. Januar 2017 21:34:40 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours That could explain detour at point 2, but I have tried downgrading implied roads up to tertiary with no routing change. Point 1 is a straight road, but MapSource prefers to turn right and then left instead. El 05/01/17 a las 21:13, Gerd Petermann escribió:
Hi,
my understanding so far is that the Garmin algo doesn't like a rather sharp turn on a road with highway=trunk [0x02 road_class=4 road_speed=5 resolution 18]
In Germany a trunk road is nearly like a motorway and it seems that the above rule is good for this. Maybe we should add country specific rules here?
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 5. Januar 2017 21:01:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours
El 05/01/17 a las 19:05, Andrzej Popowski escribió:
Hi Carlos,
I have your example tested in BaseCamp and I don't see any problems at point 1. At point 2 weird routing appears only for track and camper. It could be due to angle at crossroad. I could get normal turn right after changing geometry of this crossroad, as in attached picture.
I think there were some changes in mkgmap dealing with angels between roads. Maybe this code should be reviewed? Hi Andrzej Your findings in BaseCamp match what I found. I guess the problem comes from the angle between crossing roads, but modifying it as in your picture would be "tagging for the render" I suspect;-). Current angle between those two streets is wider than 90º and it shouldn't be avoided for routing anyway. Attached is a picture with the correct chart
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Por favor, no me envíe documentos con extensiones .doc, .docx, .xls, .xlsx, .ppt, .pptx, .mdb, mdbx Instale LibreOffice desde http://es.libreoffice.org/descarga/ LibreOffice es libre: se puede copiar, modificar y redistribuir libremente. Gratis y totalmente legal. LibreOffice está en continuo desarrollo y no tendrá que pagar por las nuevas versiones. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi, I have converted all trunks and primary into secondary roads and it didn't solve problem, so it is rather not connected to Garmin road type 0x02. Still rules for trunks in Spain doesn't fit well into mkgmap conversion, there could be other problems, like for example weird navigation messages. I have found another example for weird routing, where route turns form primary road into longer detour on service road, see picture angle2. In my case wrong routing is for car and motorcycle but goes correctly for truck. If I change angle for service road like on picture angle2, routing is correct. Attached is OSM data extract and test route for BaseCamp. -- Best regards, Andrzej
Hi Andrzej, I cannot reproduce this problem in MapSource. In Basecamp car and truck use the correct routing, motorcycle is as in your picture. I do not yet have a good idea where to look at. I tried changing the order of objects but that did not change the results. Maybe there is a special case with the encoding of bearings, but I have no clue. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Freitag, 6. Januar 2017 14:44:53 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Estrange detours Hi, I have converted all trunks and primary into secondary roads and it didn't solve problem, so it is rather not connected to Garmin road type 0x02. Still rules for trunks in Spain doesn't fit well into mkgmap conversion, there could be other problems, like for example weird navigation messages. I have found another example for weird routing, where route turns form primary road into longer detour on service road, see picture angle2. In my case wrong routing is for car and motorcycle but goes correctly for truck. If I change angle for service road like on picture angle2, routing is correct. Attached is OSM data extract and test route for BaseCamp. -- Best regards, Andrzej
It really seems to be a problem with the encoding of the bearings. I have attached a small patch which seems to fix the problem here, but I am pretty sure that there is more to it. The patch disables the "compacted" format of angles when an indirect arc is found. I have to analyse my Garmin maps to find out more. Please try if the results of the patched version are okay for you: http://files.mkgmap.org.uk/download/324/mkgmap.jar Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Freitag, 6. Januar 2017 16:47:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours Hi Andrzej, I cannot reproduce this problem in MapSource. In Basecamp car and truck use the correct routing, motorcycle is as in your picture. I do not yet have a good idea where to look at. I tried changing the order of objects but that did not change the results. Maybe there is a special case with the encoding of bearings, but I have no clue. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Freitag, 6. Januar 2017 14:44:53 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Estrange detours Hi, I have converted all trunks and primary into secondary roads and it didn't solve problem, so it is rather not connected to Garmin road type 0x02. Still rules for trunks in Spain doesn't fit well into mkgmap conversion, there could be other problems, like for example weird navigation messages. I have found another example for weird routing, where route turns form primary road into longer detour on service road, see picture angle2. In my case wrong routing is for car and motorcycle but goes correctly for truck. If I change angle for service road like on picture angle2, routing is correct. Attached is OSM data extract and test route for BaseCamp. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
It doesn't make any difference for my test case in MapSource, but in BaseCamp routing is correct now in point 2 both for car and truck. Seems to be in the right way... El 06/01/17 a las 18:04, Gerd Petermann escribió:
It really seems to be a problem with the encoding of the bearings. I have attached a small patch which seems to fix the problem here, but I am pretty sure that there is more to it. The patch disables the "compacted" format of angles when an indirect arc is found. I have to analyse my Garmin maps to find out more.
Please try if the results of the patched version are okay for you: http://files.mkgmap.org.uk/download/324/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Freitag, 6. Januar 2017 16:47:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours
Hi Andrzej,
I cannot reproduce this problem in MapSource. In Basecamp car and truck use the correct routing, motorcycle is as in your picture. I do not yet have a good idea where to look at. I tried changing the order of objects but that did not change the results. Maybe there is a special case with the encoding of bearings, but I have no clue.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Freitag, 6. Januar 2017 14:44:53 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Estrange detours
Hi,
I have converted all trunks and primary into secondary roads and it didn't solve problem, so it is rather not connected to Garmin road type 0x02. Still rules for trunks in Spain doesn't fit well into mkgmap conversion, there could be other problems, like for example weird navigation messages.
I have found another example for weird routing, where route turns form primary road into longer detour on service road, see picture angle2. In my case wrong routing is for car and motorcycle but goes correctly for truck. If I change angle for service road like on picture angle2, routing is correct.
Attached is OSM data extract and test route for BaseCamp.
-- Best regards, Andrzej
I double checked your patch and it also fixes routing in MapSource, with or without --preserve-element-order. Sorry for the previous wrong feedback El 06/01/17 a las 20:09, Carlos Dávila escribió:
It doesn't make any difference for my test case in MapSource, but in BaseCamp routing is correct now in point 2 both for car and truck. Seems to be in the right way...
El 06/01/17 a las 18:04, Gerd Petermann escribió:
It really seems to be a problem with the encoding of the bearings. I have attached a small patch which seems to fix the problem here, but I am pretty sure that there is more to it. The patch disables the "compacted" format of angles when an indirect arc is found. I have to analyse my Garmin maps to find out more.
Please try if the results of the patched version are okay for you: http://files.mkgmap.org.uk/download/324/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Freitag, 6. Januar 2017 16:47:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours
Hi Andrzej,
I cannot reproduce this problem in MapSource. In Basecamp car and truck use the correct routing, motorcycle is as in your picture. I do not yet have a good idea where to look at. I tried changing the order of objects but that did not change the results. Maybe there is a special case with the encoding of bearings, but I have no clue.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Freitag, 6. Januar 2017 14:44:53 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Estrange detours
Hi,
I have converted all trunks and primary into secondary roads and it didn't solve problem, so it is rather not connected to Garmin road type 0x02. Still rules for trunks in Spain doesn't fit well into mkgmap conversion, there could be other problems, like for example weird navigation messages.
I have found another example for weird routing, where route turns form primary road into longer detour on service road, see picture angle2. In my case wrong routing is for car and motorcycle but goes correctly for truck. If I change angle for service road like on picture angle2, routing is correct.
Attached is OSM data extract and test route for BaseCamp.
-- Best regards, Andrzej
Hi Carlos, that's great! I'll continue to investigate tomorrow. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Freitag, 6. Januar 2017 20:49:26 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours I double checked your patch and it also fixes routing in MapSource, with or without --preserve-element-order. Sorry for the previous wrong feedback El 06/01/17 a las 20:09, Carlos Dávila escribió:
It doesn't make any difference for my test case in MapSource, but in BaseCamp routing is correct now in point 2 both for car and truck. Seems to be in the right way...
El 06/01/17 a las 18:04, Gerd Petermann escribió:
It really seems to be a problem with the encoding of the bearings. I have attached a small patch which seems to fix the problem here, but I am pretty sure that there is more to it. The patch disables the "compacted" format of angles when an indirect arc is found. I have to analyse my Garmin maps to find out more.
Please try if the results of the patched version are okay for you: http://files.mkgmap.org.uk/download/324/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Freitag, 6. Januar 2017 16:47:42 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours
Hi Andrzej,
I cannot reproduce this problem in MapSource. In Basecamp car and truck use the correct routing, motorcycle is as in your picture. I do not yet have a good idea where to look at. I tried changing the order of objects but that did not change the results. Maybe there is a special case with the encoding of bearings, but I have no clue.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Freitag, 6. Januar 2017 14:44:53 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Estrange detours
Hi,
I have converted all trunks and primary into secondary roads and it didn't solve problem, so it is rather not connected to Garmin road type 0x02. Still rules for trunks in Spain doesn't fit well into mkgmap conversion, there could be other problems, like for example weird navigation messages.
I have found another example for weird routing, where route turns form primary road into longer detour on service road, see picture angle2. In my case wrong routing is for car and motorcycle but goes correctly for truck. If I change angle for service road like on picture angle2, routing is correct.
Attached is OSM data extract and test route for BaseCamp.
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, BaseCamp has a lot of options for each type of routing. Maybe some of them influence outcome in this case. I have reset all options recently. I haven't tested in Mapsource. I'm not sure if I remember correctly. I think you wrote sometime about crossroad angle coded into NOD or NET subfile. Is it possible, that this angle is calculated or encoded wrong? A side note: in my example detour goes by service road. Default style set road_speed=2 for service roads, which seems too high. 0 or 1 would look more realistic. I would set 0 for service=parking_aisle too. -- Best regards, Andrzej
Hi, difficult to understand for me: http://wiki.openstreetmap.org/wiki/Highway:International_equivalence I guess that in Spain, highway=trunk should include motorrad=yes to become Garmin's highway. -- Best regards, Andrzej
El 05/01/17 a las 23:20, Andrzej Popowski escribió:
Hi,
difficult to understand for me: http://wiki.openstreetmap.org/wiki/Highway:International_equivalence
I guess that in Spain, highway=trunk should include motorrad=yes to become Garmin's highway.
Most trunk roads in Spain are single roads with traffic in both directions. Only those with one road for each direction are tagged motorroad=yes
Hi Carlos, just want to mention that the command in your first post has an error in the options: --overview-mapname=55190000 --mapname=55190000 this cannot work, the values must be different. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Donnerstag, 5. Januar 2017 23:36:30 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours El 05/01/17 a las 23:20, Andrzej Popowski escribió:
Hi,
difficult to understand for me: http://wiki.openstreetmap.org/wiki/Highway:International_equivalence
I guess that in Spain, highway=trunk should include motorrad=yes to become Garmin's highway.
Most trunk roads in Spain are single roads with traffic in both directions. Only those with one road for each direction are tagged motorroad=yes _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
El 06/01/17 a las 09:06, Gerd Petermann escribió:
just want to mention that the command in your first post has an error in the options: --overview-mapname=55190000 --mapname=55190000 this cannot work, the values must be different.
It seems mkgmap automatically increases mapname 1 unit. This is what I get after running that command: 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190001.img If I use --overview-mapname=55190000 --mapname=55190001 I get 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190002.img
Hi Carlos, that is interesting. I added the option --nsis (as last option) for my tests and with your command I got only the overview map named 55190000.img. With --mapname=55190001 I got an additional file with the real map named 55190001.img Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Freitag, 6. Januar 2017 19:32:52 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours El 06/01/17 a las 09:06, Gerd Petermann escribió:
just want to mention that the command in your first post has an error in the options: --overview-mapname=55190000 --mapname=55190000 this cannot work, the values must be different.
It seems mkgmap automatically increases mapname 1 unit. This is what I get after running that command: 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190001.img If I use --overview-mapname=55190000 --mapname=55190001 I get 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190002.img _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I also suggest to use --preserve-element-order to make results predictable. If that option changes the routing we have a good hint that something has to be in a specific order. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Freitag, 6. Januar 2017 19:56:02 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours Hi Carlos, that is interesting. I added the option --nsis (as last option) for my tests and with your command I got only the overview map named 55190000.img. With --mapname=55190001 I got an additional file with the real map named 55190001.img Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Freitag, 6. Januar 2017 19:32:52 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours El 06/01/17 a las 09:06, Gerd Petermann escribió:
just want to mention that the command in your first post has an error in the options: --overview-mapname=55190000 --mapname=55190000 this cannot work, the values must be different.
It seems mkgmap automatically increases mapname 1 unit. This is what I get after running that command: 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190001.img If I use --overview-mapname=55190000 --mapname=55190001 I get 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190002.img _______________________________________________ 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, I have retested both examples in BaseCamp with your patched versions of mkgmap. All routes seems to be good, thanks! -- Best regards, Andrzej
participants (3)
-
Andrzej Popowski -
Carlos Dávila -
Gerd Petermann