[OSM-talk] How to start to remove non-CT compliant data..
isergean at hih.com.au
Wed Sep 7 05:59:11 BST 2011
Andrew Harvey <andrew.harvey4 at gmail.com> wrote on 06/09/2011 07:37:05 PM:
> On Tue, Sep 6, 2011 at 2:45 PM, Jo <winfixit at gmail.com> wrote:
> > It would indeed be great if we could use an arbitrary version of an
> > to continue to build upon. Now, I have to start all over on each
> > was touched by somebody who didn't agree (yet) to the CTs, which is
> > annoying, as it disrupts the entire history.
> Yes, inas has done this for some objects already, I don't think it is
> optimal as you break the history of the object (when really such
> history should be there to give credit to the mapers who helped build
> up the object in OSM).
Currently I'm using the attribution tag for credit when I work with a
CT-compliant earlier version.
There is more to the history of an object than just attribution though,
and modifying the API to allow it to be preserved would be a step forward.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk