<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Comments interspersed. . .<br class=""><div><blockquote type="cite" class=""><div class="">On Apr 29, 2015, at 2:57 PM, Bryce Nesbitt <<a href="mailto:bryce2@obviously.com" class="">bryce2@obviously.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">Ok, lets see if we can land this.</div><div class="gmail_extra">Existing practice varies:<br class=""></div><div class="gmail_extra"><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra">tourism=camp_site + name=<pitch number></div><div class="gmail_extra"><div class="gmail_extra">tourism=camp_site + ref=<pitch number></div></div><div class="gmail_extra"><div class="gmail_extra">tourism=camp_site + addr:unit=<pitch number></div></div><div class="gmail_extra"><div class="gmail_extra">tourism=camp_site + addr:housenumber=<pitch number></div></div><div class="gmail_extra"><div class="gmail_extra">camp_site=pitch + name=<pitch number></div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">camp_site=pitch + ref=<pitch number></div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class=""><div class="gmail_extra">camp_site=pitch + addr:unit=<pitch number></div></div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class=""><div class="gmail_extra">camp_site=pitch+ addr:housenumber=<pitch number></div></div></div></div><div class="gmail_extra">camp_site=<pitch number></div><div class="gmail_extra"><div class="gmail_extra">tourism=caravan_site + name=<pitch number></div></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra"><div class="gmail_extra">building=cabin + ref=<number></div></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra"><div class="gmail_extra">name=<pitch number></div></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra"><div class="gmail_extra">ref=<pitch number></div></div></blockquote></div></div></blockquote><div><br class=""></div><div>You found more variations than I’ve noticed. It seems to be a good summary.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra">There's a lot of activity in the "camp_site" namespace:</div><div class="gmail_extra"><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra">camp_site:water (412)</div><div class="gmail_extra"><div class="gmail_extra">camp_site:parking (333)</div></div><div class="gmail_extra"><div class="">camp_site:fire=ring</div><div class="">....</div></div></blockquote><div class="gmail_extra"><br class=""></div></div></div></blockquote><div><br class=""></div><div>I suspect that this is because of the suggested tagging at <a href="http://wiki.openstreetmap.org/wiki/Proposed_features/Extend_camp_site#Tagging_of_individual_pitches" class="">http://wiki.openstreetmap.org/wiki/Proposed_features/Extend_camp_site#Tagging_of_individual_pitches</a></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""></div><div class="gmail_extra">The least disruptive tagging seems to be;</div><div class="gmail_extra"><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">tourism=camp_site (for the site) or tourism=caravan_site<div class="gmail_extra"><br class=""></div><div class="gmail_extra">camp_site=pitch</div>camp_site:<amenity>=yes/no<div class="gmail_extra"><div class="gmail_extra">addr:unit=<pitch number></div></div></blockquote></div></div></blockquote><div><br class=""></div>Which, other than addr:unit=<pitch number/name>, matches the tagging at the link above.<br class=""><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_extra">Tagging that avoids the namespace is: </div><div class="gmail_extra"><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class="">tourism=camp_site (for the site) or tourism=caravan_site<div class="gmail_extra"><br class=""></div><div class="gmail_extra">camp_site=pitch</div><amenity>=yes/no (e.g. drinking_water=yes).<div class="gmail_extra"><div class="gmail_extra">addr:unit=<pitch number></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div><div>Any reason to avoid a namespace? Seems like tagging things like water availability as amenities would show a lot of amenities that are not really available to everyone. That is things like the picnic table, fire ring or fire place and possible water may be dedicated to the people who are occupying the unit/pitch/site.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"></div></div><div class="gmail_extra">If the community is willing to mechanically retag, it could be:</div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">tourism=camp_site</div></div></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"><amenity>=yes/no</div></div></div></blockquote><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"><br class=""></div><div class="gmail_extra">camp_site:pitch=yes<br class=""></div></div></div><div class="gmail_extra"><div class="gmail_extra"><amenity>=yes/no</div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">addr:housenumber=<pitch number></div></div></div></div></blockquote></div></div></blockquote><div><br class=""></div><div>Looks like you are strongly in favor of not using a namespace. In the case of individual campsite pitches I think there is a strong case to be made for using a namespace. Maybe not camp_site:*=* as “camp_site” is, unfortunately, established for the overall campground. But there ought to be a way to show that a pitch as a number of amenities that are dedicated to that site and not to others which a namespace can easily do.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_extra">I chose <b class="">addr:housenumber</b> because that's perfectly set up for routers. If a router can find a camp ground mapped as an area,</div><div class="gmail_extra">it should be able to find the number inside. It's also unrealistic at this time to expect osm-carto to render ref addr:unit or other names.</div></div></div></div></blockquote><br class=""></div><div>That sounds like “tagging for the renderer” to me. I find it distasteful to reuse part of the addr:* namespace for this but if it must be done then addr:unit is far more appropriate than addr:housenumber.</div><br class=""></body></html>