[Talk-us] Network edge cases

[Paul Johnson]

Some difficult edge cases I foresee will be in the US:TX:* network space,
since they have a *ton* of secondary networks.  The Ranch and Farm to
Market networks are also a fairly unreal mess, since Texas signs the two
interchangeably even though in reality, all the ranch to market routes are
in the farm to market network (except for the one lone member of the ranch
road system that passes in front of LBJ's ranch).  Not sure how much of a
practical difference this will make for Americana, but definitely a
tripping point.

And US:MO:Branson (or is it US:MO:Taney:Branson?) will have colors instead
of ref if those city-level routes are mapped...these color coded routes
have examples in the MUTCD, so this might not be unique to Branson.

On Wed, Jan 26, 2022 at 6:47 PM Brian M. Sperlongano <zelonewolf at gmail.com>
wrote:

> The bare minimum that's required for highway shields is for a route
> relation which has a network+ref combination that can be unambiguously
> associated with a particular highway shield.  What's preferable is if each
> network value corresponds to a single shield design, for example, US:PA
> corresponds to a white keystone with a black outline.  Since the shield
> generation code is in javascript, it's possible to code any special case of
> course, but in general we've found that the 1:1 relationship between shield
> blank and network value seems to hold with only a handful of exceptions.
> So far these are the PA turnpike segments that have no ref, and two Georgia
> state routes that each have a different color shield because they're
> Appalachian corridor routes.
>
> On Wed, Jan 26, 2022 at 5:59 PM Eric Patrick <txemt1 at gmail.com> wrote:
>
>> For those states who use a different shield for toll roads vs free roads,
>> is that something that can be looked at as well? Texas colors the shields
>> in red, white, blue for those roads that are toll, while all others are
>> black and white. There are a few exceptions like the Sam Houston Tollway
>> around Houston. You can also include the Florida Turnpike in this as well.
>>
>> On Wed, Jan 26, 2022 at 5:20 PM Elliott Plack <elliott.plack at gmail.com>
>> wrote:
>>
>>> Paul, great point. Taking a look at how Apple Maps handles their state
>>> shields
>>> <https://www.justinobeirne.com/google-maps-apple-maps-highway-shield-icons>,
>>> they appear to use Helvetica in place of Highway Gothic, or one of the open
>>> variants. At that scale it is hard to tell other than at a side by side
>>> comparison level. I think Helvetica would probably be fine for this purpose
>>> if it matches the 'style' of US-type shields at a 12pt scale (ish).
>>>
>>> Google Maps vs. Apple Maps: U.S. State Highway Shield Icons
>>> (justinobeirne.com)
>>> <https://www.justinobeirne.com/google-maps-apple-maps-highway-shield-icons>
>>>
>>> Thanks for the comment!
>>>
>>> - Elliott
>>>
>>>
>>> On Wed, Jan 26, 2022 at 4:55 PM Paul Johnson <baloo at ursamundi.org>
>>> wrote:
>>>
>>>> On Wed, Jan 26, 2022 at 3:06 PM Elliott Plack <elliott.plack at gmail.com>
>>>> wrote:
>>>>
>>>>> Great work Brian and Collaborators! I too would love to see those
>>>>> shields use the FHWA standard  Highway Gothic - Wikipedia
>>>>> <https://en.wikipedia.org/wiki/Highway_Gothic> fonts where
>>>>> applicable. They should be public domain as works of the US Federal
>>>>> Government.
>>>>>
>>>>
>>>> I'm not sure it'll work in a lot of cases...if only because some
>>>> shields interior size is pretty small, and Highway Gothic is a pretty
>>>> chunky sign font really not designed to scale down to small sizes on
>>>> screens.  Clearview does slightly better at small on-screen sizes but is
>>>> also a chunky sign font that doesn't work great as a screen font.  I think
>>>> the current version has a pretty acceptable compromise in terms of
>>>> appearance while still being a font that's actually legible when small.
>>>>
>>>> There's very few sign fonts that also work as screen fonts; they're
>>>> rather opposite goals.  Helvetica's the only one that comes to mind.
>>>> _______________________________________________
>>>> Talk-us mailing list
>>>> Talk-us at openstreetmap.org
>>>> https://lists.openstreetmap.org/listinfo/talk-us
>>>>
>>> _______________________________________________
>>> Talk-us mailing list
>>> Talk-us at openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-us
>>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20220126/675d23e3/attachment-0001.htm>