<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/30/13 4:54 AM, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote
cite="mid:CABPTjTC9uB8pFF0JNSeoVDnkWxC6URVg5pHUdFM8RRZ65g0+UQ@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">2013/11/30 Peter Davies <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:peter.davies@crc-corp.com" target="_blank">peter.davies@crc-corp.com</a>></span><br>
<blockquote class="gmail_quote">
<div>So we have way ref I 394 instead of I 394;US 12. For
my applications I'd prefer it said I 394;US 12, because
we need to track the overlaps (which we and our 10 state
DOT customers call double banding). But if you also
want to suppress shields from maps in such areas, could
we enter the way ref as I 394;US 12|unsigned ?</div>
<span class="HOEnZb">
</span></blockquote>
</div>
<br>
<br>
</div>
<div class="gmail_extra">Usually you would have (at least) 2
relations, one for each ref. The way ref (if set at all) will
often have multiple values, semicolon separated. Not sure if
you have a different agreement in the US, but it doesn't
matter if the ref is signed or not, as long as you can find it
in some kind of publicly available documentation (with
compatible licensing).<br>
</div>
</div>
</blockquote>
in the US, we've been trying to use unsigned_ref= for situations
where the road<br>
has a designation but no signage. County routes in Westchester and
Onondaga Counties<br>
in NY are examples of this. additionally, many of the highways in
the NYS parkway<br>
system have public designations like "Taconic State Parkway" but
they also have<br>
unsigned reference numbers in the state inventory, so ref=TSP
combined with<br>
unsigned_ref=<inventory number> is the way we've been going.<br>
<br>
richard<br>
<br>
</body>
</html>