<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="font-family: Helvetica, Arial; font-size: 13px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="color: black; "></div><div><div><div dir="ltr"></div></div></div>Seems to me that if a bot could easily to this then a router could do it without having a bot go through and tag things.</div><div><br></div><div>I'd change the rules posted just a little. If…</div><div><br></div><div>1) Tagged with "tiger:reviewed=no"</div><div>2) Tagged with "highway=residential"</div><div>3) Missing "name=*"</div><div><br></div><div>Then consider same as highway=service for routing purposes.</div><div><br></div><div>I haven't delved into the preprocessing and database creation that any specific router does, but that does not seem undoable. I guess the issue would be convincing non-US based routing project(s) to include that logic in their database creation scripts.</div><div><br><blockquote type="cite"><div style="color: black; ">From: <span style="color: black; ">Nick Hocking</span> <a href="mailto:nick.hocking@gmail.com"><nick.hocking@gmail.com></a><br>Reply: <span style="color: black; ">Nick Hocking</span> <a href="mailto:nick.hocking@gmail.com"><nick.hocking@gmail.com>></a><br>Date: <span style="color: black; ">September 1, 2014 at 9:28:45 PM</span><br>To: <span style="color: black; "><a href="mailto:talk-us@openstreetmap.org">talk-us@openstreetmap.org</a></span> <a href="mailto:talk-us@openstreetmap.org"><talk-us@openstreetmap.org>></a><br>Subject: <span style="color: black; ">Re: [Talk-us] Dirt Roads (formerly: Abandoned railway)<br></span></div><br><div><div><div dir="ltr"><p><span>While people work out how to remove the multitude of tiger ways that don't actually exist, downgrade others from the incorrect "residential" to "unclassified" or "track"<br>depending on imagery or ground survey, and fix the geometry of all unedited TIGER data, I beleive that it's absolutely essential (from safety and useability perspectives) to immediately mark all these uncertain ways as unroutable.</span></p><p><span>Whether to make them driveways or use access=no , I've no idea.</span></p><p><span>I think thrse ways can easily be identified by...</span></p><div><span>1) They are original TIGER data import<br>2) They have not been edited since import<br>3) They are "higway=residential"<br>4) They are unnamed</span></div><div><span><br></span></div><div><span>A bot could do this easily and then it really doesn't matter how long it takes to find the best solution.</span></div></div></div></div></blockquote></div></div></span></div></div></span></div></body></html>