<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
Am 31.08.2011 02:19, schrieb Ian Sergeant:
<blockquote
cite="mid:OF9448106F.F2DF221F-ONCA2578FC.0081049F-CA2578FD.0001D343@hih.com.au"
type="cite">
<br>
<font face="sans-serif" size="2">I think the strategy to remove
all non-CT
compliant data in one big bang is flawed. <br>
</font></blockquote>
<br>
I don't know of anybody who has proposed such a strategy (well at
least nobody serious about the matter). It is clear, at the very
end, there will be some automated deletes, but with some exceptions
these should be very limited in scope. But will probably include
cleaning objects that are in principle CTs compliant, but have had
edits that are not, there is work going on on the German forum to
define a reasonable rule set for that.<br>
<br>
Right -now- the best thing to do is:<br>
<br>
- contact mappers that haven't agreed or disagreed to the CTs (see
<a class="moz-txt-link-freetext" href="http://odbl.poole.ch">http://odbl.poole.ch</a>). Worldwide we still have a good 60% of pre-CT
mappers that haven't reacted to now, with some effort that can be
halved. <br>
<br>
- 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.<br>
<br>
- ignore trolling by JohnSmith<br>
<br>
Simon<br>
<br>
<br>
<br>
<br>
</body>
</html>