Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions data/fields/climbing/bolted.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"key": "climbing:bolted",
"type": "check",
"label": "Bolted"
}
6 changes: 6 additions & 0 deletions data/fields/climbing/bolts.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:bolts",
"type": "number",
"minValue": 0,
"label": "Number of Bolts"
}
6 changes: 6 additions & 0 deletions data/fields/climbing/grade/french.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:grade:french",
"type": "text",
"label": "Grade (French)",
"placeholder": "5c"
}
6 changes: 6 additions & 0 deletions data/fields/climbing/grade/saxon.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:grade:saxon",
"type": "text",
"label": "Grade (Saxon)",
"placeholder": "VIIa"
}
6 changes: 6 additions & 0 deletions data/fields/climbing/grade/uiaa.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:grade:uiaa",
"type": "text",
"label": "Grade (UIAA)",
"placeholder": "6-"
}
6 changes: 6 additions & 0 deletions data/fields/climbing/grade/yds_class.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:grade:yds_class",
"type": "text",
"label": "Grade (YDS)",
"placeholder": "5.10a"
}
6 changes: 6 additions & 0 deletions data/fields/climbing/length.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:length",
"type": "number",
"minValue": 0,
"label": "Length (m)"
}
17 changes: 17 additions & 0 deletions data/fields/climbing/orientation.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
{
"key": "climbing:orientation",
"type": "combo",
"label": "Orientation",
"strings": {
"options": {
"N": "North",
"NE": "North-East",
"E": "East",
"SE": "South-East",
"S": "South",
"SW": "South-West",
"W": "West",
"NW": "North-West"
}
}
}
10 changes: 10 additions & 0 deletions data/fields/climbing/quality.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
{
"key": "climbing:quality",
"type": "combo",
"options": [
"fragile",
"medium",
"solid"
],
"label": "Rock Quality"
}
19 changes: 19 additions & 0 deletions data/fields/climbing/rock.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"key": "climbing:rock",
"type": "combo",
"label": "Rock Type",
"strings": {
"options": {
"limestone": "Limestone",
"sandstone": "Sandstone",
"granite": "Granite",
"quartzite": "Quartzite",
"gritstone": "Gritstone",
"gneiss": "Gneiss",
"porphyry": "Porphyry",
"basalt": "Basalt",
"conglomerate": "Conglomerate",
"slate": "Slate"
}
}
}
6 changes: 6 additions & 0 deletions data/fields/climbing/routes.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"key": "climbing:routes",
"type": "number",
"minValue": 0,
"label": "Number of Routes"
}
9 changes: 9 additions & 0 deletions data/fields/climbing/summit_log.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"key": "climbing:summit_log",
"type": "check",
"label": "Summit Log",
"terms": [
"route log",
"summit register"
]
}
34 changes: 34 additions & 0 deletions data/presets/climbing/crag.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
{
"icon": "temaki-abseiling",
"geometry": [
"point",
Comment thread
zbycz marked this conversation as resolved.
"line",
"area",
"relation"
],
"fields": [
"name"
],
"moreFields": [
"climbing/length",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it really make sense to specify the length of a climbing crag? Is it the sum of the routes on it? What practical use would such a number have?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The length in climbing terminology means how long is the route from bottom to top (longer climbs are usually more fun), and this also implies needed rope length.

Often the crag has almost all routes with the same lenght, but usually there are few shorter routes, or perhaps one longer. So this value on the crag works as a default for all the routes, but each route can overwrite it.

Of course, if each route is different length, the it probably wouldn't make sense to tag it on crag as well.

"climbing/routes",
"climbing/bolted",
"climbing/orientation",
"climbing/quality",
"climbing/rock",
"website",
"ele"
],
"terms": [
"rock climbing",
"climbing"
],
"tags": {
"climbing": "crag"
},
"addTags": {
"sport": "climbing",
"climbing": "crag"
},
"name": "Climbing Crag"
}
37 changes: 37 additions & 0 deletions data/presets/climbing/route.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
{
"icon": "temaki-abseiling",
"geometry": [
"point",
"line"
],
"fields": [
"name",
"climbing/length",
"climbing/bolted",
"climbing/rock"
],
"moreFields": [
"climbing/grade/uiaa",
"climbing/grade/french",
"climbing/grade/saxon",
"climbing/grade/yds_class",
"climbing/bolts",
"climbing/orientation",
"climbing/quality",
"climbing/summit_log",
"website",
"ele"
],
"terms": [
"rock climbing",
"climbing"
],
"tags": {
"climbing": "route"
},
"addTags": {
"sport": "climbing",
"climbing": "route"
},
"name": "Climbing Route"
}
25 changes: 25 additions & 0 deletions data/presets/climbing/route_bottom.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
{
"icon": "temaki-abseiling",
"geometry": [
"point",
"vertex"
],
"fields": [
"{climbing/route}"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it does not make sense to just copy-paste the fields from the climbing route preset here. There are quite a few of them which do not make sense (e.g. what is the length of the bottom of a climbing route?), and/or which would just duplicate the property of the respective climbing route object (e.g. the rock type of the route, etc.).

Please specify a list of tag which make sense to be used for these features. 🙇 For example, ele seems to be a reasonably popular one (example).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the issue here is that climbing=route_bottom is very often used as a synonym for "here is the route", and in that case it technically suits as climbing=route.

Eg. there are 4822 nodes with this tag, and 4575 have name (overpass) which may imply this case.

The wiki even specifies this scenario:

Climbing routes can be mapped with a single node marking the bottom of the route, tagged as climbing=route_bottom, or two nodes tagged with climbing=route_bottom and climbing=route_top connected by a way tagged as climbing=route.

Do you think we can leave the "route" fields on the "route_bottoms" then?

],
"moreFields": [
"{climbing/route}"
],
"terms": [
"rock climbing",
"climbing"
],
"tags": {
"climbing": "route_bottom"
},
"addTags": {
"sport": "climbing",
"climbing": "route_bottom"
},
"name": "Climbing Route Start"
}
25 changes: 25 additions & 0 deletions data/presets/climbing/route_top.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
{
"icon": "temaki-abseiling",
"geometry": [
"point",
"vertex"
],
"fields": [
"{climbing/route}"
],
"moreFields": [
"{climbing/route}"
Comment on lines +8 to +11
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see above

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see above :)

],
"terms": [
"rock climbing",
"climbing"
],
"tags": {
"climbing": "route_top"
},
"addTags": {
"sport": "climbing",
"climbing": "route_top"
},
"name": "Climbing Route Top"
}