[mkgmap-dev] strange routing

Fri May 2 15:15:39 BST 2014

On 02.05.2014 15:53, Minko wrote:
> Hi Gerd,
> I have checked if those routing errors still exist by making a street non routable, eg
> highway=* & name=x [0x05 resolution 20]
>
> The addresses at street x are not in the index anymore and therefore not findable.
> A few years ago those were still in the index and caused problems.
> But now this bug seems eliminated, those warning messages are also not needed anymore?
>
> Now I've tried what happens if I make this street x with type 0x15 routable.
> highway=* & name=x [0x15 road_class=2 road_speed=2 resolution 20]
>
> 0x14, 0x15, 0x19 even 0x32 are routable, type 0x10014 not
> So I guess there are more routable types? Which types appear in NOD?
Are they also shown and routbale in:
Mapsource 6.13
Mapsource 6.16
Basecamp (don't mind version 1 or 2, they had too many problems and are 
not related much to GPS) - so just latest version
new generation GPS like Oregon
old generation like Vista HCx

and the jackpot - Nuvi??
Nuvis are somehower superspecial, and really behave different. On many 
Nuvis lots of extended types that show on all other units, do not show...

>
>
>> Hi Minko,
>>
>> okay, I have to try that. My understanding is that address search
>> knows only
>> routable ways (those that appear in NOD). And to NOD we write
>> all lines with road_class/road_speed attribute and a non-extended
>> type.
>> Maybe Garmin software expects (or expected) to find NOD data for
>> all lines with routable types.
>>
>> Gerd
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-- 
keep on biking and discovering new trails

Felix
openmtbmap.org & www.velomap.org