<div dir="auto">I agree on the separation of building:part=* for architectural distinct building parts and room=* for mostly functionaly distinct parts of a building. I think there should be a general indoor=part or something (don't quote me on that tag, I can't really think of something better). This would then replace the room=restaurant and would serve to separate functionaly different parts of a building. Another example apart from a restaurant is a building containing both classrooms and a library. The library would be tagged as indoor=part and the relevant amenity (with optional room=*'s inside that) and the classrooms would just be tagged as room=* and indoor=room as they don't really form a whole.</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Apr 18, 2018, 18:54 marc marc <<a href="mailto:marc_marc_irc@hotmail.com">marc_marc_irc@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">@ubipo for indoor=level, I suppose you mean indoor=yes indoor=thenumber :)<br>
<br>
building:part is for a part of a building where tag related to the <br>
building itself doesn't have the same value for one part <> another part<br>
for exemple a building that have one part with one level :<br>
building:part=yes<br>
building:levels=1<br>
and another part with 2 levels<br>
building:part=yes<br>
building:levels=1<br>
both parts make one building with building=yes on the outline<br>
<br>
but inside a buidling, room nearly never affect the building "external look"<br>
so it should not be any building:part tag on a room,<br>
except if a building:part is made by only one room of course.<br>
<br>
for room=restaurant on amenety=restaurant, I've been talking with <br>
PanierAvide who add this to the wiki. he agree that this is not good.<br>
we are working on on howto make it better.<br>
<br>
Le 18. 04. 18 à 18:43, Pieter Vander Vennet a écrit :<br>
> I have some experience with indoor mapping.<br>
> <br>
> I would invite you guys to have a look at my work of the Blekerij in <br>
> Gent <br>
> <<a href="https://openlevelup.net/old/?lat=51.060092&lon=3.732321&z=19&t=0&lvl=0&tcd=1&urd=0&bdg=0&pic=0&nte=0&ilv=0" rel="noreferrer noreferrer" target="_blank">https://openlevelup.net/old/?lat=51.060092&lon=3.732321&z=19&t=0&lvl=0&tcd=1&urd=0&bdg=0&pic=0&nte=0&ilv=0</a>>, <br>
> as example. Toilets can be mapped as either a point or area with <br>
> 'amenity=toilets, indoor=yes; level=0' (or perhaps 'level=0-2', e.g. for <br>
> a building with toilets on the same location on floors 0 till 2.). Note <br>
> that 'level=0' is the ground floor (gelijkvloers).<br>
> <br>
> I have no experience with the building:part=yes. I assume that <br>
> indoor=yes implies 'building:part=yes' and that 'building:part' is <br>
> rather used for roofs etc...<br>
> <br>
> <br>
> <br>
> <br>
> Met vriendelijke groeten,<br>
> Pieter Vander Vennet<br>
> <br>
> 2018-04-18 18:13 GMT+02:00 joost schouppe <<a href="mailto:joost.schouppe@gmail.com" target="_blank" rel="noreferrer">joost.schouppe@gmail.com</a> <br>
> <mailto:<a href="mailto:joost.schouppe@gmail.com" target="_blank" rel="noreferrer">joost.schouppe@gmail.com</a>>>:<br>
> <br>
> How does this relate to the building:part=yes strategy that<br>
> L'imaginaire has been playing with, e.g.<br>
> <a href="https://www.openstreetmap.org/way/283645760" rel="noreferrer noreferrer" target="_blank">https://www.openstreetmap.org/way/283645760</a><br>
> <<a href="https://www.openstreetmap.org/way/283645760" rel="noreferrer noreferrer" target="_blank">https://www.openstreetmap.org/way/283645760</a>><br>
> <br>
> 2018-04-18 15:56 GMT+02:00 Ubipo . <<a href="mailto:ubipo.skippy@gmail.com" target="_blank" rel="noreferrer">ubipo.skippy@gmail.com</a><br>
> <mailto:<a href="mailto:ubipo.skippy@gmail.com" target="_blank" rel="noreferrer">ubipo.skippy@gmail.com</a>>>:<br>
> <br>
> After furter consideration I think indoor=level combined with<br>
> amenity=restaurant should solve most problems.<br>
> Improving the map would then be as simple as not editing the<br>
> general indoor=level and just drawing new ways for individual<br>
> rooms (not tagged amenity=restaurant).<br>
> <br>
> A restaurant on multiple floors would indeed be tricky as<br>
> indoor=level implies a single level, although I think just<br>
> adding level=0;1 shouldn't be that bad, right?<br>
> <br>
> On 18 April 2018 at 13:58, Marc Gemis <<a href="mailto:marc.gemis@gmail.com" target="_blank" rel="noreferrer">marc.gemis@gmail.com</a><br>
> <mailto:<a href="mailto:marc.gemis@gmail.com" target="_blank" rel="noreferrer">marc.gemis@gmail.com</a>>> wrote:<br>
> <br>
> how does someone "improve" your mapping to add a separate<br>
> area for<br>
> room=toilets ? nested room areas ? split it off ?<br>
> <br>
> m.<br>
> <br>
> On Wed, Apr 18, 2018 at 12:43 PM, Ubipo .<br>
> <<a href="mailto:ubipo.skippy@gmail.com" target="_blank" rel="noreferrer">ubipo.skippy@gmail.com</a> <mailto:<a href="mailto:ubipo.skippy@gmail.com" target="_blank" rel="noreferrer">ubipo.skippy@gmail.com</a>>> wrote:<br>
> > Regarding the housenumbers: street and number is as said<br>
> probably not needed<br>
> > and better reserved for the actual building, although a<br>
> specialised<br>
> > addr:addition=a could be useful for the rooms.<br>
> > Regarding room=restaurant, I think that tag is perfectly<br>
> fine. It just<br>
> > indicates the restaurant in it's entirety, with dining<br>
> room, kitchen etc.<br>
> ><br>
> > On Wed, Apr 18, 2018, 12:10 marc marc<br>
> <<a href="mailto:marc_marc_irc@hotmail.com" target="_blank" rel="noreferrer">marc_marc_irc@hotmail.com</a><br>
> <mailto:<a href="mailto:marc_marc_irc@hotmail.com" target="_blank" rel="noreferrer">marc_marc_irc@hotmail.com</a>>> wrote:<br>
> >><br>
> >> for the addr : it look like strange that the room is in<br>
> 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<br>
> 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<br>
> room, toilets,<br>
> >> cloakroom<br>
> >> so what's a room=restaurant ? it can not be the same as<br>
> the area used<br>
> >> for amenity=restaurant. maybe it should be the area for<br>
> the dining room.<br>
> >> the wiki advice to put both tag to the same polygon look<br>
> 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<br>
> multiple floors ?<br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> > On Wed, Apr 18, 2018 at 11:55 AM, Marc Gemis<br>
> <<a href="mailto:marc.gemis@gmail.com" target="_blank" rel="noreferrer">marc.gemis@gmail.com</a> <mailto:<a href="mailto:marc.gemis@gmail.com" target="_blank" rel="noreferrer">marc.gemis@gmail.com</a>>><br>
> >> > wrote:<br>
> >> >> The idea of using indoor mapping is good, and it's<br>
> probably the future<br>
> >> >> to solve all the problems you mention. (we had a<br>
> 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<br>
> number and a street<br>
> >> >> ? I would expect those on the building, and floor or<br>
> level or so on<br>
> >> >> the room.<br>
> >> >> - I'm not familiar enough with the simple indoor<br>
> tagging, but I would<br>
> >> >> expect that a restaurant exists of multiple rooms<br>
> (dining, toilets,<br>
> >> >> kitchen) not just one.<br>
> >> >> - On the Riot channel the entrance to the restaurant<br>
> was also seen as<br>
> >> >> important.<br>
> >> >><br>
> >> >> m<br>
> >> >><br>
> >> >> On Wed, Apr 18, 2018 at 10:06 AM, Ubipo .<br>
> <<a href="mailto:ubipo.skippy@gmail.com" target="_blank" rel="noreferrer">ubipo.skippy@gmail.com</a> <mailto:<a href="mailto:ubipo.skippy@gmail.com" target="_blank" rel="noreferrer">ubipo.skippy@gmail.com</a>>><br>
> >> >> wrote:<br>
> >> >>> Everyone,<br>
> >> >>><br>
> >> >>> A long standing question for osm mapping in cities<br>
> 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<br>
> amenity=* (only<br>
> >> >>> valid<br>
> >> >>> with single-amenity buildings)<br>
> >> >>> The node approach has consistency issues like these<br>
> buildings:<br>
> >> >>> <a href="https://www.openstreetmap.org/node/656793551" rel="noreferrer noreferrer" target="_blank">https://www.openstreetmap.org/node/656793551</a><br>
> <<a href="https://www.openstreetmap.org/node/656793551" rel="noreferrer noreferrer" target="_blank">https://www.openstreetmap.org/node/656793551</a>> .<br>
> >> >>><br>
> >> >>> The area approach is more consistent but doesn't<br>
> really allow<br>
> >> >>> multi-purpose<br>
> >> >>> buildings.<br>
> >> >>> A third, lesser used method is to use part of the<br>
> simple indoor<br>
> >> >>> tagging<br>
> >> >>> schema. I've used a simplified version of this for<br>
> this restaurant:<br>
> >> >>> <a href="https://www.openstreetmap.org/way/580985564" rel="noreferrer noreferrer" target="_blank">https://www.openstreetmap.org/way/580985564</a><br>
> <<a href="https://www.openstreetmap.org/way/580985564" rel="noreferrer noreferrer" target="_blank">https://www.openstreetmap.org/way/580985564</a>> .<br>
> >> >>> This approach uses two overlapping ways, one for the<br>
> general building<br>
> >> >>> (tagged building=house) and one for the restaurant<br>
> on the ground floor<br>
> >> >>> (tagged room=restaurant and of course<br>
> amenity=restaurant).<br>
> >> >>><br>
> >> >>> Drawbacks of this are for one that the two ways<br>
> fully overlap. This<br>
> >> >>> triggers<br>
> >> >>> the JOSM validator and probably some QC tools.<br>
> Secondly renderers<br>
> >> >>> might have<br>
> >> >>> trouble placing the icons and house numbers of<br>
> multiple areas like<br>
> >> >>> this.<br>
> >> >>> Luckily both these problems could be fixed. The<br>
> positives are of<br>
> >> >>> course:<br>
> >> >>> consistency and the possibility for multiple<br>
> 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" rel="noreferrer">Talk-be@openstreetmap.org</a><br>
> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> >> >>> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" 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" rel="noreferrer">Talk-be@openstreetmap.org</a><br>
> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> >> > <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" 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" rel="noreferrer">Talk-be@openstreetmap.org</a> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> >> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" 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" rel="noreferrer">Talk-be@openstreetmap.org</a> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> > <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" 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" rel="noreferrer">Talk-be@openstreetmap.org</a> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a>><br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Talk-be mailing list<br>
> <a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a>><br>
> <br>
> <br>
> <br>
> <br>
> -- <br>
> Joost Schouppe<br>
> OpenStreetMap<br>
> <<a href="http://www.openstreetmap.org/user/joost%20schouppe/" rel="noreferrer noreferrer" target="_blank">http://www.openstreetmap.org/user/joost%20schouppe/</a>> | Twitter<br>
> <<a href="https://twitter.com/joostjakob" rel="noreferrer noreferrer" target="_blank">https://twitter.com/joostjakob</a>> | LinkedIn<br>
> <<a href="https://www.linkedin.com/pub/joost-schouppe/48/939/603" rel="noreferrer noreferrer" target="_blank">https://www.linkedin.com/pub/joost-schouppe/48/939/603</a>> | Meetup<br>
> <<a href="http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/" rel="noreferrer noreferrer" target="_blank">http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/</a>><br>
> <br>
> _______________________________________________<br>
> Talk-be mailing list<br>
> <a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a> <mailto:<a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a>><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
> <<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a>><br>
> <br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Talk-be mailing list<br>
> <a href="mailto:Talk-be@openstreetmap.org" target="_blank" rel="noreferrer">Talk-be@openstreetmap.org</a><br>
> <a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" 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" rel="noreferrer">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><br>
</blockquote></div>