[Talk-us] US State Shield rendering - Modifiers

[Phil! Gold]

* Mike N <niceman at att.net> [2012-11-13 09:38 -0500]:
> WOOT!  We may have hooked a new US mapper because of the shield
> rendering on the test shield development server!

Awesome!

>   That leads to a related question - what is the best way to tag for
> modified state routes.   For example in South Carolina:
> 
>   State route 49 -  US:SC , ref = 49    (That is clear)
>   State Route 49 Bypass -  US:SC:Bypass , ref = 49 , modifier = Bypass
>   State Route 49 Truck  -  US:SC:Truck , ref = 49 , modifier = Truck
>   State Route 49 Business - US:SC:Business , ref = 49 , modifier = Business

This matches the on-list consensus on the topic and is what the shield
rendering currently understands.

>   State Route 49 Truck Bypass -  US:SC:Truck:Bypass , ref = 49 , modifier = Bypass:Truck   (in any order)

This would also match the list consensus.  In the absence of any
compelling reason not to, I've set up the rendering to accept modifiers in
any order, so it would treat US:SC:Truck:Bypass and US:SC:Bypass:Truck
identically.

Personally, I'd probably tag "modifier=Bypass;Truck", with a semicolon, to
match multi-value usage in other tags.

>   What do we need to do to enable shields for this?

Well, someone could put together the necessary sequence files and template
images, if needed, and send me either a merge proposal or a patch from the
code at https://launchpad.net/osm-shields.

Alternately, I can set them up if you can get me some images of what the
bannered shield signs look like and a list of bannered routes in South
Carolina.  (I can manage with just the reference images if you're okay
waiting until I notice the unmatched routes in the OSM data.)

I've gotten a bit behind in code maintenance--the most recent reason being
a new job that's absorbing more of my time than usual--but I hope to get
back to the shield rendering soon.  (Take heart, Minh Nguyễn, I'll get the
Ohio county routes in yet.)