Hi Andrzej,
I can confirm that way 227105752 seems to get a wrong road speed when
using your sample data. ("seems" because that's what GMapEdit tells me -
there is no guarantee that there isn't a bug in GMapEdit)
I have done some tests and found a problem in mkgmap which need to be
fixed although I cannot say now that it is the source of the described
problem.
@Gerd: StyledConverter.postConvertRules can change the road speed in the
type. But this hasn't been copied before so I guess it's changing the
global type of the rule. Can you check that?
I added
type = new GType(type);
at line 202 but this didn't change the overall result. So it seems not
to be the only problem.
WanMil
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.
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
