>> == "Inconsistent State Prefixes" ==<br>
<br>I wish there was a better (simpler) way to consistently tag the state and county shields but I do not have one. I think it needs to be done though. Compared to the rest of the world, I think the US has an extra layer of 50 varying standards to deal with.<br>
<br>I would add to Val's e-mail that county roads might need the same US:UT:CR-14 as I believe they are handled differently in some state as well. Also to differentiate them from tags from other parts of the world.<br>
<br>-- <br>Dale Puch<br><br><br><div class="gmail_quote">On Fri, Oct 15, 2010 at 12:47 PM, Val Kartchner <span dir="ltr"><<a href="mailto:val42k@gmail.com">val42k@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Fri, 2010-10-15 at 12:08 -0400, Phil! Gold wrote:<br>
> == "Hyphens" ==<br>
><br>
> There's a lot of inconsistency in tagging in road's ref= tags. The main<br>
> wiki pages (Interstate Highways, United States road tagging) specifically<br>
> call for using spaces between the network designation and the network<br>
> number. A lot of people still use dashes for Interstates, because thet's<br>
> how they're commonly written (and because "I-5" is more obvious than<br>
> "I 5", which might be read as "15").<br>
<br>
</div>At least here in the US, the dash is convention so it should be used in<br>
the map.<br>
<div class="im"><br>
> == "Inconsistent State Prefixes" ==<br>
><br>
> This is another very inconsistent area. The main US wiki page (United<br>
> States road tagging) says to use the state's two-letter postal code<br>
> (optionally with a US: prefix). In practice, usage varies wildly,<br>
> generally based on how individual states prefer to represent their routes:<br>
> in states like Maryland that use their postal code, usage is pretty<br>
> uniform; in states like Ohio that use a "SR" prefix, usage is mixed<br>
> between local customs and the postal code standard.<br>
><br>
> A further complication is the presence of county roads. The wiki doesn't<br>
> mention any standard for those. From what I've seen, they mostly end up<br>
> as "CR" or whatever the local nomenclature is.<br>
><br>
> Should we use the postal code everywhere for nationwide consistency or<br>
> should we use the prefixes that locals use? If we use postal codes, what<br>
> should we do about county or town roads?<br>
<br>
</div>We should find some consistent way to do it such that it is easy for a<br>
renderer to parse. Then the renderers will need to be changed to use<br>
them. Once this is done, people will be more likely to enter them<br>
properly since they will show up in a special way.<br>
<br>
So, for instance, in Utah the state routes are designated (without<br>
abbreviation) State Route 67 (for instance). This is abbreviated as<br>
SR-67. However, a sign with this designation is not used very much.<br>
The much more commonly used signage is "67" is the state highway shield<br>
(a white beehive on a black background). This is how the renderers<br>
should put it on the state highways. (Wikipedia does it this way on<br>
each page.)<br>
<br>
I haven't seen any county road signs (on physical roads), but I've heard<br>
the renderers will draw the number in a circle.<br>
<br>
The standard should be something easy to parse. Perhaps, for the above<br>
example, it would be "US:UT:SR-67". This would allow an easy way to<br>
parse which shield to use. For instance, a made-up Canadian route would<br>
be "CA:BC:12". The colons would designate a field, and a space or dash<br>
would indicate a subfield. The renderer could just use all but the last<br>
field to figure out which shield to use ("US:UT" or "CA:BC"), then use<br>
the last subfield of the last field to draw the shield. This would work<br>
for an instance I've seen in New Hampshire which would be "US:NH:3A".<br>
<br>
I'm sure that there are some exceptions, to using the last subfield to<br>
draw the shield. Let's hear about them.<br>
<div class="im"><br>
> == "Semi-Colons" ==<br>
<br>
> He shows a road that has a ref= of "I 88;56". I think it should be<br>
> completely uncontroversial to say that each part of a<br>
> semicolon-delimited ref should have the appropriate network<br>
> information in it.<br>
<br>
</div>I agree with your solution. Again, the renderer needs to draw the<br>
highway shields. If there is no special treatment by the renderer for<br>
doing things in the proper way, then it is less likely that things will<br>
be tagged correctly. I'm reminded of the truism, "What gets rewarded<br>
gets repeated."<br>
<font color="#888888"><br>
<br>
- Val -<br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
</div></div></blockquote></div><br><br clear="all"><br>