Folks, we have been discussing this camp_site= issue for a long time. And I don't think we are making any progress. How about we apply a design approach ? Agree on how the "average" end user would use the data ?
In my opinion, a camper is likely look on a map hoping to see a camp site near where he/she is heading. They will have an idea of the type of sites they like. Some people won't camp without a toilet, others must have a swimming pool. Another person will only go somewhere they are unlikely to meet other people. When they identify the type they like, they may decide that is all they need to know or they may investigate a short list further. Now, lets imagine an OSM map that shows camp site icons, maybe five or six different colours depending on a simple set of characteristics. The user knows they camp at only green and blue ones. Easy so far. If they are after more info, the map may give them a name or locality to google for. Or maybe its a specialised camping map that will pop up a flag with more OSM date when the icon is clicked. That "more data" is made up with info from the associated tags including, perhaps, the description= key. Please identify what is wrong with this story ? In localities where special ad hoc data is important, it needs to be in the description tag. General data that may influence a search, should be tagged. We cannot expect to show all important data right there on the freshly rendered map. David _______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
