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.

[balchen]

This will be a larger change, but I would propose considering treating presets in a new way.

A combined cycle and foot path is the same thing, even if there are preferences for different tagging schemas to describe that thing.

So why not have the presets apply different tags in different regions?

[tordans]

@balchen

So why not have the presets apply different tags in different regions?

From our Guidelines: https://github.com/openstreetmap/id-tagging-schema/blob/main/GUIDELINES.md#situational-presets

🏝️ Local Presets and Fields: Generally, presets and fields in OSM should be globally applicable, and efforts should be made to ensure this. However, when local tagging conventions exist or when presets only make sense for certain regions, presets and fields can be given a local filter. This increases the need for thorough testing and makes it more challenging to maintain a good user experience.

Which means: We can do this, but we really should only do it if there is no other way. Local presets might sound easy at first, but they cause all kinds of issues along the way (this issue is an example of that).

For the case of the shared bicycle path, we already have the issue #1411 to find out if we can change the preset.

---

I will hide both of our comments now as unrelated to this thread.