<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 19, 2014, at 5:59 AM, Lukas Sommer <<a href="mailto:sommerluk@gmail.com">sommerluk@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div>* Here, I still do not see your point. What would you gain in doing so? You have more tags, which means more work. But can you do anything that you can not do with the current, yet existing tagging?<br></div></div></div></blockquote><div><br></div><div>Differentiated tagging is needed for differentiated rendering. "junction" vs "Signal". a single signal icon needs to be rendered in Japan for intersections. </div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div><br></div>* highway=junction is impossible because the OSM database does not allow two tags with the same key on the same element</div></div></blockquote><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><br></div>* junction=traffic_signals would also be problematic because in Japan you can have named traffic signals on straight road, for pedestrian crossing<br></div><span style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">, and there is not any road junction.</span></blockquote></div><br><div>is there a way to tell the renderer to not render it's icon if it is part of another area's way? that would allow the intersection tag to take over for the rendering of the signals for it's single icon. </div><div><br></div><div>if that's the case:</div><div><br></div><div>landmark=intersection ?</div><div>Intersection=signals for Japan, intersection=junction for korea, or other named junctions. </div><div><br></div><div><br></div><div>Javbw</div></body></html>