<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 all,<br><br>attached is a patch that changes the handling of option <br>--link-pois-to-ways.<br>In trunk, this option has two effects:<br>1) If a POI with a tag like access=mkgmap:road-speed=1<br>(e.g. highway=traffic-lights)<br>is found in a way, the way is split at the preceding and <br>following point and the change is applied to the remaining<br>part. The length of the effected part depends only on the distance<br>to the next point. If the way is straight, that can be > 300m,<br>if the POI is in an a curve, it might be < 10m.<br>2) If a POI with a tag like mkgmap:bicycle=no (e.g. barrier=bollard) <br>is found in a way, splits the way and before and after the POI so<br>that the length of the affected way segment is typically less 100m.<br>(max 50m before + max. 50m after the POI)<br>Next, the way is split again at the POI, so that routing <br>over the POI is not done for the restricted vehicles.<br>The effect is that routing to a point close to the POI<br>might not work (don't know that for sure, the device might<br>ignore the restriction if the target cannot be reached <br>"legally").<br><br>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>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>If I hear no complains, I'll commit that next sunday.<br><br>Gerd<br> </div></body>
</html>