|
I saw a location where a hotel (blue bed) was indicated in the map. As I know there is a good restaurant there, too, I wanted to add that information. When I selected the hotel I found out, that the restaurant was part of the hotel, to be precise an amenity of it. That is correct, but looking at the map I cannot distinguish between locations where is only a hotel or a hotel plus a restaurant. I would prefer to be able to see in the map where I can have a dinner for example. Should that be done by adding a seperate item nearby? Or what about to add another icon for a hotel plus a restaurant? That would be my proposal. That would lead to a type of building "restaurant/hotel". Thanks |
|
Hi Bergmaus, Both techniques are quite common -- tagging a single feature as both a hotel and a restaurant ( If you'd like to add a separate feature for the restaurant itself, go for it! This is especially useful if it has a different name/opening hours/contact info/website etc than the hotel. (If you do this you should remove the But note that even at the highest zoom of the openstreetmap.org map there's limited space for icons, so not everything that's mapped will appear on the screen. So there's no guarantee that the restaurant icon will show up. (Or it might show up, but the blue bed for the hotel may be gone!) Don't get hung up on exactly how things look on the map. The online map at openstreetmap.org is only one view of the map data, really just a demo. The goal of OSM is to get the correct data in the database, so it can be used for any kind of project, not just for a particular map rendering. If you want to use OSM data to make a map that emphasises the restaurants, or that shows a different icon for hotels that include a restaurant, you can do that -- but it takes some programming skill. Alternately you can use a tool like Overpass Turbo: https://overpass-turbo.eu/s/Naj I would even go so far to say that putting more than one real world object (hotel and restaurant) is bad practice albeit it being done so often. Name, opening hours, phone number, outdoor seating etc. are very unlikely to be exactly the same for both, nor do they occupy the exact same space. Creating two objects (e. g. building or grounds for the hotel and node within for the restaurant) is better tagging practice.
(15 Oct '19, 20:13)
TZorn
For most hotel restaurants I'd agree with you, and I almost always map them that way. In fact I was a little astonished to see how frequently hotel and restaurant are mapped as a single element -- over 11000 uses. I have, though, seen establishments that are both hotel and restaurant but still feel like a single "real world object" -- small places where the hotel proprietor is also the bartender, and the spouse is in the kitchen. Barring any tag conflicts, I'd probably map those as a single feature.
(15 Oct '19, 23:44)
jmapb
|
|
Thanks jmapb for the answer. In fact, the restaurant part always has different opening hours: you can reach the hotel late night or enter your room during a time where the restaurant is closed. A database must be seen as like a model and the reason of existence is solely to answer certain questions. If that is not given, the database does not have any sense. This means: On one hand as a guest of the hotel you want to know if there is a restarant as amenity. But on the other - not interested in a hotel, but searching a restaurant, the map should allow me to find them. Currently I only see hotel icons and some may have a restaurant but most not. Your argument that there is limited space for icons is very true. And therefore I do not believe adding a second item very close to the hotel to stand for the restaurant is not a good solution. And that leads to the proposal to add a different icon so allow to distinguish between hotels with and without restaurant. (and use that trivial common approach without coding needed) Coming to TZorns comment: Even having one Item, there is no problem to store a second telephone number or opening hours for the amenity restaurant. In fact they occopy the same space, just the bedrooms are maybe some levels above. For practical reasons it is one location (reaching, parking). Often even the entry is the same. The granularity is limited, remark the point that icon space is limited even in highest zoom level. |