"...why do you duplicate the tag waterway=river on every way...."
Because the relation can contain more than simply the waterway. For instance, one could add the riverbank, islets, and slips if one were so inclined. By letting each component way retain an identity of what it is, the relation grouping takes on the purpose of telling what it's called, "it" being the variety of component types which make up the thing called "Tappahanna Ditch". I just haven't added any of the extra things (chief being the riverbank) to the relation (and likely never will). --ceyockey -----Original Message----- >From: Georg Feddern <o...@bavarianmallet.de> >Sent: Jan 6, 2013 11:30 AM >To: "Tag discussion, strategy and related tools" <tagging@openstreetmap.org> >Subject: Re: [Tagging] Names on relations and not component ways > >Hello, > >Am 04.01.2013 14:43, schrieb dies38...@mypacks.net: >> I recently created a waterway where I put the name of the waterway on the >> relation but not on the component ways which are grouped by the relation. > >> To me, not duplicating data would seem to be the better overall practice, >> and duplication of > >well, it's one acceptable perception to enter the data into a >'relational' database - opposite to the 'keep it simple on every way' >perception. >But why do you duplicate the tag waterway=river on every way then ...? > >Regards >Georg > >_______________________________________________ >Tagging mailing list >Tagging@openstreetmap.org >http://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
