<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>As I mentioned in the diary post, it doesn't handle any of those cases. To be sure, there is a regular expression behind the scenes to ensure that Texas Loop highways for instance aren't given the us-state shield value. On the other hand, there isn't any logic to sort out true edge cases like Arkansas Highway 43.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I still believe combining that regular expression with the spatial query is a step up from the common practice of using only a regular expression, and in optimistic that, if nothing else, this demonstration will spur others to keep working toward true route relation support.<br><br>Minh Nguyễn<div>Sent from my autocorrect-ennobled device</div></div><div><br>On Jul 27, 2016, at 11:43, Paul Johnson <<a href="mailto:baloo@ursamundi.org">baloo@ursamundi.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">OK, but how does it handle literal edge cases? Such as WA 433 in Oregon, OK 20 in Arkansas, or AR 43 in Oklahoma? Or not-so-edge cases such as Texas' infamous multitude of state highway networks, or the two state highway systems in Oklahoma, Kansas and Missouri?</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 27, 2016 at 2:12 AM, Minh Nguyen <span dir="ltr"><<a href="mailto:minh@nguyen.cincinnati.oh.us" target="_blank">minh@nguyen.cincinnati.oh.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A couple days ago, I posted a diary entry about rendering state-specific highway shields using Mapbox tools. It's a topic of special interest to the U.S. community, so I figured I'd give the talk-us list a heads-up since not everyone reads the diaries regularly:<br>
<br>
<<a href="http://www.openstreetmap.org/user/Minh%20Nguyen/diary/39123" rel="noreferrer" target="_blank">http://www.openstreetmap.org/user/Minh%20Nguyen/diary/39123</a>><br>
<br>
The diary entry begins with a summary of the arguments for pictographic shield rendering and the challenges facing renderers that attempt to differentiate between each state's design. I also argued against using regular expressions to select state route shields.<br>
<br>
I developed a demonstration vector renderer, called Interstate, that differentiates between the Ohio, Kentucky, and Indiana state route shields, despite ambiguous `ref=SR 123` tagging in both Ohio and Indiana:<br>
<br>
<<a href="http://nguyen.cincinnati.oh.us/minh/osm/interstate/" rel="noreferrer" target="_blank">http://nguyen.cincinnati.oh.us/minh/osm/interstate/</a>><br>
<br>
Though Interstate is only a proof of concept design-wise, it runs on production servers and mainstream software. The second half of the diary entry walks you through the steps to create your own, prettier version of Interstate using free Mapbox tools.<br>
<br>
(Full disclosure: I work at Mapbox. But my motivation for posting the tutorial is to nudge the community away from relying on regular expressions to select shields and towards eventually using route relations for that purpose.)<br>
<br>
For now, I continue to point people to <<a href="http://elrond.aperiodic.net/shields/" rel="noreferrer" target="_blank">http://elrond.aperiodic.net/shields/</a>> when I want to show them what route relations are good for, but Interstate is another option when the issue of way `ref` formats comes up.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
<a href="mailto:minh@nguyen.cincinnati.oh.us" target="_blank">minh@nguyen.cincinnati.oh.us</a><br>
<br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org" target="_blank">Talk-us@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-us" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-us</a><br>
</font></span></blockquote></div><br></div>
</div></blockquote></body></html>