On Fri, Nov 20, 2009 at 4:52 AM, Sam Vekemans
wrote:
> Hi Steve,
>
> The reason i didnt include attribution as part of the changeset is
> because I didnt know how. :)
>
> i chose to put the 'attribution' tag on each point, line, area map
> feature, so that way, anyone editing will immediatly
On Fri, Nov 20, 2009 at 7:26 AM, Andy Allan wrote:
> I think (hope?) we all agree that there shouldn't be
> a created_by:bulkupload.py on the geo-features any more. So I think we
> can change our recommendations for where the attribution should go
> too.
>
> What do you all think?
I agree.
_
On Fri, Nov 20, 2009 at 1:26 PM, Andy Allan wrote:
> My reasoning is
> that we don't store attribution for normal contributors on the
> geo-features, so we should be consistent with imports. When a
> contributor creates a new way we don't add tags to the way to say who
> contributed it, so I don't
On Fri, Nov 20, 2009 at 13:26, Andy Allan wrote:
> My take on it is that is should not be on the geo-features, but it
> should be on the changeset (and the wiki if you like). My reasoning is
> that we don't store attribution for normal contributors on the
> geo-features, so we should be consistent
2009/11/20 Andy Allan :
> I want to take what Sam has said out of context here, so this isn't a
> question of Geobase/Canvec, let's consider the wider issue of
> attribution on imported data. Should the attribution be on the
> geo-features (nodes,ways,relations), or on the changeset, on the wiki,
>
Andy Allan writes:
> I want to take what Sam has said out of context here, so this isn't a
> question of Geobase/Canvec, let's consider the wider issue of
> attribution on imported data. Should the attribution be on the
> geo-features (nodes,ways,relations), or on the changeset, on the wiki,
> a
On Fri, Nov 20, 2009 at 14:56, Greg Troxel wrote:
> source=canvec_import_20091120
this really depends from the bulk dataset which we are talking about.
if it is something easy to tell apart from other versions, this source
tag is not needed.
if it is something that contains single feature ident
2009/11/20 Simone Cortesi :
> I'm all for it. Geo has nothing to do with attribution. We give credit
> to the geodata-maker by informing the user that the given feature
> comes from a certain contributed dataset...hence exposing this
> information in the changeset comment is the way to go.
One iss
On Fri, Nov 20, 2009 at 8:56 AM, Greg Troxel wrote:
> I agree that the created_by tag isn't useful, but a tag that says
>
> source=canvec_import_20091120
>
> or some such on the point/way/relation can be used to see if the way has
> been edited since import,
How so? The way you check if a way ha
2009/11/20 Anthony :
> Ideally, you could put the tag in the changeset or on a particular
> feature, and it would get saved, once, as part of the history. Then
> when you selected a feature and clicked history you'd see < source=canvec_20091120; version 2, source=local knowledge; version 3
> [no s
On Fri, Nov 20, 2009 at 1:49 PM, andrzej zaborowski wrote:
> 2009/11/20 Andy Allan :
>> I want to take what Sam has said out of context here, so this isn't a
>> question of Geobase/Canvec, let's consider the wider issue of
>> attribution on imported data. Should the attribution be on the
>> geo-fe
On Fri, Nov 20, 2009 at 1:16 PM, Pieren wrote:
> On Fri, Nov 20, 2009 at 1:26 PM, Andy Allan wrote:
>> My reasoning is
>> that we don't store attribution for normal contributors on the
>> geo-features, so we should be consistent with imports. When a
>> contributor creates a new way we don't add t
12 matches
Mail list logo
