[Talk-us] Trunk

Bradley White theangrytomato at gmail.com
Sun Oct 15 05:40:16 UTC 2017

If we can determine importance (which is what the 'highway=' tag
fundamentally represents per the wiki) solely by what's on the ground,
why not just tag what's physically there, ditch the 'highway' tag
altogether, and let the renders handle it with their own algorithms?

>On Sun, Oct 15, 2017 at 12:19 AM, Paul Johnson <baloo at ursamundi.org> wrote:
>> The US is pretty well known for overbuilding highways.  Are we trying to
>> document how things are on the ground or how things are actually
>> connected?  If we're going for the former, then yeah, only Bend Parkway and
>> a brief streak through Klamath Falls is a trunk part of US 97.  If we're
>> going for the latter, then go ahead with NE2's idea and smash almost
>> everything into trunk.
>Keep hitting send too soon.  Personally, I find what's on the ground to be
>more useful than the connections.  Game theory and any routing engine can
>figure out the connections.  But knowing what's a stupid rural road with an
>overly generous speed limit and what's almost but not quite a freeway is
>more useful.  If I'm driving a big rig going from southwestern Canada or
>Alaska to somewhere in Nevada, I don't give two shakes what some toolbag
>things is the most prominent road.  I care more about what *actually is a
>big road*.  Calling a two leg segment of US 97 30km outside of East
>Butthump, Oregon a trunk is a great disservice when it's basically on par
>with County Road Number Who Even Cares tracing off to Outer
>Smalltownsville, other than the fact that it goes through.  Calling it a
>trunk when it's not is going to set an unreasonably high expectation for
>what is otherwise an overtravelled, glorified two digit National Forest
>route through the east Cascades frontier.  Primary is definitely ample for
>that road, even if you're going a more obscure minor haul route like Salem
>to Reno.

More information about the Talk-us mailing list