On Sat, Nov 7, 2009 at 9:48 AM, James A. Treacy <[email protected]> wrote:
> > There are cases where the same way exists in different data sets but > with different uses. A good example is that islands in the waterbody > data are often repeated in the wooded data (if the island happens to > be wooded, which happens a lot). Importing one set after another leads > to duplicated ways. This case is time consuming to fix because you > have to reconcile two ways and a relation. This same issue arises with > wetlands. Probably others too but these are the ones I've encountered > most often. > > This is the desired effect. Technically there should be one multipolygon defining the waterway (or lake) and another multipolygon for the wooded area (with separate ways? or maybe the wooded area's outer way should be the lake's inner way?). Keep in mind that removing duplicate nodes/ways in all cases is bad ... in some cases there actually are two features at the exact same point.
_______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
