<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2018-09-10 02:27, André Pirard
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f894cd10-02ce-ebfc-af29-0837fe82af71@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Hi,<br>
<br>
According to my OSM readings, I thought that a terrace was
something very special, but, according to <a
moz-do-not-send="true"
href="https://www.dictionary.com/browse/terrace">dictionary.com</a>,
a terrace is most exactly like French, mainly a) raised ground, b)
flat top of a building c) an accessible area connected to a
building at ground or upper level, such as for living or other
purposes..<br>
But beside that, dictionary.com defines a Terrace as a plain row
of houses without a terrace at all and so does <a
moz-do-not-send="true"
href="https://wiki.openstreetmap.org/wiki/Tag:building%3Dterrace">building=terrace</a>,
unlike French and Wikipedia which calls it <a
moz-do-not-send="true"
href="https://en.wikipedia.org/wiki/Terraced_house">Terraced_house</a>
(adjective).<br>
<br>
Practically, I'm correcting hundredths of houses tagged at 3-5m+
away from their true location, with incorrect shape and without
any addr:* at all. And during this I met areas tagged
building=terrace that, of course, are just as imprecise: they get
across the houses.<br>
If I map the houses that are inside, I get a very logical JOSM
congratulation: "building inside a building".<br>
In my mind, building=terrace is a bad tag. It should be:<br>
building=house<br>
house:terraced=yes<br>
be it as a row of houses or a single one.<br>
But I'm sure a reply will be "we" are not doing like that. Like
what, then.<br>
What should I do? <a moz-do-not-send="true"
href="https://wiki.openstreetmap.org/wiki/Tag:building%3Dterrace">building=terrace</a>
describes mapping separate houses as an <b>alternative</b>.<br>
Erase what another mapper did, and replace that element with
houses?<br>
While waiting, I converted them to landuse=terraced (invisible).<br>
<br>
On the other hand, I once asked how to map a part of the street
that is fitted with tables and seats near a café or restaurant.<br>
That is a <b>real</b> terrace.<br>
No answer.<br>
<br>
All the best, <br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
</blockquote>
So, in summary of this discussion, we have terraces, flat surfaces,
and we have houses that are houses and not those flat terraces but
that we call building=terrace and not houses. The wiki suggests to
map then separately which stops calling them terraces and to call
them building=house because they are not another kind of houses that
some do not call houses but detached.<br>
I said that, while waiting to know what to do, I would temporarily
keep the outline tagged with landuse=terrace. Someone suggested that
I should keep the outline (permanently, I suppose) but he didn't say
with which tag. Someone suggested that I should use
landuse=residential instead. I said that I kept the outline
temporarily and a so-called terrace landuse shouldn't be transformed
to residential which already exists and is around the village
instead of a few houses.<br>
<br>
I disagree with suggesting a whole menagerie of tags for houses, so
that someone making a search for them has to consult a whole
inexisting catalog of keywords to use.<br>
I suggest a single building=house plus a series of attributes like
house:terraced=yes if you like it, dot disappearing if the house
stops being mapped as a row, house:detached=yes for those who didn't
notice and to avoid calling 90% of the houses like that,
house:row=yes etc to your imagination and liking.<br>
<br>
Now, finally, the only terrace in that story is (thanks, Marc)
called a leisure.<br>
<br>
Thanks to all,<br>
All the best,
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</body>
</html>