Treat presets with locationSet.exclude as unsearchable presets with low score instead of hiding them

[tordans]

Update 2024-12-20: I updated this issue to be more clear.

We have two sets of "Cycle & Foot Path" presets presets (https://github.com/search?q=repo%3Aopenstreetmap%2Fid-tagging-schema+bicycle_foot.json&type=code) that use locationSet.exclude / locationSet.include to model local preferences on how to tag a foot + cycle way.

However, those presets only describe the preferred method of tagging, but both styles (hw=cycleway / hw=path) are valid ways to model the infrastructure and in use.

For Germany, https://wiki.openstreetmap.org/wiki/DE:Tag:traffic_sign%3DDE:240 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.