I'm thinking of how it represents the shoreline, and as one logical object rather than touching 'lakes'. And I'm sure I'm not the only one who has considered mapping roads as multilinestrings.
I think Julien's approach is best with regards to repair: revert, teach the new user, and then let them make the edit in the right way. That treats the cause, not the symptom. - Jw --- Sent from a cell phone On Jan 4, 2013 1:22 PM, "Ben Laenen" <benlae...@gmail.com> wrote: > On Friday 04 January 2013 13:09:02 Jan-willem De Bleser wrote: > > Just keep an eye on them, as Julien has done, and teach the new users > about > > relations as needed. The larger multipolygon is a more accurate > > representation, as long as we don't have a proper area data type. > > It's not really more accurate, as we don't have a one to one mapping from > real > life objects to OSM objects. Our roads for example are also often split up > into many pieces. And by breaking up a huge object into manageable parts > you > can more easily repair it when someone does something wrong, which still > matters because we don't have a review process so we can intervene before > the > bad edit is uploaded. > > Ben > > _______________________________________________ > Talk-be mailing list > Talk-be@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-be >
_______________________________________________ Talk-be mailing list Talk-be@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-be
