[Tagging] How does an end user use camp site data ?
ralph.aytoun at ntlworld.com
Sat Mar 28 10:50:59 UTC 2015
David Bannon, a great approach to rendering information on the
OpenStreetMap which should be adopted for deciding all symbols... HOW DOES
AN END USER USE THE DATA.
If the overall area rendering for a campsite remains the same and a node
symbol within the campsite is rendered in the colour depicting the type of
campsite and or it's amenities (private, public, communal ablutions,
swimming pool, etc) then it would solve many problems. The information
could be tagged on the reception desk node with additional tags for
available amenities and the link to a website. As Bryce mentioned, he would
do a web search so getting the correct name for the campsite would also be
paramount to helping in that.
On 28 March 2015 at 02:37, David Bannon <dbannon at internode.on.net> wrote:
> 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.
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging