Setting: keep huts & refreshment POIs visible at all zoom levels on the Outdoors (hiking) map, with an optional double icon size

[LocalHorst3000]

⚠️ I searched existing issues/discussions. Related but not duplicates: #1479 (POIs hide when zooming out, search-focused), #1145 (custom map styles), and discussions #4178, #7991, #5177. This proposes a dedicated, scoped hiking setting rather than a general styling system.

Is your feature request related to a problem? Please describe.
When planning or following a hike on the Outdoors map style, mountain huts and places to eat/drink are the POIs that matter most, but they disappear as soon as you zoom out a little. To check "is there a hut / an inn along this next section?" I constantly have to zoom in, pan, zoom out, repeat. On a phone in the field that is slow and easy to miss things. The icons are also small and hard to spot against dense terrain shading or with direct sunlight hitting the screen.

Describe the ideal solution
Two related toggles in Settings, active in the Outdoors map style (the hiking map):

1. "Always show huts & refreshment stops" — a defined set of POI types stays visible at every zoom level at which the feature is present in the loaded map data (see note below). Proposed type set:
   tourism=alpine_hut, tourism=wilderness_hut, amenity=shelter,
   amenity=restaurant, amenity=cafe, amenity=fast_food,
   amenity=bar, amenity=pub, amenity=biergarten
   (open to trimming/extending — e.g. tourism=guest_house, amenity=drinking_water).

2. "Enlarge these POIs" — when the first option is on, render that same set at roughly double icon size so they stand out for quick scanning.

Both default off, so nothing changes for users who don't opt in.

Transparency on "all zoom levels": a setting can only force a POI visible where it actually exists in the map tiles; below the zoom at which the data carries the feature there is nothing to draw. So in practice this means "show them much earlier / down to the data floor," not literally at world zoom.

Describe alternatives you have considered

• Search surfaces POIs but is a modal, query-driven flow — not "glance at the route."
• Bookmarks require manually saving every candidate in advance.
• Custom map styles ([FR] Support custom map styles #1145) would be a much larger, general-purpose feature; this is a small, hiking-specific, discoverable setting.
• Doing it purely in the style would be global for everyone and add clutter; a per-user setting avoids that.

Additional context / implementation sketch
I'd be happy to implement this and open a PR. Sketch, following existing patterns:

• A runtime toggle plumbed Setting → Framework → DrapeEngine → drape_frontend, exactly like the existing Isolines / 3D-buildings / Transit-scheme toggles, gated to the Outdoors style.
• In the rule/visibility path, override the drawable scale range for the target type set when enabled; apply a symbol-size multiplier for the second toggle.
• Settings persisted via platform/settings.hpp, exposed to Android (SettingsPrefsFragment + Config) and iOS settings.
• Target platforms: Android + iOS. Would include tests where applicable.
• Note: parts of this would be developed with LLM-assisted tooling (disclosed per the PR guide).

Before writing code I wanted to check whether the maintainers would welcome this and whether a scoped hiking setting is the right shape (vs. a broader "more detail" toggle). Feedback very welcome.

[biodranik]

Thanks! Please type ?debug-info in the search and estimate zoom levels where these objects should be visible without making the map unreadable.

Adding setting or increasing the size doesn't feel like an "organic" way.