<html>
<head>
</head>
<body class='hmmessage'><div dir='ltr'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><br> <br><div>> Date: Thu, 20 Jun 2013 15:15:02 -0400<br>> From: phil_g@pobox.com<br>> To: talk-us@openstreetmap.org<br>> Subject: Re: [Talk-us] ref tags<br>> <br>> * Clay Smalley <claysmalley@gmail.com> [2013-06-20 09:26 -0700]:<br>> > Also, even if it were the case that they were the same network, it makes<br>> > sense to keep them separate because that is how the shield renderer<br>> > determines which shield to put on the road.<br>> <br>> My shield renderer is pretty flexible. I can assign shields on a<br>> ref-by-ref basis, if need be (though it means that networks' shields<br>> require more maintenance in the long run).[0] As long as the solution<br>> has local consensus I'll find a way to work with it.[1]<br>> <br>> [0] See, for example, Georgia route 515, which gets a blue sign because<br>> it's part of an Appalachian Highway Development System corridor:<br>> <br>> http://elrond.aperiodic.net/shields/?zoom=12&lat=34.66561&lon=-84.48668&layers=B<br>> <br>> [1] Or throw up my hands and say, "I don't know how to handle that," but<br>> that shouldn't impede consensus. There are still a bunch of things I<br>> don't have a good way to handle yet, like the way Tennessee does<br>> primary and secondary state highways, or the way Maryland signs<br>> Business US Highways.<br>> <br>> _______________________________________________<br>> Talk-us mailing list<br>> Talk-us@openstreetmap.org<br>> <a href="http://lists.openstreetmap.org/listinfo/talk-us">http://lists.openstreetmap.org/listinfo/talk-us</a><br></div><div> </div><div>Well, for the Tennessee State Highways, as long as we can find out which are "secondary", we could tag them in the relations as "US:TN:SR" or "US:TN:Secondary" and then use a Super relation to tie together routes that have segments with both primary and secondary segments types. The kicker is how to find out which segments are which. I don't know if TDOT has any GIS data out there to download that would be compatible with OSM that would allow us to figure out which is which.</div><div> </div><div>-James</div></div>
</div></body>
</html>