<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Sep 13, 2021, 10:43 by minh@nguyen.cincinnati.oh.us:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Vào lúc 16:47 2021-09-12, Eric Patrick đã viết:<br></div><blockquote>I have a thought regarding trunks in regards to functional classification, and this is going to come from a different viewpoint. Why not make Primary Arterials trunk roads, from a coding standpoint. They're coded lower than a motorway, but higher than everything else. Any GPS system will use the highest coded route, with the fewest penalties, they can get to between points A and B. I understand that in doing this, a lot of downtown areas will look like a sea of red, due to the density of the Primary Arterials within those areas (cue Brian's groan about this).<br></blockquote><div><br></div><div>As far as I can tell, no mainstream OSM-based router directly penalizes a road based on its highway=* value per se. If it lacks a maxspeed=* tag and real-time or historical traffic data is unavailable or unsupported, then the router would assume a speed limit based on the highway=* value. From what I've seen, these assumptions are usually wrong for... just about everywhere.<br></div></blockquote><div dir="auto">bicycle-focused and foot-focused ones often try to avoid large roads,<br></div><div dir="auto">highway=track is often avoided (though maybe it would not be described as a road).<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><blockquote>Functional classification isn't going for looks, though, it's going for function. The states have spent a lot of time and effort since FC was first introduced about a decade ago.<br></blockquote><div><br></div><div>OK, but is it a good fit? The highway=* key (other than highway=motorway) is defined as indicating the road's importance in the road network. [1] That sounds vaguely functional. But the ultimate goal of this key is indeed "going for looks", and optimal routing behavior, because OSM data is primarily used by renderers and routers.<br></div></blockquote><div dir="auto">Though functional classified roads (not by number of lanes of something) are very useful.<br></div><div dir="auto"><br></div><div dir="auto">When I was designing new road style for OSM Carto it was quite irritating that in many regions<br></div><div dir="auto">people used highway=trunk for "double carriageway road" or "designated as expressway".<br></div><div dir="auto"><br></div><div dir="auto">It made basically impossible to have decent rendering on lower zoom levels that would show<br></div><div dir="auto">basic structure of a road network.<br></div> </body>
</html>