mirror of
https://github.com/openstreetmap/id-tagging-schema.git
synced 2025-10-28 05:13:50 +01:00
crossing: New approach with @templates/crossing/bicycle_more, adding segregated
The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping https://github.com/openstreetmap/id-tagging-schema/issues/317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
This commit is contained in:
parent
8ca0db555c
commit
46ac97189c
18 changed files with 66 additions and 28 deletions
|
|
@ -1,13 +1,14 @@
|
|||
{
|
||||
"fields": [
|
||||
"moreFields": [
|
||||
"oneway",
|
||||
"access"
|
||||
"access",
|
||||
"segregated"
|
||||
],
|
||||
"geometry": [
|
||||
"line"
|
||||
],
|
||||
"tags": {
|
||||
"@template": "crossing/bicycle_relevance"
|
||||
"@template": "crossing/bicycle_more"
|
||||
},
|
||||
"searchable": false,
|
||||
"locationSet": {
|
||||
Loading…
Add table
Add a link
Reference in a new issue