[OSM-talk] Patch to render names from routes and custom highway shields on a per country basis

John Smith deltafoxtrot256 at gmail.com
Mon Sep 21 02:38:34 BST 2009


2009/9/21 Richard Weait <richard at weait.com>:
> In earlier discussions with Paul (cc:'d) we talked about using the
> network key to distinguish road networks that use shields[1].  We had
> agreed on using a ":" separator like "US:I" but I'm arguing against
> that now.  First we are not separating equal items, we're adding
> specificity to one selector.  Second, we're planning to use the
> network values in filenames, we should choose characters that won't
> lead to problems in on OS or another when used as a file name.  Third
> OSM key:values have been lower case other than Proper (Street) Names.
> So I suggest we pattern on network=us_i for Interstates, us_us for US
> Routes, us_ny_ny for New York State Routes, us_ny_ny_co for New York
> county roads, etc.  These tags should sort nicely alphabetically for
> bug-squashing and allow collision avoidance with imperfect knowledge
> of other international network naming systems.

What you are doing specifically will end up causing inconsistent data
because you don't see us_ny_ny_co on signs and people won't tag it.

In the case of US interstate it should just be network=I, state
highways network=S

That is enough information combined with a database or shape file with
all the meta information about what shield exists in which location,
and defaulting to UK style signs if a localised style hasn't been
defined otherwise.




More information about the talk mailing list