<div dir="ltr"><div><div>Greetings!<br><br></div>I'm an avid rock climber and open
source enthusiast. I want to build better climbing maps and an
easy-to-use mobile app for climbers to share information. <br><br></div><div>Many
climbing walls/crags/areas are currently defined as nodes in OSM. In
contrast, in my proof-of-concept app users can define and save crag
boundaries by drawing polygons on the map. The search function would
then use spatial queries to find features contained within a polygon.<br><br></div><div>The linked photo below illustrates typical layout of a climbing area. Crag
boundaries are often loosely defined by climbers... so I'm not sure
whether saving those polygons to OSM is a good idea.<br><br><a href="https://s9.postimg.org/xg4dq6mbj/nested-boundaries-example.jpg">https://s9.postimg.org/xg4dq6mbj/nested-boundaries-example.jpg</a><br><br><div><br>Also I have looked into using Relations but the concept seems rigid for
this use case as it would require the users (or the code) to associate
climbing routes to a relation. Perhaps I misunderstand the concept of relations?<br></div><br></div><div>I'm
looking for guidance and suggestions on how to best implement this
feature. Having all geo-data in OSM (single source of truth) would be
ideal, but I can just store those polygons in my own database as well.<br><br></div><div>Here's my proposal:<br></div><div><br><a target="_blank" href="https://wiki.openstreetmap.org/wiki/Proposed_features/OpenBeta_Initiative_workflow">https://wiki.openstreetmap.<wbr>org/wiki/Proposed_features/<wbr>OpenBeta_Initiative_workflow</a><br><br><br></div><div>Thanks,<br><br></div>Viet Nguyen<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><a href="https://s9.postimg.org/xg4dq6mbj/nested-boundaries-example.jpg">https://s9.postimg.org/xg4dq6mbj/nested-boundaries-example.jpg</a><br></div>