<div dir="ltr">Well, it can be dafaulted to on, but sometimes one may want to not translate node properties to ways. For example: a map may have barriers and one may want to have such as POIs in an alert file for Garmin POI Loader instead of them interfering with routing. It all depends on map purpose.<br>
<div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-08-06 8:44 GMT-03:00 Greg Troxel <span dir="ltr"><<a href="mailto:gdt@ir.bbn.com" target="_blank">gdt@ir.bbn.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
Paulo Carvalho <<a href="mailto:paulo.r.m.carvalho@gmail.com">paulo.r.m.carvalho@gmail.com</a>> writes:<br>
<br>
> Just checking: did you remember to use the --link-pois-to-ways option in<br>
> your compile command? Also, did you place the barrier node apart from the<br>
> way or did you format a way node as a barrier? (the latter is preferable, I<br>
> think.)<br>
<br>
</div>As I understand it, the semantics of OSM are that a barrier node in a<br>
way does control access. So it's a bug if mkgmap by default does not<br>
produce a map that respects that. Essentially, I'm arguing that<br>
--link-pois-to-ways should default to on, following the principle that<br>
there is a correct garmin representation of OSM semantics and that this<br>
correct representation should be the default.<br>
</blockquote></div><br></div></div></div>