<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi WanMil,<br><br><div>> > I think the wanted behaviour is this:<br>> > 1) The change in speed should be applied to max. 25m<br>> > before and after the POI or to the connection<br>> > with another way, whatever comes first.<br>> > 2) A POI like a barrier should not change access<br>> > to the way before or after the POI, only at the POI.<br>> ><br>> > The attached patch implements this changed behaviour.<br>> > The type 2) POI are converted to route restrictions.<br>> <br>> I've tested part 2) of the patch and it worked fine for me!<br><br>well, I think that means that part 1) is not yet working. <br>I am not sure, but I think you moved the evaluation of the<br>tags mkgmap:road-speed and mkgmap:road-class <br>so that the interpretation of the POI has no effect.<br>Was that intended?<br><br>> <br>> <br>> ><br>> > The patch also changes the meaning of route restrictions.<br>> > In r2907 and before, route restrictions prohibit access for<br>> > pedestrians and emergency, the patched version<br>> > allows them by default.<br>> <br>> Does that mean a common turn restriction from a=>b also means that <br>> pedestrians never can route a=>b?<br><br>yes, in trunk all turn restrictions are created without an exception<br>for pedestrians or emergency. <br><br>> ><br>> > If I hear no complains, I'll commit that next sunday.<br>> <br>> I propose to move the link-pois-to-ways handling before merging roads. <br>> Do you think it's complicated to move it?<br><br>Ahh, I forgot about this. I got a cold last weekend, so I'm not able to concentrate<br>very well. If I got this right, it should work if we add new <br>instances to roads and roadTypes for each part of the way, maybe with <br>a fake id. Not sure if it will reduce the number of roads,<br>I think more important is to fix the above problem.<br><br>Gerd<br></div> </div></body>
</html>