<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20498">
<style><!--
html {
font-family:"Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif";
}
--></style><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;">
<div>No, it is a miscasting the problem to suggest we don’t tag trunk roads (which clearly was not part of the problem). The problem is that there is a tagging system in place which is ambiguous from an International point of view. So there should be a clear tagging that is distinct for the meaning of “trunk (UK sense)” vs “trunk (International sense)”</div><div><br></div><div>I am simply suggesting that it would be sensible to resolve the underlying data so that anyone choosing to use the data is able to understand it readily without having to assess what country the way has been created in. </div><div><br></div><div>So yes, it is an issue for the renderer or the router but I’d ask the question that if it is a problem for mappers to consider the convenience of the renderer or the router, then who are you mapping for?</div><div><br></div><div>The problem is very simple, for arbitrary reasons in the past the “trunk” has been used to mean two very different types of highway - in Germany and as far as I can tell in all other countries a trunk road has default rules that exclude pedestrians and cyclists by law, in the UK the very same tag is used to mean simply a preferred chosen national navigation route with no other implications.</div><div><br></div><div>From a database background, is it wise to have such ambiguity in the core data of a project when there is some way of resolving it?</div><div><br></div><div>Perhaps the rest of the world is wrong and should not be using “trunk” but that is the state of the database we have. I’m not aware of any other attribute of highway that causes this issue.</div><div><br></div><div>Regards</div><div><br></div><div>Ian</div><div><br></div><div><br></div><div><br></div><div data-signatureblock="true"><br></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><div><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style='line-height: 15pt; letter-spacing: 0.02em; font-family: "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;'><b>From:</b> <a href="mailto:forums@david-woolley.me.uk" target="_parent">David Woolley</a><br><b>Sent:</b> Friday, 25 July 2014 17:37<br><b>To:</b> <a href="mailto:talk-gb@openstreetmap.org" target="_parent">talk-gb@openstreetmap.org</a></font></div></div><div><br></div><div dir=""><div id="readingPaneBodyContent">On 25/07/14 17:15, Philip Barnes wrote:<br>> Are you proposing we tag for the renderer by not tagging trunk roads as<br>> trunk?<br><br>No. He wants people to tag for the router, not the renderer.<br><br>I think that is a bad idea, although not as bad when most trunk roads <br>weren't already mapped, as it is doing something for the convenience of <br>a small number or routing software developers rather than a large number <br>of mappers.<br><br>It could be argued that the current approach is actually tagging for the <br>renderer, except that the details in question don't get rendered in the <br>standard rendering.<br><br>In practice, though, it is more likely that roads would have been <br>mis-tagged if the most common case required extra permissions to be be <br>explicitly added.<br><br>_______________________________________________<br>Talk-GB mailing list<br>Talk-GB@openstreetmap.org<br>https://lists.openstreetmap.org/listinfo/talk-gb<br></div></div>
</div>
</body>
</html>