<div dir="ltr">I like the direction this is going. A couple of things come to mind though. If we use the model requiring different amenities to flesh out the description of the site that will require a separate node for each of them. The nodes will be hard to place unless you actually visit the campground in question. Being an armchair mapper I use the Internet to determine a great many of the details of the things I map. I won't be able to add nodes using that scenario. The category approach might be easier except in the cases where a site has all of the basics but only some of the luxury items; which category applies?<div><br></div><div>Relations make a lot of sense except they are tricky to get right. Noobies will inevitably screw them up. Plus, I'm still looking for a way to force simple site relations to render on my Garmin. I realize this is not a propoer issue to raise here but I also know some of you are wanting a way to use the data you've added to OSM to help find these places at vacation time. </div><div><br></div><div>Just a few thoughts to add to the mix...</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 25, 2015 at 3:43 PM, David Bannon <span dir="ltr"><<a href="mailto:dbannon@internode.on.net" target="_blank">dbannon@internode.on.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Warin suggested new category names and implied meanings. Think it was a<br>
quick draft, I have a counter "quick draft" along same lines.<br>
<br>
On Wed, 2015-03-25 at 11:06 +1100, Warin wrote:<br>
> None= nothing other than an area to pitch a tent or park a vehicle.<br>
> Basic = None + a toilet<br>
> Standard = Basic + water<br>
> Comfort = Standard + shower<br>
> First Class = Comfort + cloths washing (+ power?)<br>
> Luxury =Comfort + camp kitchen/swimming pool/restaurant<br>
<br>
David's model (camp_site=* ) -<br>
Basic = nothing other than an area to pitch a tent or park a vehicle.<br>
Standard = Basic + toilets and water<br>
Serviced = Standard + shower + power<br>
Fully_Serviced = Serviced + camp kitchen + Laundry<br>
Deluxe = Fully_Serviced + swimming pool/restaurant<br>
<br>
And define all the other aspects with additional tags. Good so far. But<br>
I am sure someone can think of an anomaly.<br>
<br>
BUT - its silly to have all those other things (mostly amenity=) on one<br>
node or area. So, now we need to define different nodes. And that leads<br>
to having to establish exact location of each. Thats too much trouble in<br>
many cases. I don't know ....<br>
<br>
Jan suggests a relation to link them all together, makes sense to me,<br>
but does it make sense to renderers and thus end users ? I've never used<br>
relations, seems the docs concentrate more on when not to use them.<br>
<br>
Jan, I am really sorry to be suggesting such drastic changes to your<br>
proposal so late but I think might be more acceptable to the community.<br>
<br>
David<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Dave Swarthout<br>Homer, Alaska<br>Chiang Mai, Thailand<br>Travel Blog at <a href="http://dswarthout.blogspot.com" target="_blank">http://dswarthout.blogspot.com</a></div></div>
</div>