<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.m4757128666660274552hoenzb
{mso-style-name:m_4757128666660274552hoenzb;}
span.E-mailStijl18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NL-BE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For this particular example, I thought it was quite appropriate. The different shops are in the same building (according to GRB), but can also be clearly separated
‘architecturally’ (see <a href="https://www.google.be/maps/@51.0899216,3.4454343,3a,75y,37.39h,83.82t/data=!3m7!1e1!3m5!1sx4e3GkQ16irl8xvamEQedw!2e0!6s%2F%2Fgeo0.ggpht.com%2Fcbk%3Fpanoid%3Dx4e3GkQ16irl8xvamEQedw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D9.20368%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656?hl=nl">
streetview</a>). But as others point out, this method will probably not always work.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Seppe<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Van:</span></b><span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> joost schouppe [mailto:joost.schouppe@gmail.com]
<br>
<b>Verzonden:</b> woensdag 18 april 2018 18:15<br>
<b>Aan:</b> OpenStreetMap Belgium<br>
<b>Onderwerp:</b> Re: [OSM-talk-be] Nodes or areas to tag amenities<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">How does this relate to the building:part=yes strategy that L'imaginaire has been playing with, e.g.
<a href="https://www.openstreetmap.org/way/283645760">https://www.openstreetmap.org/way/283645760</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2018-04-18 15:56 GMT+02:00 Ubipo . <<a href="mailto:ubipo.skippy@gmail.com" target="_blank">ubipo.skippy@gmail.com</a>>:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">After furter consideration I think indoor=level combined with amenity=restaurant should solve most problems.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Improving the map would then be as simple as not editing the general indoor=level and just drawing new ways for individual rooms (not tagged amenity=restaurant).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A restaurant on multiple floors would indeed be tricky as indoor=level implies a single level, although I think just adding level=0;1 shouldn't be that bad, right?<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 18 April 2018 at 13:58, Marc Gemis <<a href="mailto:marc.gemis@gmail.com" target="_blank">marc.gemis@gmail.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">how does someone "improve" your mapping to add a separate area for<br>
room=toilets ? nested room areas ? split it off ?<br>
<span style="color:#888888"><br>
<span class="m4757128666660274552hoenzb">m.</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
On Wed, Apr 18, 2018 at 12:43 PM, Ubipo . <<a href="mailto:ubipo.skippy@gmail.com" target="_blank">ubipo.skippy@gmail.com</a>> wrote:<br>
> Regarding the housenumbers: street and number is as said probably not needed<br>
> and better reserved for the actual building, although a specialised<br>
> addr:addition=a could be useful for the rooms.<br>
> Regarding room=restaurant, I think that tag is perfectly fine. It just<br>
> indicates the restaurant in it's entirety, with dining room, kitchen etc.<br>
><br>
> On Wed, Apr 18, 2018, 12:10 marc marc <<a href="mailto:marc_marc_irc@hotmail.com" target="_blank">marc_marc_irc@hotmail.com</a>> wrote:<br>
>><br>
>> for the addr : it look like strange that the room is in a building that<br>
>> doesn't have the same addr:housenumber as the building.<br>
>><br>
>> for multiple floors poi, you can draw all room with level=* tag<br>
>> or as a first step only use indoor=yes for the whole area<br>
>><br>
>> room=restaurant look like also strange for me.<br>
>> a restaurant is several room=* item : kitchen, dining room, toilets,<br>
>> cloakroom<br>
>> so what's a room=restaurant ? it can not be the same as the area used<br>
>> for amenity=restaurant. maybe it should be the area for the dining room.<br>
>> the wiki advice to put both tag to the same polygon look like wrong.<br>
>><br>
>><br>
>> Le 18. 04. 18 à 11:56, Marc Gemis a écrit :<br>
>> > o, I forgot, what about a restaurant that occupies multiple floors ?<br>
>> ><br>
>> ><br>
>> ><br>
>> > On Wed, Apr 18, 2018 at 11:55 AM, Marc Gemis <<a href="mailto:marc.gemis@gmail.com" target="_blank">marc.gemis@gmail.com</a>><br>
>> > wrote:<br>
>> >> The idea of using indoor mapping is good, and it's probably the future<br>
>> >> to solve all the problems you mention. (we had a similar discussion<br>
>> >> last Friday on the Riot channel)<br>
>> >><br>
>> >> Some remarks:<br>
>> >><br>
>> >> - does it make sense for a "room" to have an house number and a street<br>
>> >> ? I would expect those on the building, and floor or level or so on<br>
>> >> the room.<br>
>> >> - I'm not familiar enough with the simple indoor tagging, but I would<br>
>> >> expect that a restaurant exists of multiple rooms (dining, toilets,<br>
>> >> kitchen) not just one.<br>
>> >> - On the Riot channel the entrance to the restaurant was also seen as<br>
>> >> important.<br>
>> >><br>
>> >> m<br>
>> >><br>
>> >> On Wed, Apr 18, 2018 at 10:06 AM, Ubipo . <<a href="mailto:ubipo.skippy@gmail.com" target="_blank">ubipo.skippy@gmail.com</a>><br>
>> >> wrote:<br>
>> >>> Everyone,<br>
>> >>><br>
>> >>> A long standing question for osm mapping in cities is wether to tag<br>
>> >>> amenities in multi-purpose buildings as:<br>
>> >>> - a separate node inside the building's way<br>
>> >>> - the building itself, using both building=house and amenity=* (only<br>
>> >>> valid<br>
>> >>> with single-amenity buildings)<br>
>> >>> The node approach has consistency issues like these buildings:<br>
>> >>> <a href="https://www.openstreetmap.org/node/656793551" target="_blank">https://www.openstreetmap.org/node/656793551</a> .<br>
>> >>><br>
>> >>> The area approach is more consistent but doesn't really allow<br>
>> >>> multi-purpose<br>
>> >>> buildings.<br>
>> >>> A third, lesser used method is to use part of the simple indoor<br>
>> >>> tagging<br>
>> >>> schema. I've used a simplified version of this for this restaurant:<br>
>> >>> <a href="https://www.openstreetmap.org/way/580985564" target="_blank">https://www.openstreetmap.org/way/580985564</a> .<br>
>> >>> This approach uses two overlapping ways, one for the general building<br>
>> >>> (tagged building=house) and one for the restaurant on the ground floor<br>
>> >>> (tagged room=restaurant and of course amenity=restaurant).<br>
>> >>><br>
>> >>> Drawbacks of this are for one that the two ways fully overlap. This<br>
>> >>> triggers<br>
>> >>> the JOSM validator and probably some QC tools. Secondly renderers<br>
>> >>> might have<br>
>> >>> trouble placing the icons and house numbers of multiple areas like<br>
>> >>> this.<br>
>> >>> Luckily both these problems could be fixed. The positives are of<br>
>> >>> course:<br>
>> >>> consistency and the possibility for multiple amenities (using the<br>
>> >>> level=*<br>
>> >>> key).<br>
>> >>><br>
>> >>> What do you all think of this approach?<br>
>> >>><br>
>> >>> Kind regards,<br>
>> >>> Pieter (Ubipo)<br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> Talk-be mailing list<br>
>> >>> <a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
>> >>> <a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">
https://lists.openstreetmap.org/listinfo/talk-be</a><br>
>> >>><br>
>> ><br>
>> > _______________________________________________<br>
>> > Talk-be mailing list<br>
>> > <a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
>> > <a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Talk-be mailing list<br>
>> <a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
>> <a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
><br>
><br>
> _______________________________________________<br>
> Talk-be mailing list<br>
> <a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
><br>
<br>
_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Joost Schouppe<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.openstreetmap.org/user/joost%20schouppe/" target="_blank">OpenStreetMap</a> | <a href="https://twitter.com/joostjakob" target="_blank">Twitter</a> | <a href="https://www.linkedin.com/pub/joost-schouppe/48/939/603" target="_blank">LinkedIn</a> | <a href="http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/" target="_blank">Meetup</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>