Proposed features/OpenBeta Initiative workflow

From OpenStreetMap Wiki
Jump to: navigation, search
OpenBeta app workflow
Status: Proposed (under way)
Proposed by: Vietgoeswest
Tagging: climbing=*
RFC start: 2017 April 19

Proposal

This proposal is for synchronizing contents between OSM and OpenBeta Initiative. Users of OpenBeta app may push edits to OSM.

OpenBeta Initiative (founded 2016, https://openbeta.io) is US-based not-for-profit tech organization whose first project is to build a modern web and mobile app to make it easier for climbers to share maps of climbing routes and approach trails. The project is Open Source (GPLv3).

  1. OpenBeta backend process periodically syncs OSM features with sport=climbing tag to its own PostGIS database.
  2. Web and mobile app query OpenBeta Rest API.
  3. To submit write-edit the user must have an account linked with OSM.
  4. OpenBeta app submits edits to OSM on user's behalf.

Rationale

There are over ten thousand sport=climbing tags but there isn't a tool made specifically for editing climbing data. iD and JOSM are too technical to most rock climbers.

Examples

(I will upload app mockup screens after new user upload restriction is lifted)

Tagging

Proposed new sub-tags:

  • climbing:uuid
  • climbing:top_level

Unless specifically noted we will strive to follow conventions outlined in Climbing proposal [1].

A. Climbing Routes and Individual Boulder Problems
Key Value Mandatory Comment Example
name * Y La Dura Dura
climbing route | boulder Y climbing=route
climbing:grade:* * Y see [1] climbing:grade:french=9b+
climbing:<style>

where style=sport boulder

trad

ice

mixed

yes | no Y see [2] climbing:sport=yes
climbing:uuid * Y Universal Unique ID for referencing this climb in another database such as OpenBeta where we can store additional info not suitable on OSM such as First Ascent records, detailed description and photos. climbing:uuid=C10005
climbing:length:.* * N Users are discouraged to set these unless the route is a long and wandering alpine route. N/A
climbing:route_bottom * N N/A
climbing:route_top * N N/A
B. Crags, Large Boulders and Climbing Destinations
Key Value Mandatory Comment Example
name * Y Frankenjura
area yes Y area=yes
climbing crag | boulder Y climbing=crag
climbing:top_level yes | no Y yes to signify this is the outer most polygon encompassing the whole climbing region which may contains one or more sub-areas. For example,
  • Frankenjura: climbing:top_level=yes
  • Waldkopf (a crag in Frankenjura): climbing:top_level=no
  • Yosemite: climbing:top_level=yes
  • Half Dome (a sub-area in Yosemite): climbing:top_level=no
climbing:top_level=yes
climbing:uuid * Y Universal Unique ID for referencing this climb in another database such as OpenBeta where we can store additional info not suitable on OSM such as First Ascent records, detailed description and photos. climbing:C10005

Applies to

Features with sport=climbing tag.

Rendering

No rendering is required

Features/Pages affected

None

External Discussions

Comments

Please comment on the discussion page.

References

[1] Proposed features/Climbing

[2] Tags: sport=climbing