<br><div class="gmail_quote">On Thu, Jul 29, 2010 at 7:55 PM, Anthony <span dir="ltr"><<a href="mailto:osm@inbox.org">osm@inbox.org</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 Thu, Jul 29, 2010 at 7:49 PM, Alan Millar <<a href="mailto:amillar503@gmail.com">amillar503@gmail.com</a>> wrote:<br>
>> Furthermore, don't store redundant data in the OSM database. There's<br>
>> absolutely no excuse for having 200 ways which all say name=Cain Rd,<br>
>> name_base=Cain, name_type=Rd. It's absolutely terrible design.<br>
><br>
> Patches welcome. Please contribute a fix.<br>
<br>
</div>I've been fixing it. The fact that "Cain Rd" has a base of "Cain" and<br>
a type "Rd" is already in the database over and over and over again.<br>
I've been taking out the redundant copies of that information (which<br>
should have been in a separate lookup table from the beginning<br>
anyway).<br>
<div><div></div><br></div></blockquote><div> I was never a fan of splitting a way, duplicating its tags, for something like a small bridge over a creek<br>It would be great if attributes could be assigned to a number of ways, at least from a normalization standpoint.<br>
>From a UI standpoint, I don't really know how it would be done, but it could be possible.<br>Modifying all the existing OSM data would be a challenge though.<br></div></div>