+1 for # of rooms. It's pretty much the same as # of parking spots in a parking lot, imho.
As per prices I think hotel prices are not _that_ different from toll prices (at highways, parking, etc). For hotels, I'd opt for a price range system rather than exact prices, though, due to both the range of prices as well as price changes over time (due to inflation). A bit similar as the hotel ranking star system but classes for eg cheap, inexpensive, mid-range, costly, expensive, shit-expensive? Cheers, -Jaakko http://osm.org/user/jaakkoh Sent from my BlackBerry® device from Digicel -- Mobile: +509-37-26 91 54, Skype/GoogleTalk: jhelleranta -----Original Message----- From: Martin Koppenhoefer <[email protected]> Date: Fri, 13 Apr 2012 13:10:22 To: Andrew Errington<[email protected]> Cc: openstreetmap<[email protected]> Subject: Re: [OSM-talk] POI for Hotel Am 13. April 2012 07:14 schrieb Andrew Errington <[email protected]>: > On Fri, April 13, 2012 12:33, Frans Thamura wrote: > Option 1: Add all data for all hotels into OSM. Now you have only one > database. But the problem is that some data should probably not be > entered into OSM. For example, number of rooms, or price of rooms. probably this is offtopic in this thread, but the number of rooms would be an interesting information to roughly tell how important a hotel is. I would like to have this in OSM. Prices on the other hand are also of interest if you look for a hotel, but there is currently no hope to keep this information up to date (and usually there are lots of prices, dependent on the particular room (view/orientation, location, size, ...). cheers, Martin _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
