On Thu, Jul 29, 2010 at 7:55 PM, Anthony <[email protected]> wrote:
> On Thu, Jul 29, 2010 at 7:49 PM, Alan Millar <[email protected]> wrote: > >> Furthermore, don't store redundant data in the OSM database. There's > >> absolutely no excuse for having 200 ways which all say name=Cain Rd, > >> name_base=Cain, name_type=Rd. It's absolutely terrible design. > > > > Patches welcome. Please contribute a fix. > > I've been fixing it. The fact that "Cain Rd" has a base of "Cain" and > a type "Rd" is already in the database over and over and over again. > I've been taking out the redundant copies of that information (which > should have been in a separate lookup table from the beginning > anyway). > > I was never a fan of splitting a way, duplicating its tags, for something like a small bridge over a creek It would be great if attributes could be assigned to a number of ways, at least from a normalization standpoint. >From a UI standpoint, I don't really know how it would be done, but it could be possible. Modifying all the existing OSM data would be a challenge though.
_______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
