
To Specify it a bit more: Affected are currently only GPS devices which support active routing (this new profile based stuff which we don't know how it is encoded), and Basecamp v 3.3 upwards (including Basecamp v4 beta). Using older GPS Firmware or Mapsource this problem is not present. I'm still trying to debug it however. Strangely GPSMapedit reports several polylines as type=0x5 instead of 0x05, or 0x6 instead of 0x06 - but no such types are present in my style... On 13.08.2012 18:42, Felix Hartmann wrote:
Well the title says most of it. AFAIK there is some setting in mkgmap, that splits up ways, or adds additional points to ways that are fully straight.
I tested around and to me it seems that it needs to be less than 800m as this might solve some long distance routing probs, and routing probs over tile borders. Currently it's much longer. Can this be adjusted in sourcecode easily?
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org