I would go so far as to say, don't delete *anything* until legally you absolutely have to. There are a number of non-CT-accepting contributors in my area, for instance, and I don't think the map should be interfered with unless it's absolutely necessary. Remember that by doing so, the quality of the OSM map - already a useful resource for the general public - will be affected.
Nick -----Nathan Edgars II <nerou...@gmail.com> wrote: ----- To: talk@openstreetmap.org From: Nathan Edgars II <nerou...@gmail.com> Date: 31/08/2011 08:17AM Subject: Re: [OSM-talk] How to start to remove non-CT compliant data.. On 8/31/2011 3:06 AM, Simon Poole wrote: > - use the license status tools in Potlatch and JOSM when you are editing > anyway to only leave compliant data after an edit (for example by not > moving non-compliant nodes in a way, but by replacing them). This is > naturally assuming that you have tracks and other information to allow > you to do this. Hoe about this: if you decide to delete data that the OSMF has decided not to accept, look at the history and only delete what's necessary. There's no need to make it harder on ordinary mappers who don't care about the license change. This should be treated similarly to an import: if you're not willing to merge the existing data, don't do it. If your change results in the deletion of tags like highway=traffic_signals and lanes=* that have been added by CT-agreeing mappers, you're doing it wrong. (Oh, and don't forget to change the number of lanes properly if you're changing a dual carriageway to a single carriageway or vice versa. Enough mappers fail to do this even when making ordinary edits.) In short, if you're not willing to fix any damage you create, don't delete non-CT data. _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
