<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p> </p>
<div> </div>
<p>Are there not going to be some complaints from Florence for example? Why should it be invalid by definition to have an address on a bridge?</p>
<p>Sometimes the bridges are tagged (often wrongly, IMHO) with the name of the bridge and not the name of the road carried by the bridge. Some people use bridge_name=* to make it explicit, but often you see the value of name=* changing for a bridge. I expect it would be up to the local authority whether any addresses which might be present are given the name of the bridge, or the name of the road leading to the bridge.</p>
<p>//colin</p>
<p>On 2015-06-06 16:29, Gerd Petermann wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="ltr">Hi all,<br /><br />Mario Batschke suggested in a private mail to use<br />highway=* & bridge=yes {set mkgmap:numbers=false}<br />in the finalize section for lines so that addresses are not<br />assigned to bridges. <br /><br />I think this is a good idea.<br /><br />He also suggested to exclude tunnels, but I see quite a lot<br />cases where this doesn't improve the address search, e.g.<br />for shops in underground stations.<br /><br />Any comments?<br /><br />Gerd</div>
<!-- html ignored --><br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br /> mkgmap-dev mailing list<br /><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br /><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></div>
</blockquote>
</body></html>