Cheers, I can confirm that there is a strange behavior of the road speed generation. My first test with the echotags function, indicates that roads without maxspeed value, are handled if they had one. A simple "highway=primary" (and no more tags) cause trouble. Please see tha attached test case. My mkgmap version is 2946 Best regards, Manfred
Gesendet: Sonntag, 19. Januar 2014 um 20:11 Uhr Von: "Andrzej Popowski" <popej@poczta.onet.pl> An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Weird road speed
Hi WanMil
you can find a rather complete documentation of all mkgmap:* tags in the mkgmap style documentation
Thanks, this was the first place where I have looked, I don't know how could I miss it.
osmid()=227105752 & highway=* { echotags "Wrong roadspeed?" }
It is nice debugging facility. This is what I have found:
All tags displayed by echotags look correctly.
Value from mkgmap:road-speed-class is applied wrongly!
In case of my sample data way ID=227105752 gets value computed for way ID=227105746, which is tagged as maxspeed=100. If I set other maxspeed for way ID=227105746 then this value appears at way ID=227105752. Cropping input data removes way ID=227105746 and speed for ID=227105752 changes, but still is wrong.
I have checked speeds in img using GPSMapEdit and verified with nuvi in route simulation. It is serious bug in mkgmap.
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev