<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>FWIW, my technique has been to map the building outlines from
aerial photography (having established any necessary imagery
offset), then print that out on paper and walk round the houses,
noting the house numbers and where the front doors are. Then, add
additional front door node(s) to the building outline areas, and
attach the address information to those nodes.</p>
<p>I think that's more 'honest' than trying to divide a semi-,
terrace, or more complicated building into separate house areas,
when I've got no idea where the dividing walls are internally. And
it has the added benefit of pointing a map user at the main
entrance, which is probably what they want to find.<br>
</p>
<p>John<br>
</p>
<div class="moz-cite-prefix">On 29/12/2020 10:25, Michael Collinson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d5200f02-b580-9b2c-9d78-599e3a3d4dca@ayeltd.biz">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+++1 to mapping addresses as standalone nodes!<br>
<br>
While it is an alternative accepted style to put them on
buildings, I personally loathe it. A building is a building, an
address is an address. A one-to-one relation is common but not
100%. The address may not even be logically applicable to a
building, examples: schools (a cluster of buildings on a site),
recreation grounds (perhaps no building at all).<br>
<br>
Dividing a building vertically for the purpose of address in
messy. Yes, there is some logic to the concept of separate
living/working volumes but then that should apply to horizontal
division as will, common in some parts of the world. For me, a
semi-detached house is a semi-detached house and a terrace is a
terrace.<br>
<br>
And the worst thing, and my main motivation for writing, is that
is destroys simple 3-D modelling, <a
class="moz-txt-link-freetext"
href="https://wiki.openstreetmap.org/wiki/Simple_3D_buildings"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Simple_3D_buildings</a>
. A semi-detached house with a hipped roof becomes impossible to
model if two conjoined buildings or even building parts as far as
I can see (?).<br>
<br>
I suggest always modelling addresses as separate nodes placed in a
logical place for navigation.<br>
<br>
A jolly Christmas rant brought to you by Mike. Best wishes to all.<br>
<br>
<div class="moz-cite-prefix">On 2020-12-29 09:28, Simon Poole
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f3ad06de-5350-6e9c-8c65-cfcc12ee9c4b@poole.ch">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p>At the danger of pointing out the blatantly obvious: you can
easily survey and add addresses as stand alone nodes without
adding buildings before. <br>
</p>
<p>It is quite a fast process and, at least for me, is only
limited by walking speed and getting distracted by other
details which you tend to only see when surveying on foot. It
is what we used to do before aerial imagery was widely
available and will result in fully functional routing. Given
how painful correcting building geometries is I would always
prefer an address node over mapping a building outline from a
sub-par source.</p>
<p>Simon<br>
</p>
<div class="moz-cite-prefix">Am 28.12.2020 um 17:21 schrieb Rob
Nickerson:<br>
</div>
<blockquote type="cite"
cite="mid:CAK4yQTkSS52-2Q2saANbVZpv_3WFZZneT9h_sKnrvu5_wErPUA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>I just spotted that Google Maps has added house numbers
to their map of the UK. They are all over the place - does
anyone recognise the source?</div>
<div><br>
</div>
<div>What can we do to improve coverage of addresses in OSM?
I notice that we have some pretty good aerial imagery now.
Should we see if we can get good building outline from an
AI / machine learning approach? If the quality is good we
can then use these to help add addresses. For example we
can ask new mappers to add addresses using tools such as
StreetComplete.<br>
</div>
<div><br>
</div>
<div>Any thoughts much appreciated. I have a feeling that if
we can come up with a plan we may be able to get some help
from several of the big tech companies now interested in
the UK. It would be better if we were steering this rather
than it happening to us.<br>
</div>
<div><br>
</div>
<div> </div>
<div>Best wishes,<br>
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr"><span style="color:rgb(0,0,255)"><b>Rob</b></span><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-GB mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-GB@openstreetmap.org" moz-do-not-send="true">Talk-GB@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-gb" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-gb</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-GB mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-GB@openstreetmap.org" moz-do-not-send="true">Talk-GB@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-gb" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/talk-gb</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-GB mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-gb">https://lists.openstreetmap.org/listinfo/talk-gb</a>
</pre>
</blockquote>
</body>
</html>