Talk:Remapping/License Change View on OSM Inspector
Doesn't work?
Call me thick as mince, but I can't call up this layer in my browser --Scruss 02:42, 12 December 2011 (UTC)
- What happens if you try? --Frederik Ramm 22:16, 18 December 2011 (UTC)
Override options
There definitely needs to be some kind of per-object override as mentioned on the page. Not just for this view but obviously the license change process in general. Example: Way 33576021 was originally imported from a PD source (TIGER) by an agreeing user. This particular way was split from the imported one by a non-agreeing user. However, since that user last touched it, the way has gone through 20 revisions by 7 different agreeing users and every single one of its member nodes has been modified in the process. There is absolutely no actual value left in the data from the non-agreeing user. This same case goes for appreciable chunks of I-70 in Kansas. Without an override option of some kind I would have absolutely no qualms about doing a copy/paste on these objects to nuke their history and "claim" them as my own. But I would rather not do that out of respect for the other editors. ToeBee 04:53, 14 December 2011 (UTC)
- Should now be possible with odbl=clean but note caveats described on page. --Frederik Ramm 22:16, 18 December 2011 (UTC)
It would also be nice to be able to specify using the override option which subset is odbl clean, tag by tag, and coords separately. Ij 23:34, 14 December 2011 (UTC)
- That would be too much effort for all parties involved. Instead, edit the object so that the current state is odbl clean, and then place odbl=clean. --Frederik Ramm 22:16, 18 December 2011 (UTC)
Relations?
Can I assume "odbl=clean" applies to all kinds of "objects", including relations? Furthermore marking a relation as clean will not be cascaded down to the individual members of a relation? --mmd 30 December 2011, 12:19 (UTC)
- Yes, I'm quite confident that odbl=clean is meant to be applied to any relation as well, but I cannot imagine that this information would be inherited by its members as relation and members have independent license status "by design". G0ldfish 14:49, 8 February 2012 (UTC)