<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Talk-us] Bike route relation
issues</title></head><body>
<blockquote type="cite" cite>On Sun, Jan 11, 2015 at 1:54 PM, stevea <<a
href="mailto:steveaOSM@softworkers.com">steveaOSM@softworkers.com</a>>
wrote:<br>
<blockquote>I do not agree: again, I find no evidence (from the
Oregon DOT map) that bicycles are explicitly designated "legal"
on I-5. It may be the case that explicit statute specifies
bicycles are allowed on I-5 in Oregon, but this map does not
explicitly do so. Again, please note that no specific "bike
routes" are designated on that map, either. It simply
displays some highways as Interstates and some highways as containing
wide shoulders or narrow shoulders. While not complaining about
Oregon's DOT helping bicyclists better understand where they might or
might not ride a bicycle in that state, I characterize these map data
as "early" or "underdeveloped" w.r.t. helpful
"bicycle routing" by a DOT.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
Oregon and Washington allow all modes on all routes unless otherwise
posted. They have to explicitly sign exclusions, and they do.
Here's the list for Oregon<br>
</blockquote>
<blockquote type="cite" cite><a
href="http://www.oregon.gov/ODOT/HWY/BIKEPED/docs/freeway_ban.pdf"
>http://www.oregon.gov/ODOT/HWY/BIKEPED/docs/freeway_ban.pdf</a><br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>And Washington:</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><a
href="http://www.wsdot.wa.gov/bike/closed.htm"
>http://www.wsdot.wa.gov/bike/closed.htm</a></blockquote>
<div><br></div>
<div>My previous post was California centric, going too far assuming
for other states. (And fifty-at-a-time only in certain
circumstances).</div>
<div><br></div>
<div>A starting place (properly placed in the locus of each state,
with perspective as a router might parse logic and build a routing
set...) is the following:</div>
<div><br></div>
<div>For 100% of ways with tag highway, set bicycle legality_status =
"legal." (This keeps "everything still in the
running.") Now, apply a per-state rule (could be a table
lookup, could be a smarter data record):</div>
<div><br></div>
<div>With both Washington and Oregon:</div>
<div> exclude from our data set ways where helpful
OSMers have tagged "bicycle=no"</div>
<div><br></div>
<div>With California:</div>
<div> exclude from our data set ways tagged
highway=motorway,</div>
<div> add to the set cycleways and highways tagged
bicycle=yes.</div>
<div><br></div>
<div>We are right in the middle of "fifty ways of calculating a
set." Those target objects might be elements of a bicycle
route. As we get the tags right (critical, on the data and
"at the bottom") we must also treat the rules of what we
seek from those data as critical, too (from the top, down). It's
reaching across and shaking hands with a protocol, or a stack of
protocols. It's data, syntax and semantics. When the
sentence is grammatical (tags are correct for a parser), it clicks
into place with the correct answer (renders as we wish).</div>
<div><br></div>
<div>For the most part, we get it right. But we do need to
understand the whole stack of what we do every once in a while, and
pointing out "data in California, treat like this, data in
Oregon, Washington..., treat like that..." is helpful to
remember. Can we get to a place where everybody can do things
(tag) "just right for them" and have it always work
(render), everywhere every time? Mmmmm, not without
documentation and perhaps conversations like this.</div>
<div><br></div>
<div>This is why documenting what we do and how we do it (and
referring to the documentation, and trying to apply it strictly,
unless it breaks, then perhaps talk about it and even improve it...)
is so important.</div>
<div><br></div>
<div>Listen, build, improve, repeat. Thank you (Paul, for your
specific answer, as well as others for participating).</div>
<div><br></div>
<div>SteveA</div>
<div>California</div>
</body>
</html>