Tobias 46ac97189c 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.		2024-04-26 13:18:25 +02:00
..
fields	crossing: Use the same property order for fields/crossing/markings*	2024-04-26 12:00:45 +02:00
preset_categories	add 'informal path' to path category (#1131)	2024-02-24 18:31:10 +01:00
presets	crossing: New approach with @templates/crossing/bicycle_more, adding segregated	2024-04-26 13:18:25 +02:00
deprecated.json	fix wrong tag in deprecation rule, fixes #1180	2024-04-05 18:25:05 +02:00
discarded.json	Treat converted_by as discardable	2021-01-26 17:18:16 +01:00
preset_defaults.json	refactor crossing presets to use (new) crossing:markings tag	2022-09-23 15:22:38 +02:00