|Rendered as:||icon by value|
The amenities tag is overloaded. Divide the values accepted for amenities into functional groups. The proposed group "motorist" would include items interesting to / catering to motorists.
The following items will be rendered on maps that include the functional amenity group, "motorist".
- fuel stations / service stations
- hotels / lodging
- travel / tourist offices
- rest areas
- construction zones
- etc, . . .
Call for discussion
Please discuss. There is probably a better name for the key.
See also the related key, Proposed_features/Administration which is also intended to unload amenity.
- As somebody who has never learnt to drive I resent the idea that hotels , tourist offices and other tags are only for motorists ;-) Then again once you recognise that, I don't really know what else makes the example values related. I'm sure there are a good collection of motorist-only features, though. TomChance 08:16, 22 December 2006 (UTC)
- See my comments on the Proposed_features/Administration proposal, about doing this wholesale rather than piecemeal --Batchoy 09:55, 22 December 2006 (UTC)
- Better categorisation of points of interest, POIs, is desirable, agreed. The problem is that many items can belong in more than one category but like a library book indexing system, we only get one choice and it should be as neutral as possible. I am a driver but think that putting, say, hotels under motorist and camp sites under hiker is not worthwhile. Batchoy's Proposed_features/Administration proposal for base categorisation is a good one and I suggest following that and discontinuing this one for the present. A future way forward might be to have renderers and search algorythms intelligently pick out POIs of interest to a motorist. This might be supported in OSM by an xml list feature, i.e. a 'motorist' list would include all the tag/values for the items of high potential interest to motorists. MikeCollinson 03:20, 26 January 2007 (UTC)