Okay. I’ll adapt the few remaining building=* value wiki pages that do
not allow nodes …
2015-02-17 0:32 GMT, Dave Swarthout daveswarth...@gmail.com:
On Tue, Feb 17, 2015 at 1:30 AM, Dan S danstowell+...@gmail.com wrote:
All building=* on nodes is fine. As others have pointed out, it is
In a discussion with Ivan Gayton of MSF on this subject and his view on the
humanitarian angle isthey prefer the area to be shown rather than the
node. They use the area in estimating the number of occupants (for which
they have worked out an average table for the areas they require). So
I would like to return to the original question:
1.) I think it is confusing to have building=cowshed allowed on nodes,
but building=cabin not allowed. We should unify this. Either _all_
building=* keys can be used on nodes, or _none_.
2.) If we agree on 1.), would we opt to allow nodes or to
All building=* on nodes is fine. As others have pointed out, it is
often necessary in HOT aerial mapping when we have low-resolution
imagery to work from.
Also, for humanitarian purposes there are serious uses for node-only
buildings, for estimating the population or the population
distribution
On Tue, Feb 17, 2015 at 1:30 AM, Dan S danstowell+...@gmail.com wrote:
All building=* on nodes is fine. As others have pointed out, it is
often necessary in HOT aerial mapping when we have low-resolution
imagery to work from.
Agree. As for the Wiki editing, I too hope it doesn't lead to a
Am 14.02.2015 um 23:06 schrieb Tobias Knerr:
On 14.02.2015 22:11, SomeoneElse wrote:
... it also says that it shouldn't be used on relations, which would
exclude perfectly valid multipolygons, such as this one:
Multipolygons are a means to map areas. So they are covered by the area
icon.
I see nothing wrong with building=* on a node, used 772612 times.
Typical cases are:
- somebody collects house numbers along a road, but has no access
to the geometry. Thus she can use plain addr: tags on unbuilt
properties, and add building=* where a building is visible.
- aerial imagery
On 14.02.2015 12:23, Tom Pfeifer wrote:
I see nothing wrong with building=* on a node, used 772612 times.
Which is still only 0.006 of all buildings.
Personally, I don't think building nodes are really useful. They are
little more than a formalized note, as most applications using buildings
I must chime in on this discussion. I disagree with Tobias' view. Some of
us are mapping in areas with very low resolution imagery. Yet, if a house
is visible, especially in remote regions, I want to be able to map it even
if it's not clear enough or large enough to have a shape drawn. I have
On Sat, Feb 14, 2015 at 4:16 AM, Tobias Knerr o...@tobias-knerr.de wrote:
Personally, I don't think building nodes are really useful. They are
little more than a formalized note, as most applications using buildings
will want areas.
It terms of locating the building, and understanding it's
On 14/02/2015 07:45, Lukas Sommer wrote:
Hello.
The english wiki page key:building says that this key may not be used
on nodes.
... it also says that it shouldn't be used on relations, which would
exclude perfectly valid multipolygons, such as this one:
On Sat, 14 Feb 2015, Tom Pfeifer wrote:
I see nothing wrong with building=* on a node, used 772612 times.
Typical cases are:
- somebody collects house numbers along a road, but has no access
to the geometry. Thus she can use plain addr: tags on unbuilt
properties, and add
On 15/02/2015 8:11 AM, SomeoneElse wrote:
It appears that again people are trying to use the wiki to tell other
people how to map rather than describe how things tend to be mapped.
A tenancy to instruct rather than guide?
The wiki should be a usefull guide as to best practice rather than
Hello.
The english wiki page key:building says that this key may not be used
on nodes. However, most (but not all) of the english wiki pages for
the individual values (like building=apartments) allow the usage on
nodes.
I’m not sure if it is useful to have a different policy for different
values
14 matches
Mail list logo