<div dir="ltr"><div class="gmail_extra">"seamark" uses a highly hierarchical tag scheme, but it limits that project's interoperability  with the rest of OSM.</div><div class="gmail_extra"><br></div><div class="gmail_extra">-----------------------</div><div class="gmail_extra">Realistically: If camp_site:identifier is used it will be a looooong time before it's ever rendered<br></div><div class="gmail_extra">or routable.  That's just reality.</div><div class="gmail_extra"><br></div><div class="gmail_extra">addr:housenumber has the advantage of rendering and perhaps routability today.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I think that future routing software can be smart enough to work without addr:street.</div><div class="gmail_extra">If the router gets you as far as a campground (or other) polygon, and within that</div><div class="gmail_extra">polygon are bare addr:unit or addr:housenumber, it should be able to figure out what</div><div class="gmail_extra">to do.</div></div>