Am 02.01.2013 18:16, schrieb Martin Koppenhoefer:
+1, the smaller (and more sorted by kind of change action) changesets
get, the better the chance that the following mapping will understand
easily what it is about. There is really no point in grouping
different kinds of edits in the same set of
2013/1/3 Georg Feddern o...@bavarianmallet.de
Am 02.01.2013 18:16, schrieb Martin Koppenhoefer:
+1, the smaller (and more sorted by kind of change action) changesets
get, the better the chance that the following mapping will understand
easily what it is about. There is really no point in
2013/1/2 John F. Eldredge j...@jfeldredge.com:
There is also a long tradition of new, small churches being
located in converted retail buildings until they can afford to build space
specifically designed as a church.
that's a nice example for an amenity=place_of_worship,
religion=christian in
2013/1/3 Georg Feddern o...@bavarianmallet.de:
Am 02.01.2013 18:16, schrieb Martin Koppenhoefer:
+1, the smaller (and more sorted by kind of change action) changesets
get, the better the chance that the following mapping will understand
easily what it is about. There is really no point in
On 2 January 2013 15:49, Serge Wroclawski emac...@gmail.com wrote:
There are many people (myself included) who believe that source /on
objects/ is not useful, and most OSMers have moved away from using it,
and toward source on changesets.
I don't see any evidence that most OSMers act this
On 02.01.2013 14:16, Chris Hill wrote:
Secondly, any changeset can have multiple sources so adding the source
tag to a changeset is not flexible enough.
Any object can have multiple sources, so adding the source tag to an
object is not flexible enough either.
There are workarounds for either
On Thu, Jan 3, 2013 at 7:23 AM, Jason Cunningham
jamicu...@googlemail.com wrote:
From my experience most mapping sessions involve changes and additions made
to a wide variety of objects with a several sources used. Effectively
requiring a new changeset for each object edit makes complicated
