<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<blockquote type="cite">
<div>
On 02/12/2022 8:29 PM Tom Crocker <tomcrockermail@gmail.com> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div dir="auto">
<div>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Sat, 12 Feb 2022, 17:34 Paul Berry, <<a href="mailto:pmberry2007@gmail.com">pmberry2007@gmail.com</a>> wrote:
<br>
</div>
<blockquote>
<div dir="ltr">
<div>
Hi Mark,
</div>
<div>
<br>
</div>
<div>
I'd map that as:
</div>
<div>
<br>
</div>addr:street=Abbots Walk
<div>
addr:parentstreet=Boat Lane
</div>
<div>
<br>
</div>
<div>
I'm not hung up on Abbots Walk being a building rather than a street. We're fitting addressing to the best available tags, not the other way around.
</div>
<div>
<br>
</div>
<div>
Regards,
</div>
<div>
Paul
</div>
<div dir="auto">
<br>
</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto">
<br>
</div>
<div dir="auto">
Hi Paul
</div>
<div dir="auto">
<br>
</div>
<div dir="auto">
For what it's worth, I'm inclined to agree that having only one tag would be ideal. The reason I'd go with addr:place is various tools like nominatim won't use the address if addr:street doesn't match a highway. So we'll tag it but it won't show up in search results, which seems a bit self-defeating.
</div>
</div>
</blockquote>
<div class="default-style">
This sounds like "tagging for the renderer"... And addr:place in particular was rather frowned upon in the discussion in December 2020...
</div>
<blockquote type="cite">
<div dir="auto">
<div dir="auto"></div>
<div dir="auto">
Cheers
</div>
<div dir="auto">
Tom
</div>
</div>_______________________________________________
<br>Talk-GB mailing list
<br>Talk-GB@openstreetmap.org
<br>https://lists.openstreetmap.org/listinfo/talk-gb
<br>
</blockquote>
</body>
</html>