Add highway=path+bicycle=designated as regional preset(?)

[tordans]

We have the bicycle_foot.json presets (https://github.com/search?q=repo%3Aopenstreetmap%2Fid-tagging-schema+bicycle_foot.json&type=code) that allow to search for a "Cycle & Foot Path" and use the tagging highway=cycleway + foot=designated + bicycle=designated.

Those presets are only active in some regions (see locationSet.exclude).

https://github.com/openstreetmap/id-tagging-schema/pull/1044/files#diff-a834664ac0cff3853300a80fc424c63679502e50a1a7894067b2eb2ffd3b6503R2 suggest to expand on this schema to add the remaining crossing cases to this setup.

#1201 suggest to add (un-searchable) highway=path crossing presets that are named "Cycle & Foot Crossing".

Looking at the situation in Germany, we are missing a searchable preset for highway=path as a designated bike + foot infrastructure. This is the same idea that the bicycle_foot have but the local community prefers highway=path instead of highway=cycleway.

https://wiki.openstreetmap.org/wiki/DE:Tag:traffic_sign%3DDE:240 describes such a signed infrastructure and references both tags (path and cycleway) as possible highway classes (with a preference for path).

What would be the best way to solve this for this schema?

• We could expand the schema with Introduce locationSet.unsearchable to hide presets for regions but not disable them ideditor/schema-builder#150 and make those presets unsearchable/searchable in certain regions. That would be ideal, because we don't have to duplicate presets.
• We could duplicate presets and make them unsearchable in those regions that prefer a different tagging style. That would improve the situation in a way that it makes the data visible but still has a clear recommendation for one tagging schema (in a given region).
• We could leave it as is on the premise that users know about access tagging (how to add and how to read it) in order to fully interpret the given infrastructure.