<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>> r2790 is quite old. I have tested the link-pois-to-ways code at some <br>> time after that but maybe I did check access restrictions only. The <br>> change was intended to implement the calculation at one point only. The <br>> main idea is, that there is a clear distinction between code before <br>> postConvertRules() and after that. Code before postConvertRules() can <br>> use (and has to implement) several more tags than after postConvertRules().<br><br>okay<br><br>> <br>> I get the feeling that it might be easier to move the handling of the <br>> link-pois-to-ways to an earlier point in the processing. The current <br>> code is quite complicated. Maybe it could be moved after processing the <br>> points style file and just before processing the lines and polygons <br>> style file. At this point modifications might be possible on the OSM way <br>> data like we do before the style processing is started (e.g. <br>> LinkDestinationHook).<br><br>I think we have to process the lines style first, because we need to know<br>the access tags and road speed and road class.<br><br>> <br>> If you want to leave the code where it is I would recommend to put the <br>> mkgmap:road-speed calcs etc. to separate methods so that they can be <br>> called from postConvertRules() and the pois handling. That also <br>> encapsulates these tags.<br>I prefer to create a modified copy of the GType instance. <br>I have to find out why it was not done like this all the time.<br>An old comment for the POI handling in StyledConverter says:<br> // we can't modify the road class or type in<br> // the GType as that's global so for now just<br> // transfer the tags to the way<br><br>Gerd<br></div> </div></body>
</html>