[mkgmap-dev] Routeable line types
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Thu Jul 9 11:06:24 BST 2020
Hi Gerd I had used 0x2d and 0x2e in my style and hadn't had any problems on my devices, but when looking at the recent routing problems I'd tried the same map on BaseCamp and areas on the map resorted to straight line routing. Joris had mentioned problems with this range so I tried 0x2c .. 0x2f and 0x13 in turn and BaseCamp failed in the areas where they were used for non-routable lines. I've assumed that the other ones already in the list will cause problems (ie 0x01..0x12, 0x16, 0x1a/b) MapSource had no problems - its algo seems to match my eTrex 30x (2018) and eTrex HCx (2009) Ticker On Thu, 2020-07-09 at 09:42 +0000, Gerd Petermann wrote: > Hi Ticker, > > please can describe the procedure you used to verify which types make > Basecamp routing fail? > > Gerd > > ________________________________________ > Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag > von Ticker Berkin <ticker at jagIT.co.uk> > Gesendet: Donnerstag, 9. Juli 2020 10:14 > An: mkgmap development > Betreff: [mkgmap-dev] Routeable line types > > Hi Gerd > > Patch attached that fixes isSpecialRoutableLineType to values that > definitely make BaseCamp routeing to fail when they are used for a > non > -routeable line and a change to allow mkgmap:set-[un,semi-]connected > -type to be a non-routeable type lower than 0x30 > > Ticker > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
- Previous message: [mkgmap-dev] Routeable line types
- Next message: [mkgmap-dev] Routeable line types
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list