Re: [Talk-us] Another state route shield renderer and tutorial

[Minh Nguyen]

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.

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.

Minh Nguyễn
Sent from my autocorrect-ennobled device

> On Jul 27, 2016, at 11:43, Paul Johnson  wrote:
> 
> 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?
> 
>> On Wed, Jul 27, 2016 at 2:12 AM, Minh Nguyen  
>> wrote:
>> 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:
>> 
>> 
>> 
>> 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.
>> 
>> 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:
>> 
>> 
>> 
>> 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.
>> 
>> (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.)
>> 
>> For now, I continue to point people to 
>>  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.
>> 
>> -- 
>> m...@nguyen.cincinnati.oh.us
>> 
>> 
>> ___
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
> 
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Another state route shield renderer and tutorial

[Paul Johnson]

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?

On Wed, Jul 27, 2016 at 2:12 AM, Minh Nguyen 
wrote:

> 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:
>
> 
>
> 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.
>
> 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:
>
> 
>
> 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.
>
> (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.)
>
> For now, I continue to point people to <
> http://elrond.aperiodic.net/shields/> 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.
>
> --
> m...@nguyen.cincinnati.oh.us
>
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Another state route shield renderer and tutorial

[Minh Nguyen]

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:




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.


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:




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.


(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.)


For now, I continue to point people to 
 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.


--
m...@nguyen.cincinnati.oh.us


___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us